Real artifacts, not opinions same input → same output

Examples — what a defensible decision
actually looks like.

This page shows finished RPO artifacts: a canonical JSON structure, a human-readable PDF, and a public SHA-256 hash. These examples do not “prove truth”. They preserve what existed at the time — so decisions remain reconstructable and tampering becomes detectable.

You are not challenged for what you decided. You are challenged for what you cannot reconstruct.

No AI. No hidden ranking. No silent rewrite. If the narrative changes, the hash changes — that’s the boundary.

What this page is

A gallery of finished RPO bundles you can open and inspect. Not a demo of an app — a demo of a trust boundary.

What each example contains

Canonical JSON, human-readable PDF, SHA-256 public hash. Nothing proprietary. Nothing hidden.

What it proves

Reconstructability. If the story changes later, the integrity anchor reveals it.

Example gallery
HR

Promotion decision — March 2024

An internal promotion is challenged six months later: “show the rationale and the chain”. This RPO preserves what existed at the time and prevents silent narrative drift.

  • What existed: approvals, criteria, meeting rationale, exceptions.
  • What is structured: canonical fields, evidence list, narrative block.
  • What cannot be rewritten: the initial state without hash mismatch.
Bundle
rpo-example-hr-promo-2024-03
Integrity
SHA-256
View PDF View JSON
Public hash (placeholder): e.g.-sha256-hex-here
This does not prove truth. It proves integrity and reconstructability.
Governance

Termination decision — September 2023

A termination becomes a liability when the organization cannot reconstruct the decision chain. This example shows how RPO preserves the decision state “as it was”.

  • What existed: documented reasons, approvals, timelines.
  • What is protected: integrity of the narrative and evidence references.
  • What becomes detectable: tampering, omissions, retroactive edits.
Bundle
rpo-example-governance-termination-2023-09
Integrity
SHA-256
View PDF View JSON
Public hash (placeholder): e.g.-sha256-hex-here
Decision becomes defendable because the chain is reconstructable.
Compliance

Internal investigation summary — Q2 2024

Investigations fail in court or audit when the timeline is unclear or “rewritten”. This RPO locks the initial narrative state so later interpretations stay comparable.

  • What existed: allegations, dates/places anchors, evidence pointers.
  • What is canonical: stable fields for issuer, subject, created_at.
  • What remains auditable: transformations and revisions as deltas.
Bundle
rpo-example-compliance-investigation-q2-2024
Integrity
SHA-256
View PDF View JSON
Public hash (placeholder): e.g.-sha256-hex-here
RPO makes later reinterpretation possible without rewriting history.
Operations

Single-source procurement exception — April 2024

Exceptions are where governance breaks first. This artifact shows how a “non-standard” decision stays defensible when the chain remains reconstructable.

  • What existed: exception reason, approvals, constraints.
  • What is stable: the canonical payload and integrity anchor.
  • What becomes accountable: who signed what, and when.
Bundle
rpo-example-ops-procurement-exception-2024-04
Integrity
SHA-256
View PDF View JSON
Public hash (placeholder): e.g.-sha256-hex-here
Same structure. Different decision. Same accountability format.
Board

Board memo — Strategic pivot

When strategy is later questioned, you need the original state: assumptions, inputs, and sign-offs. This example shows how RPO preserves “what was known when”.

  • What existed: assumptions, constraints, risk notes.
  • What is readable: PDF for humans, JSON for verification.
  • What stays comparable: revisions as explicit deltas.
Bundle
rpo-example-board-memo-strategic-pivot
Integrity
SHA-256
View PDF View JSON
Public hash (placeholder): e.g.-sha256-hex-here
The artifact answers one question: “Show me the chain.”
Security

Security incident report — Initial assessment

Incident response is all about timing. This example locks the first assessment state, so later reports can’t quietly overwrite what was initially stated.

  • What existed: first timeline, impact statement, evidence pointers.
  • What is stable: canonical payload + integrity anchor.
  • What is enforced: no silent rewrite of the initial report.
Bundle
rpo-example-security-incident-initial
Integrity
SHA-256
View PDF View JSON
Public hash (placeholder): e.g.-sha256-hex-here
Integrity is measurable. Transformations become explainable.
Compare them

Same structure, different decisions

All examples share the same canonical fields and the same integrity boundary. Different domains, same accountability format. That is the point: you can enforce it across tools, reorganizations, and handovers — without losing reconstructability.