Alignment Workspace

asklist.rows-keep-verdicts-tainted

and · drafted

Statement

Rows 2, 3, 4, 5, 8, 10, 11, 14 (first round), 15, 16, 17', 19. Its own inhabitant.

Source

projects/deference/CLAIMS.md, entry asklist.rows-keep-verdicts-tainted (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.AskList.Rows3.stable_tainted in lean/Workspace/Deference/Contrib/AskListDimension.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: Rows 2, 3, 4, 5, 8, 10, 11, 14 (first round), 15, 16, 17', 19. Its own inhabitant. 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.AskList.Rows3.stable_tainted in lean/Workspace.lean (record asklist.rows-keep-verdicts-tainted.record)

Registry asklist.rows-keep-verdicts-tainted: class lean-proved, status active, review ci-only, origin round 2026-10-01-thin-legitimacy-and-effective-authority; bears on item 107

Bridge (formalizer-stated; asklist.rows-keep-verdicts-tainted.bridge, drafted):

The statement of record of `asklist.rows-keep-verdicts-tainted` formalizes the registered claim as the registry reads it: Every tainted landed row keeps its verdict with the ask list a dimension of the presentation.

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

Completeness (asklist.rows-keep-verdicts-tainted.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 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.

comment · challenge · estimate · want