Skip to content

I0605 — Publish the shared-policy claim and what sharing still cannot do

Move the shared-policy claim to guaranteed, cite the implementation and the cases, and state plainly what a shared policy does not provide: no service, no registry, no cross-machine visibility, and no enforcement of a repository that never adopts it.

BLOCKED wave 4 · p3 · implementation profile · runs alone

Part of shared-policy — Shared policy across repositories and workers.

Blocked. This issue cannot start until I0604, milestone:shared-policy are done. The status is derived from that, not declared.

Objective

Move the shared-policy claim to guaranteed, cite the implementation and the cases, and state plainly what a shared policy does not provide: no service, no registry, no cross-machine visibility, and no enforcement of a repository that never adopts it.

Why

Shared policy is the version most easily read as an organisational control plane. The claim has to name the boundary in the same place it names the capability, or the boundary will be assumed away.

Current state

The claim is planned, and the design document places multi-repository policy outside the local-first scope with a note that it returns here.

Desired state

The claim is guaranteed for what is implemented, the limitations page names what it is not, and the design document's deferral is reconciled with what now exists.

Scope

  • docs
  • site/data/generated

Out of scope

  • Any claim about repositories that have not adopted the shared source

Dependencies

Acceptance criteria

  • The claim cites an implementation path and a test path that both exist
  • The limitations page names what shared policy does not do
  • The design document no longer defers what has shipped, and still refuses what has not
  • The generated site data regenerates with no stale file

Validation

  • scripts/generate-site-data --check
  • bash test/run.sh

Evidence required

  • docs_build

Evidence

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

Risk

This claim is the one a reader will most want to be wider than it is.

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/I0605.yaml. Read it back with majordomus plan show I0605.