Intent workspace
From what the work is for to the move that starts it.
One intent and everything that serves it: its milestones, their issues and what blocks them, the waves the dependencies allow and the graph of what waits for what.
- Intents5intents.list /intents
- Milestones41plan.roadmap /milestones
- Roadmap nowM002plan.roadmap /now
- Plan's next issueI0702plan.next /issue/id
Intents
What the work is for: pick one to see what serves it.
A link that names no intent opens the first one intents.list reports executing, then verifying, then planned, then declared, in that order.
intents.list726 msread 9 s agoAPI/api/v1/intentsCLImajordomus intent listMCPmajordomus_intentstechnical view
Intent
What the work is for, what it holds the work to, and whether the evidence says it is met.
a-session-leaves-what-it-observed
Every managed session leaves what it observed, and the repository groups and routes it without being asked
satisfiedsatisfied4 of 4 criteria metClose
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
When it is satisfied
| Criterion | Evidence | State | Met | Reproduce |
|---|---|---|---|---|
| an-observation-is-recordedknowledge observe records one observation.recorded line with its kind, subject, statement and evidence references inside an open episode, inside or outside a task, and refuses an unknown kind, a malformed subject or evidence reference, a multi-line statement, a transcript marker or the absence of an episode without writing | test | current | met | bash test/run.sh 980_a_session_records_what_it_observed |
| an-observation-becomes-a-candidateClosing an episode derives one candidate per observation it recorded, carrying the subject as about, with no model; a second derivation writes nothing; an episode that recorded nothing derives nothing and still records that it was evaluated | test | current | met | bash test/run.sh 981_an_observation_becomes_a_grouped_candidate |
| recurrence-is-groupedTwo episodes observing the same subject write one file each, and the candidates listing groups them under that subject with both episodes, on the command line and in the Rust reader alike; a rejected candidate stays rejected and a later observation of its subject is listed beside it | test | current | met | bash test/run.sh 981_an_observation_becomes_a_grouped_candidate |
| route-is-structuralEvery observation candidate carries a route derived from its subject's structure — platform, enforcement, generator, documentation or project — and in an adopting repository with a share/ directory of its own, a project path never routes platform | test | current | met | bash test/run.sh 982_a_candidate_is_routed_by_what_it_is_about |
intents.list726 msread 9 s agoAPI/api/v1/intentsCLImajordomus intent listMCPmajordomus_intentstechnical view
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
Milestones
The milestones this intent names, in the roadmap's order; issues done is a count, not the milestone's acceptance.
| Milestone | State | Issues done | Waits for |
|---|---|---|---|
| a-session-leaves-what-it-observedA session leaves what it observed, and the repository routes it | done | 3 of 3 | nothing |
plan.roadmap0 msAPI/api/v1/plan/roadmapMCPmajordomus_plan_roadmaptechnical view
Issues
Every issue of its milestones or naming it, by wave; a move opens the issue's page, where plan.transition makes it and refuses one the plan does not allow.
| Issue | Milestone | Status | Wave | Priority | Blocked by | Move |
|---|---|---|---|---|---|---|
| I2073A worker records an observation in one command | a-session-leaves-what-it-observed | done | 0 | p1 | nothing | none |
| I2074An observation becomes a candidate that says what it is about, and reading groups recurrence | a-session-leaves-what-it-observed | done | 1 | p1 | nothing | none |
| I2075A candidate is routed by what it is about | a-session-leaves-what-it-observed | done | 2 | p1 | nothing | none |
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view
plan.waves192 msread 6 s agoAPI/api/v1/plan/wavesMCPmajordomus_plan_wavestechnical view
plan.next79 msread 10 s agoAPI/api/v1/plan/nextMCPmajordomus_plan_nexttechnical view
Waves
An issue enters a wave once every dependency has left it; sharing a wave is necessary to run together, not sufficient.
plan.waves192 msread 6 s agoAPI/api/v1/plan/wavesMCPmajordomus_plan_wavestechnical view
Dependencies
What waits for what, as the plan records it; a dependency outside this intent is drawn small.
plan.issues0 msAPI/api/v1/plan/issuesMCPmajordomus_plan_issuestechnical view