Skip to content

deed: apply owner rulings — STATE option B, AI-MANIFEST option A - #95

Merged
hyperpolymath merged 1 commit into
mainfrom
claude/rename-everytype-anytime-repos-w4t306
Nov 10, 2026
Merged

hyperpolymath merged 1 commit into
mainfrom
claude/rename-everytype-anytime-repos-w4t306

Conversation

@hyperpolymath

Copy link
Copy Markdown
Owner

Summary

Applies the two owner rulings of 2026-11-10 to the draft systemet_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

  • systemet_chora.deed only (one file). Also corrects its header to the .machine_readable/descriptiles/ path, which main moved to after the first draft.
    • 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).

Findings worth a look

  1. 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.
  2. STATE [position] phase = "implementation" has no home under B. It uses a different vocabulary 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.
  3. The VIBE role still says "ReScript components". ReScript is banned (destination: AffineScript). It is carried verbatim because translators tidy nothing; the fix belongs in the source manifest and the generator. anytype's copy already says AffineScript.
  4. 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 (47 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/descriptiles/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).

Generated by Claude Code

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
@coderabbitai

coderabbitai Bot commented Nov 10, 2026 •

Copy link
Copy Markdown
Contributor

Explain Change →

Caution

Review failed

The pull request is closed.

  • 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.

Share

@sonarqubecloud

Copy link
Copy Markdown

@hyperpolymath
hyperpolymath marked this pull request as ready for review November 10, 2026 18:21
@hyperpolymath
hyperpolymath merged commit bbe1d13 into main Nov 10, 2026
30 of 31 checks passed
@chatgpt-codex-connector

Copy link
Copy Markdown
Codex Review Summary: ❌ Failed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ❌ Failed 2026-11-10T18:21:25.665852Z
We couldn’t complete this review. Comment @codex review to try again.
e3bf626 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@hyperpolymath
hyperpolymath deleted the claude/rename-everytype-anytime-repos-w4t306 branch November 10, 2026 18:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants