Initiative Registry

Treat the user-specified GitHub repository as the shared Registry fact source. Require its URL on first use; never infer a writable remote from the current repository.

Workflow

1. Resolve the Registry URL and local checkout. Use an existing checkout map or ask for a local path; clone only after explicit authorization.
2. Read the Registry repository's AGENTS.md and protocol Spec before changing manifests or generated files.
3. Classify the request as query, validation, registration, removal, drift check, closeout check, or publication.
4. For registration or ownership changes, present the proposed Initiative, Spec, and Plan relationship and obtain Human confirmation.
5. Change only the owning manifest through the Registry's deterministic admin script; compile and validate before publication.
6. Show the semantic diff. Use a scoped branch and pull request by default; direct default-branch publication requires explicit authorization.
7. Report the Registry repository URL, commit or branch, changed IDs, validation result, and unresolved warnings.

Closeout reminder

Run closeout-check after a Plan reaches a terminal state or before declaring a multi-device work session complete. The command reads each registered roadmap Plan from its local Initiative checkout and reports one of three outcomes: