Problem
DRS has strong verification and storage layers, but no user-facing tool for inspecting stored delegation chains. Operators and auditors cannot easily browse, search, or understand the delegation history without reading raw JWT strings.
Proposed Solution
Build an audit explorer with two interfaces:
- CLI command (
drs audit explore) — queries the verification server's store and displays chain details in a human-readable format
- Web UI (optional, served by drs-verify) — a minimal single-page interface for browsing stored chains
Acceptance Criteria
Relevant Files
drs-sdk/src/cli/commands/audit.ts — existing audit CLI command to extend
drs-verify/pkg/store/store.go — store interface for reading receipts
drs-verify/cmd/server/main.go — server to add optional web endpoint
Implementation Notes
Start with the CLI command. The web UI can be a follow-up. The CLI should work against any drs-verify instance via HTTP.
Problem
DRS has strong verification and storage layers, but no user-facing tool for inspecting stored delegation chains. Operators and auditors cannot easily browse, search, or understand the delegation history without reading raw JWT strings.
Proposed Solution
Build an audit explorer with two interfaces:
drs audit explore) — queries the verification server's store and displays chain details in a human-readable formatAcceptance Criteria
Relevant Files
drs-sdk/src/cli/commands/audit.ts— existing audit CLI command to extenddrs-verify/pkg/store/store.go— store interface for reading receiptsdrs-verify/cmd/server/main.go— server to add optional web endpointImplementation Notes
Start with the CLI command. The web UI can be a follow-up. The CLI should work against any drs-verify instance via HTTP.