One policy will be shared across repositories and workers

declared status○declared status: planned Specified and not implemented. Named so the omission is visible.

recorded evidence○recorded evidence: no test Not judged: only a guaranteed claim is held to a recorded run. how evidence is recorded

What it means

Planned. One canonical policy distributed to many repositories, with the same projections, the same finish contract and the same drift checks everywhere a team's workers run.

How it works

Nothing is implemented. Today it is local-first: one policy per repository, one active task per checkout, overlap seen across worktrees on one machine.

How to see it

There is nothing to run.

What it does not cover

Everything about organisations, today. There is no server, no account and no central store, and there will be none in the local tool.

Why it exists

The design's expansion path — shared policy across a team, then measurement, then recommendations — is stated so that the local tool is built with it in mind and not against it.

Detail rendered from docs/claims/shared-policy.md.

From the statement to the proof

1. 1 · the public statement

   One policy will be shared across repositories and workers

   Made on Policy.

2. 2 · the canonical claim

   shared-policy○declared status: planned in docs/CLAIMS.yaml

   Defined in read it on this site · docs/DESIGN.md

3. 3 · the implementation

   Nothing implements it yet.

4. 4 · the test and the scenarios

   No executable evidence linked: the claim names no test, and no use case executes it.

5. 5 · the recorded runs

   ○recorded evidence: no test how evidence is recorded

What would make this guaranteed

Shared policy across repositories and workers BLOCKED Blocked by routing-recommendations, so this claim cannot move yet. Shipping the milestone does not promote the claim: it reaches guaranteed when an implementation, a behavioural test and a blocking CI job exist for it.