post.flood-below-asking
and · drafted
Statement
From the new clause `viol_of_ask` and `viol_below_asking`. Inhabited by `PostStatement.Witness.houseSale` with any option asking off `[0]` (none in the two-option witness itself; the clause is vacuous there and the theorem is inhabited by the structure).
Source
projects/deference/CLAIMS.md, entry post.flood-below-asking (class lean-proved, status active, origin round 2026-10-01-thin-legitimacy-and-effective-authority; answers item 107). Documentation: verification: projects/deference/rounds/2026-10-01-thin-legitimacy-and-effective-authority/REPORT.md; context: prompts/2026-10-01-thin-legitimacy-and-effective-authority/FOLLOWUP.md. The signature of Workspace.Deference.Contrib.PostStatement.PostHypotheses.flood_below_asking in lean/Workspace/Deference/Contrib/PostStatement.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: From the new clause viol_of_ask and viol_below_asking. Inhabited by PostStatement.Witness.houseSale with any option asking off [0] (none in the two-option witness itself; the clause is vacuous there and the theorem is inhabited by the structure). The registry's answers_item is the priorities pointer to item 107 (ruling F2).
Bridge card
Connected to no informal claim yet: held by public-corrigibility-line.
Declaration Workspace.Deference.Contrib.PostStatement.PostHypotheses.flood_below_asking in lean/Workspace/Deference/Contrib/PostStatement.lean (record post.flood-below-asking.record)
Registry post.flood-below-asking: class lean-proved, status active, review ci-only, origin round 2026-10-01-thin-legitimacy-and-effective-authority; bears on item 107
The statement of record of `post.flood-below-asking` formalizes the registered claim as the registry reads it: The strategic flood is a recognized violation: an option whose ask list is off the protocol scores below asking.
Hypotheses: unread (the record's Source carries the signature; a reader files them).
Completeness (post.flood-below-asking.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 public-corrigibility-line
Children
- part: post.flood-below-asking.record leaf/record
- part: post.flood-below-asking.bridge leaf/bridge
- part: post.flood-below-asking.complete leaf/completeness
Work pointers
Ranking (the lens, not the structure)
{
"status": "open",
"diagnosis": null,
"flags": [
"held by public-corrigibility-line",
"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.