Roadmap

A worker of any provider records friction it met — a workaround, a defect, a drift, a repeated manual step — as a typed observation with a subject and evidence, in one command, inside the episode it works in. At that episode's boundary, with no model and no prompt, the repository turns each observation into a knowledge candidate that says what it is about and which owner should look first — the tool itself, its enforcement, a generator, the documentation or the project — derived from the subject's structure, never from the wording. Reading the candidates groups them by what they are about, so the same defect seen by three sessions is one group with three episodes behind it. An episode that observed nothing records that it was evaluated and found nothing; rejecting a candidate is a recorded act and stays recorded.

What it holds the work to

• Observations are typed ledger lines and candidates are knowledge records; no second store, kind or queue (ADR 0010, ADR 0091)
• Nothing reads a conversation, a transcript or a prompt; a statement is one line a worker wrote, refused when it carries a transcript marker
• Derivation needs no model, no network and no provider, writes no event it reads, and writes only its own episode's files, so a derivation never triggers another and never rewrites another episode's record
• A route is derived from the subject's structure, and in a repository that adopted the tool only the tool's own identifiers and vendored rules route to the platform
• Promotion, routing into the plan and rejection are acts; the deriver proposes and never promotes

Milestones that serve it

a-session-leaves-what-it-observeddone

Issues that serve it

I2073I2074I2075

When it is satisfied