M6: specify progressive source-qualification readiness - #39
Conversation
|
Independent exact-head review requested for |
|
Refreshed independent exact-head review request for What changed
Conflicts (2), both resolved as unions:
Taken from main without conflict: ID collision scanScanned Validation at
|
|
Independent merged-head review is complete at
SR-075 records the exact-main integration review. The specification task is |
|
Self-review status at |
…lan path main advanced past this branch's 5b1c134 merge point with the strict-syntax owner architecture, the past/history implementation campaign (PLAN-010), and the TL-182 MSRV bump to 1.98.1 (PR #84). Rebasing surfaced real ID collisions that a mechanical merge would have hidden: - FR-014 through FR-018 collided with main's own FR-014 (publish-strict-syntax- artifacts, landed by #66). Renumbered this branch's five FRs to FR-015 through FR-019 and updated every cross-reference and the census list. - SR-058 through SR-076 collided by filename with main's SR-058 through SR-072 (past-formula-v2, past-history-corpus, strict-owner-readers, tl-core-owner, and PLAN-010-closure reviews). Renumbered this branch's nineteen reviews to SR-084 through SR-102, clear of both the colliding filenames and main's highest declared `id:` (SR-083, from date-named cross-cutting reviews). - The Plan-007 bundle lived at a legacy top-level `plan/Plan-007-.../`, a location the repository stopped using before this branch's own base commit (every other plan, PLAN-001 through PLAN-010, already lived under `spec/plans/PLAN-NNN-.../` at 5b1c134). That path also was not covered by `is_archival_record`'s `spec/plans/` prefix, so it would have counted as a new top-level "plan" census area instead of the archival record it is. Moved it to `spec/plans/PLAN-007-source-qualification-readiness/` to match the established convention and its own archival exclusion. - Regenerated `EXPECTED_LIVE_TRACKED` and the per-area counts in tests/shared_assurance.rs from the actual post-rebase, post-renumber tree instead of hand-merging the conflicting hardcoded arrays. No MSRV references needed correction: this branch's own spec content never hardcoded 1.75, and CLAUDE.md/Cargo.toml/rust-toolchain.toml/clippy.toml were untouched by this branch, so the rebase picked up main's 1.98.1 pins cleanly. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
96fed20 to
b10bad9
Compare
…with PLAN-010 Independent review of this PR found that PLAN-007's own repository-unique Task-009 through Task-012 (renumbered on 2026-09-13 per FND-6601/SR-092) now collide with PLAN-010-past-history-implementation's own Task-009 through Task-012, which main landed independently after this branch was authored. quire validate --strict does not check id uniqueness, so the collision was silent; several PLAN-007 tasks reference these ids via repo-scoped ix://agent-ix/tl-syntax/Task-009..012 relationships that had become genuinely ambiguous. Renumber PLAN-007's Task-009..012 to the next free ids in its own sequence (Task-017..020): rename the four task files, update their id: frontmatter and in-body headings, and fix every cross-reference within PLAN-007 (plan.md, index.md, tasks/Task-013..016) plus the live cross-references in spec/requirements/FR-019 and spec/source-readiness.md and spec/reviews/SR-092/093/095/102 findings that pointed at the old ids. Historical log/review entries that narrate the 2026-09-13 renumbering event itself are left as an accurate record of what happened then; a new log.md entry documents today's renumbering separately. PLAN-010's own Task-009..012 are untouched. Re-verified zero remaining id: collisions across spec/plans/**/tasks/*.md; the only other duplicate ids (Task-001..007, reused across several older, plan-scoped plans) are pre-existing, not part of the repository-unique convention, and are not cross-referenced ambiguously between plans. make spec, make check-corpus and make fmt-check were run from a clean, isolated CARGO_TARGET_DIR; the only failures present (an unrelated pre-existing SpecReview frontmatter enum value in spec/reviews/26-09-14-temporal-ecosystem-architecture.md, and Rust example/assurance-env gaps requiring local setup) are identical before and after this change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
1 participant
Closes #34.
Outcome
Defines the M6 source-qualification-readiness boundary without introducing a
second user-authored language or a repository-local assurance framework. Native
Quire remains the sole editable formal-clause source. The branch adds MRS-004,
TM-004, StR-004, FR-014 through FR-018, NFR-004 and NFR-005, AP/AD/MP-002,
IT-001 and IT-002, Plan-007, and the complete SR-058 through SR-075 review set.
This PR is the specification deliverable. It does not claim that the 17 M6
implementation rows or a human source-release decision are complete.
Independent review changes
every task to its GitHub issue ([TL Syntax#34] Specify progressive TL source-qualification readiness and integrator boundary #34 and [TL Syntax#45] Admit M6 source-readiness external prerequisites #45 through [TL Syntax#51] Close M6 implementation assurance and human release gate #51), owner, consumers,
evidence method and explicit resume conditions.
descriptor-backed/capability snapshot whose bytes are consumed, with no
pathname reopen and a change-then-restore mutation control.
one immutable, bounded event snapshot (maximum 4096), detect gaps, duplicates,
reordering and cross-snapshot mixing, and use verified time authority and
canonical ordering for expiry.
top-level
plan/to be treated as archival. Only Markdown plan/review recordsare archival now, and a tracked extensionless
plan/runfixture is a positivecontrol.
5b1c134, preserving the landed W/M source andcanonical-graph corpus work and its exact source-census population.
Statusmatrix-column contract.merged, but no current immutable compatible release yet carries that contract.
Reviewed snapshots
767dc92a97f1b3d9ffbb76467bdda9ecf2261e4033678fa9598fea7a3d15bSR-066 through SR-075 record the independent base, failure-domain, integrity,
dependency, evidence, risk/complexity, scope-boundary, EARS, Rust and merged-head
reviews.
Verification
No hosted CI run is claimed.
make ciat9598fea— pass: formatting, feature matrix, strict Clippy, 75Rust tests plus one doctest, corpus/digest/oracle checks, cargo-deny, fuzz-target
build, unsafe audit, strict spec validation, MSRV tests, rustdoc, shared pin
checks, mutation probes and the complete assurance chain.
quire validate --scope . 'spec/**/*.md' --strict --summary— 164/164grammar-clean and structurally valid.
quire validate --scope . 'plan/**/*.md' --strict --summary— 11/11grammar-clean and structurally valid.
quire coverage --scope .— 99/165 rows backed overall; Rust 76/76; TM-004remains truthfully planned at 0/17.
quoin advisefor StR-004, FR-014 through FR-018, NFR-004 and NFR-005 — 48obligations; 0 mismatches, 0 uncatalogued methods and 0 inconclusive results.
Status and resume conditions
The specification/review task (#34, Plan-007 Task-009) is complete and ready for
human acceptance. Implementation issues #45 through #51 remain blocked on their
declared external release, retention/lifecycle, authority/event-source,
runner/integrator-package and LR08 owner conditions. No local substitute is
authorized.