chore: sync README, ROADMAP, Justfile, template updates

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: hyperpolymath

Justfile

@@ -30,6 +30,10 @@ clean:
 assail:
     @command -v panic-attack >/dev/null 2>&1 && panic-attack assail . || echo "panic-attack not found — install from https://github.com/hyperpolymath/panic-attacker"
 
+# Stable release gate audit
+v1-audit path=".":
+    @./release-pre-flight/v1-audit.sh "{{path}}"
+
 # Self-diagnostic — checks dependencies, permissions, paths
 doctor:
     @echo "Running diagnostics for standards..."

README.adoc

@@ -18,6 +18,8 @@ This repository serves as the canonical source for policies, templates, and spec
 * **Language Policy** -- Which languages and tools are permitted across the ecosystem
 * **6A2 Format Family** -- 7 machine-readable project metadata formats in A2ML (see link:SATELLITES.a2ml[SATELLITES.a2ml])
 * **Build System** -- Mustfile/justfile (no Makefiles)
+* **Stable Release Gate** -- link:release-pre-flight/V1-GATE.adoc[hard `v1.0.0` audit requirements] for all repos and multi-repo systems
+* **Publication Pre-Flight** -- link:publication-pre-flight/PREFLIGHT.adoc[submission gate] for papers, DOI deposits, and venue-ready artifacts
 * **Governance Templates** -- Reusable CODE_OF_CONDUCT, CONTRIBUTING, and SECURITY documents
 * **Licensing Framework** -- PMPL-1.0-or-later with Palimpsest philosophical principles
 * **Enforcement** -- CI/CD workflows and pre-commit hooks

ROADMAP.adoc

@@ -76,6 +76,29 @@ Development roadmap for the Hyperpolymath standards and specifications repositor
 * [ ] **Badge system** — Visual indicators of standards compliance
 * [ ] **Migration guides** — Transitioning existing projects to Hyperpolymath standards
 
+=== Phase 6: Full-Release Best Practice Convergence
+
+These items close the remaining gap between audited stable release and
+best-practice-complete full release.
+
+* [ ] **Release telemetry standard** — Rollout health, adoption, regression, and failure signals captured per release
+* [ ] **Operational observability standard** — Logs, metrics, traces, and service-level evidence for projects that run beyond a local machine
+* [ ] **Industrialised release tooling** — Standard release pipelines, evidence collection, rollback support, and demotion workflows
+* [ ] **Automatic evidence capture** — Tests, benchmarks, proofs, audits, and build outputs recorded automatically as release evidence
+* [ ] **Claim-to-artifact traceability** — Machine-readable mapping from public claims to proof files, tests, benchmark outputs, and source modules
+* [ ] **Cross-repo release dashboards** — System-level release views so the weakest in-scope repo is visible before shipment
+* [ ] **External validation standard** — Rules for what counts as beyond-repo release evidence for `beta`, `rc`, and later maturity
+* [ ] **Provenance and attestation standard** — Signed, reproducible provenance for releases, benchmark results, and proof artifacts
+* [ ] **Automated stable-claim demotion** — Tooling that flags or retracts `stable`/`v1` claims when later audits fail
+* [ ] **Evidence retention policy** — How long release evidence, audit logs, benchmark records, and proof outputs must remain available
+
+=== Phase 7: Full-Release Definition
+
+* [ ] **Full release terminology** — Reserve "full release" for best-practice-complete projects, not merely `v1.0.0` stable ones
+* [ ] **Mature-phase policy** — Define when a project may move from audited stable to mature/full-release standing
+* [ ] **Estate-wide release registry** — One canonical view of draft/alpha/beta/rc/stable/mature status across all repos
+* [ ] **Best-practice completion rubric** — A single rubric combining proof rigor, testing depth, observability, telemetry, provenance, and traceability
+
 == Conceptual Work
 
 === Palimpsest License Development

a2ml-templates/STATE.a2ml.template

@@ -16,10 +16,10 @@ version = "0.1.0"
 
 # phase: What development stage is this project in?
 #   concept  — idea only, no code yet
-#   alpha    — early code, unstable APIs
-#   beta     — feature-complete, testing
-#   stable   — production-ready
-#   mature   — long-term maintenance
+#   alpha    — internally dogfooded hard enough to absorb the first wave of breakage
+#   beta     — seen behaving as a release beyond this repo; external release exposure exists
+#   stable   — passed the stable release gate; audited, not merely feature-complete
+#   mature   — full-release standing; best-practice operational gaps closed
 phase = "{{PHASE}}"
 
 # updated: ISO 8601 timestamp of last state change.

component-readiness-grades/COMPONENT-READINESS-GRADES.a2ml

@@ -3,13 +3,13 @@
 
 ; Component Readiness Grades (CRG) — Machine-readable specification
 ; Format: A2ML (AI-to-Machine Language)
-; Standard: CRG v1.0
+; Standard: CRG v2.0
 
 (standard
   (name "Component Readiness Grades")
   (abbreviation "CRG")
-  (version "1.0")
-  (date "2026-02-28")
+  (version "2.0")
+  (date "2026-03-30")
   (author "Jonathan D.A. Jewell <j.d.a.jewell@open.ac.uk>")
   (license "PMPL-1.0-or-later")
   (family "RSR"))
