Type: Node / Temporal Unfolding
Placement note: Process belongs in Division II (Process and Event) because it supplies the temporal form in which Events, Actions, Acts, and Transformations can remain related beyond a single occurrence. It is general rather than institutional by definition. A storm, a conversation, recovery, and an editorial review may all be Processes, although only some are governed through a Procedure.
Working Definition: A process is a temporally extended unfolding composed of related events, actions, acts, or transformations. A Process description identifies the basis on which those occurrences belong together and the boundary within which the unfolding is tracked, without by itself prescribing participants, transitions, or valid outcomes.
Function in the Grammar: Process supplies temporal composition. Event answers what occurred at a locatable point or interval. Process answers how occurrences remain related as parts of an unfolding through time. This makes it possible to describe initiation, continuation, interruption, overlap, branching, resumption, and termination without assuming that every unfolding is linear, designed, agentive, progressive, or complete.
The grammar keeps a Process distinct from the description of it. A storm can unfold without anyone identifying it as a Process. A recovery can continue without an institution recording its stages. When an agent or institution makes a Process claim, however, the claim must disclose enough of its continuity_basis and boundary to show why these occurrences are being grouped and why others are excluded. That requirement makes the description contestable without making the underlying unfolding observer-created.
The continuity_basis field is not the encyclopedia's technical Continuity concept. It is an argument that records the causal, agentive, purposive, structural, biological, narrative, institutional, or other warranted basis on which occurrences are treated as parts of one Process. Continuity remains the narrower institutional property by which an institution stays accountable to its authorized past.
Formal Grammar Representation
<process> ::= Process(
id: <process-id>,
occurrences: <occurrence-set>,
interval: <temporal-extent>,
continuity_basis: <basis>,
boundary: <boundary>
)
<occurrence-ref> ::= Event(e)
| Action(a)
| Act(a)
| Transformation(tau)
<occurrence-set> ::= one or more <occurrence-ref> values
<temporal-extent> ::= a stated interval or set of temporal relations
<basis> ::= a disclosed relation or criterion under which the occurrences
belong to one unfolding
<boundary> ::= criteria for inclusion and, where applicable, initiation,
suspension, branching, resumption, and termination
Process(p) is well-formed when:
occurrences(p) = E
E contains multiple related occurrences, or one duration-bearing occurrence
whose distinguishable phases are under examination
temporal_extent(p) = T, where T has nonzero duration
continuity_basis(p) = k, where k states why the members or phases belong together
boundary(p) = b, where b states what is included and excluded from p
for each occurrence x in E:
b admits x as part of p
k relates x to the unfolding described as p
Semantic Constraints
Process(p, E, T, k, b) is well-formed when its occurrences or phases, temporal extent, continuity basis, and boundary can be stated. The syntax does not establish that every listed occurrence happened, that the proposed relation is real, or that the boundary is uniquely correct. Those claims may require evidence, interpretation, or domain knowledge. Different warranted descriptions may place the same occurrence in overlapping Processes or draw different boundaries around one unfolding.
The occurrence forms are not disjoint types. One occurrence may be an Event, an Action because it is attributable and purposive, an Act because it is institutionally recognized, and a Transformation because it marks a consequential state crossing. Applying several predicates to one occurrence does not create several Process parts or license counting it more than once.
For an ongoing, emergent, or poorly observed Process, the boundary may be open or provisional. Stating what remains unknown is more accurate than manufacturing a definite beginning or end. A provisional boundary keeps the Process claim revisable without making every grouping equally warranted.
Well-formedness does not imply a goal, agent, procedure, progression, or successful completion. Processes may be natural or social, deliberate or emergent, bounded or ongoing, linear or branching. A process may pause and resume, recur, divide into subprocesses, overlap another process, or end without producing the outcome participants expected.
An anticipated or designed unfolding is not yet an actual Process merely because its stages have been specified. Before any occurrence begins, it is a plan, model, rule, or proposed Procedure. Once occurrences unfold, the actual Process may conform to that design, depart from it, or fail within it. The description of the intended path must not be substituted for what occurred.
Process identity is also not settled by syntax. Whether a resumed activity is the same Process, whether a branch creates a new Process, or whether Repair continues an earlier Process depends on the stated continuity basis and boundary together with the relevant domain. Process makes those questions expressible. It does not supply a universal theory of persistence.
Formal Pattern
Process(p, occurrences: E, interval: T, continuity_basis: k, boundary: b)
UNFOLDS(Process(p), through: T)
PART_OF(x, Process(p), under: k, within: b)
PART_OF(Process(p_sub), Process(p), under: k_sub, within: b_sub)
OVERLAPS(Process(p1), Process(p2), at: x)
HAS_STATUS(Process(p), Status(s), at: t)
REPRESENTS(Record(r), Process(p))
PART_OF, OVERLAPS, HAS_STATUS, and REPRESENTS are further relations, not automatic consequences of calling something a Process. HAS_STATUS requires a context in which a status has been assigned. REPRESENTS does not make the Record identical to the Process or establish that the representation is accurate.
Core Relations
| Relation | Notes |
|---|---|
| Event composes | Events supply locatable occurrences or phases within a Process. The same phenomenon may be described as an Event at one scale and a Process at another. |
| Action and Act participate | Agentive doings and institutionally recognized Acts may occur within a Process. A Process need not itself have an agent or intention. |
| Transformation may occur within | A Transformation is a material crossing between grammar-tracked states. A Process may contain, seek, culminate in, or realize several Transformations, and it may end without producing the intended one. |
| Context situates | Context affects which relations and boundaries matter when a Process is described. Context does not make arbitrary aggregation valid. |
| Decision may redirect | A Decision may initiate, suspend, redirect, terminate, or leave a Process unchanged. None of those relations follows from Decision or Process alone. |
| Procedure may govern | A Procedure is a normative specification of roles, permissible or required transitions, conditions, and outputs for Processes within a governed scope. When a governing basis makes a Procedure applicable to a particular Process, the actual unfolding may conform to or deviate from that specification. |
| Status may qualify | Institutions may recognize a Process as pending, active, suspended, complete, or failed. The label does not prove that the underlying boundary or completion condition is correct. |
| Record represents | A Record preserves a representation or trace of a Process and its occurrences. The completed Process remains part of history; the Record is not the unfolding itself. |
| Identity differs | Identity asks what remains the same bearer through change. Process asks what makes occurrences parts of one unfolding. A bearer may participate in many Processes, and a Process may involve many bearers. |
| Continuity differs | Institutional Continuity asks whether an institution remains accountable to its authorized past. A natural or personal Process may have a continuity basis without possessing institutional Continuity. |
| Narrative represents | Narrative may organize and interpret a Process, but it does not constitute the unfolding merely by describing it. A Narrative may also become an occurrence within a Process when agents act in response to it. |
| Repair specializes | Repair is a governed Process organized around acknowledged failure and an accountable path forward. Process supplies its temporal genus without supplying Repair's normative purpose. |
| Appeal specializes | Appeal is a governed Process initiated to challenge an existing appealable disposition. Process supplies the unfolding without supplying Standing, appellate Jurisdiction, review scope, or effect. |
Typical Questions
- Which occurrences are being treated as parts of this Process?
- Over what temporal extent does the Process unfold?
- What continuity basis relates these occurrences?
- What boundary determines inclusion, exclusion, initiation, interruption, resumption, branching, or termination?
- Is the Process ongoing, suspended, complete, failed, or only retrospectively described?
- Does the actual Process conform to a governing Procedure or depart from it?
- Are two descriptions identifying the same Process, overlapping Processes, or different Processes?
- Which parts of the Process are directly observed, recorded, inferred, or narrated?
Examples
| Domain | Process | Continuity basis | Boundary question |
|---|---|---|---|
| Weather | The formation, movement, and dissipation of a thunderstorm | Causal and meteorological relations among atmospheric changes | When did the storm become one system, and when did it dissipate or divide? |
| Ordinary life | A conversation that continues through pauses and topic changes | Interaction among participants around a continuing exchange | Did a long interruption end the conversation or merely suspend it? |
| Recovery | A person's recovery unfolding through practices, setbacks, support, and changed orientation | Biographical and practical relations disclosed by the person, without requiring linear progress | Which experiences belong to the recovery, and who is entitled to draw that boundary? |
| Science | An inquiry that moves from observation through experiments, criticism, and revised hypotheses | A continuing research question and traceable relation among methods and findings | Did a change of question begin a new inquiry or redirect the existing one? |
| Publishing | Revision of one manuscript through review, decision, editing, and resubmission | Artifact and version lineage organized around the same editorial matter | Does a complete rewrite remain the same revision Process or begin another? |
| Digital systems | Response to a service incident across detection, mitigation, recovery, and review | A shared incident and causal chain among system Events and Actions | Is a later recurrence part of the original incident or a new Process? |
| Law | A case unfolding through filings, hearings, Decisions, and possible Appeal | The same matter within a recognized jurisdiction and case history | Does remand continue the same case Process, reopen it, or begin a distinct proceeding? |
Distinctions
Process ≠ Event. An Event identifies an occurrence. A Process relates occurrences or distinguishable phases across temporal extent. A committee vote is an Event; the election in which registration, campaigning, voting, counting, and certification remain related is a Process. The same phenomenon may be described at either scale when the description makes the scale explicit.
Process ≠ Procedure. A Process is what unfolds. A Procedure normatively specifies how a Process is permitted, required, or recognized to unfold within a governed scope by defining roles, transitions, conditions, or outputs. It does not determine everything that can causally happen, and its existence does not prove that the specified unfolding occurred. A committee may conform to, deviate from, or only partially realize its voting Procedure; in every case, an actual Process still occurred. A thunderstorm is a Process with no Procedure.
Process ≠ Transformation. A Transformation is a material before-and-after delta in a grammar-tracked subject. A Process is the temporally extended unfolding in which crossings may occur. An application Process may seek or culminate in the Transformation from applicant to member, but it may also end without admission. The interviews, delays, and deliberations are not identical to the crossing.
Process ≠ Action. An Action is attributable doing by an Agent. A Process may contain many Actions, but it may also contain non-agentive Events and may have no single controlling Agent. One editor's request for revision is an Action within an editorial Process.
Process ≠ Identity. Identity asks whether a person, institution, artifact, or other bearer remains the same through change. Process identity asks a narrower descriptive question about whether occurrences belong to the same unfolding. A manuscript may retain Identity while moving through several editorial Processes; one Process may involve many bearers whose Identities remain distinct.
Process ≠ Continuity. Continuity is the institutional property of remaining accountable to an authorized past. A Process may be coherent under a causal or biological continuity basis without any institution, authority chain, or Ledger. Calling that basis continuity_basis does not confer the technical property Continuity.
Process ≠ Narrative. A Process unfolds; a Narrative organizes and interprets an account of what unfolded. The same Process may support several Narratives, and each may omit, reorder, or misinterpret occurrences. A Narrative can influence an ongoing Process when participants act on it, but the account and the unfolding remain different things.
Process ≠ Progress. A Process can continue without improving, converging, or approaching a goal. Recovery may include recurrence and setbacks. Deliberation may end in deadlock. Institutional review may expose failure rather than resolve it. Treating temporal continuation as progress imports an evaluation that Process itself does not supply.
Common Failure Modes
| Mode | Description |
|---|---|
| Arbitrary aggregation | Temporally adjacent occurrences are grouped as one Process without a disclosed relation that makes them belong together. Where to look: timelines whose only continuity basis is that the listed items happened near one another. |
| Boundary concealment | A Process description includes favorable occurrences and excludes inconvenient ones without stating its inclusion or termination criteria. Where to look: performance reviews or institutional histories whose start and end dates change with the conclusion being defended. |
| Linearity imposition | Branches, overlaps, pauses, recurrence, or parallel activity are forced into one ordered sequence. Where to look: workflow diagrams or narratives that assign a single path where participants actually diverged or returned to earlier work. |
| Teleology smuggling | The Process is described as naturally moving toward an outcome, improvement, or completion that was neither inherent nor achieved. Where to look: recovery, learning, or reform accounts that reinterpret every occurrence as progress toward a predetermined end. |
| Procedure substituted for Process | The declared Procedure is treated as proof of what actually unfolded. Deviations, skipped transitions, informal actions, and failures disappear because the designed path is mistaken for the historical Process. Where to look: audits that inspect the procedure document but not the Events, Records, or participants' accounts. |
| Narrative substituted for Process | A retrospective account is treated as though its selected sequence and causal connections were the unfolding itself. Where to look: Process claims supported only by a summary, with no traceable occurrences or acknowledgment of omitted material. |
| False continuity | A genuine break, replacement, or branch is described as continuation of the same Process without a warranted continuity basis. Where to look: resumed projects, successor institutions, recurring incidents, or repaired relationships where the claim of sameness hides an unacknowledged discontinuity. |
Minimum Viable Test Case
Process(p1):
description: revision of encyclopedia draft x after review
occurrences:
e1: reviewer submits review at t1
d1: human_author decides return_for_revision at t2
a1: human_author revises x at t3
e2: x is resubmitted at t4
interval: [t1, t4]
continuity_basis:
the same artifact and version lineage
the same disclosed editorial matter
boundary:
begins with receipt of this review
includes acts responding to its findings
ends with resubmission for a new review
UNFOLDS(Process(p1), through: [t1, t4])
PART_OF(Event(e1), Process(p1), under: editorial_matter)
PART_OF(Decision(d1), Process(p1), under: editorial_matter)
PART_OF(Action(a1), Process(p1), under: artifact_lineage)
PART_OF(Event(e2), Process(p1), under: artifact_lineage)
Result:
p1 is a Process even before a Procedure entry specifies how editorial
revision ought to occur.
d1 is one occurrence within p1, not the Process as a whole.
a later Record may represent p1, but the Record is not p1.
a Narrative may explain p1, but its sequence remains contestable against
the occurrences and Records it cites.
Failure case:
If unrelated edits to other entries are included only because they occurred
between t1 and t4, temporal proximity does not supply the missing
continuity basis. The expanded grouping is not yet a well-formed account
of one Process.
Cross-References
Required
- Event: supplies the locatable occurrences or duration-bearing phenomenon that Process relates through time
- Action: agentive doing that may initiate, redirect, or participate in a Process
- Act: institutionally recognized Action that may occur within an institutional Process
- Transformation: a material state crossing that may occur within, result from, or delimit a Process
- Context: situates Process descriptions and affects which relations and boundaries are relevant
Consequential
- Procedure: a normative specification that may govern a Process and support contestable conformance or deviation assessments
- Decision: an action of resolution that may initiate, redirect, suspend, or terminate a Process
- Status: may qualify a Process as pending, active, suspended, complete, or failed when institutionally assigned
- Repair: a governed Process organized around acknowledged failure and accountable continuation
- Appeal: a governed Process initiated to challenge an existing appealable disposition
Evidential
- Record: preserves a selective representation of a Process and its occurrences without becoming the unfolding
- Identity: distinguishes persistence of a bearer from the relation among occurrences in one Process
- Continuity: the narrower institutional property that
continuity_basismust not duplicate - Narrative: may organize and interpret a Process without constituting or proving the unfolding it describes