Decision Provenance Standard™ v1.3 · Reading Edition (rev. 11)

Optional Extensions

An optional extension is an addition that sits beside the Standard without changing it. This page lists the extensions the Steward has added to this site so far. The standard repository may hold others while they are under review.

An extension is not part of the Standard. Its requirements bind only an implementation that says it uses that extension, at that version. It does not change what a core field means or when one is required, and where an extension and the Standard's text disagree, the text governs. Extensions are not part of the Standard's releases: they are not in its downloads, bundles or checksum lists. Using one makes no one certified, compliant or approved.

Portable verification 0.3.0

How to export sealed decision records so that someone else can check them, and how that check reports what it found. It adds two objects beside the records, an export and a verification report, and adds no field to a decision record. A signed entry's signature is the organisation's seal from the signatures extension, so a signature copied onto another entry fails the check. The export may also be sealed as a whole, by a document beside it. In 0.3.0, a timestamp gives an entry a time only when the entry's own signature checks out, including the state of the issuer's key when it signed.

Action binding 0.3.0

For a decision that authorises an outside action, such as a payment or a message to a third party. It says how to record the action that was approved and the action that was carried out, and how a check reports what it found. It adds two objects beside the record, an attachment and a verification report, and adds no field to a decision record. In 0.3.0, a signed attachment's signature is the organisation's seal from the signatures extension, so a signature copied onto another attachment fails the check. Version 0.3.0 can also record a standing approval, added after review with nothing newly required: a named person approves bounds once, such as an operation, a target, a number of requests and a period, and requests inside them need no review of each. The check then shows only that each request the attachment records stayed inside those bounds. It does not show that anyone looked at a run, and a standing approval approves nothing in any legal sense. A matching digest shows only that both stages name the same bytes. It does not show that the reviewer read them, that the action was right, or that the named person acted. Like the records, the attachment is input, not evidence.

Anchoring 0.2.0

How to anchor sealed decision records with evidence from outside the issuer, and how a check of that evidence reports what it found. It defines two assertions: an independent timestamp, which shows that exact bytes existed by a time or, for an OpenTimestamps proof, that they existed before a block was mined, and an independent checkpoint, which fixes a chain of records at one point. Each is an object beside the export or the records, and neither adds a field to a decision record. A verified RFC 3161 timestamp shows only that the bytes existed by that time, according to an authority the verifier trusts. It does not show when the decision was made. A timestamp may instead be an OpenTimestamps proof, anchored in the Bitcoin chain. A verified proof shows only that the bytes existed before the block it names was mined, according to a block header from the verifier's own source, never from the attachment. It shows no time: a block's time is only the miner's statement. A matching checkpoint shows only that the export's first entries are the ones the issuer had committed when the checkpoint was made, not that the issuer recorded every event. Neither shows that a record is true, complete or lawful. A checkpoint is independent only when the verifier gets it from a source its own trust policy lists for that chain, never from the export or the attachment. Every source of trust comes from that policy. A checkpoint source may also be a SCITT transparency service (RFC 9943), which gives the checkpoint as a signed statement with the service's receipt. Only a statement the verifier selects from the service itself is independent, never one the issuer supplied or pointed to. A verified receipt shows only that the service's key signed that the statement is in its log, not when it was registered, that the log was never rewritten, or that the service showed everyone the same log.

Signatures 0.2.0

How a person signs what they decided, how an organisation signs exactly what it issued, and how a check of those signatures reports what it found. It defines two assertions: the person's signature, made by the person who gave an outcome, approved bounds once or affirmed a record, over what they decided, and the organisation's seal, made by the issuer over an export, an action binding attachment or a record. Each is an object beside the records, the export or the attachment, and neither adds a field to a decision record. A verified person's signature shows only that the holder of a key signed these bytes, with this outcome. A signature over bounds shows nothing about the requests made under them, how many there were, or that the bounds were in force at any time. A verified seal shows only that the holder of the organisation's key issued these exact bytes. Neither shows that a record is true, complete or lawful, that the person read what they signed, or who held the key: only the verifier's own trust policy links a key to a person or an organisation. Whether a signature or a seal has any legal effect is outside the extension.

The rules every extension follows

The standard repository sets these rules for every extension: it is optional, it sits beside the Standard, it has its own version number, it names the release it was written against, and it says nothing about what any law requires. The records remain input, not evidence.

← Back to the Decision Provenance Standard

The records are input, not evidence. The Standard informs frameworks without satisfying them. Conformance is self-declared; no body certifies it. It is not legal advice and not a regulatory substitute.
Decision Provenance Standard™ v1.3 — Reading Edition (rev. 11). Open standard under CC-BY 4.0. Not a certified product. Founding Steward: Yohay Etsion; institutional Steward: Etsion Brands Ltd.