Receipts, changes, and history
Use this guide when you need the shortest explanation of what belongs in /guard/receipts, /guard/changes, and /guard/history.
Start with receiptsDirect link to Start with receipts
Receipts are the latest proof objects Guard synced. Open /guard/receipts first when you want to know:
- what Guard saw most recently
- which decisions just landed
- whether sync is actually producing evidence
Receipts answer “what happened now?”
Open changes when something driftedDirect link to Open changes when something drifted
The Changes route exists for approved artifacts that no longer match the last trusted state.
Open /guard/changes when you need to answer:
- what changed after approval
- which artifact now needs another decision
- which item should be reviewed before someone retries it elsewhere
Changes answer “what needs a decision now?”
Use history for longer-term contextDirect link to Use history for longer-term context
History is where you go after the immediate queue is understood.
Open /guard/history when you need:
- a longer timeline for one artifact or trust pattern
- older receipt evidence
- proof that the same drift pattern keeps repeating
History answers “has this happened before?”
Recommended operator loopDirect link to Recommended operator loop
- check Receipts for the latest evidence
- open Changes when a current decision is needed
- move to History only when the short queue needs longer context
- update policy or alerts after a repeated pattern becomes obvious