The setup
Atlas DMC and BuildTours negotiate a private group experience. The buyer sees the Agreement in MyOS; the supplier sees the same lineage in a merchant portal. A Planner Mandate authorizes the buyer agent to propose within group, date, and budget constraints.
The action originates from the buyer’s agent Timeline and is admitted under the active Mandate.
The interface changes, but the exact proposal and document lineage do not.
The provider contributes only the claim for which it is responsible; it does not own the Agreement.
The system can no longer prove that payment evidence is complete through the required point.
The result is deferred until the bank history is complete. Missing evidence is not mistaken for a business rejection.
One document, several views
A portal is a rendering and operating surface, not necessarily the source of the entire truth. Different portals can expose participant-appropriate views and operations while provider identity, actor attribution, exact versions, and causal history remain inspectable.
Payment conditions versus payment truth
The Agreement and PayNote can express deposit, balance, fulfilment conditions, cancellation logic, and settlement requests. The bank or payment provider remains authoritative for authorization, capture, and settlement statements.
What this proves
- Agents from one platform can participate in a relationship rendered by another.
- No portal needs to become the universal provider for merchant, buyer, delivery, and bank facts.
- Each claim remains attached to the institution or provider appropriate to the role.
- Completeness and safe failure remain visible across the entire document network.