How MyOS relates to Blue
Blue defines portable documents and processing semantics. MyOS provides one practical portal, Timeline and session environment, operator path, and product experience.
Blue and MyOS solve different layers#
Blue defines the open content and coordination model: typed documents, BlueId, Contracts, BEX, Timelines, Messages, Mandates, and reusable packages.
MyOS turns those ideas into an operating environment for people, businesses, agents, and service providers. It can manage document sessions, participant experiences, user actions, Timeline entries, processing, subscriptions, bootstrap, Mandate workflows, and provider integrations.
The product can combine several roles, but the architecture should keep them conceptually visible.
Portal#
The portal renders participant-appropriate views and captures user intent. A merchant may see orders and fulfilment. A consumer may see approvals and payments. An operator may see missing confirmations. An agent consumes structured operations and messages.
Timeline provider#
A MyOS Timeline can record attributed principal, agent, service, and document-session actions. It assigns provider timestamps, maintains history, and can expose fast completeness for the contexts it operates.
MyOS is not automatically the provider for bank settlement or official public facts. A document can include those providers directly through other Timeline Channels.
Operator#
An operator can run feeders, sessions, storage, processing, subscriptions, bootstrap, Mandate resolution, audit, and failover. MyOS may act as a first/default operator, but open architecture requires export, exact identities, verifiable processing, and the possibility of other operators.
Mandate guarantor and intermediary#
In MyOS-hosted authority flows, MyOS Admin may confirm a Mandate or perform a provider-mediated operation call when an active matching Mandate permits it. The target feeder still verifies the resulting action independently.
Document and session services#
MyOS can bootstrap documents, establish participant mappings, initialize processing, maintain state lineage, expose related documents, and deliver selected subscription updates.
The initial document identity, current state BlueId, and session/epoch progression are different concepts even when MyOS displays them as one continuous business object.
One document, several providers#
A MyOS-operated Order may still contain a bank Timeline for payment, a government Timeline for a permit, a KYA Timeline for an agent, and a courier Timeline for delivery. MyOS coordinates the experience; it does not need to translate every claim into a private MyOS-only truth.