Type: Relation / Resulting Effect
Placement note: Consequence belongs in Division V because it supplies the general relation needed to say what follows from an occurrence, act, condition, or governed determination. It is broader than an institutional penalty or response. Some consequences are natural, social, psychological, or economic. Others arise because a Rule, Obligation, or institution connects one condition to another. The concept therefore belongs beside Obligation without being limited to normative cases.
Working Definition: A consequence is an effect, resulting condition, or later occurrence that follows from an identified source under a stated basis of connection, within a bounded scope and temporal horizon. Calling something a Consequence does not by itself establish that it was intended, foreseen, authorized, recognized, deserved, or attributable to one source alone.
Function in the Grammar: Consequence makes the relation between what happened and what followed explicit. It identifies the source, the effect, the basis on which they are connected, the scope in which that connection is asserted, and the temporal horizon over which it is assessed. This lets the grammar describe an outage following a deployment, distrust following a betrayal, an Obligation following a Breach, or loss of eligibility following a missed deadline without treating those relations as identical.
The connection_basis is essential because "followed" can name different kinds of dependence. Flooding may follow rainfall through a physical causal relation. Loss of voting eligibility may follow a missed filing deadline because a Rule makes that effect constitutive within an election. An Obligation to repair may follow a Breach under a governing basis. Reduced trust may follow deception through a social relation that is real but difficult to measure. The entry does not reduce these bases to one universal theory of causation. It requires the basis being claimed to remain inspectable.
Consequence is many-to-many. One source may have several consequences that emerge at different times and affect different subjects. One consequence may result from several contributing Events, Actions, conditions, Rules, or Decisions. The grammar should not force a single cause, a single affected party, or a single time scale where the available Evidence supports a more distributed account.
Consequences may be intended or unintended, direct or mediated, immediate or delayed, beneficial or harmful, reversible or irreversible, recognized or unrecognized, and foreseeable or unforeseeable. These are independent properties, not mandatory modes. None follows merely from the existence of the Consequence relation. In particular, a harmful consequence is not automatically a Breach, and a foreseeable consequence is not automatically intended.
Claims about future consequences are projections, not completed relations. They may be well supported and may properly inform a Decision, Standard, or precaution, but the projected effect remains possible until it occurs or otherwise obtains. The grammar should preserve the difference between MAY_HAVE_CONSEQUENCE(x, y) and HAS_CONSEQUENCE(x, y).
Formal Grammar Representation
<consequence> ::= Consequence(
id: <consequence-id>,
source: <source-reference>,
effect: <effect-reference-or-description>,
connection_basis: <connection-basis>,
scope: <scope>,
temporal_horizon: <time-interval-or-relation>
)
<source-reference> ::= Event | Process | Action | Act | Decision
| Status | Transformation | Obligation | Breach
| condition | omission | compound source
<effect-reference-or-description> ::= Event | Status | Transformation
| Obligation | relation | condition
| change in capacity, opportunity,
cost, risk, or other identified effect
Consequence(c) is well-formed when:
source(c) = x, where x is identifiable
effect(c) = y, where y is distinguishable from x
connection_basis(c) = k, where k warrants treating y as following from x
scope(c) = S, where the subjects and domain of the relation are bounded
temporal_horizon(c) = T, where the relevant interval or ordering is stated
HAS_CONSEQUENCE(x, y, under: k, within: S, over: T)
MAY_HAVE_CONSEQUENCE(x, y, under: k, within: S, horizon: T)
Semantic Constraints
The expression Consequence(c, x, y, k, S, T) is well-formed when the source, effect, basis of connection, scope, and temporal horizon are stated. Its form does not establish that the asserted relation is true, complete, morally important, institutionally recognized, or sufficient to assign responsibility. Those questions require Evidence, interpretation, Judgment, a governing basis, or other relations appropriate to the case.
Temporal order is necessary in many consequence Claims but is not sufficient. If one Event occurs after another, the later Event does not become a Consequence merely because of succession. The connection_basis must state why the relation is warranted. That basis may cite a causal mechanism, a constitutive Rule, a normative ground, a dependency, a documented social relation, or another disclosed form of dependence. Correlation without a warranted connection remains correlation.
MAY_HAVE_CONSEQUENCE records a projected, conditional, or risk-bearing relation. It must not be restated as HAS_CONSEQUENCE before the effect occurs or obtains. Conversely, uncertainty about future effects does not license an institution to omit the projection or its Evidence from a Decision for which that risk is relevant.
The source may be compound. Where an effect depends on several contributing conditions, the grammar should preserve them rather than select one for narrative convenience. Conversely, background conditions should not be inflated into equivalent causes merely because they were present. The strength and kind of each contribution remain matters for attributable Claims and Evidence.
Institutional recognition is neither necessary nor sufficient for a Consequence to exist. A pollution event may harm a community before any forum recognizes the harm. A Judgment may recognize a claimed consequence without making the underlying causal account true. Recognition changes institutional standing; it does not create every effect it names.
Consequences do not carry value or Significance automatically. The same price increase may benefit one seller and burden many buyers. The same publication may advance knowledge, expose a participant, and create an editorial correction burden. Assessments of importance, harm, benefit, proportionality, or deservedness must disclose their affected subject, perspective, basis, and scope.
Formal Pattern
Consequence(c, source: x, effect: y,
connection_basis: k, scope: S,
temporal_horizon: T)
HAS_CONSEQUENCE(x, y, under: k, within: S, over: T)
MAY_HAVE_CONSEQUENCE(x, y3, under: projected_basis(k3),
within: S3, horizon: T3)
CLAIMS(
Agent(a),
proposition: HAS_CONSEQUENCE(x, y, under: k, within: S, over: T),
supported_by: EvidenceSet(E),
at: t
)
RECOGNIZES(
Agent(r),
Consequence(c),
on_behalf_of: Institution(I),
under: Authority(A),
within: Scope(S)
)
HAS_CONSEQUENCE(x, y1, under: k1, within: S1, over: T1)
HAS_CONSEQUENCE(x, y2, under: k2, within: S2, over: T2)
HAS_CONSEQUENCE({x1, x2, x3}, y, under: compound_basis(k),
within: S, over: T)
CLAIMS and RECOGNIZES remain separate from HAS_CONSEQUENCE. The first attributes an assertion. The second gives the relation an institutional treatment within scope. Neither substitutes for the underlying connection, and the underlying connection need not wait for either act before it can obtain.
Core Relations
| Relation | Notes |
|---|---|
| Event and Process may source | An Event may have later effects. A Process may generate effects across its unfolding or after it ends. Consequence connects occurrences without turning the connected set into one Process. |
| Action and Act may source | An Action may produce practical effects, while an institutionally recognized Act may also produce constitutive effects. Intention and institutional recognition must remain separate from what actually follows. |
| Decision may source | A Decision resolves among live possibilities. Its consequences arise through later Actions, Rules, reliance, recognition, or other connections. They are not automatic merely because the Decision is well-formed. |
| Status and Transformation may effect | A Consequence may be a changed condition or a crossing from one Status to another. Transformation names the crossing itself; Consequence names its relation to a source. |
| Rule and Obligation may constitute or ground | A Rule may specify that one condition has another as an institutional consequence. A Breach may ground a secondary Obligation to repair. The Rule or governing basis must support that effect rather than merely naming it. |
| Breach and Repair connect without collapsing | Breach may have practical, relational, normative, or institutional consequences. Repair is a governed response that may address some of them. Neither concept is reducible to the effects surrounding it. |
| Enforcement is a distinct response | Enforcement is an authorized institutional Action undertaken to give practical effect to a governing basis. It can itself have consequences, but not every Consequence is Enforcement. |
| Intention may orient | An Agent may aim at one effect and produce another. Intention helps explain Action but does not determine the Consequence relation. |
| Power shapes practical effect | Power can affect whose conduct produces consequences, who bears them, which effects become visible, and whether an authorized response works in practice. Power does not make every resulting effect legitimate. |
| Claim and Evidence support attribution | Statements about consequences are Claims whose source, Evidence, scope, and limits should remain visible. Evidence may support a connection without establishing sole causation or complete impact. |
| Significance assesses | Significance states why a consideration matters within a Frame. A Consequence may be significant or negligible for a stated purpose, but being a Consequence does not determine its weight. |
| Record and Narrative represent | A Record may preserve traces of an effect, and a Narrative may organize an account of what followed. Neither representation makes the asserted connection true or complete. |
| Accountability may examine | An Agent may be accountable for producing, preventing, disclosing, or responding to a Consequence under a governing basis. The existence of the effect alone does not create answerability. |
Typical Questions
- What identified Event, Action, Act, Decision, Process, condition, or omission is the claimed source?
- What exactly followed, and for whom or what did it follow?
- What basis connects the source and effect: causal mechanism, constitutive Rule, normative ground, dependency, social relation, or something else?
- Is the relation observed, inferred, predicted, contested, or institutionally recognized?
- What Evidence supports the connection, and what alternative explanations remain live?
- Is the source singular or compound? Which contributing and background conditions are being omitted?
- What scope and temporal horizon are being used?
- Are immediate and visible effects displacing delayed, distributed, or externalized ones?
- Was the effect intended, foreseen, authorized, or preventable, and which of those properties is actually relevant?
- Does the governing basis assign responsibility, answerability, Repair, or Enforcement, or is that being inferred from harm alone?
- Who benefits, who bears cost or risk, and from whose perspective is the Consequence being assessed?
- Is a Record or Narrative being mistaken for the occurrence or relation it represents?
Examples
| Domain | Source | Consequence and basis | What does not follow automatically |
|---|---|---|---|
| Natural systems | Sustained rainfall over saturated ground | Flooding follows through a physical causal mechanism within a watershed | That one rainfall Event is the sole cause or that any Agent is responsible |
| Ordinary life | A person repeatedly breaks confidences | Reduced trust follows through a documented relational pattern | That the person intended the distrust or that the relationship must end |
| Health | A medication is taken | Symptom relief and an adverse effect may both follow through physiological mechanisms | That either effect was certain, intended, or adequately disclosed |
| Law | A filing deadline passes without a required submission | Loss of eligibility follows if the applicable Rule constitutively specifies that effect | That the Rule is legitimate, the omission culpable, or no Exception applies |
| Publishing | An inaccurate article is published and relied upon | Reader error and a correction burden may follow through reliance and editorial obligations | That publication alone proves every claimed downstream harm |
| Markets | A dominant supplier restricts output | Higher prices and shortages may follow through a stated market mechanism | That every price movement has this one cause or affects every participant equally |
| Community governance | A meeting is moved online without accessible participation | Some members lose practical access through the interaction of format and access conditions | That formal notice made the exclusion intended or acceptable |
| Digital systems | A software release corrupts stored identifiers | Failed authentication follows through a reproduced technical dependency | That the deployment Decision alone, rather than implementation and control failures, is the sole source |
| Normative relations | An applicable safety Obligation is breached | A secondary Obligation to disclose and repair may arise under the governing policy | That punishment, waiver, or successful Repair has already occurred |
Distinctions
Consequence ≠ Event. An Event is an occurrence. A Consequence is a relation in which an occurrence, condition, or other effect follows from an identified source under a basis of connection. The outage is an Event. Its relation to the deployment is a Consequence Claim that requires its own support.
Consequence ≠ outcome. An outcome is an ordinary term for a result, often selected or measured within a Process, Decision, experiment, contest, or evaluation. Consequence emphasizes the relation between a source and an effect, including indirect, unintended, delayed, or distributed effects outside the designated outcome. A trial may have an acquittal as its outcome and renewed public attention as a further Consequence.
Consequence ≠ risk or projected effect. A risk identifies a possible adverse effect together with uncertainty about whether it will occur. A projection states what may follow under assumptions. Both may support precaution or Decision, but neither is an obtained Consequence merely because it is credible. After the effect occurs, the earlier projection becomes part of the provenance of what was anticipated, not proof that its causal account was correct.
Consequence ≠ Transformation. Transformation is a crossing from one Status or condition to another. Consequence states how that crossing relates to a source. A missed deadline may have loss of eligibility as a Consequence; the change from eligible to ineligible is the Transformation.
Consequence ≠ intention or purpose. Intention is an Agent's directedness toward an aim. Purpose describes what an Action, Process, or institution is for. Consequence describes what follows. An intended effect may fail to occur, and an unintended effect may become the most practically important Consequence.
Consequence ≠ responsibility or blame. Responsibility attributes conduct, duty, causal contribution, or answerability to a bearer. Blame evaluates a bearer negatively. A Consequence may be traced to several sources, including non-agentive conditions. Assigning responsibility requires further grounds such as control, contribution, Role, knowledge, foreseeability, or Obligation.
Consequence ≠ Breach. Breach is failure relative to an applicable Obligation, Rule, or Commitment under the relevant conditions. Consequence is what follows from a source. Harm may occur without Breach, and Breach may be found before its longer-term consequences are known.
Consequence ≠ Enforcement. Enforcement is an authorized institutional response undertaken to give practical effect to a Rule, Obligation, Commitment, Judgment, or Decision. Consequence is broader and may be natural, social, psychological, economic, normative, or institutional. A fine can be Enforcement and can also have further consequences for the person, institution, and community.
Consequence ≠ Repair. Repair is a governed Process that acknowledges failure and produces an accountable path forward. It may address some consequences, create new Obligations, and produce additional effects. The existence of harm does not prove that Repair has begun, and the completion of a Repair Process does not imply that every Consequence has ended.
Consequence ≠ Significance. Consequence identifies what follows under a basis of connection. Significance assesses why a consideration matters within a Frame. A statistically small effect may have great Significance for a vulnerable group, while a large aggregate effect may be irrelevant to the Decision currently under Review.
Common Failure Modes
| Mode | Description |
|---|---|
| Post hoc causation | Temporal succession or correlation is presented as a warranted consequence relation without a mechanism, constitutive Rule, normative ground, or other disclosed basis. Where to look: Claims that say "after" or "associated with" in the Evidence and silently become "because of" in the conclusion. |
| Monocausal compression | A compound effect is attributed to one salient Agent, Action, or Decision while other contributing and enabling conditions disappear. Where to look: incident reports with one named operator and no account of system design, supervision, incentives, or prior failures. |
| Intention laundering | An observed effect is represented as the Agent's purpose, or an intended effect is treated as if it actually occurred. Where to look: praise or blame that moves from outcome to motive without independent Evidence of Intention. |
| Normativity or desert laundering | What happened is treated as what ought to have happened, or a harmful effect is treated as a deserved penalty without an applicable governing basis and authorized Judgment. Where to look: phrases such as "the natural consequence" used to avoid disclosing who designed, imposed, or could have prevented the condition. |
| Scope, horizon, or distribution truncation | Immediate, measurable, aggregated, or institutionally convenient effects are counted while delayed, cumulative, externalized, or unevenly distributed effects are omitted. Where to look: net-positive summaries that stop at transaction completion without identifying later costs or the subjects who bear concentrated harm. |
| Institutional or representational substitution | A Recognition, Record, or Narrative is treated as creating the underlying effect or as a complete account of its connection, while unrecognized or undocumented effects are treated as nonexistent. Where to look: official labels cited as the sole Evidence of harm, or dashboards and timelines that omit their selection rules, provenance limits, and unresolved alternatives. |
| Response collapse | Accountability, punishment, Repair, or Enforcement is treated as an automatic property of the underlying effect. Where to look: systems that move from detecting harm directly to sanction without separately establishing attribution, Obligation, Authority, Jurisdiction, and Procedure. |
Minimum Viable Test Case
d1 = Decision(
decider: release_manager,
matter: service_v4,
content: deploy_release_4_2,
scope: production_service,
basis: approved_change_request,
time: t1
)
a1 = Action(execute_deployment, actor: deployment_operator, at: t2)
e1 = Event(authentication_failure, interval: t3_to_t4)
c1 = Consequence(
source: {a1, corrupted_identifier_migration, missing_rollback_check},
effect: e1,
connection_basis: reproduced technical dependency and incident Evidence,
scope: accounts using migrated identifiers,
temporal_horizon: t2_to_t4
)
HAS_CONSEQUENCE(
{a1, corrupted_identifier_migration, missing_rollback_check},
e1,
under: reproduced technical dependency,
within: affected_account_scope,
over: t2_to_t4
)
CLAIMS(
incident_reviewer,
proposition: c1,
supported_by: {deployment_log, migration_diff, reproduction_test},
at: t5
)
Result:
e1 is an Event.
c1 relates that Event to a compound source under a disclosed basis.
The deployment Decision is relevant but is not declared the sole cause.
c1 does not establish Intention, Breach, blame, or Enforcement.
A governing incident Rule may separately create Obligations to disclose,
restore service, preserve Records, and conduct Repair.
Failure case:
"The release manager decided to cause an outage and must be punished"
does not follow from c1. It launders a compound consequence into Intention,
sole responsibility, Breach, and Enforcement without the relations and
Evidence each conclusion requires.
Cross-References
Required
- Event and Process: supply occurrences and unfoldings that may source or instantiate effects
- Action and Act: distinguish practical conduct from institutionally recognized conduct and its constitutive effects
- Decision: may organize what happens next without containing every later effect
- Status and Transformation: describe resulting conditions and crossings that may stand as effects
- Rule and Obligation: may constitute or ground normative and institutional consequences
Consequential
- Breach: may source practical, relational, normative, or institutional consequences
- Repair: may address consequences through a governed response without erasing them
- Enforcement: an authorized institutional response distinct from Consequence
- Intention: may orient an Action without determining what follows
- Power: shapes the production, distribution, visibility, and practical force of effects
- Significance: assesses why an identified Consequence matters within a Frame
- Recognition: may give a Consequence institutional treatment without creating every effect it names
- Accountability: may make an Agent answerable for producing, preventing, disclosing, or responding to a Consequence
Evidential
- Claim: makes the asserted source-effect relation attributable and contestable
- Evidence: supports or undermines the stated basis of connection
- Record: may represent sources, effects, and traces without constituting the relation
- Narrative: may organize what followed while selecting and interpreting connections