Skip to content

Native SU32 record comparison versus source release ​

Reported Boolean reader classification; original release and physical signal remain unbound

This page summarizes the linked research at its stated verification level. It is not a new proof certificate or experimental confirmation.

Reported result ​

The generic native shared-reader join retains both actual operand derivations and their compatibility witness without assuming an equivalence of the operands. For the corrected Boolean record fragment, a complete four-record reader classifies the current carrier; the specified pointed, full-record-preserving filler is contractible. A native comparison exchanges the preparation/consumer presentations while retaining their endpoint derivations.

Controls and exclusions ​

Equal geometric output ports can conceal different current record values. Full-record reader preservation is the declared policy under which uniqueness is proved; it is not a universal physical reader law. Current-value uniqueness does not identify native producer programs, earlier packages, external histories or the original five-cell incidence paths. The source flags remain nativeSignalExecuted: false and originalIncidencePathsCompared: false.

First unresolved obligation ​

The original release audit still requires a source-admitted contextual release constructor on the complete signed preparation, including outputs, histories, occurrence maps, readers and continuations. Candidate record regroupings have nativeFiller: null; the inspected incidence walks do not provide parallel native port paths or the missing charged-cell internal transfers. Their deck discrepancy is uncomputed, not zero. Neither the generic join nor the classified Boolean fragment supplies a global physical assembly.

Verification and sources ​

The source reports safe Cubical classification, expected-failure controls and separate executable geometry/record audits. They were not rerun for publication. Native shared-reader join · Exact reader/classification scope · Release-source blocker.

Checker: research/strominger/checkers/check_su32_record_reader_classification.py; research/strominger/checkers/check_su32_release_source_audit.mjs

Publication provenance: Versioned source/checker and historical receipt identifiers. Metadata validation is not scientific replay.

Back to results