compiler.deductive-end-to-end
and · drafted
Statement
The source's criterion over D together with per-date conformance at a computable tolerance schedule, assuming nothing about the deductive process beyond the source's own certificate plus propositional satisfiability of each stage. Computable, not efficient: the generator is doubly exponential in the fragment dimension.
Source
projects/normativity/CLAIMS.md, entry compiler.deductive-end-to-end (class lean-proved, status active, origin round 2026-08-18-projection-enforcement; answers item 48). Documentation: verification: projects/normativity/notes/GENERALIZED_LI_PAPER_HANDOFF.md; context: projects/normativity/rounds/2026-08-18-projection-enforcement/FINAL_FORMALIZATION_STATUS.md. The signature of Workspace.Normativity.Contrib.DeductiveEffective.deductive_end_to_end in lean/Workspace/Normativity/Contrib/DeductiveEffective.lean.
Notes
Filed by the map-as-canonical round (prompts/2026-10-22-map-as-canonical) from the registry entry and the declaration's signature. The site-vertical-slice round (projects/enabling/rounds/2026-10-24-site-vertical-slice) connected it by reading: its hypotheses are the four leaves (two schedules, the source's certificate, satisfiable stages), its bridge names the gap between the claim and the declaration, and it is a conjunct of the informal claim traderized-finite-date-conformance, a shared-claim root of operative-force, rather than a node that frame holds. Registry note: The source's criterion over D together with per-date conformance at a computable tolerance schedule, assuming nothing about the deductive process beyond the source's own certificate plus propositional satisfiability of each stage. Computable, not efficient: the generator is doubly exponential in the fragment dimension. The registry's answers_item is the priorities pointer to item 48 (ruling F2).
Bridge card
A conjunct of the informal claim traderized-finite-date-conformance: A constraint on prices compiles to a legal trading strategy inside the market recursion, giving per-date conformance within a schedule while preserving the logical induction criterion.
Declaration Workspace.Normativity.Contrib.DeductiveEffective.deductive_end_to_end in lean/Workspace/Normativity/Contrib/DeductiveEffective.lean (record compiler.deductive-end-to-end.record)
Registry compiler.deductive-end-to-end: class lean-proved, status active, review ci-only, origin round 2026-08-18-projection-enforcement; bears on item 48
The claim asserts that a constraint on prices compiles to a legal trading strategy inside the market recursion, giving per-date conformance within a schedule while preserving the logical induction criterion. The declaration certifies this for a deductive process: the market compiled from the deductive projection schedule is a logical inductor over the process, and at every date its distance from the day's representation on the fragment is within that date's tolerance. The gaps: the claim speaks of constraints on prices in general, and the declaration of the deductive region alone (the constraint-schedule forms are the companion declarations end_to_end_effective and end_to_end_of_constraints_effective, which this record does not certify); the claim leaves the schedules free, and the declaration fixes the fragment and tolerance schedules as primitive recursive data; preserving the criterion means the pinned source's own IsLogicalInductor over the deductive process, under the source's certificate, not an absolute criterion; and the construction is computable, not efficient, the generator being doubly exponential in the fragment dimension, which the claim does not say.
Hypotheses, read:
- compiler.deductive-end-to-end.h-fragment-schedule definitional: The fragment schedule assigns each date a duplicate-free list of sentences and is primitive recursive.
The binders `coords`, `nodup` and `hcoords`: the schedule object's own data and its computability, read as one hypothesis. Definitional: it says what a fragment schedule is, and asks nothing of the deductive process. - compiler.deductive-end-to-end.h-tolerance-schedule definitional: The tolerance schedule assigns each date a strictly positive rational and is primitive recursive.
The binders `tol`, `tol_pos` and `htol`, read as one hypothesis. Definitional: the schedule's own data; any computable positive schedule serves. - compiler.deductive-end-to-end.h-process-certificate definitional: The deductive process carries the pinned source's own computability certificate: a program that eventually emits each stage.
The binder `process : DeductiveProcessComputation DP`. Definitional: the source's definition of a deductive process (a computably enumerable stage sequence), the hypothesis the source's own theorem carries, and no restriction added by this declaration; the file's header says no hypothesis about the process beyond the source's own is needed. - compiler.deductive-end-to-end.h-stages-satisfiable open: Every stage of the deductive process is propositionally satisfiable: some propositionally consistent world agrees with the stage.
The binder `hsat`. Open: a consistency assumption on the process that the declaration consumes and does not derive; the source's deductive processes are consistent by stipulation, and a reader granting the claim for a given process must grant this of it. It does not restate the conclusion.
Completeness (compiler.deductive-end-to-end.complete): No premise beyond the signature's binders enters the declaration; the kernel checks it as stated. The result is the record, the four hypothesis leaves filed by reading (the fragment schedule, the tolerance schedule, the pinned source's computability certificate on the process, and the satisfiability of every stage), the bridge and this leaf; the premise list is the signature's, grouped as a reader states it.
What remains (traderized-finite-date-conformance.improvable)
The compiled per-date conformance, in which a constraint on prices compiles to a legal trading strategy that conforms within a schedule while preserving the criterion, can be improved until it reflects a logical inductor whose prices answer a normative seed's constraints under a finite liability account well.
- item-129: The compiled enforcer's per-day gap bets are bounded below by a schedule while the criterion is preserved, so that the conformance the compiler gives is a trust bound the deference line can read. — this is item 129
- route-conformance-credal-constraint: Normative statics produce a credal constraint on prices rather than only a price demand, so that what the compiler enforces is the seed's own constraint. — item 39
- route-conformance-efficient-rows: An efficiently presentable sufficient row family for coherence replaces the doubly exponential generator the declaration's construction uses. — item 42
- route-conformance-exact-and-safe: A compiler that is both exact and conformance-preserving exists, or a proof says there is none, so that conformance within a schedule is not bought by inexactness. — item 43
- traderized-finite-date-conformance.residual (residual): A refinement of the compiled conformance that none of the other routes describes reflects a logical inductor whose prices answer a normative seed's constraints under a finite liability account.
Author and human events
Author @smithy-verity; version 1; size M.
No human event has touched this node.
Edges
Above
Children
- part: compiler.deductive-end-to-end.record leaf/record
- part: compiler.deductive-end-to-end.bridge leaf/bridge
- part: compiler.deductive-end-to-end.complete leaf/completeness
- part: compiler.deductive-end-to-end.h-fragment-schedule leaf/hypothesis
- part: compiler.deductive-end-to-end.h-tolerance-schedule leaf/hypothesis
- part: compiler.deductive-end-to-end.h-process-certificate leaf/hypothesis
- part: compiler.deductive-end-to-end.h-stages-satisfiable leaf/hypothesis
Work pointers
- round 2026-08-18-projection-enforcement
- item 48
- round 2026-10-24-site-vertical-slice
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [],
"V": {
"V_prior": null,
"display": "2",
"headline": 2,
"ref": 2,
"valid": 2,
"weaker": "both"
},
"belief": null,
"draft": "ai"
}Say something about it
Each verb opens a prefilled issue; a round files what lands as the ledger event it is.