MyOS, other portals, and certified operators
MyOS can be the first complete portal and operator experience while banks, platforms, providers, and agents retain their own interfaces and trusted roles.
Portal versus substrate#
A portal owns the user experience, customer relationship, notifications, local policy, and attached products. The substrate provides document identity, sessions, state lineage, Timeline and feeder integration, processing, Mandate verification, provider evidence, storage, availability, and audit.
One company may operate both in an initial deployment, but the protocol should not confuse them.
Participant-specific views#
MyOS may show an Order as a workflow with required confirmations. A bank portal may show the financing approval. A courier interface may show delivery tasks. A legal service may show Requests awaiting response. An agent runtime may see only machine-oriented operations and messages.
These views do not need identical layouts or fields. They need to refer to the same logical document lineage and contribute valid provider-backed actions.
The operator questions serious platforms ask#
- Who runs Timeline and session services?
- Who retains evidence and for how long?
- Which providers and assurance profiles are accepted?
- Can the portal switch operators?
- How are keys, registries, and processor versions managed?
- What are the SLA, audit, recovery, and incident obligations?
- Can the operator censor, delay, or inspect content?
- How are export, disputes, and failover handled?
Certified operator model#
A credible model separates:
- portals — business surface and customer relationship;
- operators — feeders, sessions, storage, processing, Mandate resolution, provider integrations, audit, and SLAs;
- protocol and registries — exact meaning and portable processing dependencies;
- providers — identity, external facts, service outcomes, and payment evidence.
Open protocol does not automatically create neutrality. Multiple operators, independent verification, portable evidence, export, and governance are the mechanisms.
The two-portal proof#
The most efficient demonstration is a payment approval shown in MyOS and a bank portal. The principal acts in the bank interface. The bank Timeline provider records the action. The PayNote changes. MyOS updates. The audit explains the provider and eligibility path.
That one minute shows shared state, portal independence, institutional trust, and deterministic consequence more clearly than a long architecture slide.