A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live

I0815

Say what is now true in the claims, the documentation and the worker instructions

Where it stands

devtask.issue

Readiness: blocked 1 of its dependencies is not DONE
Status: BLOCKED
Can start: not now
Milestone: M003
Milestone status: ACTIVE
Wave: 7
Waiting on: I0813
Holds back: I0816
Behind it in all: 1
Evidence: 0 of 2

In the way	Subject	Detail
issue	`I0813`	I0813 is not DONE

Moves

plan.transition

What it is

Objective: Add the behavioural claims this milestone earns to docs/CLAIMS.yaml with real implementation and test paths, document the commands in docs/CLI.md, correct the sentence in docs/CONTINUITY.md that says no index is maintained, write docs/KNOWLEDGE.md, and extend the provider-neutral instruction source so a fresh worker knows the session and knowledge steps of the lifecycle.
Why: A capability with no claim is invisible, a claim with no test is the failure this project measures in other people's repositories, and a document that contradicts the code teaches the wrong thing to every worker that reads it.
Now: docs/CONTINUITY.md states that search maintains no index because the corpus is a handful of files, which describes the record corpus correctly and the repository corpus not at all. The instruction source describes the task lifecycle with no session step.
Wanted: The distinction is stated: record search is a direct literal scan with no index, knowledge search is a derived index over a broader corpus, and neither outranks git or the canonical files. Claims name behaviour rather than subcommands. The worker instructions describe the loop from session start to session close, and teach retrieval of what is needed rather than reading the whole base.
Done when: unknown: the record declares no `completion`
Risk: The always-loaded budget is a hard cap with a failing check. Adding lifecycle steps to the instruction body can push it over, and the fix must be to say less rather than to raise the cap.

Acceptance

Every added claim has a source, an implementation and a test path that all exist, and no guaranteed claim lacks a test
docs/CONTINUITY.md distinguishes the two searches, and the old sentence no longer contradicts the code
The Clean Extraction Boundary and the continuity document agree with each other about the graph
The regenerated provider projections stay under the always-loaded budget
The instruction source teaches retrieval, not reading the whole base

Validation: bin/majordomus doctorbin/majordomus updatebash test/run.sh
Evidence required: claims_addeddocs_consistent
Evidence present: unknown: the record carries no `evidence` entries

Scope

Touches: docsshare/skeleton/providers.majordomus/providersCLAUDE.mdAGENTS.mdtest/cases
Not: Any website changeA claim for a subcommand that has no behaviour of its own
Depends on: I0813 I0814
Priority: p1
Profile: deep-work
Parallel safe: false
Owner: unknown: the record declares no `owner`

The work so far

Branches: none
Merged: none
Commits: 0
Trunk: master
Sessions: none
Created: 2026-09-04
Updated: 2026-09-04
Started: unknown: the record declares no `started_at`
Verified: unknown: the record declares no `verified_at`
Completed: unknown: the record declares no `completed_at`

Synchronisation

Adapter: scripts/github-sync
Repository: unknown: the derived plan's header carries no repository
External issue: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
State there: unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it

Findings

Nothing is wrong with these records.