Problem
DRS needs a real offline evidence story, but the first version should be boring and machine-readable. PDF, ZIP, and web UI can wait. The useful first step is a stable JSON export an auditor or operator can keep and re-check later.
What to do
Build a JSON-first evidence export for a stored chain or supplied bundle. Include:
- original receipts
- decoded claims
- verification result
- timestamp metadata when present
- enough metadata to re-run verification later
Acceptance criteria
- export has a versioned JSON schema
- export can be re-verified without relying on application logs
- tests cover valid, revoked, and timestamped chains
- docs explain when to use export vs live
/verify
Out of scope
- PDF generation
- web UI
- chain visualization
- compliance-specific templates
Problem
DRS needs a real offline evidence story, but the first version should be boring and machine-readable. PDF, ZIP, and web UI can wait. The useful first step is a stable JSON export an auditor or operator can keep and re-check later.
What to do
Build a JSON-first evidence export for a stored chain or supplied bundle. Include:
Acceptance criteria
/verifyOut of scope