inductor.rebuttal-run
and · drafted
Statement
warrant_inductor at the same fixture with a quiet docket: the strength is operative until its consequent is refuted at date 8 and leaves by rebuttal (operative_before, withdrawn); every date is enforced; the bankroll is −72 (liability) with the applicability row among those the post-refutation slack world dominates. The same question (act on the conclusion or refrain) is posed at dates 4 and 9: the region flips (region_flips), no Excludes or Margins certificate exists at date 9 (no_certificate_after), and the gate's mass on acting goes from at least 24/25 to 0 at the realized market (same_question); the dropped service's mass 1/4 is in the residual (residual_restricted).
Source
projects/normativity/CLAIMS.md, entry inductor.rebuttal-run (class lean-proved, status active, origin round 2026-10-23-normative-inductor-consolidation; answers item 35). Documentation: verification: projects/normativity/rounds/2026-10-23-normative-inductor-consolidation/THEOREM.md; context: projects/normativity/rounds/2026-10-23-normative-inductor-consolidation/THEOREM_STORY.md. The signature of Workspace.Normativity.Contrib.WarrantInductorRebuttal.inductor in lean/Workspace/Normativity/Contrib/WarrantInductorRebuttal.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: warrant_inductor at the same fixture with a quiet docket: the strength is operative until its consequent is refuted at date 8 and leaves by rebuttal (operative_before, withdrawn); every date is enforced; the bankroll is −72 (liability) with the applicability row among those the post-refutation slack world dominates. The same question (act on the conclusion or refrain) is posed at dates 4 and 9: the region flips (region_flips), no Excludes or Margins certificate exists at date 9 (no_certificate_after), and the gate's mass on acting goes from at least 24/25 to 0 at the realized market (same_question); the dropped service's mass 1/4 is in the residual (residual_restricted). The registry's answers_item is the priorities pointer to item 35 (ruling F2).
Bridge card
Connected to no informal claim yet: held by normative-inductor.
Declaration Workspace.Normativity.Contrib.WarrantInductorRebuttal.inductor in lean/Workspace/Normativity/Contrib/WarrantInductorRebuttal.lean (record inductor.rebuttal-run.record)
Registry inductor.rebuttal-run: class lean-proved, status active, review ci-only, origin round 2026-10-23-normative-inductor-consolidation; bears on item 35
The statement of record of `inductor.rebuttal-run` formalizes the registered claim as the registry reads it: the warrant Normative Inductor, run on the rebuttal of a still-active strength (Scenario B).
Hypotheses: unread (the record's Source carries the signature; a reader files them).
Completeness (inductor.rebuttal-run.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 normative-inductor
Children
- part: inductor.rebuttal-run.record leaf/record
- part: inductor.rebuttal-run.bridge leaf/bridge
- part: inductor.rebuttal-run.complete leaf/completeness
Work pointers
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"held by normative-inductor",
"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.