Skip to content
Cockpit0.29.0
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

I0104

Move the claim from planned to guaranteed

Where it stands

devtask.issue
Readiness
complete completion is recorded and every required evidence token is present
Status
DONE
Can start
not now
Milestone
M001
Milestone status
DONE
Wave
3
Waiting on
none
Holds back
none
Behind it in all
0
Evidence
1 of 1

Moves

plan.transition
A move writes the repository: it stamps one field of this issue's record and appends one event to the ledger, and a commit will carry both.
The same moves from a terminal

majordomus plan start I0104

majordomus plan verify I0104

majordomus plan done I0104

What it is

Objective
Update docs/CLAIMS.yaml and the claim's detail page so the public surface states what is now true, with the file that implements it and the test that proves it.
Why
A capability that works and is still published as planned understates the tool; one published as guaranteed without a test overstates it. The matrix is the only place either is caught.
Now
blocker-survives-handover is planned, with implementation and test both '-', and a note describing the gap.
Wanted
The claim is guaranteed, cites lib/question.sh and the case from I0103, and its detail page says what the behaviour does not cover.
Done when
unknown: the record declares no `completion`
Risk
Promoting a claim is the moment the repository starts being believed on it.

Acceptance

  • The claim is guaranteed and both paths exist
  • The detail page has a section saying what the behaviour does not cover
  • The generated site data regenerates without a stale file
Validation
scripts/generate-site-data --checkbash test/run.sh
Evidence required
docs_build
Evidence present
docs_build

Scope

Touches
docs/CLAIMS.yamldocs/claimsdocs/CONTINUITY.md
Not
Any behaviour change
Depends on
I0103
Priority
p2
Profile
implementation
Parallel safe
true
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-04T07:34:58Z
Started
2026-09-04T07:32:26Z
Verified
2026-09-04T07:34:55Z
Completed
2026-09-04T07:34:58Z

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.