gnomonlearn
Docs/RFC-0036 conditional XOR proof repair

RFC-0036 conditional XOR proof repair

Versioned draft snapshot

RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.

Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.

This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.

This bounded repair replaces one opaque deferred obligation with the exact write-time XOR proposition already represented by RFC-0036 b25 and reviewed rfc0036_write_predicate_xor. The generated theorem identifier deriv_6a569d7c360a, authored statement, RDF identities, and external pin are unchanged. The proof projects the first two conjuncts of AX-008, whose k2 boundary-fidelity assumption and opaque presence predicates remain explicit. This is not backend validation or diagnostic conformance evidence.

Direct inspection of the same pinned framework prevented a misleading second repair: AX-011 distinguishes tagged EntityId constructors even when numeric rawId values coincide. The Lean control constructs default Resource and Statement values with equal raw IDs and distinct tagged IDs. This is an observation about the formal representation, not a deployed backend counterexample or a claim that the entire external axiom model is consistent. RFC-0036 b33’s citation review now records the mismatch with its shared-bigint exclusion requirement. Its generated obligation remains deferred; no numeric allocation axiom or identity policy was introduced. The related Foundation tagged-ID theorem has no currently matching citation review.

Terminal results

evidence.textproto uses the existing ValidationEvidence protobuf and binds current source bytes, exact argv, logs, exit codes, and the pinned external inputs. record.py records terminal observations; verify.py validates all bindings and the latest scoped outcomes, resolving historical inputs through the recorded Git commit or preserved snapshots.

GateBeforeFinal
Deterministic derivation emitter721 entries; 719 deferred; two candidates721 entries; 718 deferred; three candidates
Candidate semantic reviewsTwo reviewed matchesThree reviewed matches; zero unreviewed
Authored citation reviews722 links; 714 mismatches722 links; 715 mismatches; seven matches
Derivation inventoryExisting catalog722/722 emitted derivations accounted for
Coverage and proposition reuseExisting reportsRegenerated from source; drift checks pass
Pinned allow-deferred compilationNot repeated for baselineAll 721 generated theorems plus focused Lean controls compile
Authored citation release modeNot repeated for baselineExpected exit 1 for 715 mismatches

The first edit removed the fragment’s required trailing blank line. The emitter rejected it before Lean compilation. That malformed source, failed terminal logs, and the resulting stale-coverage observation are preserved. Restoring the source ending allowed regeneration and all eight final scoped checks to pass with their recorded expected exits. The earlier failures are retained as failures, not converted into acceptance evidence.

The controls compile inside check_derivations.py after the actual generated proof catalog, reusing its exact compiled external inputs. They separately project both XOR conjuncts and exhibit equal raw/tag-distinct IDs. The external sources are a detached local clone at 3725bd9f6d2711aa9bb179deea84f51e4424382a, restored under /Volumes/Workspace/gnomon-sh/.work/spec-framework-rfc0036-20261013; the original /Volumes/Workspace/fastverk/spec checkout remains unchanged at 883f40713a4c91235e5c260d32c0cbb4e021ffd3. The compiler is the pinned leanprover/lean4:v4.30.0-rc2 through elan. External formal source bytes are bound by hash and pin rather than copied into this repository.

The strict proof/release blockers, including 718 deferred bodies and 715 mismatched authored citations, remain. This work does not establish framework, Roma, database, compiler, or full normative release conformance. Generation and site artifact refresh at the final clean spec commit are separate steps.