Coordination and Timelines
The external coordination layer for Messages, Requests, Responses, actors, sources, Timeline Channels, provider-backed history, completeness, feeders, and document interaction.
What it answers#
Coordination answers: who or what acted, through which provider-backed history, in what safe order, through which document role, and with which message?
It also defines typed communication patterns and the service protocols that connect separate documents.
Key concepts#
- Timeline — one provider-backed append-only perspective;
- Timeline Entry — the attributed envelope around one business Message;
- Actor — the person, organization, service, or agent the provider attributes;
- Source — the browser, API, device, document request, or other submission mechanism;
- Timeline Channel — binds a Timeline and Actor to one role in a document;
- Message — threadable, addressable content;
- Request and Response — exact causal service communication;
- Operation Request — an invocation that names the effective channel and operation;
- Feeder — closes complete windows, orders entries, verifies eligibility, and invokes the processor.
Current Timeline architecture#
Within one Timeline, a provider assigns at most one entry to a microsecond. The timestamp is therefore the strict internal order. Across independent Timelines, equal timestamps are resolved by a published deterministic rule using stable identities.
A provider must close history through a binding completeness or finality frontier before the feeder can safely process the window.
Multiple providers#
One Root may use MyOS, bank, government, KYA, service, and blockchain-backed channels simultaneously. Provider identity remains visible. The package does not pretend those institutions make equivalent claims.
Package status#
Coordination concepts have implemented subsets and active repository types, while the wider Timelines, provider, feeder, Mandate integration, and portal architecture continue to evolve. The v1.3 white paper is the current explanatory architecture; canonical package content and specifications remain the exact source for released types.