RULES v10.67 - Architecture Conformance and No-Fork Gates
RULES v10.67 — Architecture Conformance and No-Fork Gates
RULES v10.67 adds a deterministic architecture-conformance path across three existing Runtime Rule owners without expanding the 19-rule runtime inventory.
Highlights
- Requires active-design and current architecture-path inspection before material route, service, client, transport, state, fallback, or authority mutation.
- Classifies incomplete architecture as
OBSERVE_ONLY, bounded defects inside the current authority asREPAIR_IN_PLACE, and additive or authority-changing topology behind exact approval. - Distinguishes existing-path regression, state/config drift, dormant or disconnected paths, contract mismatch, unresolved state, and verified capability gaps before new infrastructure is proposed.
- Requires functional proof through the selected design path plus negative architecture-fitness checks against unauthorized alternate owners, routes, clients, transports, registries, state keys, dual read/write, shadow paths, and automatic fallback.
- Treats a user or checked-design no-fork correction as an active constraint that retires incompatible tasks, plans, tests, and source branches.
- Adds Case 18 and matrix coverage M35–M40 with explicit rule-enforced, observed, and virtual evidence boundaries.
Runtime Scope
Exactly three Runtime Rules advance:
execution-and-goal-frame.md1.32 → 1.33action-safety.md1.5 → 1.6coding-discipline.md1.5 → 1.6
The other 16 Runtime Rules remain byte-and-mode identical to v10.66. Bash and PowerShell installers and fixtures retain the same ordered 19-file payload.
Verification
- Exact 25-path candidate scope: 20 modified and 5 created; no deletion, rename, symlink, submodule, binary, or tracked-mode drift.
- Focused architecture doctrine, Case 18, triad, metadata, link, mode, and protected-byte checks passed.
- Bash installer fixtures passed.
- PowerShell installer fixtures passed.
- Patch timeline suite passed: 32/32.
- Two-pass disposable installation passed with 19/19 byte parity, identical second pass, manifest convergence, and unrelated-sentinel preservation.
- Independent doctrine/security, runtime-payload, and release/no-drift reviews passed in their checked scopes.
Boundaries
This release does not add a Runtime Rule, change installer behavior, reconcile the protected dirty backup checkout, or promote project-specific architecture into portable doctrine. Published tags and Releases remain immutable; any later correction must use a later release.