OPENPROOF · DOCUMENTATION RPO

RPO v0.1 specification — format guide

RPO (Registered Probative Object) is OpenProof’s public structured-record format. This v0.1 draft describes file fields; it does not provide an account or an analysis service.

Read the reference JSON Schema · Versioned technical guide

What the file contains

`rpo_version · type`

Version 0.1 ; type evidence_bundle.

`bundle_id · created_at`

UUID identifier and creation date.

`issuer · subject`

Issuer and subject, each with name, id and role.

`evidence`

Evidence references; id and type required.

`narrative`

Summary and pdf_hash string required; additional references are optional.

`registry · signatures`

Optional fields. Their presence does not establish verified registration or signatures.

What verification can show

The public check compares the complete JSON object with a retained reference using recursively ordered keys. Changing a value or array order changes the fingerprint. Whitespace and object-key order do not.

Atlas is fictional: its evidence references are illustrative, its PDF is a placeholder and it contains no signatures. The basic checker is not full JSON Schema validation. A matching fingerprint does not establish truth, source authenticity or professional approval.

Try an example

Follow Atlas step by step · Compare a copy with its reference

Technical references are available without an account. To use OpenProof for a real case, start with a pilot request.