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
I0206
Publish the runtime-adapters claim with the test that proves it and the limits it does not cover
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- PLANNED
- Wave
5- Waiting on
- Holds back
- none
- Behind it in all
0- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I0205 | I0205 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Move the runtime-adapters row from planned to guaranteed, citing the adapter and the case, and state on its detail page which axes remain advisory and why, so that the guarantee is narrower than the milestone title rather than as wide as it.
- Why
- A claim promoted to the width of its milestone title overstates what one adapter does. The matrix is where the difference between what is enforced and what is described is either kept honest or lost.
- Now
- The claim is planned, with no implementation and no test, and its note describes the rolled-back attempt.
- Wanted
- The claim is guaranteed for the limits that are actually applied, names the file and the case, and says plainly which axes are still advice.
- Done when
- unknown: the record declares no `completion`
- Risk
- This is the moment the repository starts being believed about runtime enforcement; a claim wider than the adapter is worse than no claim.
Acceptance
- The claim cites an implementation path and a test path that both exist
- The detail page names the axes that remain advisory
- The generated site data regenerates with no stale file
- Validation
scripts/generate-site-data --checkbash test/run.sh- Evidence required
docs_build- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
docssite/data/generated- Not
Any behaviour changeWidening the claim beyond the limits an adapter applies- Depends on
- Priority
- p2
- Profile
- implementation
- 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.