authority.revocation-default
and · drafted
Statement
Re-pointed by the follow-up (prompts/2026-10-01-thin-legitimacy-and-effective-authority/FOLLOWUP.md, Part 4) from `atrophy_counted_by_default`, arithmetic on four numbers that did not use the module. `Dep.revocationJ` is the entry of `AuthAlloc`; `Dep.depI` the interaction whose correction *revoke at level d* costs d; `revocation_short_iff`, `build_caused_iff`, `build_entrenches` (the crossing is the landed `EntrenchAt`).
Source
projects/deference/CLAIMS.md, entry authority.revocation-default (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/REPORT.md. The signature of Workspace.Deference.Contrib.EffectiveAuthority.Dep.atrophy_on_module in lean/Workspace/Deference/Contrib/EffectiveAuthority.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 filed as leaves, its bridge names the gap between the claim and the declaration, and it is one of the twelve conjuncts of the informal claim effective-authority-layer (the effective-authority layer), a shared-claim root of authorship-and-transparency and public-corrigibility-line, rather than a node a frame holds. The registry's answers_item is the priorities pointer to item 107 (ruling F2).
Bridge card
A conjunct of the informal claim effective-authority-layer: Effective authority is modelled with a queue that cannot be bypassed, caused and flood-caused shortfalls, a comprehension shortfall, approval discounts and a revocation default, with sincerity conditions on which verdicts count.
Declaration Workspace.Deference.Contrib.EffectiveAuthority.Dep.atrophy_on_module in lean/Workspace/Deference/Contrib/EffectiveAuthority.lean (record authority.revocation-default.record)
Registry authority.revocation-default: class lean-proved, status active, review ci-only, origin round 2026-10-01-thin-legitimacy-and-effective-authority; bears on item 107
The claim asserts that revocation is protected by default: a dependency built through delegated work raises the cost of taking the matter back, and past the bound that is a shortfall the agent caused without her having reserved anything. The declaration certifies it on the atrophy fixture: at depth one the matter is not short, at depth two it is, the step from one to two is a caused shortfall and an entrenchment of the revocation entry, and the step from zero to one is not. The gap: one fixture with bound one and four numbers; the default entry's presence in every allocation is a modelling decision (ruling P3), not what this record certifies.
Hypotheses, read:
- authority.revocation-default.h-fixture definitional: The dependency fixture: the atrophy model on the authority module with the revocation entry at bound one and the build policy, over any environment signal.
The binder `z : ℕ → Unit` and the fixture definitions `depI`, `revocationJ`, `depCost`, `buildPolicy`. Definitional: no hypothesis beyond the fixture; it is its own inhabitant.
Completeness (authority.revocation-default.complete): No premise beyond the signature's binders enters the declaration; the kernel checks it as stated. The result is the record, the hypothesis leaf filed by reading, the bridge and this leaf.
What remains (effective-authority-layer.improvable)
The effective-authority layer, in which authority is exercised through a protocol that cannot be bypassed, with caused and flood-caused shortfalls, a comprehension shortfall, approval discounts and a revocation default, and sincerity conditions on which verdicts count, can be improved until it reflects a principal whose later judgment counts as her own because the agent asks through her protocol, keeps her attention budget and takes no authority back from her well.
- item-131: The ask-list deviation is a dimension of the counted trace, so that asking off the declared protocol is tainted by the record's own counting rather than by a self-checkable clause beside it. — this is item 131
- route-authority-blackwell-converse: What item 107 leaves open behind the post is closed: Blackwell's converse for the thin specification's value clause, the loss of correctness, and the remaining items of the post's backing. — item 107
- route-authority-attention-physics: The attention budget is realized in a physics rather than given as a cost table, so that a flood shortfall and a comprehension shortfall are events the market prices, as the shortfall security prices them. — item 101
- effective-authority-layer.residual (residual): A refinement of the effective-authority layer that none of the other routes describes reflects a principal whose later judgment counts as her own because the agent asks through her protocol, keeps her attention budget and takes no authority back from her.
Author and human events
Author @smithy-verity; version 1; size M.
No human event has touched this node.
Edges
Above
- part of effective-authority-layer
Children
- part: authority.revocation-default.record leaf/record
- part: authority.revocation-default.bridge leaf/bridge
- part: authority.revocation-default.complete leaf/completeness
- part: authority.revocation-default.h-fixture leaf/hypothesis
Work pointers
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.