Skip to content

docs(deed): family-4 completion — PLAYBOOK [rsr-repo-skeleton] tabled #848

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
hyperpolymath merged 1 commit into from
Sep 17, 2026
Merged

docs(deed): family-4 completion — PLAYBOOK [rsr-repo-skeleton] tabled #848

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions 1-formats/deed/mappings/agentic-neurosym-playbook-to-repo-deed.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,7 @@ Observed instance: all five sections (`deployment`, `incident-response`,

| `[metadata] version` / `last-updated` | `(playbook :version "0.1.0" :last-updated "…")` | verbatim STRINGs
| the five operational sections | **slot-preserved as empty clauses**: `(playbook (deployment)(incident-response)(release-process)(docs-format)(maintenance-operations))` | the family-1 slot doctrine applies: operations contracts exist to be greppable *as positions*, even before contents. Empty CLI with content-shaped fails-closed.
| `[rsr-repo-skeleton] skeleton-version` (rsr instance) | `(playbook (skeleton :version "1.0" :last-updated "…" :authority-allowlist ".machine_readable/root-allow.txt" :enforcement-workflow ".github/workflows/estate-rules.yml"))` | verbatim STRINGs; the skeleton's own field model. The large comment inventory of required-root files below the fields is D4-1 template-canon (identical across rsr fleet) — deeds carry the pointer fields only; a DIVERGENT comment inventory fails closed via the same canon-diff doctrine.
|===

== 4. Provenance & validation (extends P-1..P-8)
Expand Down
Loading