Core concepts
Learn the Blue model from exact connected content through deterministic execution, provider-backed coordination, authority, and document networks.
Each concept page answers one question and preserves the boundaries that make the wider system understandable. Read in order for a complete learning path, or open the concept required by the solution you are designing.
Foundations#
Understand what a Blue document is before adding execution or coordination.
Execution#
Turn one document state and one eligible event into one deterministic result.
Coordination and authority#
Connect deterministic processing to independent people, providers, institutions, and agents.
Timelines, providers, and completeness
Attribution, multi-provider windows, deterministic ordering, feeders, checkpoints, and replay.
Mandates, agents, and KYA
Bounded delegation, exact state at the action time, revocation, and operation-level agent admission.
TrustProviders, trust, and safe failure
Provider-specific claims, withheld versus deferred, evidence, disputes, privacy, and explainable non-action.
Systems#
Compose the pieces into practical applications without creating a distributed monolith.
Reading rule: When two concepts appear similar, keep them separate until the documentation explicitly connects them. Content identity is not actor identity. Attribution is not authorization. A Request is not a Response. A payment request is not payment truth. MyOS is not Blue.