@@ -19,6 +19,7 @@
     (code X)
     (name "Untested")
     (release-stage #f)
+    (stability-posture #f)
     (ordinal 0)
     (description "No testing has been performed. Status unknown.")
     (evidence-required "none")
@@ -27,6 +28,7 @@
     (code F)
     (name "Harmful / Wasteful")
     (release-stage #f)
+    (stability-posture #f)
     (ordinal 1)
     (description "Actively harmful, wasteful, or better handled externally. Reject, deprecate, or delegate.")
     (evidence-required "documented test results showing harm, waste, or redundancy; comparison with alternatives")
@@ -35,6 +37,7 @@
     (code E)
     (name "Minimal / Salvageable")
     (release-stage "pre-alpha")
+    (stability-posture "unstable")
     (ordinal 2)
     (description "Does something slight. Barely functional. Needs redesign or major work.")
     (evidence-required "at least one successful test case; documented failures and limitations")
@@ -43,30 +46,34 @@
     (code D)
     (name "Partial / Inconsistent")
     (release-stage "alpha")
+    (stability-posture "unstable")
     (ordinal 3)
     (description "Works on some things but not systematically.")
-    (evidence-required "matrix of tested scenarios; documented scope vs actual capabilities")
+    (evidence-required "matrix of tested scenarios; documented scope vs actual capabilities; RSR compliance or documented equivalent repository discipline")
     (minimum-for "alpha"))
   (grade
     (code C)
     (name "Self-Validated")
-    (release-stage "beta")
+    (release-stage "alpha")
+    (stability-posture "stable-in-home-context")
     (ordinal 4)
     (description "Tested on the tool/project itself (dogfooding). Reliable in home context.")
-    (evidence-required "active dogfooding; CI integration or equivalent; no known failures in home context")
-    (minimum-for "beta"))
+    (evidence-required "active dogfooding; CI integration or equivalent; no known failures in home context; deep code and folder annotation")
+    (minimum-for "alpha"))
   (grade
     (code B)
     (name "Broadly Validated")
-    (release-stage "release-candidate")
+    (release-stage "beta")
+    (stability-posture "stable-for-broad-trial")
     (ordinal 5)
-    (description "Tested on at least 6 disparate, unrelated targets.")
-    (evidence-required "list of 6+ diverse targets with test results; evidence of feedback incorporation")
-    (minimum-for "release-candidate"))
+    (description "Tested on at least 6 disparate, unrelated targets beyond the home repo.")
+    (evidence-required "list of 6+ diverse targets with test results; evidence of feedback incorporation; minimum threshold for non-abstract publication")
+    (minimum-for "beta"))
   (grade
     (code A)
     (name "Field-Proven")
     (release-stage "stable")
+    (stability-posture "stable")
     (ordinal 6)
     (description "Real-world external feedback confirms value. Does no harm in the wild.")
     (evidence-required "real-world usage data; feedback incorporation evidence; no unresolved harm reports")
@@ -80,9 +87,9 @@
   (promotion
     (from E) (to D) (requirement "Fix critical failures. Document scope."))
   (promotion
-    (from D) (to C) (requirement "Dogfood on own project. Fix what breaks."))
+    (from D) (to C) (requirement "Dogfood on own project hard enough to absorb the first major breakages. Fix what breaks. Add deep code and folder annotation."))
   (promotion
-    (from C) (to B) (requirement "Test on 6+ diverse external targets. Fix what breaks."))
+    (from C) (to B) (requirement "Release beyond the home repo and test on 6+ diverse external targets. Fix what breaks."))
   (promotion
     (from B) (to A) (requirement "Ship. Collect external feedback. Demonstrate no harm."))
   (demotion
@@ -105,4 +112,16 @@
   (rule "Each grade above X MUST be supported by evidence per section 4.")
   (rule "Assessments MUST be recorded in a version-controlled location.")
   (rule "Assessments MUST be reviewed at least once per release cycle.")
-  (rule "Release stages MUST respect minimum grade thresholds."))
+  (rule "Release stages MUST respect minimum grade thresholds.")
+  (rule "Components graded D or above MUST satisfy RSR compliance or a documented equivalent repository discipline.")
+  (rule "Components graded C or above MUST have deep code and folder annotation.")
+  (rule "Non-abstract publication claims about implementation-facing work MUST NOT be made below grade B.")
+  (rule "Release-candidate is a project-level integration state, not a distinct component-grade threshold.")
+  (rule "Beta implies stability for broad trial; externally visible but shaky components SHOULD remain in alpha.")
+  (rule "This v2 standard is intentionally challengeable; missing evidence classes SHOULD be raised explicitly by reviewers."))
+
+(editorial-signoff
+  (reviewer "Codex")
+  (date "2026-03-30")
+  (scope "strictness and evidence posture of the standard itself")
+  (basis "NIST SP 800-218 SSDF; ACM Artifact Review and Badging; CompCert verified compiler practice; seL4 assumption-explicit verification practice"))