Why You Need MyOS

Blue already gives you deterministic documents that any compliant processor can run.

MyOS supplies the day-to-day infrastructure around those documents — private timelines, ordered event delivery, user interfaces, and optional platform services such as payments and cross-agent calls.

1. Core capabilities and where to learn more

Capability	What MyOS contributes	Further reading
Timeline automation	Creates and permissions timelines from simple MyOS Account references; no manual key-management or event sequencing code.	Timeline Management
Document processors ("agents")	Hosted Blue engines with web UI, chat, and webhook outputs.	Quick-Start
Blink assistant	Natural-language interface; explains documents, turns chat into operation calls.	Built-in Platform Agents
Custom UI tabs	Recognises standard operation sets (e.g. Online Lessons Operations) and renders a task-specific dashboard.	Assistant Agents
Agent marketplace	Optional listing; users still need explicit access grants before invoking operations.	Assistant Agents » Publishing
Access management	UI and contracts for Account → Agent and Agent → Agent permissions, with conditions encoded in Blue.	MyOS Agents
Agent-to-agent calls	Call Agent workflow step for synchronous operation invocations inside the platform.	MyOS Agents » Calling Operations
Payment & offer services	Paula (payments) and Ophelia (offers) agents; package operations into sellable products.	Assistant Agents
Workspaces	A workspace is a Blue document pre-loaded with Chat Ops, Access Management, and Subnodes contracts; useful for multi-party projects.	Quick-Start » Adding to Workspaces

2. How MyOS works for you

2.1 Timeline management

MyOS automatically handles timelines across accounts, making event coordination between parties straightforward. When you create a document with account references:

contracts:
  alice:
    type: MyOS Account
    email: alice@example.com
  bob:
    type: MyOS Account
    email: bob@example.com

At runtime MyOS:

• Allocates a private timeline for each account
• Records its real ID inside the running document
• Guarantees that authorised processors always see a complete, ordered view

This eliminates the need for complex timeline management code.

2.2 Document processing paths

Role	Typical path
Developer	POST YAML to /agents, receive webhooks for every change. See Warm-Up Example in the Quick-Start.
Business user	Create a document in the web interface or convert an existing agreement with Blink's help. Walk-through in B2B Agreement Conversion (link forthcoming).

2.3 Event coordination

For your own document processors leveraging MyOS for event handling, create a /timeline-group with your relevant timelines. MyOS will deliver events through webhooks while maintaining consistent state and order as a single, deduplicated event feed that external engines can replay.

2.4 Service integration

Publish your API as an agent:

1. Write a Blue document with operations that map to your endpoint
2. Install it as an agent
3. Share it with partners via access-grant documents

Examples:

• Teaching service in Alice and Bob Lesson

Enterprise AI agents follow the same pattern; see MyOS Chats for custom UI approaches.

3. Agent interaction inside MyOS

Blue itself is deterministic and decentralised. Within the hosted environment agents can also listen to, or call, other agents:

# Listen
supportChannel:
  type: MyOS Agent Channel
  agent: customerSupport
  event: { type: Ticket Closed }

# Call
- type: Call Agent
  agent: paymentProcessor
  operation: capture
  params: { amount: 120, currency: USD }

Access is controlled by dedicated Blue documents:

• Account-to-Agent Access Grant – permits a user to invoke selected operations
• Agent-to-Agent Access Grant – permits one processor to call another, subject to conditions (balance > 0, specific data present, etc.)

These documents are optional; if omitted, agents remain isolated and purely deterministic.

4. Trust model in detail

Running on MyOS entrusts the platform with four responsibilities:

Responsibility	What MyOS does	How you can verify
Timeline custody	Stores entries in hash-chained order; enforces declared visibility.	Compare entry hashes with external copies; inspect access logs.
Contract execution	Runs documents exactly as written; supports all mandatory and widely-used contract types.	Re-process the same event log on an independent engine; compare BlueIds.
Event delivery	Publishes processor-emitted events to timelines or webhooks without loss.	Check that each emitted event's hash appears on the target timeline.
Permission enforcement	Applies Account→Agent and Agent→Agent grants; rejects unauthorised calls.	Review the audit stream of successful and denied invocations.

For external assurance, embed a MyOS Event Monitor that republishes chosen events to a timeline owned by a neutral party (e.g. Stripe or a regulator). Monitors themselves are Blue documents, so their guarantees are transparent.

5. Illustrative scenarios

• Warm-Up Counter – minimal agent demonstrating timeline creation, chat operations, and a simple increment workflow.
• Online Lessons service – combines Online Lessons Operations with Access Management; MyOS adds scheduling and payments UI.
• E-learning resale agreement – standalone document tracking bookings, revenue share, and termination between two organisations.
• Xavier–Alice collaboration – marketing agent links to teaching agent via an Event Monitor and recurring payment document; illustrates cross-agent calls and external timeline publication.

6. When MyOS is a good fit

Situation	Benefit
Non-technical participants	Blink explanations, natural-language chat, ready dashboards.
Rapid SaaS offering	Avatar, marketplace listing, built-in payments and offers.
High event volume	Managed coordinators and consolidated webhook streams.
Multi-agent orchestration	Call Agent steps avoid bespoke API gateways.
Enterprise AI tooling	Host AI agents that interact with partners through the same Blue language.

You can move documents freely: develop on MyOS, export to a private processor, or mix hosted and self-hosted engines inside one arrangement. The choice depends on how much infrastructure you wish to operate yourself.

7. Financial platform capabilities

MyOS is a next-generation financial platform designed to transform money movement.

For financial institutions: See how payment gateways can enhance their APIs with conditional payments and advanced workflows in our Payments section.

For solution builders: Incorporate these financial services directly into your Blue documents and MyOS agents to create unique payment flows, conditional transactions, and multi-party agreements that were previously impossible to implement without extensive custom development.