This worked example demonstrates proposal, acceptance, action, evidence, Verification, Recognition, Registry publication, standing and Resolution as linked but constitutionally separate events. It is illustrative and creates no real standing.
1. Status and Use
This example is fictional and non-authoritative. It demonstrates a complete record without prescribing a data format or implementation architecture.
2. Scenario
Northbridge Community Health Trust proposes that Meridian Clinical Systems Ltd produce and submit an accessibility-impact review for release 4.2 of an appointment-triage service. Meridian accepts through an authorised officer. A separate evaluator later verifies the record. A separate Recognition authority determines the claim. The Registry then publishes standing.
3. Core Record
| Record ID | ROID:GB-NCHT-RREC-2026-0042 |
|---|---|
| Proposing party | ORG:GB-NCHT-001 |
| Responsible party | ORG:GB-MCS-017 |
| Authority | AUTH:NCHT-CONTRACT-2026-118 §14.3 |
| Defined responsibility | Complete and submit the release 4.2 accessibility-impact review. |
| Intended outcome | Authorised reviewers can determine whether identified accessibility risks were assessed and addressed before release. |
| Proposal time | 2026-06-01T09:00:00Z |
| Due time | 2026-06-15T17:00:00Z |
4. Event History
| Event | Time | Actor | Relationship and material content |
|---|---|---|---|
| EVT-0001 Proposal | 2026-06-01T09:00:00Z | PERSON:NCHT-AO-14 | Creates RREC-2026-0042 under AUTH:NCHT-CONTRACT-2026-118. |
| EVT-0002 Acceptance | 2026-06-01T13:42:11Z | PERSON:MCS-DO-08 | Accepts EVT-0001 without qualification. |
| EVT-0003 Action | 2026-06-10T15:18:02Z | PERSON:MCS-AC-21 | Records completion activity under accepted responsibility. |
| EVT-0004 Evidence | 2026-06-10T15:22:36Z | PERSON:MCS-DO-08 | Attaches EP:2026-0042-01, SHA-256: 45d8…a912, to EVT-0003. |
| EVT-0005 Submission | 2026-06-10T15:25:04Z | PERSON:MCS-DO-08 | Submits the record and evidence for evaluation. |
| EVT-0006 Verification | 2026-06-13T11:06:55Z | ORG:GB-AIE-003 | VR:2026-0042 finds the stated review completion supported within defined scope. |
| EVT-0007 Recognition | 2026-06-16T10:30:00Z | AUTH:RI-REC-PANEL-02 | RD:2026-0042 recognises the bounded completion claim; relies on but does not repeat Verification. |
| EVT-0008 Registry | 2026-06-16T11:02:18Z | AUTH:RIR-PUBLISHER-01 | Publishes RE:2026-0042 from RD:2026-0042; standing becomes ACTIVE. |
| EVT-0009 Resolution | 2026-06-20T08:14:40Z | ORG:GB-NCHT-001 | Resolves RE:2026-0042 as ACTIVE at the stated time. |
5. Evidence Package
EP:2026-0042-01 identifies the artefact, submitting actor, creation and submission times, media type, integrity hash, access restriction and relationship to the Action event. The example does not require the artefact to be stored in the Responsibility Record itself.
6. Standing and Resolution
Recognition is the determination recorded by RD:2026-0042. Standing does not originate at Recognition. It originates when RE:2026-0042 is published by the authorised Registry. The resolved result is time-bound: ACTIVE at 2026-06-20T08:14:40Z. A later suspension or revocation would not erase the earlier resolution.
7. Reconstruction
- Resolve the stable record identifier.
- Confirm authority and the proposed terms.
- Confirm explicit Acceptance followed the Proposal.
- Trace Action and Evidence to the accepted responsibility.
- Inspect Verification scope and limitations.
- Inspect the separate Recognition Decision.
- Resolve the Registry Entry for current Standing.
- Preserve the query time and returned status for the reliance record.
8. Conformance Trace
The example demonstrates CONF-01 through CONF-15. It does not prove that any real implementation conforms and it does not create Recognition, Registry standing or a right to display a conformance mark.
- 2026-08-03Drafted · Version 0.1 Working Draft prepared