Workflows

Start with the work.

Choose the job that matches what you need from the bundle. Each path names the work in order and links to the relevant product areas.

Understand an unfamiliar bundle

Someone handed you a bundle. What is actually in it?

Open the folder, or explicitly download a GitHub URL, and land on Bundle Home to see recent activity and the next maintenance step.
Switch among graph, treemap, sunburst, and circle packing to see shape, hubs, and clusters.
Read concepts with hover previews, and branch side quests into tabs with their own history.
Trace dependencies across hops in the lineage panel.
Let inline validation flag what is broken; a sloppy bundle still opens.

You need an answer whose evidence you can inspect.

Connect the agent you already use, or a fully local model.
Ask in a thread beside the graph and reader; a local structural search runs before the prompt is sent.
See exactly what context goes in, and remove what should not.
Open Inspect on the answer: excerpts, source conflicts, and missing chronology.
Follow citations back into the reader.

The bundle is missing something, or says it badly.

Create a bundle from zero with a short form, no agent involved, or start authoring from the object in view.
The agent writes with a versioned method that names the reader's question and preserves claims.
Review the proposed change claim by claim in the staged tree.
Validate against the OKF spec, then apply in one restorable transaction.

Is it good enough to hand to an agent or a teammate?

Run health checks: conformance, connectivity, provenance, freshness, duplication, coverage.
Repair findings with suggestions tied to observed problems.
Review repository changes and stage exactly what should land.
Commit, then fetch, pull, or push when you decide.

Free and open source. Windows and Linux builds; macOS from source.