compiler.schedule-end-to-end
and · drafted
Statement
No supplied market, region or representation. The one standing hypothesis is that the enforcer's trade map is primitive recursive, which is the definition of an effective enforcer and sits where the source's own process certificate sits.
Source
projects/normativity/CLAIMS.md, entry compiler.schedule-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.EnforcedCompiler.ProjectionSchedule.end_to_end_effective in lean/Workspace/Normativity/Contrib/EnforcedCompiler.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; its hypotheses are unread (ruling F1, 2026-10-23): the record's Source carries the signature verbatim, and a reader files the hypothesis leaves. Registry note: No supplied market, region or representation. The one standing hypothesis is that the enforcer's trade map is primitive recursive, which is the definition of an effective enforcer and sits where the source's own process certificate sits. The registry's answers_item is the priorities pointer to item 48 (ruling F2).
Bridge card
Connected to no informal claim yet: held by operative-force.
Declaration Workspace.Normativity.Contrib.EnforcedCompiler.ProjectionSchedule.end_to_end_effective in lean/Workspace/Normativity/Contrib/EnforcedCompiler.lean (record compiler.schedule-end-to-end.record)
Registry compiler.schedule-end-to-end: class lean-proved, status active, review ci-only, origin round 2026-08-18-projection-enforcement; bears on item 48
The statement of record of `compiler.schedule-end-to-end` formalizes the registered claim as the registry reads it: the projection schedule's effective market is a logical inductor.
Hypotheses: unread (the record's Source carries the signature; a reader files them).
Completeness (compiler.schedule-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, this leaf and the bridge, and its hypotheses are unread: the record's Source carries the signature verbatim and no hypothesis leaf is filed until a reader files one.
Author and human events
Author @smithy-verity; version 1; size M.
No human event has touched this node.
Edges
Above
- held by operative-force
Children
- part: compiler.schedule-end-to-end.record leaf/record
- part: compiler.schedule-end-to-end.bridge leaf/bridge
- part: compiler.schedule-end-to-end.complete leaf/completeness
Work pointers
- round 2026-08-18-projection-enforcement
- item 48
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"held by operative-force",
"hypotheses unread"
],
"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.