I1303 — The store is bounded, measured and invisible to every published projection

BLOCKED wave 2 · p0 · deep-work profile · runs alone

Part of external-workspaces — An external workspace is read the way this repository reads anything else, and its content never becomes public by accident.

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.

Current state

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.

Desired state

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.

Scope

• .ai/repo/policy.yaml
• .ai/repo/ci/gates.yaml
• lib/doctor.sh
• scripts
• test/cases

Out of scope

• Declaring the store as a knowledge-sources class; ADR 0025 rejected it and the reasons are recorded there
• Any adapter that writes into the store

Dependencies

• I1302READY Identity, provenance and support level are typed fields, not prose

What waits on this

• I1306BLOCKED A sync resumes, repeats itself without harm, and says how fresh it is
• I1308BLOCKED The executable's share is one capability, shaped like continuity
• I1309BLOCKED The boundaries this milestone asserts are gates, not sentences

Acceptance criteria

• 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.sh
• bin/majordomus doctor

Evidence required

• layout_schema
• retention_capped
• boundary_gated
• gate_proven

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

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.

Timeline

started

—

verified

—

completed

—

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I1303.yaml. Read it back with majordomus plan show I1303.