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
I0601
Let a policy name a shared source it does not copy
Where it stands
devtask.issue- Readiness
- waiting every dependency is satisfied; the milestone shared-policy waits on an outcome of its own
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
0- Waiting on
- Holds back
- Behind it in all
4- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| milestone | shared-policy | the milestone shared-policy waits on an outcome of its own |
Moves
plan.transitionWhat it is
- Objective
- Let a repository's policy name a shared policy source and resolve it offline from the filesystem, so that one statement of a rule can govern more than one repository without being pasted into each.
- Why
- Copying is what makes organisational policy drift: every repository holds a fork of the rule and nobody can see which forks moved. A named source is the smallest change that makes drift detectable at all.
- Now
- Policy is per repository and entirely local. Nothing refers to anything outside the checkout.
- Wanted
- A policy names a shared source, the tool resolves it without a network call, and every command that reads policy reads the resolved result.
- Done when
- unknown: the record declares no `completion`
- Risk
- This is where a local-first tool grows a dependency outside its checkout; keeping resolution to the filesystem is what preserves the offline guarantee.
Acceptance
- A shared source is resolved from the filesystem with no network access
- Every policy reader sees the resolved policy, and no reader bypasses resolution
- An unresolvable source is a named finding that stops the command, never a silent fallback to local
- A repository that names no shared source behaves exactly as it does today
- Validation
bash test/run.shbin/majordomus doctor- Evidence required
suite- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
libsharedocs- Not
Fetching a policy over a network, from a registry, or from any serviceA hosted component that must be running for the tool to work- Depends on
- none
- Priority
- p3
- 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-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.