Shared record

What a permitted reader might see when the unit of record is a scoped shared state. Synthetic. Not a live tenant payload.

Section guide: Records. Write sequence: Write path.

What this illustrates

• One shared answer to “where is the record”
• Record scope, not a global dump
• Integrity as a signal (proof available), not a mechanism tutorial
• No real tokens, org names, or production identifiers

Example (synthetic)

{
  "record_kind": "scoped_shared_state",
  "scope_id": "scope_example_001",
  "status": "active",
  "revision": "rev_example_42",
  "updated_at": "2026-08-06T18:00:00Z",
  "summary": {
    "headline": "Example shared operational state",
    "parties": ["org_example_a", "org_example_b"]
  },
  "next_actions": ["observe", "prepare_with_write_pack"],
  "integrity": {
    "proof_available": true
  }
}

Ask whether this picture matches your multi-party problem. Do not codegen clients from it.