Evidence Packets
REST-first workflow for agents that assemble evidence from verified records.
An evidence packet is a machine-readable artifact an agent can assemble from PacSpace records. It helps a vendor, customer, middleware, or support workflow review a question in the vendor's own channel by checking shared evidence.
PacSpace does not host the question lifecycle or accept outcomes.
Agent Workflow
- Fetch the customer live record.
- Fetch the relevant period or compare two periods.
- Export the evidence bundle when full context is needed.
- Attach the evidence packet to the vendor's support workflow.
- Let the vendor, customer, or middleware decide the next step outside PacSpace.
REST Resources
| Resource | Purpose |
|---|---|
/api/v1/middleware/customers/:customerId/live | Current Shared Record state |
/api/v1/middleware/customers/:customerId/period/:checkpointId | Closed period detail |
/api/v1/middleware/customers/:customerId/compare | Difference between two periods/checkpoints |
/api/v1/middleware/customers/:customerId/export | Evidence bundle |
/api/v1/middleware/customers/:customerId/close-package | Finance-ready package |
Packet Contents
A packet should include:
customerIdcheckpointIdor period scope- Verification reference (record root)
verificationReference- Selected record manifest
- Unit labels and recorded values needed for checking
- Actor type and actor reference
- Evidence timestamps
Neutrality Rules
Agents should say "matches the verified record" instead of making a final judgment. They should route questions through the vendor's own support channel instead of implying PacSpace accepted or resolved the result.
See also: