Type: Node / Normative Specification
Placement note: Procedure belongs in Division VII because it specifies how institutional activity is governed. Process supplies the descriptive temporal unfolding. Procedure supplies a contestable normative specification that may apply to such an unfolding when a governing basis gives it force.
Working Definition: A procedure is a normative specification for a class of processes within a stated scope. It identifies roles or participants, governing conditions, recognized outputs, and transitions that are permitted, required, or prohibited. A Procedure does not itself unfold. It does not authorize its own application. It does not prove that an actual Process conformed to it.
Function in the Grammar: Procedure makes institutional conduct assessable as governed form. It identifies who may participate, how a matter may enter, what transitions are permitted or required, what conditions attach to them, what outputs may be recognized, and what records must be produced. This allows an actual Process to be compared with a disclosed specification without substituting the specification for what occurred.
A Procedure may be proposed, adopted, amended, suspended, or superseded. Those are further properties and relations. The specification can exist before it governs any Process, and a Process can unfold without a Procedure. When a Constitution, Rule, authorized Decision, or other governing basis makes a Procedure applicable, the actual unfolding may conform fully, conform partially, deviate, or fail to reach any recognized output.
Procedure constrains an institutional possibility space, not causal possibility as such. It can state what Agents may, must, or must not do and what an institution will recognize as valid. It cannot prevent unauthorized conduct from occurring. Some Procedures are regulative, guiding activity that could happen without them. Others are constitutive, helping determine what counts as a vote, Appeal, appointment, publication, or Amendment within an institution.
Formal Grammar Representation
<procedure> ::= Procedure(
id: <procedure-id>,
scope: <scope>,
roles: <role-set>,
entry_conditions: <condition-set>,
transitions: <transition-set>,
transition_conditions: <condition-set>,
outputs: <output-set>,
record_requirements: <record-set>,
version: <version-reference>
)
<role-set> ::= identified Roles, participant classes, or explicitly open participation
<transition> ::= Transition(
from: <procedure-state>,
to: <procedure-state>,
performed_by: <role-or-participant>,
modality: permitted | required | prohibited,
conditions: <condition-set>
)
<output-set> ::= the results, statuses, artifacts, or other products
the Procedure specifies as recognizable under stated conditions
Procedure(pi) is well-formed when:
scope(pi) = S, where S states the class of matters or Processes addressed
roles(pi) = R, where participation and role requirements are stated
entry_conditions(pi) = C_in, where invocation conditions are stated
transitions(pi) = X, where governed changes and their modalities are stated
transition_conditions(pi) = C_x, where relevant deadlines, thresholds,
sequencing constraints, and decision points are stated
outputs(pi) = O, where recognized outputs or terminal conditions are stated
record_requirements(pi) = K, where required artifacts and receipts are stated
version(pi) = v, where the applicable specification can be identified
Semantic Constraints
The expression Procedure(pi, S, R, C_in, X, C_x, O, K, v) is well-formed when its governed form can be inspected. The syntax does not establish that the Procedure was authorized, that it applies to a particular Process, that participants had meaningful access, that stated conditions were satisfied, that an output is wise or just, or that compliance establishes Legitimacy.
A Procedure does not authorize or apply itself. GOVERNS(pi, p, under: g) requires a disclosed governing basis with the relevant Authority, Jurisdiction, scope, and effective time. A well-designed Procedure may be inapplicable to a matter. A defective Procedure may be validly adopted. An unauthorized Procedure may be followed in practice without acquiring institutional force.
Conformance is a relation between an actual Process and an applicable Procedure under a stated scope and version. It is not inferred from the existence of required Records, from the claimed output, or from a participant's assertion. Whether conformance holds may require Evidence, Interpretation, and Judgment.
Deviation is not limited to a forbidden Event. It may consist of an omitted notice, an unauthorized participant, an invalid transition, a missed deadline, an unmet condition, a defective output, or a missing Record. The deviation locus must therefore remain open rather than being typed only as an occurrence.
Procedural validity is bounded. Following a Procedure may establish that specified formal conditions were met. It does not establish truth, substantive justice, adequate deliberation, correct Judgment, or justified authority. Conversely, a desirable outcome does not cure a required procedural defect unless an authorized Exception or corrective rule supplies that effect.
Procedure does not impose a universal workflow on the encyclopedia. Institutions may compose different Procedures from shared concepts, omit transitions another institution requires, permit branching or iteration, and recognize different outputs.
Formal Pattern
Procedure(pi, scope: S, roles: R, entry: C_in,
transitions: X, conditions: C_x, outputs: O,
records: K, version: v)
GOVERNS(Procedure(pi), Process(p), under: GoverningBasis(g),
within: S, at: t)
INVOKES(Act(alpha), Procedure(pi), for: Matter(m), at: t)
PARTICIPATES_AS(Agent(a), Role(r), in: Process(p), under: Procedure(pi))
CONFORMS_TO(Process(p), Procedure(pi), within: S, version: v)
DEVIATES_FROM(Process(p), Procedure(pi), at: Locus(l), kind: k)
SPECIFIES_OUTPUT(Procedure(pi), Output(o), when: C_o)
REQUIRES_RECORD(Procedure(pi), Record(r), for: Transition(x))
GOVERNS, INVOKES, CONFORMS_TO, DEVIATES_FROM, and SPECIFIES_OUTPUT are further relations, not consequences of Procedure(pi) alone. CONFORMS_TO and DEVIATES_FROM should be treated as attributable, contestable assessments when their application is disputed.
Core Relations
| Relation | Notes |
|---|---|
| Process is governed or assessed | Procedure specifies a normative form against which an actual Process may be assessed. The two are related by governance and possible conformance, not subtype inheritance. |
| Constitution and Rule may ground | A Constitution or Rule may adopt, require, delimit, or authorize a Procedure. The Procedure does not manufacture its own governing force. |
| Role and Agent participate | Procedure may assign transitions, notices, decisions, or review rights to Roles or participant classes. Actual Agents participate through attributable positions and acts. |
| Authority enables | Authority determines who may adopt, invoke, administer, waive, or alter a Procedure and who may perform its reserved transitions. |
| Jurisdiction bounds | A Procedure may be valid yet unavailable for a matter outside the Forum's or institution's Jurisdiction. |
| Act invokes or advances | Recognized Acts may invoke a Procedure or perform governed transitions. An Action outside the Procedure may still occur without having the claimed institutional effect. |
| Decision may be governed | A Procedure may specify notice, quorum, voting, reasons, review, or other conditions for an InstitutionalDecision. It does not decide the matter itself. |
| Validity assesses | Procedural validity asks whether applicable criteria were satisfied. It remains distinct from truth, wisdom, justice, and Legitimacy. |
| Standard may specify comparison | A Procedure may state which Standard governs an assessment, who applies it, at which transition, and what further Act may follow. The Standard supplies evaluative criteria without becoming the Procedure. |
| Record and Receipt preserve | A Procedure may require Records or Receipts for transitions and outputs. Their existence does not prove conformance, and missing artifacts do not prove non-occurrence unless the Procedure makes recording constitutive. |
| Exception authorizes bounded departure | An applicable Exception may permit departure from a procedural requirement within a defined instance and scope. It does not silently amend the Procedure. |
| Amendment changes | A Procedure may be amended through an authorized higher-order Procedure. Practice drift does not update the specification by itself. |
Typical Questions
- What class of Processes or matters does this Procedure govern?
- Which version applies, under what governing basis, scope, and effective time?
- Who may invoke it, participate, perform transitions, decide, review, or contest?
- What entry conditions, deadlines, thresholds, sequencing constraints, and outputs are specified?
- Which Records or Receipts are required, and are they constitutive or merely evidential?
- Did the actual Process conform, partially conform, or deviate?
- Where did any deviation occur: Event, omission, participant, transition, condition, deadline, output, or Record?
- Was an Exception authorized, or is the departure a procedural defect?
- Is procedural compliance being used to overclaim truth, justice, or Legitimacy?
Examples
| Domain | Procedure | What it governs | Possible divergence |
|---|---|---|---|
| Ordinary life | A household process for resolving shared-expense disputes | Notice, participants, discussion, decision, and recording of agreement | One person decides privately and presents the outcome as agreed |
| Law | Civil hearing procedure | Filing, notice, evidence, hearing, Judgment, and available challenge | A required party receives no notice |
| Science | Institutional review procedure for human-subject research | Submission, conflict checks, review, conditions, and approval | Research begins before approval |
| Publishing | Peer-review and editorial-decision procedure | Reviewer selection, review, response, Decision, and publication status | The editor publishes without required human review |
| Markets | Procurement procedure | Thresholds, bids, conflict disclosures, approvals, and contract award | A buyer divides a purchase to evade an approval threshold |
| Community governance | Election procedure | Eligibility, nomination, voting, counting, challenge, and certification | Ballots are counted correctly but by an unauthorized body |
| Digital systems | Incident-response procedure | Triage Roles, escalation conditions, mitigation authority, Records, and review | The service is restored while required notice and incident recording are omitted |
Distinctions
Procedure ≠ Process. A Process is the actual temporal unfolding. A Procedure is a normative specification that may govern it. A hearing still unfolds as a Process when notice is omitted; it is the Process's conformance to the Procedure that is defective.
Procedure ≠ Rule. A Rule states a condition, permission, prohibition, requirement, or constitutive relation for a class of cases. A Procedure organizes multiple roles, conditions, transitions, and outputs into a governed form. Rules may compose or authorize a Procedure without each Rule becoming a Procedure.
Procedure ≠ Workflow. A workflow commonly describes or implements an operational sequence. A Procedure states institutionally permitted, required, or recognized form. A software workflow may automate transitions without being authorized as the governing Procedure, while a Procedure may allow discretion, branching, or human Judgment that no fixed workflow implements.
Procedure ≠ Policy. A policy states governing principles or operational expectations. A Procedure specifies how identified matters are initiated, advanced, and concluded under conditions. A conflict-of-interest policy may require disclosure; the Procedure states who files it, who reviews it, and what transitions follow.
Procedure ≠ Authority. Procedure structures how authorized action may occur. It does not grant Authority merely by describing a path. An elaborate approval form cannot empower a Role that the Constitution did not authorize.
Procedure ≠ Decision. Procedure defines the governed conditions under which a Decision may be made. Decision resolves among live possibilities. Completing every procedural step without resolving the matter is not a Decision, and reaching a Decision does not prove that the Procedure was followed.
Procedure ≠ Validity or Legitimacy. Procedure supplies criteria that may support a claim of procedural Validity. Compliance does not exhaust substantive justification, and deviation does not by itself settle every question of justice or institutional Legitimacy.
Common Failure Modes
| Mode | Description |
|---|---|
| Procedure substituted for Process | The specification is treated as proof of what actually unfolded. Where to look: audits that inspect the procedure document and required forms without reconstructing Events, omissions, and participant accounts. |
| Applicability without basis | A Procedure is imposed on a Process without identifying the Rule, Constitution, Authority, Jurisdiction, scope, or version that makes it applicable. Where to look: procedural demands justified only by custom or administrative preference. |
| Role or access ambiguity | The Procedure reserves participation or transitions to unclear Roles, or formally permits participation while practical access is unavailable. Where to look: matters where eligible parties cannot determine how to enter, receive notice, submit material, or contest an output. |
| Transition indeterminacy | Required, permitted, and prohibited transitions or their conditions are not distinguishable. Where to look: cases stalled between states because no actor can determine what may happen next or who may act. |
| Procedural legitimacy laundering | Formal compliance is used to silence questions about coercion, capture, evidence, substantive justice, or Legitimacy. Where to look: defenses that say only "the proper process was followed" without addressing the challenged grounds. |
| Procedure capture | A formally valid Procedure is designed or administered so that one interested party controls access, evidence, transitions, or review. Where to look: procedures whose outcomes remain invariant because the same party controls both initiation and disposition. |
| Version drift or bypass | Practice follows an obsolete, informally modified, or selectively ignored Procedure without an Amendment or Exception linking the divergence to authority. Where to look: forms, manuals, and software workflows that disagree about the current version. |
Minimum Viable Test Case
pi1 = Procedure(
scope: publication_of(encyclopedia_entry),
roles: {model_assistant, human_author},
entry: draft exists with human_reviewed: false,
transitions: {
model_assistant may draft,
human_author must review,
human_author may approve or return_for_revision,
only human_author may set human_reviewed: true
},
conditions: publication requires status: published and human_reviewed: true,
outputs: {approved_draft, revision_request, published_entry},
records: {review_record, publication_record},
version: editorial_protocol_v1
)
p1 = Process(actual development of entry_x)
g1 = publication_rule adopted by human_author
GOVERNS(pi1, p1, under: g1, within: publication_of(entry_x))
Observed Process:
model_assistant drafts entry_x
model_assistant sets human_reviewed: true
no human review Action occurs
DEVIATES_FROM(
p1,
pi1,
at: unauthorized_transition(model_assistant sets human_reviewed: true),
kind: role_and_condition_violation
)
Result:
p1 occurred, but it does not CONFORM_TO pi1.
The field value is a Record of a claimed status, not proof of review.
A substantively strong entry does not cure the procedural defect.
Cross-References
Required
- Process: the actual unfolding a Procedure may govern
- Agent: the attributable participant who may occupy a Role or perform a governed transition
- Rule: may compose, require, or authorize procedural conditions
- Constitution: may establish Procedures and the Authority to adopt or amend them
- Role: locates governed participation and reserved transitions
- Authority: determines who may adopt, invoke, administer, or alter a Procedure
- Jurisdiction: bounds the matters and parties a Procedure may govern
Consequential
- Review: an actual examination whose participation, grounds, transitions, outputs, and Records a Procedure may govern
- Act: may invoke or advance a Procedure through recognized transitions
- Decision: may be produced under procedural conditions without being reducible to them
- Validity: assesses conformance to applicable procedural criteria
- Exception: authorizes bounded departure without silently amending the Procedure
- Amendment: changes procedural specification through authorized form
- Standard: may supply disclosed evaluative criteria applied at a governed transition
- Appeal: a governed challenge whose entry, participation, scope, materials, and possible responses a Procedure may specify
Evidential