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
I0605
Publish the shared-policy claim and what sharing still cannot do
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
4- Waiting on
- Holds back
- none
- Behind it in all
0- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I0604 | I0604 is not DONE |
| milestone | shared-policy | the milestone shared-policy waits on an outcome of its own |
Moves
plan.transitionWhat it is
- 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.
- Now
- The claim is planned, and the design document places multi-repository policy outside the local-first scope with a note that it returns here.
- Wanted
- 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.
- Done when
- unknown: the record declares no `completion`
- Risk
- This claim is the one a reader will most want to be wider than it is.
Acceptance
- 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 --checkbash test/run.sh- Evidence required
docs_build- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
docssite/data/generated- Not
Any claim about repositories that have not adopted the shared source- Depends on
- Priority
- p3
- 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.