You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
deed: apply owner rulings — STATE option B, AI-MANIFEST option A - #76
Applies the two owner rulings of 2026-11-10 to the draft anytype_chora.deed: STATE v1 → option B (extract the state, archive the journal) and 0-AI-MANIFEST → option A ((manifest …) on the repo deed). The deed stays inert; nothing reads it, and the a2ml sources stay live.
Changes
anytype_chora.deed only (one file, +69/−11).
STATE B:[position] maturity → (maturity :level experimental) (no :since; STATE carries no date for it). [metadata] status "active" dedupes into (status :phase active). Journal sections and the derivable completion-percentage are not carried.
AI-MANIFEST A: root 0-AI-MANIFEST.a2ml → (manifest), 4× (agent), (policy), 4× (work), verbatim. Agent seen-set left at the spec default (open, flag-any-unknown); the owner ruled the home, not ask (ii).
Header comment updated: families 3 and 7 are now ruled; META/ECOSYSTEM remain PROPOSAL.
Findings worth a look
Spec defect (found by the linter). The AI-MANIFEST mapping table writes (policy (rules ("…" "…"))). deed.abnf rejects it: a list is only a value after a :keyword, so the bare ("…") parses as a nested clause with no symbol. Written here as (policy :rules ("…" "…")), which keeps the meaning and the order. The mapping spec needs the same fix upstream.
STATE [position] phase = "implementation" has no home under B. It uses a different vocabulary (design | implementation | testing | maintenance | archived) from the closed lifecycle enum on (status :phase …), and maturity has its own clause. It is noted in-file as an owner question and survives only in the archive.
The spec does not say where (agent)/(policy)/(work) nest. Its table shows them without a (manifest) wrapper, so they sit beside it.
Not done, on purpose
STATE.a2ml and 0-AI-MANIFEST.a2ml are not archived or deleted yet. Gates still require them: openssf-compliance.yml hard-fails without STATE.a2ml, the Must invariant and validate-template.sh test for it, extract.sh aborts without it, and the arrival-pack drift gate lists it as a source (46 files reference it in all). There is also no in-repo "v2 journal" for the dropped blockers and next-actions to move to. Archiving needs those consumers rewired first.
RSR Quality Checklist
Required
Tests pass — N/A: one .deed data file; nothing executable changed.
Code is formatted — N/A.
Linter is clean — the canonical standards/1-formats/deed/tools/deed_lint.js reports OK.
No banned language patterns; no unsafe; no banned functions.
SPDX headers present/unchanged.
No secrets, credentials, or .env files included.
As Applicable
.machine_readable/6a2/STATE.a2ml updated — not changed (see above).
Documentation updated: the deed header records the rulings.
Testing
deed_lint.js → OK. It also failed the first draft (the :rules defect above), so it is exercising the grammar.
Fidelity: 4 agents and 4 work items match the source arrays one-for-one; every string is a verbatim substring of 0-AI-MANIFEST.a2ml; 0 literal true/false tokens.
scripts/check-root-shape.sh → PASS (no new root files).
Extends the draft chora deed with the two families the owner ruled on
2026-11-10 (standards 1-formats/deed/mappings/):
state-v1-decision.adoc, option B (extract the state, archive the journal):
- [position] maturity -> (maturity :level experimental). No :since: STATE
carries no date for it and the vocabulary makes :since optional.
- [metadata] status "active" dedupes into (status :phase active).
- Journal sections and the derivable completion-percentage are NOT carried
into the deed.
ai-manifest-decision.adoc, option A:
- root 0-AI-MANIFEST.a2ml -> (manifest) (agent) x4 (policy) (work) x4,
verbatim. Agent seen-set left at the spec default (open, flag-any-unknown):
the owner ruled the home, not ask (ii).
Spec defect found by the linter: the AI-MANIFEST table writes
(policy (rules ("..." "..."))), which deed.abnf rejects because a list is only a
value after a :keyword. Written as (policy :rules (...)), same meaning and order.
Also flagged in-file, not fixed: STATE [position] phase "implementation" has no
home under B (different vocabulary from the closed lifecycle enum), and
systemet's VIBE role still says ReScript (carried verbatim; translators tidy
nothing).
The STATE.a2ml and 0-AI-MANIFEST.a2ml sources stay live: openssf-compliance,
the Must invariant, validate-template.sh and the arrival-pack generator still
require them. They are archived only once those consumers are rewired.
Verified: deed_lint.js OK; agent and work counts match the source arrays
one-for-one; every string is a verbatim substring of its source; no literal
true/false tokens.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01J1XmMC49T8sZ3uUuvrgB7y
No actionable comments were generated in the recent review.
Summary
Summary by CodeRabbit
Documentation
Updated project documentation to record the current maturity and active status of the STATE specification.
Added entries covering the AI manifest, agent roles, policy rules and related work assignments.
META and ECOSYSTEM remain pending, and the STATE and manifest sources remain available while consumer updates are pending.
The deed now records the ruled STATE v1 and root AI manifest mappings. It adds STATE maturity metadata and AI manifest entries for agents, policy rules, and work assignments. META and ECOSYSTEM remain pending.
Changes: Deed mappings
Layer / File(s)
Summary
Record STATE mapping decisions anytype_chora.deed
The mapping notes identify STATE v1 metadata as the source for the active lifecycle phase. They also record omitted STATE fields and note that the STATE and manifest source files remain live pending consumer rewiring.
Add maturity and AI manifest entries anytype_chora.deed
The deed adds experimental maturity metadata and records the AI manifest, four agent-role entries, policy rules using :rules, and matching work assignments.
hyperpolymath/anytype#74: PR #74 introduced the draft deed and left STATE and AI-MANIFEST untranslated. This PR adds those mappings.
Merge Risk: Minimal · up to 62a2e
No merge-blocking issue is established by the supplied evidence.
Pre-merge checks: 4
Check name
Status
Explanation
Title check
The title clearly identifies the deed changes and the two rulings: STATE option B and AI-MANIFEST option A.
Description check
The description includes a summary, key changes, checklist status, testing details, and reasons for deferring source-file changes. The optional screenshots section is not needed for this data-only cha…
Linked Issues check
Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check
Check skipped because no linked issues were found for this pull request.
Full details: Description check
Explanation
The description includes a summary, key changes, checklist status, testing details, and reasons for deferring source-file changes. The optional screenshots section is not needed for this data-only change.
Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
File: No configuration file from this repository applied
Commit: Unavailable
Layers: Organization UI
Review profile: ASSERTIVE
Plan: Advanced
Run ID: c7c3b2a9-49d3-4fcb-a69d-c4a08d326b52
Commits
Reviewing files that changed from the base of the PR and between 75f3b58 and 62a2e67.
Files selected for processing: 1
anytype_chora.deed
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.
Recent review details
Context from checks skipped due to timeout: 2
GitHub Check: Dogfooding compliance summary
GitHub Check: CodeRabbit
CI failures not shown inline: 2
GitHub Actions: SonarQube / 0_SonarQube.txt: deed: apply owner rulings — STATE option B, AI-MANIFEST option A
##[group]Run SonarSource/sonarqube-scan-action@e805d875275f728fac1885b413934be6d7c63f65
with:
projectBaseDir: .
scannerVersion: 8.3.1.16491
scannerBinariesUrl: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli
skipSignatureVerification: false
env:
SONAR_***REDACTED_SECRET_ASSIGNMENT***
##[warning]Running this GitHub Action without SONAR_TOKEN is not recommended
Installing Sonar Scanner CLI 8.3.1.16491 for linux-x64...
Downloading from: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-8.3.1.16491-linux-x64.zip
Downloading signature from: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-8.3.1.16491-linux-x64.zip.asc
Importing SonarSource public key from hkps://keyserver.ubuntu.com...
[command]/usr/bin/gpg --homedir /home/runner/work/_temp/gpg-ba973158 --batch --keyserver hkps://keyserver.ubuntu.com --recv-keys 679F1EE92B19609DE816FDE81DB198F93525EC1A
gpg: keybox '/home/runner/work/_temp/gpg-ba973158/pubring.kbx' created
gpg: /home/runner/work/_temp/gpg-ba973158/trustdb.gpg: trustdb created
gpg: key 1DB198F93525EC1A: public key "SonarSource S.A. <infra@sonarsource.com>" imported
gpg: Total number processed: 1
gpg: imported: 1
Successfully imported key from hkps://keyserver.ubuntu.com
✓ SonarSource public key imported successfully
Verifying GPG signature...
[command]/usr/bin/gpg --homedir /home/runner/work/_temp/gpg-ba973158 --batch --verify /home/runner/work/_temp/56f45eae-0957-4cae-bbbf-3dc84d3d8514 /home/runner/work/_temp/0b77b2ea-5913-48f2-8cc5-179aabe52628
gpg: Signature made Mon Nov 2 14:30:12 2026 UTC
gpg: using RSA key 06D0369BE1D0B06997DA66E8C33B56C147B01975
gpg: Good signature from "SonarSource S.A. <infra@sonarsource.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 679F 1EE9 2B...
GitHub Actions: SonarQube / SonarQube: deed: apply owner rulings — STATE option B, AI-MANIFEST option A
##[group]Run SonarSource/sonarqube-scan-action@e805d875275f728fac1885b413934be6d7c63f65
with:
projectBaseDir: .
scannerVersion: 8.3.1.16491
scannerBinariesUrl: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli
skipSignatureVerification: false
env:
SONAR_***REDACTED_SECRET_ASSIGNMENT***
##[warning]Running this GitHub Action without SONAR_TOKEN is not recommended
Installing Sonar Scanner CLI 8.3.1.16491 for linux-x64...
Downloading from: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-8.3.1.16491-linux-x64.zip
Downloading signature from: https://binaries.sonarsource.com/Distribution/sonar-scanner-cli/sonar-scanner-cli-8.3.1.16491-linux-x64.zip.asc
Importing SonarSource public key from hkps://keyserver.ubuntu.com...
[command]/usr/bin/gpg --homedir /home/runner/work/_temp/gpg-ba973158 --batch --keyserver hkps://keyserver.ubuntu.com --recv-keys 679F1EE92B19609DE816FDE81DB198F93525EC1A
gpg: keybox '/home/runner/work/_temp/gpg-ba973158/pubring.kbx' created
gpg: /home/runner/work/_temp/gpg-ba973158/trustdb.gpg: trustdb created
gpg: key 1DB198F93525EC1A: public key "SonarSource S.A. <infra@sonarsource.com>" imported
gpg: Total number processed: 1
gpg: imported: 1
Successfully imported key from hkps://keyserver.ubuntu.com
✓ SonarSource public key imported successfully
Verifying GPG signature...
[command]/usr/bin/gpg --homedir /home/runner/work/_temp/gpg-ba973158 --batch --verify /home/runner/work/_temp/56f45eae-0957-4cae-bbbf-3dc84d3d8514 /home/runner/work/_temp/0b77b2ea-5913-48f2-8cc5-179aabe52628
gpg: Signature made Mon Nov 2 14:30:12 2026 UTC
gpg: using RSA key 06D0369BE1D0B06997DA66E8C33B56C147B01975
gpg: Good signature from "SonarSource S.A. <infra@sonarsource.com>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg: There is no indication that the signature belongs to the owner.
Primary key fingerprint: 679F 1EE9 2B...
Validate K9 contracts is red here, but not because of this PR.
This PR changes one file, anytype_chora.deed, and the K9 validator does not scan it: it reports the same 18 files scanned, 20 errors and 4 warnings as the earlier runs on #74. Every error is in the template and scaffold K9 files (.machine_readable/self-validating/template-*.k9.ncl, container/stapeln/deploy.k9.ncl, coordination.k9, session/custom-checks.k9): missing K9! magic line and missing pedigree block.
No fix exists yet. That content debt, and the K9 spec question that the K9! magic line collides with the Nickel body, are estate-level and belong upstream in standards. I'm not widening this PR to cover them, and not re-running a deterministic failure.
The SonarQube PR quality gate passes. The deed itself is validated with deed_lint.js (OK).
SonarQube is red here, also not because of this PR, and the cause is not what I said on #74.
I described this check as a coverage gate earlier. That was wrong. The job log shows the scanner ran with an empty SONAR_TOKEN (Running this GitHub Action without SONAR_TOKEN is not recommended), and SonarQube Cloud then answered Fail to load the list of plugins installed on the server: Not authorized or organization not found and exited with code 3. The analysis never starts, so this PR's diff can't affect it.
That makes it a missing or invalid SONAR_TOKEN repo secret, which a repo owner has to set. There is no code fix to port.
The separate SonarCloud Code Analysis PR quality gate does run and passes (0 new issues). Hypatia neurosymbolic scan is now green on this PR as well. The only red checks are this one and Validate K9 contracts.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Summary
Applies the two owner rulings of 2026-11-10 to the draft
anytype_chora.deed: STATE v1 → option B (extract the state, archive the journal) and 0-AI-MANIFEST → option A ((manifest …)on the repo deed). The deed stays inert; nothing reads it, and the a2ml sources stay live.Changes
anytype_chora.deedonly (one file, +69/−11).[position] maturity→(maturity :level experimental)(no:since; STATE carries no date for it).[metadata] status "active"dedupes into(status :phase active). Journal sections and the derivablecompletion-percentageare not carried.0-AI-MANIFEST.a2ml→(manifest), 4×(agent),(policy), 4×(work), verbatim. Agent seen-set left at the spec default (open, flag-any-unknown); the owner ruled the home, not ask (ii).Findings worth a look
(policy (rules ("…" "…"))).deed.abnfrejects it: a list is only avalueafter a:keyword, so the bare("…")parses as a nested clause with no symbol. Written here as(policy :rules ("…" "…")), which keeps the meaning and the order. The mapping spec needs the same fix upstream.[position] phase = "implementation"has no home under B. It uses a different vocabulary (design | implementation | testing | maintenance | archived) from the closed lifecycle enum on(status :phase …), and maturity has its own clause. It is noted in-file as an owner question and survives only in the archive.(agent)/(policy)/(work)nest. Its table shows them without a(manifest)wrapper, so they sit beside it.Not done, on purpose
STATE.a2mland0-AI-MANIFEST.a2mlare not archived or deleted yet. Gates still require them:openssf-compliance.ymlhard-fails withoutSTATE.a2ml, the Must invariant andvalidate-template.shtest for it,extract.shaborts without it, and the arrival-pack drift gate lists it as a source (46 files reference it in all). There is also no in-repo "v2 journal" for the dropped blockers and next-actions to move to. Archiving needs those consumers rewired first.RSR Quality Checklist
Required
.deeddata file; nothing executable changed.standards/1-formats/deed/tools/deed_lint.jsreports OK.unsafe; no banned functions..envfiles included.As Applicable
.machine_readable/6a2/STATE.a2mlupdated — not changed (see above).Testing
deed_lint.js→ OK. It also failed the first draft (the:rulesdefect above), so it is exercising the grammar.0-AI-MANIFEST.a2ml; 0 literaltrue/falsetokens.scripts/check-root-shape.sh→ PASS (no new root files).Generated by Claude Code