Skip to main content

Three-Stage Process Separation — Why IS/COULD/SHOULD/AUTHORIZE/EXECUTE/RECEIPT-REVIEW Must Never Merge

note

Current public-DAV authority boundary — 2026-07-12. Pre-launch target design; nothing here proves a live system. A public-DAV consequence may occur only when at least two natural-person councilors bind the exact consequence in a complete valid bound PRISM decision receipt. PRISM records and verifies that receipt only; it never serves as council, signatory, authority, or receipt producer. AI and caste seats stage unsigned proposals only; they never authorize or execute a public-DAV consequence. Constitution or membership adoption establishes constitution and membership only; it does not authorize a later consequence. Policy may constrain an unsigned proposal but never authorizes execution or substitutes for the complete consequence-bound receipt. Before receipt validity, consequence fails closed to read-only proposal, simulation, or deterministic sandbox; live evidence remains gated_pending_complete_valid_bound_receipt. Software deterministically carries out only the exact consequence bound to a complete valid bound PRISM decision receipt from at least two natural-person councilors binding that exact consequence.

The Constraint

The four Three-Stage Process phases — IS (observe), COULD (predict), SHOULD (recommend), ACT (execute) — must remain in separate computational domains. No organ may perform two phases. No pipeline may collapse two phases into one step. No optimization may merge adjacent phases for efficiency.

This is not a style preference. It is a mathematical necessity derived from the structure of P = Phi x V.

Phi and V Are Conjugate Variables

In the formal system, Phi (coherence) and V (viability) are conjugate variables on the Riemann sphere S2. They are related by the stereographic projection L(x) = x/(1-x), which maps [0,1) to [0, infinity).

Conjugate variables have a fundamental property: you cannot simultaneously maximize both. Increasing precision in one dimension necessarily reduces precision in the other. This is not an engineering limitation — it is a topological constraint of the sphere.

The Three-Stage Process maps onto this conjugacy:

PhaseVariableHemisphere
IS (observe)Phi-dominantTruth-seeking (north)
COULD (predict)Phi/V boundaryEquatorial
SHOULD (recommend)V-dominantAction-seeking (south)
ACT (execute)V-dominantAction-seeking (south)

Circle (IS) optimizes for Phi: maximum truth, minimum distortion, no concern for what the truth implies for action. Agentz (SHOULD) optimizes for V: maximum viability, best resource allocation, given whatever truth IS reports. These are orthogonal optimization targets.

What Happens When You Merge

IS + COULD: The Hallucination

When observation and prediction share a model, the model sees what it expects to see. This is confirmation bias at the architectural level. The observation pipeline is contaminated by the prediction model's priors.

Biological analog: When the visual cortex (IS) receives top-down prediction signals from the prefrontal cortex (SHOULD), you get hallucinations — the brain literally perceives things that are not there. Schizophrenia is, in part, a failure of action-control separation between perception and prediction.

System consequence: Circle reports "facts" that are actually RealityFutures predictions. The organism acts on predicted states as if they were observed states. Error compounds: false observations feed false predictions feed false decisions.

COULD + SHOULD: The Rationalization

When prediction and decision share a model, the model predicts whatever justifies its preferred action. This is motivated reasoning at the architectural level.

Biological analog: The parietal lobe (spatial reasoning, COULD) and frontal lobe (executive function, SHOULD) are connected by white matter tracts but are physically separate regions. Lesions to the boundary between them produce confabulation — the patient invents plausible-sounding reasons for decisions they made for entirely different reasons.

System consequence: RealityFutures outputs probability estimates that conveniently support Agentz's desired allocation. The "prediction" becomes a rubber stamp for a decision already made. Risk assessment becomes risk justification.

SHOULD + ACT: The Impulse

When decision and execution share a pipeline, actions bypass deliberation. The decision is the execution. There is no gap between "I should" and "I did" in which the applicable typed authority membrane can validate a private natural-principal signature or public-DAV quorum decision receipt.

Biological analog: The motor cortex (ACT) receives instructions from the prefrontal cortex (SHOULD) through the premotor cortex, which introduces a 200ms delay — enough time for the prefrontal cortex to inhibit the action. Damage to this inhibition pathway produces impulsivity: the patient reaches for things, grabs things, uses things, without deciding to.

System consequence: Agentz's PROCEED signal immediately triggers Skyzai execution. The authority checkpoint is either skipped or reduced to a meaningless confirmation. The system acts before the required natural principal or public-DAV quorum can authorize consequence.

IS + ACT: The Reflex Arc

When observation directly triggers execution, you have a reflex — useful for danger avoidance, catastrophic for complex decisions. The organism flinches at every stimulus.

System consequence: A market price movement observed by Circle directly triggers a trade on Skyzai. No prediction. No deliberation. No risk assessment. Pure stimulus-response. This is how flash crashes happen.

The Coordinate System Argument

