spec: V21, proper specifications requiring

Promotes V21 as the first-gate specifying-canon release for ENGI.

Proof-source commit: `33f3a75734fd6c0213c95b48f2e373c72fb1b735`

This promotion closes V21's first gate:
- `ENGI_SPECIFYING.md` is now the one complete specifying standard, with `ENGI_SPEC_TEMPLATEGUIDE.md` reduced to compatibility-only status
- V21+ hand-authored canonical spec family is now `SPEC`, `SPEC_DELTA`, and `SPEC_PARITY_MATRIX`
- the main `SPEC` is now required to be full-system, re-implementable, and auditable current canon rather than a focus-only release note
- full-canon totality is now enforced through appendix-grade derivability carriers rather than broad section headings alone
- exact proof-family derivability is now required in `SPEC`, including exact family/member/theorem/replay inventories, member-closure criteria, theorem-by-theorem closure readings, minimum artifact/
replay binding sets, verdict carriers, generated/test bindings, and fail-closed conditions
- generated canon is now treated as active canonical drafting input, not merely release output
- canonical promotion now fails closed on stale hand-authored status truth, missing file-family members, and missing canonical generated inputs
- V21 promotion now validates both `V20` pre-mutation canon and `V21` post-generation canon in one executable gate sequence
- V21 adds the minimal version-local specifying artifact family: `.engi/v21-spec-family-report.json` and `.engi/v21-canonical-input-report.json`
- V21 generates and checks `ENGI_SPEC_V21_PROVEN.md` as canonical generated appendix output
- source-side specifying enforcement now exists in `scripts/check-engi-spec-family.mjs`, `scripts/check-engi-canonical-inputs.mjs`, promotion-time hand-authored status preparation, and V21-aware
appendix generation
- the generalized specifying checker now validates both active `V21` canon and `V20_PROPER` as a second strict full-canon validation surface
- `V20_PROPER` hardens the specifying standard by proving the full-spec structure is reusable against an already-promoted version without future-truth import

Validation completed through canonical promotion:
- typecheck
- unit, integration, and E2E suites
- inherited V19 reproducible-canon gates
- inherited V20 operator-quality gates
- aggregate non-E2E suite
- promotion-time hand-authored V21 status preparation
- V21 `_PROVEN_` generation and check
- post-generation canonical-input validation for pointed `V21`
- promoted-mode V21 spec-family validation
- `git diff --check`

V21 accepts exact derivability carriers, not line-count parity with V16, as the first-gate density threshold.
V21 intentionally adds no new runtime/proof/operator artifact family beyond the generated appendix and specifying report pair.
`ENGI_SPEC_V22_NOTES.md` opens the next non-canonical notes surface without changing V21 canon.

Author: geraldarthurdavis

.engi/v21-canonical-input-report.json

@@ -0,0 +1,27 @@
+{
+  "reportId": "v21-canonical-input-report",
+  "version": "V21",
+  "proofSourceCommit": "33f3a75734fd6c0213c95b48f2e373c72fb1b735",
+  "generatedAt": "2026-04-12T11:23:06-03:00",
+  "generatorId": "engi-demo.proven-generator.v1",
+  "worktreeState": "clean",
+  "checkedTargetVersion": "V20",
+  "pointerVersion": "V21",
+  "passed": false,
+  "failureCount": 1,
+  "failures": [
+    "ENGI_SPEC.txt points to V21 but expected V20."
+  ],
+  "specPath": "ENGI_SPEC_V20.md",
+  "provenPath": "ENGI_SPEC_V20_PROVEN.md",
+  "parityPath": "ENGI_SPEC_V20_SYSTEM_PARITY_MATRIX.md",
+  "requiredGeneratedArtifactPaths": [
+    ".engi/v20-operator-acceptance-transcript.json",
+    ".engi/v20-visual-regression-report.json",
+    ".engi/v20-accessibility-report.json",
+    ".engi/v20-performance-budget-report.json",
+    ".engi/v20-projection-quality-smoke-matrix.json",
+    ".engi/v20-quality-summary.json"
+  ],
+  "requiredGeneratedArtifactCount": 6
+}

.engi/v21-spec-family-report.json

