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
I1303
The store is bounded, measured and invisible to every published projection
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- ACTIVE
- Wave
2- Waiting on
- Holds back
- Behind it in all
4- Evidence
0of4
| In the way | Subject | Detail |
|---|---|---|
| issue | I1302 | I1302 is not DONE |
Moves
plan.transitionWhat it is
- Objective
- Declare the layout of .ai/local/workspaces/, its checkpoint file, its retention cap in policy and the doctor stanza that measures it, and prove with a gate that nothing published ever reaches it.
- Why
- mj_validate_retention is three hand-written stanzas over the ledger, handovers and checkpoints; a fourth store gets no cap and no doctor line unless one is written. An unbounded store nothing measures is the defect this repository keeps finding in itself. And the guarantee that .ai/local never reaches the site is enforced in the Rust index at three points but is, for scripts/generate-site-data, only the fact that its fixed input list does not mention it — closer to convention than to a guard.
- Now
- No store, no cap, no stanza. .ai/local/ is git-ignored at .gitignore:55 and mj_validate_ai_layout fails the pre-commit hook if a file there is tracked.
- Wanted
- The store has a declared layout per workspace, a checkpoint with a schema, a retention cap read from policy.yaml, a doctor line that reports its size against that cap, and a gate that fails if any published projection reads a path under it.
- Done when
- unknown: the record declares no `completion`
- Risk
- A cap chosen from taste rather than measurement will either never fire or fire on the first real sync. It has to be stated in terms of what the operator's own workspace actually holds.
Acceptance
- The store layout and the checkpoint are described by a schema, not by a comment
- A retention cap is stated in policy.yaml and doctor reports the store against it, in the shape the three existing stanzas use
- A gate fails if the site build, the generated documentation or any published projection names a path under .ai/local/workspaces/
- A test case proves the gate fails when the boundary is crossed deliberately
- Validation
bash test/run.shbin/majordomus doctor- Evidence required
layout_schemaretention_cappedboundary_gatedgate_proven- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
.ai/repo/policy.yaml.ai/repo/ci/gates.yamllib/doctor.shscriptstest/cases- Not
Declaring the store as a knowledge-sources class; ADR 0025 rejected it and the reasons are recorded thereAny adapter that writes into the store- Depends on
- Priority
- p0
- 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-09
- Updated
- 2026-09-09
- 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.