Review and improve

Create and write

From an empty folder to a checked concept.

Start from zero

No bundle yet? A short form creates one: name it, name its first concept, pick a folder. Studio writes a conformant OKF starter, checks it against the spec, and opens it. No agent involved.

Writing that keeps the knowledge

Name the reader's question, then write a concept or improve an existing one with the same versioned method across agents. A style-only rewrite that drops a number, a qualifier, a citation, a link, a formula, or a code block is rejected before you ever see it.

Move a concept without breaking the graph

Choose a new Markdown path from the reader. Studio previews every link and index repair, keeps a portable redirect at the old path, validates the isolated result, and applies the reviewed files in one restorable transaction.

Retire knowledge without losing the reason

Choose deprecate, redirect, tombstone, or delete. Studio shows what happens to links, indexes, and retrieval, records the reason in the bundle log, and keeps deletion behind review, validation, and a restore checkpoint.

Check

Deterministic checks first, advisory judgment second.

Conformance and portability

The Compatibility Clinic and profile checks keep OKF errors separate from optional portability and team advice. Safe link replacements and profile migrations require hunk review and validation before Apply, while the tolerant reader still opens the bundle.

Health findings with evidence

Audit conformance, graph connectivity, navigation, provenance, freshness, duplication, coverage, and writing patterns with deterministic local checks, no agent involved. A missing claim source names the exact line, and a page that changed or went offline is reported as that, never as a verdict on whether the claim is true.

Handling labels without false authority

Optional audience, sensitivity, and handling notes stay visible while you read, choose agent context, and review staged files. Studio never treats a metadata label as filesystem permission or silently drops evidence because of it.

Create a shareable bundle

Name who the copy is for, choose the knowledge to share, then review what will travel and what will stay behind. Optional safeguards can filter handling labels or remove exact text. Studio checks the separate bundle for declared leaks and never edits the source.

A second pass without write authority

Studio checks each structured result deterministically first. Studio Agent can then review the work for evidence gaps or clarity in a separate no-tool session. A critic can never approve or apply a change.

Review every change

Nothing reaches your files unreviewed.

Writes you review, always

Proposed changes land in a staged tree first. Review each diff hunk, validate against the OKF spec, then apply in one transaction you can restore. Even a verified offline agent that stages unattended still cannot apply changes.

Claim-by-claim review

A writing revision shows each claim before and after, so a meaning change cannot hide inside a style change.

Go deeper

Setup, keyboard, and reference material live in the documentation; these pages stay descriptive.

Where this shows up

Task-first paths that lean on this area.