Drafted from real work
Pages originate from traces of completed work, not from a blank template someone was assigned.
Recorded with the runSource trace citations
Knowledge & learning
Context Wiki
Documentation that stays current because it comes from the work.
A living wiki generated from the work your teams and agents actually do: runbooks, decisions, and exceptions drafted from traces, checked for drift, and reviewed by the people who own the work.
Context Wiki
Example workflow
Current · reviewed today
Refund review
Use this process for refunds above the automated threshold or with an account-risk flag.
1. Confirm scope
12 runsVerify requester authority, account, amount, and reason code.
2. Assemble evidence
Policy §4.2Collect contract terms, account history, and the originating case.
3. Request approval
8 decisionsRoute the completed packet to the designated financial reviewer.
How it works
From request to a reviewable result.
Each run keeps the request, actions, evidence, and final decision together.
01 · Observe
Collect completed, reviewed work.
Context groups approved traces, source documents, and recurring corrections around a workflow or decision.
Output · Cited source set
02 · Draft
Propose the page or update.
A draft explains the current process, calls out exceptions, and links each material claim to its source.
Output · Reviewable revision
03 · Govern
Let an owner publish it.
The designated expert reviews the diff, edits it, and sets the freshness policy for the published page.
Output · Owned documentation
What you can inspect
Capability is only useful when it leaves evidence.
Human sign-off
Experts review and approve drafts; their edits are captured as feedback like every other correction.
Recorded with the runOwner and review record
Freshness tracking
Pages that drift from current work are flagged and receive a proposed revision for the owner to review.
Recorded with the runFreshness signal and diff
Cited to the source
Every claim links to the runs and documents it came from.
Recorded with the runClaim-level provenance
Deployment boundaries
Control is part of the product.
Context Wiki can run as a standalone surface, while its traces, evals, and policy decisions remain part of the same Context system.
Drafts do not self-publish
A named owner reviews proposed pages and revisions before they become the team's current guidance.
Access follows the source
A generated page cannot broaden access to material a reader was not already allowed to use.