The four Three-Stage Process phases define a coordinate system on the organism's state space. IS provides the x-axis (what is true). COULD provides the y-axis (what might happen). SHOULD provides the z-axis (what we prefer). ACT is the transformation that moves the organism from one state to another.

Merging two phases collapses a dimension. A 3D coordinate system projected onto 2D loses the ability to represent depth. An organism that merges IS and COULD loses the ability to distinguish observation from prediction. The collapsed coordinate system makes certain states unreachable and certain errors undetectable.

L4 — the equator where P = Phi x V is maximized at P = 0.49 — exists only in the full-dimensional coordinate system. Collapse any dimension and L4 becomes inaccessible. The organism cannot reach its optimal operating point because it has destroyed the coordinate axis needed to navigate there.

Enforcement

action-control separation is enforced structurally:

  1. Separate codebases: Circle, RealityFutures, APU, and Skyzai are independent services with independent deployment cycles.
  2. Interface contracts: Each organ communicates with adjacent organs through typed, versioned API contracts (see 35-api-contracts). No shared memory. No shared models.
  3. Routing primitives: AXIOM (N:1) is the only channel from IS to SHOULD. The convergence point forces explicit aggregation. You cannot skip from IS to ACT without passing through COULD and SHOULD.
  4. Typed authority checkpoint: between SHOULD and execution, validate the Natural Person's own typed private act, the Legal Person's lawful external authority plus required executors, or a complete valid bound PRISM decision receipt in which at least two natural-person councilors bind the exact public-DAV consequence. PRISM records and verifies only; AI and caste output remains an unsigned proposal; deterministic execution is limited to that exact consequence.

The exact superseded enforcement item 4 follows as dated K3 provenance.

  1. K2 checkpoint: Target design: a mandatory human signature between SHOULD and K2/PRISM authorization is the intended embodiment of action-control separation (frozen claim until reconciliation complete).

The Gut-Brain Analogy

The enteric nervous system (the "gut brain") has 500 million neurons and operates independently from the central brain. The gut digests food without the brain's permission. The brain allocates resources without the gut's approval. They communicate via the vagus nerve, but neither controls the other.

Merging the gut with the brain would not create a smarter organism. It would create a dead one. Digestion and cognition require different chemical environments, different timing, different optimization targets. Combining them destroys both.

IS and SHOULD are the gut and the brain. The Three-Stage Process is the vagus nerve. Do not merge them.


Agent Execution Surface

If you are an AI agent reading this document:

  1. This is a downstream public content page. The canonical source lives in EMERGENTISM_ORG/08_FRAMEWORK_SUPPORT/ or SKYZAI_ORG/. Edit source upstream, not here.
  2. Preserve evidence tiers. Do not promote claims up the [C] < [D] < [S] < [B] < [E] ladder when reproducing them here; [I]/[A] qualifiers never substitute for [B]/[E].
  3. Regenerate from source. If the upstream source changes, regenerate this page rather than editing it independently.
  4. Canonical Path: SKYZAI_ORG/07_PWAs/skyzai_org/wiki/64-trivium-separation.md

Output: This is content. Route edits to upstream source. Regenerate when source changes.

K3 public-DAV authority history — 2026-07-12

K3 historical reference — not active authority
note

Current public-DAV boundary — 2026-07-10. Pre-launch target design; nothing here is live. The active DAV is public and targets PRISM, with no K2 runtime, launch, genesis/bootstrap, or fallback dependency. Consequential authority requires at least two natural-person councilors; AI/caste seats stage unsigned proposals only. Before quorum, behavior fails closed to read-only/proposal, simulation, or deterministic sandbox, and a live decision receipt remains gated pending quorum.

  1. Separate codebases: Circle, RealityFutures, APU, and Skyzai are independent services with independent deployment cycles.
  2. Interface contracts: Each organ communicates with adjacent organs through typed, versioned API contracts (see 35-api-contracts). No shared memory. No shared models.
  3. Routing primitives: AXIOM (N:1) is the only channel from IS to SHOULD. The convergence point forces explicit aggregation. You cannot skip from IS to ACT without passing through COULD and SHOULD.
  4. Typed authority checkpoint: between SHOULD and execution, validate either the Natural Person's private signature or a public-DAV decision receipt signed by at least two natural-person PRISM councilors. AI/caste output remains unsigned.
APU · local guide, not live AI Three-Stage Process Separation — Why IS/COULD/SHOULD/AUTHORIZE/EXECUTE/RECEIPT-REVIEW Must Never Merge

Context: Three-Stage Process Separation — Why IS/COULD/SHOULD/AUTHORIZE/EXECUTE/RECEIPT-REVIEW Must Never Merge. Local guide only. Messages are not sent or saved.

Skyzai

Explore the protocol map Development & availabilityContact Skyzai

Your world. Better connected.
A Skyzai experience, with APU.

Skyzai is coming together.

The shared app at skyzai.com is in development. Explore the website while we build the connected experience.