OKForest

Concepts that need attention: stale (past stale_after), draft, unverified, and deprecated, across every tree or some.

The shortest chain of links joining two concepts of one tree, following links either way (at most 6 links), each step saying which way its link points. For questions like "how does A relate to B?".

One change to a tree, as list_changes names it: what was asked, each file's edit (frontmatter field by field, then its lines), what the checks found, who decided or applied it, its comments, and its page, where editors review and apply it.

A concept's markdown body and frontmatter, with its provenance (sources, generated, verified), trust tier, status, staleness, links, and backlinks.

How a tree's concepts link to each other: the most linked concepts, those with no links at all, and its areas (concepts more linked to each other than to the rest), with how many links join each pair of areas. An area joined to no other shows where the tree lacks links between its parts.

Who changed a tree or one of its concepts, when, and why: its commits, newest first, read from Git (changes made in OKForest and directly in Git alike). With commit, what that commit changed instead: each file's frontmatter field by field, and its lines.

Every type, tag, and frontmatter key a tree uses, with counts, status and trust-tier totals, and likely near-duplicates (e.g. Policy and Policies).

The concepts a concept links to, the concepts that link to it (backlinks), and the external URLs it cites.

The changes people have asked for or proposed to a tree in OKForest, newest first: each one's title, where it is (requested, drafting, in review, or done), who asked and when, the files it touches, and its page. Everyone who reads the tree sees them, so check here before asking for something already asked. get_change shows one in full.

A directory of a tree: its index.md (when it has one), its subdirectories, and the concepts directly in it. Omit the path for the tree's root; omit the tree to list the trees.

The trees in the account's Forest: each one's slug (which concept IDs start with), name, description, and source.

The kinds of concept in the Forest (their type), across every tree or some: how many concepts have each, which trees have them, and, where a tree has a schema for the type, the fields its concepts carry. To read them, search with types and trees.

Proposes edits to a tree, written out, for its editors to review and apply in OKForest: new pages, edits to pages (front-matter fields set or removed, and text in the body replaced), and pages moved or renamed, deprecated, or deleted. Links and index.md files follow a moved, new, or deleted page, and a page's files (those only it links to, in its folder or below) move or go with it. The edits are checked first: if a page would have errors, nothing is saved, and the errors come back to fix. Keep a change small, one purpose; each page can be in one edit of it. Read a page with get_concept before editing it. An editor's own proposal is in review at once; anyone else's is a request, which the editors are emailed about. Returns the change, its warnings, and its url, to give the person.

Asks a tree's editors, in plain words, to change it: what should change, and why. It becomes a change in OKForest, which the editors are emailed about, accept, write, and apply; nothing reaches the tree until one applies it. Check list_changes first, so nobody asks twice. An editor's own request starts as drafting, ready for their edits. Returns the change and its url, to give the person.

Searches concepts by their words and by meaning, across every tree or some. By words: every word must match a word in the concept's title, description, tags, ID, or body, or the start of one (pol finds policy; fund doesn't find refund); case doesn't matter. By meaning: concepts that mean what the query asks, in other words or in another language, so describe what you need in a phrase or a question ("how we recognize revenue") rather than a single word, which matches by meaning poorly. Filter by types, tags, statuses, or trust tiers: a concept passes a filter with any of its values, and must pass every filter given. An empty query lists every concept that passes the filters.