Glossary
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.
Why it matters for reconciliation: changes to inventory, credits and prices are regulated or financial actions, and a single list with a decision on each item keeps a person accountable for every one. There is no approve-all button because that would remove the person from the decision.
Example: a manager opens the queue filtered to their store and the inventory module. Each proposal shows its evidence and the rules applied. The manager approves two, rejects one with a note and sends one back, and each action is logged under their own credential.
Where this comes up on budally.com
- Integration hub & BudAlly MCP
- A connector is a checkbox. So is a model. Here's what the moat in cannabis retail ops actually is.
- Discounts vs repeat rate: run the counterfactual before you add to Q4
- The loyalty gap: where a dispensary loses members between visit two and visit three, and the compliant way to win them back
- BLAZE
- Cova
- Dutchie POS
- Flowhub
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.
- Maker ≠ checker
The control that the person who drafts or configures something cannot be the person who approves it; cutovers and state-system-affecting changes require two different approvers.
- Audit trail
The exportable record of every proposal: evidence, confidence, rules applied, precondition hash, reviewer, approver, timestamp and the credential it executed under.
Terms that refer here
Agent (BudAlly),Drafted N · executed 0,Maker ≠ checker,Proposal