How is the Process Continuity Score (PCS) measured in practice?

Mechanically. Map the primary workflow from trigger to completed transaction, list every transition where work changes hands, systems, or stages, and classify each as encoded or human-initiated. The proportion of encoded transitions is the score — no interpretation required. The absence of interpretation is deliberate: PCS is designed to make marketing claims about process autonomy falsifiable by a count.

Can a business have autonomous stages and still score 0 on PCS?

Yes, and many do. If a person carries the work between every stage — noticing completion, deciding what happens next, starting the following step — the transitions are human regardless of how capable the agents inside each stage are. The distinction between a business with capable agents at every stage and a business with encoded transitions between every stage is precisely what PCS scores.

What is the relationship between PCS and The 80 Percent Threshold?

The 80 Percent Threshold is the boundary between a score of 1 and a score of 2: a business qualifies for the top band only when more than 80% of its cross-departmental handoffs execute without human intervention. A business at 75% encoded transitions scores 1, not 2 — the threshold is not a gradient but a structural line, because below it the remaining human handoffs are numerous enough to govern the process tempo.

How does PCS relate to Task Execution Autonomy (TEA) and Decision Execution Autonomy (DEA)?

The three axes score distinct layers of the same operation. Task Execution Autonomy (TEA) scores who executes the work within each stage. [Decision Execution Autonomy (DEA)](https://arcoventure.studio/lexicon/decision-execution-autonomy) scores who decides how work is routed and resolved. PCS scores whether the work moves between stages without a person carrying it. A business can score 2 on TEA and 1 on DEA while scoring 0 on PCS — agents execute everything and logic decides everything, but a human restart is still required at every functional boundary. Each axis catches a failure mode the others do not.

What is Suspend/Resume Architecture and why does it matter for PCS scoring?

Suspend/Resume Architecture is the infrastructure pattern that encodes external wait states as pause points rather than human handoffs. A workflow that must wait for a payment confirmation, a regulatory response, or a supplier acknowledgement does not require a human to monitor the wait and restart the process when the signal arrives — the workflow suspends on the trigger and resumes automatically when the condition is met. Without Suspend/Resume Architecture, every long-wait transition in a workflow scores as a human handoff regardless of how capable the surrounding agents are, because the waiting itself produces the person at the boundary. A business targeting a score of 2 on PCS must audit its wait states alongside its active transitions.

The Process That Does Not Stop

A business can deploy a capable agent at every stage of its operation and still wait at every boundary between stages. The intake agent finishes, and the work sits until a person notices, decides what happens next, and starts the processing agent. The processing agent finishes, and the work sits again. Each stage is autonomous; the process is not. The work does not flow — it queues at human checkpoints, and the checkpoints set the tempo of the entire business.

Process Continuity Score (PCS) is the third axis of the Autonomy Spectrum Framework: the measure of whether a business's workflows run end-to-end without halting for human input, scored 0–2 against the proportion of cross-departmental handoffs that execute without intervention. It scores the transitions, because the transitions are where autonomy is most commonly lost.

Why the boundaries break first

Stages get automated because stages are visible. A task has an owner, a tool budget, a measurable output — so the task attracts the investment, and the agent that owns it gets built. Transitions have none of these things. A handoff between departments belongs to no one; it appears in no job description and no procurement request. It is performed by whoever notices that the previous step finished — which means it is performed by attention, and attention is the most expensive and least reliable component in any operation.

This is why an organisation can genuinely transform its task layer and leave its process tempo untouched. Every Transition Is Either Encoded or Human established this structurally: every transition in a business is either encoded or human, and there is no neutral state in between. A transition nobody encoded is a human transition by default, staffed by interruption. PCS converts that argument into a count.

The scoring semantics

A score of 0 indicates that workflow transitions are human-initiated: agents may execute within stages, but a person carries the process between them. A score of 1 indicates continuity within functions but halts at functional boundaries — the workflow runs unattended inside a department and stops at the Coordination Surface between departments. A score of 2 indicates that cross-departmental handoffs execute without human intervention at or above The 80 Percent Threshold, with every transition either encoded in the business's State Machine or deliberately assigned to the Judgment Layer / Execution Layer by architectural decision rather than default.

Long workflows that wait on external signals — a payment confirmation, a regulatory response, a supplier acknowledgement — are not automatically human handoffs. Suspend/Resume Architecture is the infrastructure pattern that encodes these wait states as suspend points: the workflow pauses on an external signal rather than handing off to a human to watch for it. A business without Suspend/Resume Architecture will score its long-wait transitions as human handoffs regardless of how capable its agents are, because the waiting is what produces the person at the boundary.

Scoring the axis is mechanical, which is a virtue. Map the primary workflow from initial trigger to completed transaction. List every transition — every point where the work changes hands, systems, or stages. Classify each one: did encoded logic move the work across this boundary, or did a person notice, decide, and restart? The proportion is the score. No interpretation is required, which means no marketing survives the exercise.

The trap the axis exposes

PCS is the axis that catches the Coordination Trap — the failure mode in which a business reduces the effort of individual tasks through AI tools without removing the human coordination dependencies that govern how those tasks connect. The trapped business has a distinctive and increasingly common profile: respectable Task Execution Autonomy (TEA), near-zero Process Continuity. Its tasks complete in seconds and its processes complete in days, because the process now waits on humans at every boundary it always waited at — and the faster the tasks finish, the larger the share of total cycle time the waiting represents.

This is the Automation Paradox expressed at the process level. The business invested in task speed and left the transition architecture untouched. AI adoption demonstrably accelerated the work — individual tasks complete faster than before — while delivery times barely moved. Task speed and process speed are different quantities, governed by different architecture, and only one of them was invested in. PCS makes that gap visible as a number.

The Operator's Verdict

Walk your primary workflow once, end to end, and mark every point where the work stops to wait for a person to notice it. Each mark is a transition that was never designed — a boundary running on attention because nobody encoded it. The count is usually a shock, and it should be: it is the precise distance between a business that uses agents and a business that runs on them.

Technology changes what is possible. The transition determines what is continuous.

KEY TAKEAWAY

What is the Process Continuity Score (PCS)?

The Process Continuity Score (PCS) is the third axis of the Autonomy Spectrum Framework — the measure of whether a business's workflows run end-to-end without halting for human input, scored 0–2 against the proportion of cross-departmental handoffs that execute without intervention. A score of 0 means transitions are human-initiated; a score of 1 means continuity within functions but halts at functional boundaries; a score of 2 means cross-departmental handoffs execute without intervention at or above The 80 Percent Threshold, with every transition either encoded in the State Machine or deliberately assigned to the Judgment Layer by architectural decision. PCS exposes the Coordination Trap: businesses whose tasks complete in seconds while their processes complete in days because the Automation Paradox operates at the transition layer rather than the task layer. Suspend/Resume Architecture is the infrastructure pattern that resolves long-wait transitions without human handoffs. Source: Arco Venture Studio, arcoventure.studio.