Standing-Condition Preflight¶
Preflight checklist — instantiates Constitutive Act Governance
Runs through scope, procedure, quorum, timing, and evidence before an act is treated as valid, catching accidental or premature constitution before the state goes live.
Standing-Condition Preflight verifies the antecedent conditions an act must satisfy before it is allowed to constitute anything. Its defining move is to check the world against a list of preconditions — proper scope, correct procedure, sufficient quorum or threshold, valid timing and notice, adequate evidence — and to confirm each holds for the specific state about to be made, before the act is relied upon. It is not a check on the performer's authority, and it is not a check on the act's wording; it is a check on the surrounding conditions. An impeccably authorized body, using flawless ceremonial language, still constitutes nothing if the meeting was inquorate or the item was never noticed. Preflight is what catches exactly that: the quiet, common failure where every step looks right but a precondition was silently unmet.
Example¶
A company's board is about to pass a resolution approving a merger — a constitutive act that will bind the company. Standing-Condition Preflight is the check the corporate secretary runs before the vote is treated as a valid resolution. Was proper notice of the meeting given within the required window? Is a quorum of directors present, in person or by valid proxy? Is the merger actually on the noticed agenda, or is it being slipped in out of scope? Have interested directors recused, and is the required independent valuation in hand as evidence? Only if every precondition holds for this resolution is the vote's outcome a valid approval; miss one — no quorum, stale notice, an off-agenda item — and the "resolution" is a nullity even though every director voted yes and the minutes read cleanly. The output is a pass/fail on the antecedent conditions for the exact state being constituted, run before anyone acts on it.
How it works¶
Preflight starts from the state class about to be constituted and enumerates the standing conditions that class requires: procedure, scope and jurisdiction, quorum or voting threshold, timing and notice window, evidentiary bar, and required sequence. It then tests each against the current situation and returns which conditions are met, which are not, and whether the named state may proceed. The distinguishing discipline is that it is scoped to the specific state — it does not ask "is a board meeting valid in general" but "is this merger approval validly conditioned right now." It checks conditions, not the actor (that is the authority gate) and not the act's form (that is the binding protocol), and it runs before constitution, not after — the opposite end of the lifecycle from monitoring.
Tuning parameters¶
- Condition-set completeness — minimal (quorum only) versus exhaustive (every procedural predicate). Exhaustive catches more nullities but slows every act and can breed checklist fatigue.
- Timing of the check — long-lead (days ahead) versus at-the-moment. At-the-moment catches last-minute changes — a director leaving and breaking quorum — but leaves no time to cure the defect.
- Evidence bar — how strong the proof that a condition holds must be. A higher bar yields fewer false passes but more friction on every act.
- Scope strictness — how tightly the act must match its noticed or authorized scope. Strict scope stops creep (an unrelated item riding along) but may reject reasonable, closely-related extensions.
- Curability — whether an unmet condition blocks outright or can be cured (adjourn to reach quorum, re-notice) before the act proceeds.
When it helps, and when it misleads¶
Its strength is that it prevents the failure that is easiest to miss precisely because everyone with authority is in the room: a duly-empowered body accidentally constituting, or failing to constitute, a state because a precondition was unmet — the off-agenda vote, the inquorate meeting, the expired notice. It makes the invisible preconditions explicit and testable, functioning as the operational check on what contract law calls a condition precedent: a condition that must be satisfied before the act can take effect.[n1]
Its failure mode is checklist theater — ticking each condition as "met" without testing whether it truly holds. A director marked "present" who is asleep or disqualified still counts for quorum on paper; a notice "sent" that no one received still reads as given. The false assurance is worse than an open question, because it certifies validity that is not there. The classic misuse is running the preflight as a pretext — assembling a "all conditions met" record to legitimize a foreordained outcome. The discipline that guards against this is to derive the condition set from the actual validity rules rather than habit, to test substance rather than presence, and to keep the preflight in series with the authority gate so that "conditions met" never quietly substitutes for "the right actor made it."
How it implements the components¶
standing_conditions— its core: it enumerates and verifies the scope, procedure, quorum, timing, and evidence conditions the state requires before the act counts as valid.named_state_or_status— it runs those checks against the specific state to be constituted (this merger approval, this certification), so the preflight is scoped to what is actually being made operative rather than to the ritual in general.
It does not verify the performer's standing — an inquorate-but-authorized board and a quorate-but-unauthorized one are different failures, and the actor check is authorized_performer_or_body, its nearest twin Authority Gate Check. Nor does it fix the act's wording or ceremony (constitutive_act, ceremonial_form, Performative Formula and Context Binding) — right conditions but a botched formula is that sibling's concern, right formula but unmet conditions is this page's.
Related¶
- Instantiates: Constitutive Act Governance — preflight supplies the antecedent-conditions check the pattern needs so a state is not treated as valid before its preconditions hold.
- Sibling mechanisms: Authority Gate Check · Performative Formula and Context Binding · Constitutive Recording · Revocation or Contestation Protocol · Performative Feedback Monitoring · Uptake Confirmation
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Standing-Condition Preflight operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it runs through scope, procedure, quorum, timing, and evidence before an act is treated as valid, catching accidental or premature constitution before the state goes live.
Independent corroboration: The frozen evidence defines Standing-Condition Preflight as 'Runs through scope, procedure, quorum, timing, and evidence before an act is treated as valid, catching accidental or premature constitution before the state goes live', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Decision, Gate & Allocation — Standing-Condition Preflight includes features of a case-specific gate, selection, routing, prioritization, or resource disposition, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Law & Governance
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Universal
Rationale: Checking quorum, scope, timing, and evidence before validity is procedural governance.
Related originating lineages:
- Organizational & Management Science — Preflight checklists prevent premature activation.
- Public Administration & Policy — Public administration, policy implementation, and program oversight supplies a parallel or contributing lineage for the mechanism's defining operation: runs through scope, procedure, quorum, timing, and evidence before an act is treated as valid, catching accidental or premature constitution before the state goes live.
Review resolution: The blind reviewers agree that law_governance is the primary origin and differ only on alternate origin disagreement, origin mode disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain cross_disciplinary_synthesis because the combined evidence shows material contributions from several lineages. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] In contract and statutory law, a condition precedent is a fact or event that must occur before an obligation, right, or act takes effect. Standing-Condition Preflight is the operational check that every such precondition actually holds before a constitutive act is treated as valid. ↩