Glossary
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.
Why it matters for reconciliation: a proposal makes a change reviewable before it exists. It carries its evidence, the rules applied and the facts it assumed, so an approver can see why it was drafted and the audit trail can show what was decided.
Example: a proposal for a credit memo is Proposed, then Reviewed by a second person, then Approved. Before it executes it is revalidated against its precondition hash. If a fact changed in between, it becomes Superseded and is drafted again instead of being executed on old data.
Where this comes up on budally.com
- Metrc for dispensaries: what it records, and how a store reconciles against it
- How to get NMS2S expanded API access: CCD's validation process, step by step
- The NMS2S API for dispensary software: what exists, what it supports, how access works
- White-label menu & branded app
- Loyalty & wallet
- Digital manifests & self-delivery
- Supply chain & purchasing
- Compliance invoicing & accounting
Related terms
- Approval queue
The single list of proposals waiting for a human decision, filtered by store, module and role. There is no 'approve all'. Executed items run under the approver's own POS or state-system credential and are logged.
- 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.
Terms that refer here
Agent (BudAlly),Approval queue,Audit trail,Precondition hash,Superseded