@@ -0,0 +1,37 @@
+{
+  "reportId": "v21-spec-family-report",
+  "version": "V21",
+  "proofSourceCommit": "33f3a75734fd6c0213c95b48f2e373c72fb1b735",
+  "generatedAt": "2026-04-12T11:23:06-03:00",
+  "generatorId": "engi-demo.proven-generator.v1",
+  "worktreeState": "clean",
+  "checkedVersion": "V21",
+  "mode": "draft",
+  "currentTarget": "V20",
+  "pointerVersion": "V21",
+  "passed": false,
+  "failureCount": 4,
+  "failures": [
+    "ENGI_SPEC.txt points to V21 but expected V20.",
+    "spec status block must declare Current canonical/latest target as V20.",
+    "delta status block must declare Current canonical/latest target as V20.",
+    "parity status block must declare Current canonical/latest target as V20."
+  ],
+  "requiredFiles": [
+    "ENGI_SPEC_V21.md",
+    "ENGI_SPEC_V21_DELTA.md",
+    "ENGI_SPEC_V21_PARITY_MATRIX.md"
+  ],
+  "supportFiles": [
+    "ENGI_SPECIFYING.md",
+    "ENGI_SPEC_TEMPLATEGUIDE.md"
+  ],
+  "requiredStatusLabelCount": 4,
+  "requiredPromotedStatusLabelCount": 1,
+  "requiredSpecSectionCount": 18,
+  "requiredAppendixSectionCount": 14,
+  "requiredProofFamilyCount": 9,
+  "requiredGeneratedArtifactCatalogSectionCount": 9,
+  "requiredGeneratedArtifactPathCount": 2,
+  "requiredSubsystemCoverageCount": 18
+}

ENGI_SPEC.txt

@@ -1 +1 @@
-V20
+V21

ENGI_SPECIFYING.md

@@ -505,8 +505,14 @@ For V21+ those carriers must, at minimum, cover:
 - subsystem totality and derivability,
 - proof family closure,
 - an exact proof-family inventory matrix,
+- exact per-family member inventories,
+- exact per-family theorem inventories,
+- exact theorem-to-replay-step groupings,
+- current proof-object field carriers for each proof family,
 - generated artifact contracts,
 - an exact generated-artifact inventory matrix,
+- generated appendix rendered-content contract,
+- generated appendix regeneration and fail-closed posture,
 - validation gates,
 - current canonical source surfaces,
 - and accepted boundaries.
@@ -669,6 +675,22 @@ In addition to per-family prose, the appendix-grade proof carrier must include a
 - witness artifact paths,
 - and current source-bearing implementation basis.
 
+The normalized minimum per-family detail block must make the following exact carriers directly recoverable from the main `SPEC`:
+- `proofArtifactPath`,
+- current source-bearing implementation basis,
+- exact member ids,
+- exact theorem ids,
+- exact replay step ids,
+- exact witness artifact paths,
+- current member closure criteria,
+- current member verdict shape,
+- current theorem-by-theorem closure reading,
+- current theorem-to-replay-step grouping,
+- minimum artifact/replay binding set,
+- current proof-object fields,
+- generated-artifact and validating-test bindings,
+- and fail-closed conditions.
+
 ## 7.1 Family Questions
 
 Every proof-family section must answer:
@@ -687,8 +709,12 @@ Every proof-family section must answer:
 The normalized minimum per-family detail block should therefore make the following directly recoverable in the main `SPEC`:
 - what the family proves,
 - how current closure is carried in source and artifacts,
+- the current member closure criteria,
 - the current member verdict shape,
+- the current theorem-by-theorem closure reading,
 - the current theorem-to-replay-step grouping,
+- the minimum artifact/replay binding set,
+- the current proof-object fields that carry theorem/member/replay truth,
 - the generated-artifact and validating-test bindings,
 - and the fail-closed conditions that would reopen the family.
 
@@ -775,6 +801,38 @@ It must render:
 
 It must fail check mode when stale.
 
+## 8.1.1 Minimum Generated Appendix Rendered Contents
+
+For a current full canon, `_PROVEN_` is not complete when it only carries aggregate counts.
+
+Its minimum rendered contents must make the following exact surfaces recoverable:
+- aggregate proof verdict,
+- exact proof-family inventory,
+- exact per-family member inventory,
+- exact per-family theorem inventory,
+- exact replay-step inventories and theorem bindings,
+- witness artifact inventories,
+- generated artifact inventories,
+- scenario and run coverage matrices,
+- run-detail truth needed to interpret proof execution,
+- disclosure classification relevant to proof artifacts,
+- and incomplete or failing verdicts when any exist.
+
+## 8.1.2 Canonical Regeneration And Fail-Closed Posture
+
+The generated appendix contract must also define:
+- which canonical promotion step regenerates `_PROVEN_`,
+- which check step proves the committed appendix is current,
+- which generated and proof-bearing surfaces the appendix materially depends on,
+- and which mismatch classes block promotion.
+
+At minimum, the generator or its checker must fail closed when:
+- a required proof family is missing,
+- a required member/theorem/replay inventory cannot be rendered exactly,
+- a required witness or generated artifact inventory is missing,
+- the proof-source commit does not match the rendered appendix,
+- or the committed appendix diverges from generator output in check mode.
+
 ## 8.2 Structured `.engi` Artifacts
 
 Every canonical generated JSON artifact must have: