All findings are open at baseline. Milestone 0 records them but does not change normative standards. A later milestone may close a finding only with source changes and focused fixture evidence.
| Finding | Status | Evidence |
|---|---|---|
| F001 | Resolved in Milestone 3 | Prompts are versioned, thin, path-neutral workflow entrypoints. |
| F004 | Resolved in Milestone 3 | Canonical planning lifecycle and structural fixtures. |
| F005 | Resolved in Milestone 3 | Planning and implementation prompts have separate intent and canonical workflow links. |
| F006 | Resolved in Milestone 4 | Verification owns typed acceptance claims; Testing, Tooling, Launcher, and Release link to that authority without redefining evidence. |
| F007 | Resolved in Milestone 6.1 | Documentation profiles are selected by durable decision, contract, responsibility, or operational impact; source-directory changes alone require no artifact. |
| F008 | Resolved in Milestone 6.3 | Staged review remains per commit; full-history review occurs at branch boundaries, and rewriting requires explicit authority, unshared commits, recoverability, and topology-aware verification. |
| F009 | Resolved in Milestone 6.2 | Checker invocations explicitly select index-only staged mode or an exact base/head commit range; unresolved inputs fail instead of selecting another diff. |
| F010 | Resolved in Milestone 6.2 | Project maps bind decision-bearing paths to one boundary/profile/artifact, and mapped ADRs must identify the exact boundary ID. |
| F012 | Resolved in Milestone 4 | Universal test durations, percentages, and CI-only categories were replaced by project/risk-based selection. |
| F013 | Resolved in Milestone 5 | Contract evolution is fact-driven; universal append-only and coexistence rules were removed. |
| F014 | Resolved in Milestone 5 | Degraded outcomes require authority and semantic fidelity; default/cache/partial fallback examples were removed. |
| F015 | Partially resolved in Milestone 7.1 | Commit process now has one workflow owner, examples have a reference owner, and the legacy file is an index; other mixed-role documents remain. |
| F016 | Resolved in Milestone 7.4b7a | Security owns contract-selected listener exposure, admission, lifecycle linkage, shutdown, and liveness; the broken anchor and universal network defaults were removed. |
| F017 | Resolved in Milestone 7.4b1 | Security owns component-aware, symlink-aware containment and typed failure; Cross-Platform owns filesystem identity without lexical prefix or universal case-folding defaults. |
| F018 | Resolved in Milestone 7.4b2c | Contracts owns runtime proof, IPC owns category/action-specific decoding and validated dispatch, and Security owns untrusted-input consequences without assertion or permissive fallback. |
| F019 | Resolved in Milestone 7.4b4b | Generic Concurrency distinguishes immutable data from shared mutation, prohibits callbacks under locks, preserves related invariants without a universal lock, and owns nonblocking async failure/cancellation lifecycle without fallback. |
| F020 | Partially resolved in Milestone 5.2 | Authoritative-store deletion fallback was removed; phased-mutation atomicity remains Milestone 7. |
| F022 | Resolved in Milestone 7.4b3g | Generic Language Bindings separates representation categories; the Rust specialization requires fallible conversion and real native/host evidence without universal C-ABI labels or alternate mechanisms. |
| F023 | Resolved in Milestone 7.4b3f | Rust Interop proves foreign-memory authority, Rust Security proves checked sizes, and Rust Unsafe separates adjacent operation proof, caller contracts, module invariants, and mechanism-selected evidence without safe-path fallback. |
| F024 | Resolved in Milestone 5.2 | Rust binding compatibility is classified independently for generated, package, ABI, wire, and persisted boundaries. |
| F025 | Resolved in Milestone 7.4b5c | Rust core/binding dependencies are one-way and framework-independent; runtime ownership remains with composition/lifecycle, binding handles consume shared capability, and retained runtimes never carry prior request state. |
| F026 | Resolved in Milestone 7.4b5f | Executor delegation, filesystem authority-through-use, and listener exposure/admission now consume explicit lifecycle owners with typed outcomes and no detached-work fallback. |
| F027 | Resolved in Milestone 7.3a | Major version zero and prerelease identifiers are distinct, and retained publication guidance now consumes that decision. |
| F028 | Resolved in Milestone 7.3a | SBOM, checksum, signature, and provenance applicability follow artifact content, consumer, risk, channel, and regulatory facts. |
| F029 | Resolved in Milestone 7.3a | Release units may version independently or in lockstep, lockfiles follow dependency-resolution ownership, and publication pushes only the intended tag. |
| F031 | Resolved in Milestone 4.1 | Acceptance claim fixtures independently model proof kind, environment qualification, and execution mode. |
| D005 | Resolved in Milestone 7.1 | Commit and slice process is owned by implementation/commit workflows; prompts route only, and commit examples are non-normative reference. |
| F032 | Resolved in Milestone 7.2c2 | Documentation examples, proportional workflow policy, and release-owned changelog semantics have canonical owners; the legacy documentation file is now a bounded migration index. |
| F033 | Resolved in Milestone 7.2a | The commit disposition checker now filters its shared ledger by source; documentation rows have a separate owner-specific fixture. |
| F034 | Resolved in Milestone 7.3d | Release policy has one canonical workflow owner, optional changelog automation has a non-normative reference owner, and the legacy release file is link-only. |
| F035 | Resolved in Milestone 7.2c1 | Contract and verification ownership checks now follow the canonical release workflow instead of requiring duplicate direct links from the legacy release index. |
| F036 | Resolved in Milestone 7.3a | Retained pipeline and publication sections consume canonical artifact and prerelease decisions instead of restoring conflicting defaults. |
| F037 | Resolved in Milestone 7.3b4 | Pipeline, maintenance/channel, publication, and routing/checklist concerns completed as four independently verified slices. |
| F038 | Resolved in Milestone 7.3b1 | Provider-specific tags, workflow syntax, runner labels, and permissive artifact uploads no longer define generic release pipeline policy. |
| F039 | Resolved in Milestone 7.3b2 | Maintenance, LTS, channel, and activation policy now follows explicit contracts rather than branch names, fixed durations, named channel sets, or universal feature-flag lifetimes. |
| F040 | Resolved in Milestone 7.3b3 | Missing dispositions for removed download-example identifiers STD-0571 through STD-0574 were reconciled with explicit merge/remove outcomes. |
| F041 | Resolved in Milestone 7.3b4 | Generic release guidance now selects language profiles through the router and derives procedure steps from accepted decisions instead of universal Rust, commit, tag, audit-tool, or publication commands. |
| F042 | Resolved in Milestone 7.3c | Recovery now follows impact, destination capability, explicit authority, immutable identity, and fresh acceptance rather than assuming hosted drafts, yank support, branches, patch versions, or unilateral action. |
| F043 | Resolved in Milestone 7.4a | The remaining 698 identifiers now have complete owner-wave coverage, correctness-first ordering, and an exact first implementation slice without speculative full-sequence expansion. |
| F044 | Resolved in Milestone 7.4b4a | The premature final-closure handoff is superseded by a measured 90-ID trust remainder, a 26-ID lifecycle bridge for F025/F026, and one exact generic Concurrency next slice. |
| F045 | Resolved in Milestone 7.4b4g | Rust Async applicability, lifecycle, blocking isolation, synchronization, cancellation safety, cleanup, and observability are contract-selected without named-mechanism fallback. |
| F046 | Resolved in Milestone 7.4b7c | Cross-Platform target support, isolation, mechanism selection, semantic fidelity, and evidence now follow explicit contracts without fixed targets, universal architecture/layout, or stub fallback. |
| F047 | Resolved in Milestone 7.4b7e | Rust target triples, support claims, cfg/module placement, and evidence follow selected target and artifact contracts without fixed targets, best-effort status, numeric layout thresholds, named substitute tools, or weaker evidence. |
| F048 | Execution train active after Milestone 7.4b7o | STD-0473, STD-0757, STD-0824, STD-0583, and STD-0601 were accepted before the immutable train; its remaining Security, Cross-Platform, Interop, Rust Security, and Rust Language Binding clusters retain owner review, decomposition, and final-closure gates. |
| F049 | Resolved in Milestone 7.4b7g | Interop owns provider-selected registration, delivery, unregistration, release, and shutdown semantics with phase-aware outcomes, conditional Concurrency routing, and no destruction-linked cleanup. |
| F050 | Resolved in Milestone 7.4b7f2 | The executor-delegation checker now requires the stable resolved F026 state established by accepted Milestone 7.4b5f; all behavioral, disposition, metadata, legacy, and decomposition checks remain active. |
| F051 | Resolved in Milestone 7.4b7i | STD-0757 now has Rust Language Binding ownership: selected schema and serializer facts, complete attribute-derived representation, consumer agreement, typed outcomes, and native/host evidence replace implicit Serde defaults. |
| F052 | Resolved in Milestone 7.4b7k | STD-0824 now requires a selected queue operation/resource contract, capacity, overload/retention outcome, telemetry, current-input ownership, typed diagnostics, and Rust operation evidence instead of fixed capacity or drop-oldest defaults. |
| F053 | Resolved in Milestone 7.4b7m | Contracts now owns validation proof lifetime: authority follows the intact proof-bearing representation, invalidation or a new applicable boundary requires current proof, and unchanged validated values are not redundantly decoded. |
| F054 | Resolved in Milestone 7.4b7n | The remaining 589 identifiers now use one verified 47-cluster execution train; planning-only commits occur on actual re-plan triggers rather than between every accepted implementation slice. |
| F055 | Resolved in Milestone 7.4b7o | Execution progress is derived from exact dispositions against an immutable 589-ID manifest; routine cluster completion no longer requires shared-checker counter and cursor rewrites. |
| F056 | Resolved in Milestone 7.4b8a | Security now selects operation-specific validation authority and typed consequences without a global C# utility, fixed regex/length rules, validation-by-cast, or copied validators lacking canonical authority and conformance evidence. |
| F057 | Resolved in Milestone 7.4b8b | Mixed-role execution rows now decompose through an exact ordered overlay without mutating the immutable baseline manifest or forcing one stale proposed owner. |
| F070 | Resolved in Milestone 7.4b8l | The 43 pending train rows now use 39 risk- and train-classified semantic packages, pre-approved owner contracts, incremental reusable verification, risk-based gates, isolated drafts, and serial shared integration without weakening exact dispositions or no-fallback policy. |
| F071 | Resolved in Milestone 7.4b8m | Repeated decision-fixture parsing now has one strict table engine for schema domains, unique cases, exact observation coverage, and outcome comparison; package checkers retain domain derivation without eval, embedded generic policy, or legacy schema fallback. |
| F072 | Resolved in Milestone 7.4b8n | Immutable row 5 now has ordered Rust testability, generic mechanism-selection, Contracts evolution, and Rust discovery-adaptation children; fixed framework, compatibility, lockstep-version, and version-export defaults cannot become one binding rule. |
| F073 | Resolved in Milestone 7.4b8s | Immutable row 6 now has ordered Cross-Platform loading, Release artifact identity/installability, and Verification evidence-scheduling children; fixed Strategy, filename, platform, provider-matrix, fail-fast, and trigger defaults cannot become one cross-platform rule. |
| F074 | Resolved in Milestone 7.4b8w | Immutable row 7 now has ordered Rust workspace/evidence, Release artifact composition, Contracts compatibility, and generic binding-surface children; example layouts, test exclusion, packaging/version defaults, and automatic surface exposure cannot become one Rust rule. |
| F075 | Resolved in Milestone 7.4b29a | Immutable row 39 now separates process coordination, identity, platform capability, recovery, service ownership, convergence, and evidence authority from non-normative illustrations; the Architecture reference cannot own PID-file, retry, readiness, lifecycle, transport, diagnostic, or benefit policy. |
| F076 | Active in Milestone 7.4c | All 916 frozen identifiers are dispositioned and the source-gap audit is empty, but 27 former standard/profile sources remain normative. Sixteen require index rewrites, eleven require final purity review, and the Router retains two temporary "until migration" routes. |
| F077 | Resolved in Milestone 7.4c1 | The immutable execution-train and earlier trust/lifecycle re-plan verifiers coupled accepted evidence to parent Milestone 7.4c remaining Planned; the train now proves the stable 7.4b37b to 7.4c1 handoff and the trust/lifecycle verifier owns only its accepted 7.4b4a evidence. |
| F078 | Resolved in Milestone 7.4c3v1 | One strict reusable engine now validates source-owned fixture directories; focused negative fixtures exercise the same engine, the aggregate runs accepted sources in immutable manifest order, and the bespoke Coding verifier and flat fixture are removed. |
| F079 | Resolved in Milestone 7.4c3s | Documentation preflight found a source-specific historical checker that required obsolete migration-index wording outside the source package write set. The standing protocol now permits only the affected source package to remove obsolete structural assertions while preserving semantic evidence and keeping shared checkers serial. |
| F080 | Resolved in Milestone 7.4c3h41 | The completed row 41 checker also required obsolete Documentation migration-index prose. A separate serial repair removes only that mutable assertion while preserving immutable row 41, P33, STD-0349, route, disposition, non-authority, and transitive owner evidence. |
| F081 | Resolved in Milestone 7.4c3hdoc | The mixed Documentation changelog checker treated every level-two heading as policy. A serial repair preserves exact changelog and Release semantics, prohibits actual legacy policy sections, and leaves final index shape to the aggregate closure engine. |
| F082 | Resolved in Milestone 7.4c3p | Source closure no longer serializes disjoint checker preparation. A frozen inventory gives eight packages exclusive source, fixture, and checker writes; shared authority and manifest-ordered acceptance remain serial, and one complete-suite run closes each contiguous integrated group. |
| F083 | Resolved in Milestone 7.4c3rh | Route fixtures now separate canonical repository targets from source-relative Markdown hrefs. The engine resolves and compares path plus anchor, rejects repository escape and mismatch, and accepts no old-schema or nested-source fallback. |
| F084 | Resolved in Milestone 7.4c3hs2c | Four exclusive repairs removed shared IPC and local Security-reader dependence on transitional headings and HEAD; whole-source routes and exact prohibitions preserve semantics through pure-index closure. |
| F085 | Resolved in delegated M5-CP6 / Milestone 7.4c3.7 | Five owner-local declarative suites preserve target, loading, Release, Verification, and Rust specialization evidence; the generic source-index engine closes the former source without transitional headings, and temporary M5-CP0 is retired. |
| F086 | Active in delegated verification-engine plan | The 274-script Bash verification architecture repeats parsing, policy branches, transitive execution, and diagnostics; 166 scripts invoke verifier/helper paths and 43 parse document sections with sed. |
| ID | Class | Evidence | Required disposition | Milestone |
|---|---|---|---|---|
| F001 | Distribution gap | .gitignore:1; ignored prompts/*.md |
Decide whether prompts are versioned thin entrypoints or explicitly local; never treat ignored files as repository authority. | 1, 3 |
| F002 | Routing | README.md:5-12 |
Replace full-library reading with deterministic routing and exclusions. | 2 |
| F003 | Precedence | languages/README.md:3; languages/rust/RUST-STANDARDS.md:26-43 |
Define generic ownership, profile specialization, and explicit override semantics. | 1, 2 |
| F004 | Plan lifecycle | PLAN-STANDARDS.md:148-179,256-273; templates/PLAN-TEMPLATE.md:86,100 |
Separate active state/history, add lifecycle states, supersession, and acceptance closure. | 3 |
| F005 | Prompt conflict | prompts/planning.md:1-14; prompts/implement-plan.md:37-48 |
Separate planning from implementation and make prompts reference canonical workflows. | 3 |
| F006 | Acceptance ownership | TESTING-STANDARDS.md:141-165; PLAN-STANDARDS.md:148-179 |
Give verification levels one owner and bind plan acceptance to named evidence. | 3, 4 |
| F007 | Disproportionate documentation | DOCUMENTATION-STANDARDS.md:9-13,184-209 |
Require durable docs at meaningful decision/contract boundaries, not every source directory/change. | 6 |
| F008 | History authority | COMMIT-STANDARDS.md:210-242; PLAN-STANDARDS.md:243-252 |
Keep atomic staged review; require explicit authority for history/worktree rewriting. | 6 |
| F009 | Traceability defect | templates/check-decision-traceability.sh:103-119; TOOLING-STANDARDS.md:731-745 |
Make configured staged/PR modes inspect the changes they claim to enforce. | 6 |
| F010 | Traceability ownership | templates/check-decision-traceability.sh:130-136,209-218 |
Link a changed ADR to affected decisions; any global ADR must not satisfy every directory. | 6 |
| F011 | Broad launcher profile | LAUNCHER-STANDARDS.md:3-18,163-172 |
Make launcher guidance conditional on applications that need a common launcher. | 6, 7 |
| F012 | Broad test metrics | TESTING-STANDARDS.md:88-95,374-398,658-675 |
Move duration/coverage/tool assumptions to project profiles; preserve risk-based verification. | 4 |
| F013 | Contract overgeneralization | ARCHITECTURE-PATTERNS.md:202-220; CODING-STANDARDS.md:454-460 |
Select evolution policy from authority, persistence, consumers, and deployment. | 5 |
| F014 | Degraded-mode overgeneralization | ARCHITECTURE-PATTERNS.md:1093-1151 |
Permit degradation only with authoritative, semantically valid data; otherwise return typed diagnostics. | 5 |
| F015 | Mixed roles | ARCHITECTURE-PATTERNS.md; TOOLING-STANDARDS.md; languages/rust/RUST-LANGUAGE-BINDINGS-STANDARDS.md |
Separate policy, profiles, pattern catalog, recipes, and product-local examples. | 7 |
| F016 | Broken reference | SECURITY-STANDARDS.md:289; no matching concurrency heading |
Repair or remove the nonexistent graceful-shutdown anchor. | 7 |
| F076 | Incomplete source closure | 27 legacy standard/profile corpus rows remain normative after exact rule migration; 16 need index rewrites and the Router retains two temporary legacy routes. | Execute the owner-ordered final source-closure train, remove legacy routing first, prove every retained path is a non-normative pure index, and complete the D001 through D010 ownership review. |
7 |
| F077 | Mutable terminal-checker coupling | verify-milestone-7-execution-train.sh and verify-milestone-7-trust-lifecycle-replan.sh required parent Milestone 7.4c to remain Planned after their owned evidence was accepted. |
Preserve immutable train and trust/lifecycle evidence, assert only stable accepted outcomes, and leave current source-closure status to its active plan and focused verifier. | 7 |
| F078 | Repeated source-closure verification | verify-coding-index-source-closure.sh and 26 pending source packages share structural corpus, manifest, route, heading, authority-language, and identifier invariants. |
Establish one reusable engine, aggregate live verifier, negative engine fixtures, and source-owned fixture directories; retain source-specific semantics in existing owner verifiers. | 7 |
| F079 | Obsolete source-checker wording ownership | verify-documentation-index-closure.sh requires the exact legacy sentence This file is a migration index, while the source package must remove migration-era authority wording and was not authorized to edit the checker. |
Preflight each source-specific checker; preserve semantic evidence, permit the owning source package to remove only obsolete structural assertions, and stop for a separate re-plan when the checker is shared or mixed-source. | 7 |
| F080 | Historical checker owns mutable source prose | verify-milestone-7-row-41-decomposition.sh requires This file is a migration index even though row 41 is complete and later source closure must replace that prose. |
In a separate serial checker repair, retain immutable train/package/owner/disposition and durable route/non-authority evidence, remove only the obsolete prose assertion, and add a negative self-scan. | 7 |
| F081 | Mixed checker conflates navigation and policy | verify-documentation-changelog-closure.sh rejects every level-two Documentation heading while also owning exact changelog dispositions and canonical Release behavior. |
Repair the mixed checker serially: preserve its disposition, route, Release, and negative-content evidence; reject explicit legacy policy sections; delegate title, ordered headings, and line bounds to the aggregate source-closure engine. | 7 |
| F082 | Over-serial source-checker repair | The standing source-closure protocol required separate serial repair cycles for disjoint mixed or historical checkers, repeating planning and complete-suite gates without protecting additional shared authority. | Freeze exclusive package write sets and semantic preservation evidence; prepare disjoint packages concurrently in isolated worktrees; retain one serial integration owner, contiguous manifest acceptance, focused package gates, and a complete suite at each integrated group boundary. | 7 |
| F083 | Nested source route representation | check-source-index-closure.sh:214-220 requires a route target to be repository-relative, rejects ../, verifies $REPO_ROOT/$target, and then requires the exact ($target) link in the source. Nested indexes currently use valid ../../... Markdown links. |
Re-plan the shared route fixture and engine contract so canonical repository targets and source-relative hyperlinks are represented and validated separately. Replace the schema atomically; do not retain the old form as fallback or exempt nested sources. | 7 |
| F084 | Mixed-source checker ownership blocks Security closure | verify-input-validation-authority.sh and verify-validation-proof-lifetime.sh compare mutable Security source regions to HEAD; verify-network-transport-policy.sh, verify-milestone-7-row-42-decomposition.sh, and verify-security-index-closure.sh require transitional headings; verify-ipc-payload-validation.sh inspects Architecture, Interop, and Security legacy sections together. |
Freeze a non-overlapping checker-infrastructure decomposition before Security closure. Preserve canonical semantics, exact dispositions, routes, typed outcomes, and negative evidence; remove mutable legacy-shape ownership without retaining headings, old-schema parsers, source exceptions, or weaker checks. | 7 |
| F085 | Unassigned Cross-Platform source-shape ownership | Resolved by M5-CP1 through M5-CP6: five owner-local declarative suites preserve canonical topic, Release, Verification, and Rust specialization semantics; the generic aggregate owns index structure; source package 7 is derived navigation; temporary M5-CP0 and all dependency edges are absent. | Retain the accepted owner suites and source-owned closure fixture. Do not restore heading-delimited readers, M5-CP0, a replacement prerequisite, preparation-inventory false ownership, compatibility branches, source exceptions, or prior-source fallback. | 7 |
| F086 | Bespoke verification architecture | 274 verify-*.sh scripts; 166 transitive invokers; 43 sed parsers; 13 decision-table helper consumers |
Implement the delegated generic verification engine plan; migrate by semantic owner and delete each replaced script without command actions, compatibility schemas, or policy-specific engine branches. | 7 |
| F070 | Per-row migration ceremony | 43 pending immutable-train rows; repeated bespoke checker and owner-review patterns | Batch only rows sharing owner, semantic outcome, prerequisites, and evidence; classify risk, pre-approve owner contracts, add reusable validators incrementally, and retain serial shared integration and exact dispositions. | 7 |
| F071 | Repeated fixture plumbing | Decision-oriented owner checkers repeatedly parse TSV headers, domains, unique cases, and expected/actual comparisons | Establish one strict reusable table engine while leaving package-specific semantic derivation with each owner checker; reject malformed or incomplete tables rather than guessing. | 7 |
| F072 | Mixed-role Rust binding row | Frozen IDs STD-0804-STD-0809; immutable execution row 5 |
Decompose framework-independent testability, generic boundary selection, contract evolution, and Rust discovery adaptation before normative movement. | 7 |
| F073 | Mixed-role cross-platform row | Frozen IDs STD-0294-STD-0299; immutable execution row 6 |
Decompose native artifact loading, release artifact identity/installability, and target evidence scheduling before normative movement. | 7 |
| F074 | Mixed-role Rust binding workspace and surface row | Frozen IDs STD-0761-STD-0771; immutable execution row 7 |
Decompose Rust package/evidence boundaries, Release artifact composition, Contracts compatibility, and generic binding-surface governance before normative movement. | 7 |
| F075 | Mixed-role process-coordination reference row | Frozen IDs STD-0093-STD-0105; immutable execution row 39 |
Decompose process exclusion, identity, platform capability, recovery, service ownership, convergence, diagnostics, and evidence before retaining only conditional non-normative illustrations. | 7 |
| F032 | Consolidation ownership | DOCUMENTATION-STANDARDS.md; frozen IDs STD-0349-STD-0448 |
Move examples, documentation policy, and changelog guidance in separate reference, workflow, and release-owner slices. | 7 |
| F033 | Fixture ownership | verify-consolidation-dispositions.sh; shared disposition ledger |
Filter each owner-specific fixture by source and verify new source groups independently. | 7 |
| F034 | Missing canonical owner | ../../../evaluation/standards-effectiveness/owner-map.tsv; RELEASE-STANDARDS.md; absent workflows/release.md |
Establish release workflow ownership in an owner-bounded slice before moving changelog policy or closing the documentation index. | 7 |
| F035 | Fixture ownership | Release checks in verify-contract-ownership.sh and verify-verification-ownership.sh |
Validate the canonical release dependency chain and only require the legacy file to route to that owner. | 7 |
| F036 | Dependent legacy override | Retained release pipeline and publication sections after partial migration | Make dependent legacy sections consume canonical decisions and verify that they cannot restore removed defaults. | 7 |
| F037 | Slice ownership | RELEASE-STANDARDS.md; frozen IDs STD-0552-STD-0576 |
Decompose pipeline mechanics, maintenance/channels, publication presentation, and language/checklist routing before implementation. | 7 |
| F038 | Provider-specific pipeline policy | RELEASE-STANDARDS.md; frozen IDs STD-0552-STD-0560 |
Replace provider-specific trigger, runner, workflow-syntax, and permissive-upload defaults with authenticated dispatch, project-owned mechanisms, and fail-closed artifact collection. | 7 |
| F039 | Maintenance/channel conflation | RELEASE-STANDARDS.md; frozen IDs STD-0561-STD-0565 |
Separate support, source-lineage, delivery-channel, and runtime-activation decisions; remove fixed branch, duration, channel-name, and feature-flag defaults. | 7 |
| F040 | Disposition drift | RELEASE-STANDARDS.md; frozen IDs STD-0571-STD-0574; Milestone 7.3a history |
Reconcile previously removed download examples to canonical artifact presentation or explicit removal without restoring legacy text. | 7 |
| F041 | Routing/procedure conflation | RELEASE-STANDARDS.md; frozen IDs STD-0575-STD-0576 |
Route specialized mechanisms through selected profiles and replace the universal command checklist with a decision-derived release procedure. | 7 |
| F042 | Provider-specific rollback | RELEASE-STANDARDS.md; frozen IDs STD-0577-STD-0581 |
Replace universal unpublish/yank/branch/patch instructions with capability-driven recovery, explicit emergency authority, and impact-driven incident records. | 7 |
| F043 | Undecomposed consolidation scope | Remaining frozen inventory and Milestone 7 sequence | Decompose remaining identifiers by canonical owner and correctness dependency before another normative move. | 7 |
| F044 | Premature closure handoff | Active-plan 7.4c handoff after Milestone 7.4b3g; rolling remainder of 641 IDs and 16 missing owners |
Keep final closure reserved until the remainder reaches zero; insert the generic Concurrency and Rust Async dependency bridge before dependent trust-boundary specializations. | 7 |
| F048 | Residual owner-map drift | Frozen IDs STD-0294-STD-0299, STD-0474-STD-0482, STD-0582, STD-0588-STD-0591, STD-0758, STD-0761-STD-0771, STD-0776-STD-0780, STD-0782-STD-0789, STD-0792, STD-0793, STD-0797, STD-0804-STD-0809, STD-0821, STD-0826 |
Resolve the residual cross-role destinations through their immutable-train owner-review, decomposition, and final-closure gates before normative movement. | 7 |
| F049 | Incomplete event-registration lifecycle | INTEROP-STANDARDS.md; frozen ID STD-0473 |
Replace universal destruction-linked unsubscription with explicit registration authority, provider-selected delivery/unregistration/release/shutdown behavior, phase-aware outcomes, and conditional Concurrency routing only for callback-created work that can outlive invocation. | 7 |
| F050 | Stale verification ownership | verify-rust-binding-executor-delegation.sh; resolved F026 status |
Replace the temporary partial-status assertion with the accepted resolved state while retaining all executor-delegation behavior, disposition, metadata, legacy, and decomposition evidence. | 7 |
| F051 | Serde wire-representation ownership | languages/rust/RUST-INTEROP-STANDARDS.md; frozen ID STD-0757 |
Move Serde wire-shape mechanisms to the Rust Language Binding specialization; derive the effective representation from a selected schema and attributes, require consumer agreement and native/host evidence, and reject implicit casing, tagging, serializer, or schema-free fallback. | 7 |
| F053 | Validation proof-lifetime overgeneralization | SECURITY-STANDARDS.md; frozen IDs STD-0583, STD-0601 |
Move validated-representation lifetime to Contracts; require new proof after representation loss, unchecked mutation, contract change, or a new applicable boundary without redundantly decoding an unchanged validated value. | 7 |
| F054 | Procedural amplification | Milestone 7.4b7 planning/implementation alternation; 589-ID remainder | Freeze dependency-ordered owner clusters once, retain focused per-commit evidence and explicit re-plan triggers, and reserve complete-suite repetition for shared-boundary changes and wave checkpoints. | 7 |
| F055 | Mutable execution counters | Initial Milestone 7 execution-train checker | Derive whole-cluster completion, current residual coverage, and the active cursor from exact dispositions against an immutable baseline manifest. | 7 |
| F056 | Global validator and fixed-rule defaults | SECURITY-STANDARDS.md; frozen IDs STD-0588-STD-0591 |
Select one canonical validation authority from the complete operation contract at each applicable untrusted boundary; require generated or independent implementations to prove conformance, route specialized mechanisms to their owners, and return typed outcomes when authority is missing. | 7 |
| F057 | Mixed-role immutable-train row | Baseline execution row 2; STD-0474-STD-0482 |
Preserve baseline coverage while overlaying ordered Contracts, IPC, Language Binding, and legacy-index children with exact coverage and whole-child progress. | 7 |
| F058 | Cross-language compatibility inference | INTEROP-STANDARDS.md; frozen IDs STD-0474, STD-0475, STD-0477, STD-0481 |
Select evolution from the applicable contract classes and one canonical wire/schema authority; require deployment-matched producer/consumer evidence and typed outcomes instead of schema guessing or old/dual-shape shims. | 7 |
| F059 | Resolved in Milestone 7.4b8d | INTEROP-STANDARDS.md; frozen ID STD-0476 now routes to complete IPC consumer decoding and validated-variant dispatch without partial-field, raw-input, log-and-return, or permissive fallback. |
7 | |
| F060 | Resolved in Milestone 7.4b8e | INTEROP-STANDARDS.md; frozen IDs STD-0478-STD-0480 now derive tagged-enum, variant, and field representation from the canonical contract plus selected serializer with consumer evidence and typed outcomes. |
7 | |
| F061 | Resolved in Milestone 7.4b8f | INTEROP-STANDARDS.md; frozen ID STD-0482 is a non-normative boundary-fact routing index with no active rules, defaults, examples-as-policy, or fallback guidance. |
7 | |
| F062 | Mixed-outcome Rust binding row | Baseline execution row 3; STD-0776-STD-0780 |
Preserve the Rust Language Binding owner while decomposing error mapping, event-delivery adaptation, and callback task execution into ordered independently verifiable children. | 7 |
| F063 | Resolved in Milestone 7.4b8h | languages/rust/RUST-LANGUAGE-BINDINGS-STANDARDS.md; frozen IDs STD-0776, STD-0777 now select a host error contract and preserve typed categories, cancellation, bounded non-sensitive context, and checked native/host mapping. |
7 | |
| F064 | Resolved in Milestone 7.4b8i | languages/rust/RUST-LANGUAGE-BINDINGS-STANDARDS.md; frozen IDs STD-0778, STD-0779 now select host event delivery with governed capacity, provider authority, current-event isolation, and typed delivery outcomes without push/pull substitution. |
7 | |
| F065 | Resolved in Milestone 7.4b8i | verify-rust-binding-error-mapping.sh compared an unrelated later legacy section to HEAD, preventing its authorized owner slice; Rust binding verifiers now assert only their bounded legacy concern while staged review proves slice-local preservation. |
7 | |
| F066 | Resolved in Milestone 7.4b8j | languages/rust/RUST-LANGUAGE-BINDINGS-STANDARDS.md; frozen ID STD-0780 now requires checked, correlated, lifecycle-owned host callback-task adaptation with fresh invocation state instead of no-op, polling, or framework-specific substitutes. |
7 | |
| F067 | Resolved in Milestone 7.4b8k | languages/rust/RUST-LANGUAGE-BINDINGS-STANDARDS.md; frozen ID STD-0797 now selects enum representation from the concrete framework, wire, ABI, opaque-handle, or generated-wrapper contract without native-layout, inferred-value, sentinel, or alternate-mechanism fallback. |
7 | |
| F068 | Resolved in Milestone 7.4b8k | verify-rust-wire-representation.sh required a superseded next-slice string and compared an unrelated legacy prefix to HEAD; the permanent verifier now checks only its accepted state and bounded wire concern. |
7 | |
| F069 | Resolved in Milestone 7.4b8k | The aggregate verification invocation used pipefail without errexit, allowing a failed checker before the loop's last command to be masked; cumulative verification is rerun with set -euo pipefail. |
7 | |
| F031 | Acceptance dimensions | workflows/planning.md:91-98; tools/standards_verifier/standards_verifier/checks/plan_contract.py |
Model evidence kind, required environment, and execution mode independently; require all named claims rather than comparing one scalar rank. | 4 |
| ID | Severity | Evidence | Required disposition | Milestone |
|---|---|---|---|---|
| F017 | Critical | SECURITY-STANDARDS.md:21-45; CROSS-PLATFORM-STANDARDS.md:163-174 |
Replace string-prefix path checks with canonical, boundary-aware, symlink-aware containment. | 7 |
| F018 | Critical | ARCHITECTURE-PATTERNS.md:280,451; SECURITY-STANDARDS.md:185 |
Validate action-specific payloads before producing validated types; do not cast unknown as proof. |
7 |
| F019 | High | CONCURRENCY-STANDARDS.md:23,35-67,121 |
Avoid callbacks under locks, distinguish immutable/thread-safe data, and clarify blocking rules. | 7 |
| F020 | High | ARCHITECTURE-PATTERNS.md:965-1006,1093 |
Do not call phased mutation atomic without rollback/transaction; delete corrupt stores only when explicitly disposable. | 5, 7 |
| F021 | High | languages/rust/RUST-API-STANDARDS.md:206-209; RUST-TOOLING-STANDARDS.md:15; RUST-RELEASE-STANDARDS.md:119 |
Require --all-features only when features compose; otherwise test supported matrices. |
7 |
| F022 | Critical | Frozen IDs STD-0773-STD-0775, STD-0795-STD-0796, STD-0801-STD-0803; F022/F023 decomposition |
Use checked conversions and distinguish framework-liftable types from C-ABI-safe types. | 5, 7 |
| F023 | Critical | Frozen IDs STD-0753-STD-0755, STD-0823, STD-0845-STD-0847; F022/F023 decomposition |
State allocation, initialization, alignment, provenance, lifetime, and size preconditions; require local SAFETY: proof and caller # Safety contracts. |
7 |
| F024 | High | languages/rust/RUST-LANGUAGE-BINDINGS-STANDARDS.md:106,810-814 |
Define compatibility per framework, host language, ABI, and persisted artifact. | 5, 7 |
| F025 | High | languages/rust/RUST-LANGUAGE-BINDINGS-STANDARDS.md:31,525,635,719; RUST-ASYNC-STANDARDS.md:43 |
Keep core independent of binding frameworks and give runtime ownership to composition/lifecycle policy. | 7 |
| F026 | High | languages/rust/RUST-SECURITY-STANDARDS.md:9,96; RUST-ASYNC-STANDARDS.md:46; RUST-LANGUAGE-BINDINGS-STANDARDS.md:444 |
Track spawned work, avoid TOCTOU examples, and never reinterpret every error as unsupported fallback. | 5, 7 |
| F027 | High | RELEASE-STANDARDS.md:18-30,466-470 |
Distinguish SemVer 0.x instability from prerelease identifiers. |
5, 7 |
| F028 | High | RELEASE-STANDARDS.md:162-163,216-231,368-374 |
Make SBOM applicability consistent and artifact/risk-based. | 7 |
| F029 | High | RELEASE-STANDARDS.md:68-74,252-263,527-530 |
Separate package-version/lockfile models and push only the intended release tag. | 7 |
| F030 | High | TOOLING-STANDARDS.md:155-160,321-328,388-395 |
Reconcile fail-on-warning policy with explicitly owned temporary debt. | 6, 7 |
| F045 | High | languages/rust/RUST-ASYNC-STANDARDS.md:6-163 |
Replace blanket sync-core, runtime, abort, blocking-pool, mutex, cancellation, and inspection-tool defaults with contract-selected Rust mechanisms and typed unavailable outcomes. | 7 |
| F046 | High | CROSS-PLATFORM-STANDARDS.md:5-135; frozen IDs STD-0280-STD-0288 |
Derive target support and platform-mechanism selection from explicit project, language, build, and deployment contracts; preserve semantics with typed outcomes instead of universal Strategy/Factory, file-layout, runtime-only, or stub defaults. | 7 |
| F047 | High | languages/rust/RUST-CROSS-PLATFORM-STANDARDS.md; frozen IDs STD-0726-STD-0730 |
Derive Rust target triples, configuration boundaries, and evidence from declared target/artifact contracts; remove fixed targets, best-effort claims, universal module/trait layout, numeric cfg thresholds, and named substitute tools. |
7 |
These ten reviewed clusters form the semantic duplication baseline. The initial 30% reduction target means eliminating at least three clusters; the final single-owner requirement should eliminate all competing normative ownership.
| ID | Competing locations | Intended owner |
|---|---|---|
| D001 | Layering in CODING-STANDARDS.md:59 and ARCHITECTURE-PATTERNS.md:32-98 |
Core dependency-direction rule; architecture catalog for patterns. |
| D002 | Backend/state policy in CODING-STANDARDS.md:95 and ARCHITECTURE-PATTERNS.md:125-163 |
Core authority rule; frontend profile for projection/reconciliation. |
| D003 | Validation in Coding, Architecture, Security, and Interop | Security owns trust boundaries; Interop specializes foreign/wire boundaries. |
| D004 | README schema in Documentation, Coding, Architecture, template, and checker | Documentation workflow plus one canonical template. |
| D005 | Slice/commit procedure in Plan, Commit, and ignored prompts | Planning/implementation workflow; prompts route only. |
| D006 | Verification levels in Testing, Tooling, Launcher, and Release | Verification workflow; profiles select applicable mechanisms. |
| D007 | Rust baseline commands in API, Tooling, and Release | Rust tooling profile. |
| D008 | Rust unsafe policy in API, Interop, Bindings, and Unsafe | Rust unsafe topic/profile. |
| D009 | Generic dependency/security/cross-platform rules repeated in Rust files | Generic topic owner; Rust profile only for Cargo/Rust mechanisms. |
| D010 | Binding architecture, framework recipes, packaging, and compatibility in one Rust file | Boundary profile, framework reference, and project-local policy separated. |
- Authoritative state and policy ownership with explicit projections.
- Dependency direction without mandating one universal layer count.
- Executable boundary contracts and validation once per trust boundary.
- Exact wire formats and checked conversions.
- Explicit foreign-resource ownership, lifetime, threading, and error contracts.
- Cancellation-aware, nonblocking task ownership and shutdown.
- Canonical filesystem containment.
- Bounded, non-sensitive diagnostics and typed unavailable/invalid outcomes.
- Accessible native interaction semantics.
- Reproducible dependency ownership and declared target/toolchain support.
- Full-path acceptance for cross-layer objectives.
- Atomic commits, staged-diff review, and no rewrite of shared history.
All findings are deferred to their named milestones because Milestone 0 cannot change normative standards. Critical findings must be addressed before the affected source can become canonical in Milestone 7.
The D001–D010 review
records current findings against 2cbe11e1; the original D table above remains
the historical baseline, not the current authority map. Review completion does
not imply Milestone 7 acceptance.
| ID | Severity | Evidence and affected owner | Disposition and required verification |
|---|---|---|---|
| M7-OWN-01 | High | Legacy Tooling claims automation authority and prescribes hook, parallelism, and staged-file defaults contrary to canonical workflow.tooling; report includes exact passages. |
Resolved by Engine publication 67d3e205 and exact accepted-source review. The additional Coding fragment finding below remains separate. |
| M7-OWN-02 | High | Legacy Rust Bindings permits framework derives in core and prescribes representation/test/workspace choices contrary to profile.language.rust.language-bindings and generic binding/verification owners. |
Resolved by Engine publication 67d3e205 and exact accepted-source review. The additional Coding fragment finding below remains separate. |
| M7-OWN-03 | Medium | Launcher retains legacy authority and install-output requirements; Architecture retains contract-freeze instructions and policy summaries. Other manifest entrypoints retain migration-pending prose or imperative headings. | Resolved by Engine publication 67d3e205 and exact accepted-source review. The additional Coding fragment finding below remains separate. |
| M7-OWN-04 | Medium | Rust Security's panic-policy link targets the removed RUST-API-STANDARDS.md#result-option-panic heading; source-index suite membership does not cover the entire legacy population, and markdown_links checks file existence rather than heading fragments. |
Resolved by Engine publication 67d3e205 and exact accepted-source review. The additional Coding fragment finding below remains separate. |
| M7-OWN-05 | Medium | The old final-closure procedure treats frozen corpus classifications and retired migration gates as current authority. | Resolved by the revised closure procedure in 19764768 and final source reconciliation: frozen evidence is preserved and historical dispositions are checked separately from current authority. |
| M7-OWN-06 | Low | Current tracked planning/implementation prompts repeat procedural instructions despite D005's original route-only aspiration; no conflicting slice/commit instruction was found in the reviewed prompts. | Defer to A5 concision review in Milestone 8. Compare retained instructions with their owners and justify necessary projections before claiming route-only or reduced interaction cost. |
| M7-OWN-07 | Medium | Full-population inspection found CODING-STANDARDS.md linking to Core's removed Code And Terminology Discipline heading. The current owner is topic.code-design; the stale link is unlisted, while seventeen other Coding routes are protected by the current inventory. |
Resolved by Engine publication ff6f3b21: Coding selects Code Design, preserves all seventeen declared routes, and passes the final 27-entrypoint link audit with unchanged inventory. |
The Engine capability in c99773d8 published nine corrections in 67d3e205.
The route-preservation extension in a94bbcd2 enabled the additional Coding
correction in ff6f3b21. Accepted reads match all ten previews. Seventeen other
entrypoints and all 70 canonical modules remain unchanged. Exactly four
required-destination checks were retargeted as admitted; unrelated assertions
and the route inventory are unchanged.
The initial population audit found the additional Coding anchor after checking 195 links and 24 fragments. The final audit checks 197 local inline links and 21 fragments with no unresolved targets. All 916 historical IDs reconcile, and the live Router has 54 canonical rules. These remain separate evidence claims.
The source closure report records Milestone 7 and A2 acceptance. M7-OWN-06 remains deferred to Milestone 8's A5 review; downstream effectiveness and complete semantic coverage are not claimed.