What is OneRoute?

Performs a direct intervention that changes the state of something. Used when an agent actively causes an outcome.

Represents a rule-driven transformation where inputs change according to defined logic or natural laws, without discretionary judgment.

Captures the act of monitoring or detecting conditions without altering the system. Used to gather information needed for awareness or decisions.

Represents the passage of time while a change unfolds, typically tied to duration or external progression rather than active control.

Represents passive readiness while awaiting a triggering condition or cue, without acting or advancing time intentionally.

Marks the moment a recognizable condition or signal indicates it is time to transition to the next step.

Represents a judgment point where an outcome is selected based on criteria, rules, or situational context.

Defines an allowable variation within a step that modifies execution without creating a separate branch in the flow.

Indicates that a prior step or sequence should be performed again until a defined condition is met.

Represents gathering, organizing, or validating materials, data, or prerequisites needed before execution can proceed.

Represents setting up, configuring, or verifying the tools, systems, or capabilities required to perform an action or process.

Represents multiple actions occurring together as a single coordinated step when separation would reduce clarity or usefulness.

Marks the entry point into a linked or nested sub-flow that operates as part of a larger sequence.

Marks the return point from a sub-flow back into the main sequence, preserving continuity of execution.

Represents the formal completion of a flow, where outcomes are finalized and no further steps follow.

The OneRoute Principles define the core rules that keep routes clear, consistent, and structurally sound.
Each principle enforces a specific constraint — ensuring steps are unambiguous, time and events are explicit, branching is visible, and structure reflects reality rather than assumption.

OneRoute provides a step-by-step grammar for describing how reality unfolds across work, systems, and natural processes.

Operators capture what changes between steps, not why it happens or who intends it.

All sequences can be described using a fixed set of 15 operators — no custom step types required.

Every step must map to exactly one operator so behavior, timing, and structure remain explicit.

Action represents intentional effort that directly changes the state of a system.

Process represents transformation that occurs without active intervention once initiated.

Observe captures sensing or awareness without judgment, decision, or action.

Each step must represent only one operator behavior — mixed behaviors must be split into separate steps.

Whenever progress depends on time, it must be explicitly modeled rather than implied.

Whenever progress depends on an event or condition, it must be explicitly modeled as a Cue.

Movement between steps must always be justified by a defined operator.

All variation in a route must be explicitly represented as branching.

All loops and rework must be treated as intentional structure, not error.

Parallel work must be explicitly bounded and returned using Bridges.

System behavior emerges from route structure, not individual effort.

Every route must define a clear and explicit end state.

Routes must be recorded exactly as they occur before judgment begins.

Operators remain constant across people, systems, and natural phenomena.

OneRoute provides a clear lens for seeing how reality truly unfolds.