Alignment Workspace

legitimacy.answerable

and · drafted

Statement

A legitimate segment yields Answerability Conservation from Integrity and Robust Openness (coverage of every live concern and the protected party's standing on every applicable one, actual branch and each counterfactual) at both endpoints, and by construction at every state between. Diachronic Answerability is derived, not a third conjunct.

Source

projects/normativity/CLAIMS.md, entry legitimacy.answerable (class lean-proved, status superseded, origin round 2026-09-07-final-pressure-pass; answers item 78). Documentation: verification: projects/normativity/legitimacy/rounds/2026-09-07-final-pressure-pass/THEOREMS.md; context: projects/normativity/legitimacy/rounds/2026-09-07-final-pressure-pass/READINESS.md. The signature of Workspace.Normativity.Contrib.LegitimateEvolution.LegitimateSegment.answerable in lean/Workspace/Normativity/Contrib/OpenIntegrityEvolution.lean (an alias declared in lean/Workspace/Normativity/Contrib/LegitimateEvolution.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: A legitimate segment yields Answerability Conservation from Integrity and Robust Openness (coverage of every live concern and the protected party's standing on every applicable one, actual branch and each counterfactual) at both endpoints, and by construction at every state between. Diachronic Answerability is derived, not a third conjunct. Superseded 2026-09-25 by open-integrity.answerable; the declaration name is kept resolving by a deprecated alias for one release. The registry's answers_item is the priorities pointer to item 78 (ruling F2).

Bridge card

Connected to no informal claim yet: held by integrity-and-record.

Declaration Workspace.Normativity.Contrib.LegitimateEvolution.LegitimateSegment.answerable in lean/Workspace/Normativity/Contrib/LegitimateEvolution.lean (record legitimacy.answerable.record)

Registry legitimacy.answerable: class lean-proved, status superseded, review ci-only, origin round 2026-09-07-final-pressure-pass; bears on item 78

Bridge (formalizer-stated; legitimacy.answerable.bridge, drafted):

The statement of record of `legitimacy.answerable` formalizes the registered claim as the registry reads it: Diachronic Answerability, decomposed.

Hypotheses: unread (the record's Source carries the signature; a reader files them).

Completeness (legitimacy.answerable.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

Children

Work pointers

Ranking (the lens, not the structure)
{
 "status": "open",
 "diagnosis": null,
 "flags": [
  "held by integrity-and-record",
  "hypotheses unread",
  "superseded by open-integrity.answerable"
 ],
 "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.

comment · challenge · estimate · want