Decision Reconstruction Manifest
The Decision Reconstruction Manifest describes the information a separately governed record-review artifact would need to preserve: source identity, review conditions, chronology, provenance, integrity metadata and human-review status.
What the Manifest does
Pins the evaluation
Documents the methodology, codebook, Manifest format, and provenance fields required to interpret a future review artifact.
Preserves the result
Defines a portable structure for five condition results, routing vocabulary, warnings, and a human-review requirement.
Supports later verification
Uses an input hash and a canonical Manifest hash so later reviewers can check correspondence and detect alteration.
Describes a future storage boundary
A future authorized implementation would require a separately approved storage, retention, and access design. JRS is not presented as a public repository for records.
Record-review information model
A reconstructable review record would identify the reviewed material, the applicable method, the evidence considered, the disposition of each condition, and the responsible human reviewer. This description is not a report of an operational deployment or a public assessment service.
Minimum field groups
| Group | Purpose |
|---|---|
manifest_id, created_at | Identifies the artifact and creation time. |
manifest_version, jrs_version, codebook_version | Keeps the artifact, methodology, and rule versions distinct. |
input | Records the input hash, algorithm, length, and truncation state without requiring the underlying record to be embedded. |
condition_vocabulary, conditions | Declares which condition-key vocabulary is used and records all five results. |
routing | Records both the routing value and the vocabulary used to interpret it. |
human_review | States that human review is required and gives the reason. |
content_class | Declares whether the artifact contains no record content, derived record content, or the record itself. |
integrity | Records the canonicalization method, Manifest hash, and optional signature metadata. |
Integrity and hashing
The input hash allows a holder of the original record to test whether it corresponds to the evaluated input. The Manifest hash is computed over the canonical form of the artifact, excluding the integrity object itself. A changed routing result, version, condition, or input hash therefore changes the Manifest hash.
Human review requirement
Version 1.0 requires human_review.required. The Manifest format is not validated for autonomous consequential-decision use. A Manifest records a documentation evaluation. It does not decide whether the underlying decision is correct, lawful, compliant, or professionally justified.
Future storage boundary
The specification is designed so that a future authorized implementation could preserve evidence-artifact information without making JRS a public repository for the underlying record. No such implementation, data flow, retention practice, or integration is authorized or represented as available on this site.
Limitations
No legal conclusion
The Manifest does not establish admissibility, legal sufficiency, compliance, certification, or defensibility in law.
No autonomous decision
The Manifest preserves a review result. The responsible human or organization retains authority over the consequential decision.
Derived content may remain sensitive
Condition notes and remediation text can paraphrase the evaluated record. The content class must identify that risk.
Vocabulary remains explicit
Review-condition terminology must be explicitly identified and kept consistent with the publication actually applied. Unverified mappings must not be treated as authoritative.
Publication boundary
This explanatory page does not grant software, derivative, trademark, commercial embedding, exclusivity, or transfer rights. It does not authorize submission of confidential records to this website.