Skip to content

Chora deed: :repo-uuid is a #u5 literal the current deed reader refuses (ruling Q2) #46

Open

Description

@hyperpolymath

resource-algebra_chora.deed fails the current standards deed reader at its identity field. Checked with deed_lint.js from standards main on 2026-11-17:

FAIL resource-algebra_chora.deed: line 21: identity field :repo-uuid carries a #u5 literal; write #uuid"<v8 id>" or #u8"domain:name" (owner ruling Q2, CHORA-SPEC 7.1)

The same deed on main fails the same way, so the failure predates #45.

Why it is not simply fixed. Under the estate rules, existing identifiers are not rewritten by hand: ADR-008 phase P3 migrates them repo by repo, and U1 says an id is minted once. Moving this field to #uuid"<v8>" or #u8"domain:name" therefore belongs to the per-repo id migration, keeping the same birth preimage (github.com/hyperpolymath/resource-algebra). Under ruling V9, ids minted before V9 keep their gv-clade-index domain. No agent edit was made.

Done when. The identity field uses a form CHORA-SPEC 7.1 accepts, the chora registry's copy agrees, and deed_lint.js passes on the deed.


Generated by Claude Code

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    decisionA ruling is required before work can proceed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions