Modal Claim Table¶
Template — instantiates Necessity-Possibility-Contingency Framing
A structured table for claims, actions, modal status, assumptions, scope, defeaters, and action implications.
Modal Claim Table takes claims and recommended actions one at a time and gives each its own row: a cell for its modal status, a cell for the scope in which that status holds, a cell for how confident the classification is, and a cell for what the classification obliges you to do. Its defining move is the last cell — coupling each claim's modal force to an action implication, so that "X holds necessarily" and "Y is merely possible" land in different action columns even when the surrounding prose blurs them. Unlike its table-shaped siblings it never lays out alternative worlds and never sorts constraints by kind; it is a per-claim ledger that says what force each claim has and what follows from it.
Example¶
A structural review board is signing off on the design of a pedestrian bridge before it goes to fabrication. The design report reads confidently — "the primary girder holds under the design load," "the deck's natural frequency sits well clear of the walking band," "settlement stays within tolerance," "the salt-exposed deck connectors are fine for the service life" — so a reviewer drops each load-bearing sentence into a Modal Claim Table, one per row. Each row gets a modal-status cell (necessary / likely / possible / impossible), a scope cell recording the assumption under which that status holds, a confidence cell (how well the classification is supported), and an action-implication cell (proceed, add a check, or hold for data).
Filled in, the rows separate cleanly. The girder necessarily holds — but the scope cell pins that necessity to loads at or below the specified design load, with the stated safety factor, because the closed-form calculation and the finite-element run agree only inside that envelope; confidence high, action proceed. Resonant pedestrian-induced vibration is impossible — scoped to the as-designed deck stiffness, confidence high, action proceed. Corrosion failure of the connectors is possible — but the confidence cell reads low, the scope reads over a fifty-year horizon under de-icing-salt exposure, and the action is a modest coating spec plus a scheduled inspection, not a redesign, precisely because a low-confidence possibility is not an established risk. The row that changes the outcome is settlement stays within tolerance: written in the report as a flat assertion, the table forces it to likely, contingent on the borehole samples representing the whole site, moderate confidence. Re-deriving that row's action cell turns a silent pass into an order for confirmatory boreholes before the pour. What the board signs off on now carries each claim's modal force and the confidence behind it, not merely the report's prose.
How it works¶
Rows are claims or actions; the four columns are the status vocabulary, the scope boundary, the confidence marker, and the action implication. The distinguishing step is that last column: a translation rule maps each (status, scope, confidence) triple onto what may be relied on or built upon, so a low-confidence possibility cannot masquerade as an established necessity, and a well-supported impossibility cannot be softened into a mere maybe by hedged wording. The table classifies and translates; it does not test — a filled status cell records a claim about modal force, not a proof of it.
Tuning parameters¶
- Status vocabulary granularity — coarse (certain / possible / impossible) versus fine (necessary / contingent / likely / impossible / undecidable). Finer catches more confusions but slows filling and invites false precision.
- Scope resolution — one global scope for the whole table versus a scope cell per row. Per-row scope catches jurisdiction and time-window drift but multiplies the cells to maintain.
- Confidence scale — binary (asserted / tentative) versus graded. Graded surfaces the weak claims but tempts spurious precision.
- Action bindingness — how directly the action cell is allowed to harden a status into an enforced mandate versus a suggestion.
- Row admission — whether every clause earns a row or only decision-bearing claims do; loose admission buries the load-bearing rows.
When it helps, and when it misleads¶
Its strength is making modal-language drift visible and blocking the modal scope fallacy[n1] — the slide from "necessarily, if the load stays within spec then the girder holds" to "the girder necessarily holds." Laid out in columns, the scope of the "necessarily" is fixed and cannot travel.
Its failure mode is that the table's tidiness lends every filled cell false authority: a status asserted in a cell is not a status that survived challenge, and a Claim Table with no adversary quietly certifies its own guesses. The classic misuse is to fill the status column straight from the document's own wording, so the grid merely launders the text's confusions into rows. The guarding discipline is to treat each status cell as a hypothesis to be attacked — an informal challenge pass, or a full Necessity-Possibility Red Team — and to re-derive the action cells whenever scope or evidence changes.
How it implements the components¶
modal_status_taxonomy— supplies the controlled vocabulary of the status column, so every row is classified from the same fixed set.modal_scope_boundary— the scope column bounds where each row's status holds, keeping a within-scope necessity from being read as universal.decision_translation_rule— the action-implication column maps status to what to do, preserving the modal caveat into the review sign-off.modal_confidence_marker— the confidence column tags how strongly each classification is held, separating an asserted status from a tentative one.
It does not build or compare cases — possible_world_or_case_set and contingency_dependency_map belong to Possible-World Case Matrix, which arrays whole worlds where the Claim Table only lists claims; nor does it sort constraints by kind (accessibility_relation_or_constraint_rule, assumption_relaxation_ladder), which is Design Constraint-Relaxation Table's job. And it does not register the conditions, exceptions, and derogations under which a deontic status holds: the normative force of legally-governed actions — obligatory, permitted, or prohibited, condition_and_exception_register — is the province of its nearest twin, Legal Obligation-Permission Matrix, whereas the Claim Table grades alethic and epistemic force (necessary, possible, likely, impossible) with a confidence marker and a scope boundary.
Related¶
- Instantiates: Necessity-Possibility-Contingency Framing — the Claim Table is the per-claim ledger that classifies modal force and carries it into action.
- Sibling mechanisms: Possible-World Case Matrix · Counterfactual Minimal-Change Checklist · Assumption Lock-and-Relax Workshop · Necessity-Possibility Red Team · Legal Obligation-Permission Matrix · Design Constraint-Relaxation Table · Modal Language Review Protocol
Editorial Notes¶
Form Classification¶
Form family: Representation, Specification & Plan
Rationale: Modal Claim Table operates as a non-executable information artifact that externalizes static or prospective structure because it a structured table for claims, actions, modal status, assumptions, scope, defeaters, and action implications.
Independent corroboration: The frozen evidence defines Modal Claim Table as 'A structured table for claims, actions, modal status, assumptions, scope, defeaters, and action implications', so its operative form is Representation, Specification & Plan.
Nearest alternative: Interface, Display & Cue — The table may be consulted at decision time, but its primary form is a static modal-status representation rather than an interactive surface.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Philosophy
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Classifying propositions as necessary, possible, contingent, or impossible originates in modal logic and philosophical analysis.
Related originating lineages:
- Law & Governance — Legal drafting developed consequential distinctions among obligation, permission, discretion, and prohibition.
- Linguistics & Semiotics — Linguistic modality materially shapes how modal force is expressed and scoped in ordinary language.
- Rhetoric — Argument mapping and claim tables shape the practical review artifact.
Review resolution: Both independent reviews agree on primary origin philosophy; reconciliation resolves secondary fields (reported_ambiguity, alternate_origin_disagreement, domain_reach_disagreement). Alternate origins retained (law_governance, rhetoric, linguistics_semiotics) are the union of reviewer-supported formative lineages with explicit rationales, not a list of later application domains. Present-day breadth is represented separately as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis records the historical relationship among lineages. Confidence is conservatively reconciled to medium, and encyclopedia_synthesis=true preserves either reviewer's finding that the encyclopedia generalized the mechanism.
Attribution caveat: The table itself is a synthetic operationalization of older modal distinctions. The table is an encyclopedia synthesis that turns modal analysis into a reusable decision artifact.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; medium confidence.
Notes¶
A filled status cell is a claim, not a certificate. The table's real value is exposing modal force to challenge, which makes its worst use treating it as the last word rather than the first draft — a finished-looking grid that no one ever red-teamed.
[n1] The modal scope fallacy is the confusion between necessarily (if P then Q) and (if P then necessarily Q) — a true claim about the necessity of a conditional misread as a claim about the necessity of its consequent. Fixing the scope of the "necessarily" is exactly what the table's scope column forces. ↩