Glossary
Audit trail
The exportable record of every proposal: evidence, confidence, rules applied, precondition hash, reviewer, approver, timestamp and the credential it executed under.
Why it matters for reconciliation: a number that cannot be traced is a number an inspector or a second reviewer cannot trust. When a variance is adjusted, the trail shows what evidence the adjustment rested on, which rules were applied, who reviewed it, who approved it and which credential carried it out. That turns a month-end question such as why this package was adjusted down into a lookup instead of an investigation.
Example: a controller reviewing the 30-day report sees a negative adjustment on one tag. The trail shows the weekly cycle count that found it, the class it was given (process, because a sample was pulled without an adjustment), the reviewer, and the approver who was not the person who proposed it.
Where this comes up on budally.com
- The NMS2S API for dispensary software: what exists, what it supports, how access works
- Integration hub & BudAlly MCP
- Ten weeks after the NMS2S cutover: the year-end inventory audit every New Mexico retailer should run
- A connector is a checkbox. So is a model. Here's what the moat in cannabis retail ops actually is.
- Agents draft, humans approve: what an AI audit trail should actually contain
- Learned rules you can read: how 'tell it once and it remembers' should actually work
- The Metrc discrepancies playbook: the nine mismatches a dispensary sees, what causes each, and the fix that holds
Related terms
- Proposal
What an agent produces: a drafted action with evidence, confidence, rules applied and a precondition hash, in one of the states Proposed → Reviewed → Approved → Revalidating → Executing → Executed → Verified, or Superseded.
- Precondition hash
A fingerprint of the facts a proposal was built on. If those facts change before approval (a price moved, a manifest was edited), the proposal is marked Superseded and must re-run.