Skip to content

spec/README.adoc: two paths miss the 1-formats/ prefix, and the standards#752 status is ten days stale #66

Description

@hyperpolymath

What is wrong

spec/README.adoc under "Canonical upstream" carries three defects, all in one block (lines ~17-24). Measured 2026-09-22 against hyperpolymath/standards@main.

1. Two paths are wrong — both are missing the 1-formats/ prefix

the README says the file actually is
deed/spec/DEED-GRAMMAR-SPEC.adoc 1-formats/deed/spec/DEED-GRAMMAR-SPEC.adoc
deed/spec/abnf/deed.abnf 1-formats/deed/spec/abnf/deed.abnf

Verified with find . -name 'DEED-GRAMMAR-SPEC.adoc' -o -name 'deed.abnf' in a clean standards checkout: exactly one of each, both under 1-formats/. A reader who follows either path finds nothing.

2. The status paragraph is stale, and it is load-bearing

The README says:

Status: landing in standards#752. Until that merges this path does not yet exist on main; the pin below is deliberately left unset rather than pointed at a stale commit.

standards#752 merged on 2026-09-12T16:35:06Z (feat(deed): family-level DEED grammar specification (v0.1.0 DRAFT)). The premise for leaving the pin unset has been gone for ten days.

3. Consequence: an unset pin that is no longer justified

The pin was deliberately unset because the target did not exist. It exists. An unpinned reference to a moving upstream spec is the weaker state, and it now has no stated reason.

Acceptance criteria

  1. Both paths in spec/README.adoc resolve against a clean hyperpolymath/standards checkout — checkable as a one-liner, e.g. for each path P named in the file, test -e "$STANDARDS/$P".
  2. The standards#752 status paragraph is removed or rewritten to record that it merged, with the date.
  3. The pin is either set to a real commit in standards or the README states a current reason for leaving it unset — not the superseded one.
  4. Regression: a check that fails if any standards-relative path named in spec/README.adoc does not exist upstream. Without it this recurs on the next reorganisation, which is exactly how it arose.

Not a defect — checked and cleared

The link:../.machine_readable/anchors/ANCHOR.a2ml[ANCHOR.a2ml] reference at the end of the same file resolves correctly (.machine_readable/anchors/ANCHOR.a2ml exists). It was suspected and is not a defect. Recorded so it is not re-investigated.

Found while translating launcher-standard to .deed under hyperpolymath/standards#837 (owner ruling D73-C).

🤖 Generated with Claude Code

https://claude.ai/code/session_01WPSJ7fBhVAMcpSffCBWUDo

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

    tech-debtKnown shortcut, drift, or hygiene owed - includes cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions