Ivory · Ask Ivory
Natural language in. A reviewed, audited action out.
Ivory is the conversational operational interface inside Smoke Alarm. Ask it what is on the shelf, what a rule says or why a finding fired and it answers from the operation's own records. Ask it to change something and it structures the request, validates it against the same rules the screens use, and shows a card a person must approve before anything is committed.
Ivory · AI assistantAsk Ivory · Evergreen Dispensary (simulated)
Simulated- Why is line 4 of manifest 0000123456 on hold?
- Line 4 (Blue Ridge 3.5 g) arrived 38 of 40. The receiving rule for a short delivery held it and opened case DC-0412 for the receiving manager. The two units are not in inventory.from get_manifest · list_receiving_exceptions
- Accept the 38 that arrived and note the shortage against the vendor.
- Approval neededReview
Record 38 received on line 4 of manifest 0000123456, reason “short delivery, vendor case open”. This changes data; nothing runs until you approve.
Illustrative conversationA static illustration of the approval card. In the product the buttons run the action as the person who pressed them and write the audit entry.
Intent → structure → validate → human review → commit → audit.
Ivory is not an autonomous agent over regulatory records. Every request follows the same six steps, and the fourth one is a person.
- 01
User intent
A question or an instruction in plain words, typed or dictated. Ivory works for the people running the shop: receiving staff, managers, owners.
- 02
Structure
The request becomes a named tool call with explicit inputs: which manifest, which line, which quantity. Nothing is inferred from memory; every fact comes from a tool run against the service layer.
- 03
Validate
The same role checks and rule pack the screens use decide what the person may do and what the rules say. Ivory quotes the computed outcome and the rule it cites; it never decides a variance itself.
- 04
Human review
ReviewAnything that would change data stops here as an approval card that says plainly what will happen. The person approves or declines; declined actions are recorded too.
- 05
Commit
VerifiedAn approved action runs as the person who approved it, under their permissions, and Ivory continues from the result. Nothing runs twice, and nothing runs without the card.
- 06
Audit
Every tool run is stored with its inputs, its result, who approved it and when, and the consequential ones are written to the audit log beside every other decision in the operation.
Sixty-two tools, one approval gate.
Ivory is live inside the app as Ask Ivory. It reads widely and proposes narrowly; the list on the right is everything it can change, and each item waits for a card.
Ivory reads
- Locations and each one's connection status
- Inventory search and a package's eligibility to be sold, with the rule it cites
- Findings, investigations and recent movements
- Manifests, their lines and open receiving exceptions
- Supplier scorecards and shrink patterns
- The receiving rule pack, explained line by line
- The knowledge library: Metrc, New York guidance, point-of-sale manuals
- Setup status, connection readiness and a walkthrough of each screen
Ivory proposes, a person approves
- ReviewRecord a received quantity against a manifest line
- ReviewHold a receiving line, or approve a receiving exception
- ReviewCommit a manifest into inventory
- ReviewAcknowledge a finding or open an investigation
- ReviewChange the receiving variance threshold
- ReviewRun an analysis or a clearly labelled demonstration
- ReviewRecord business details, a location, the point-of-sale system in use, notification recipients
- ReviewTest a connection, or switch a location from the simulated to the live Metrc adapter
A conversational interface over the operation's own records; anything that would change data waits on a card for a person's approval, and nothing it does can write to Metrc.
Speak instead of type, through the browser's own speech recognition; the words are shown before anything is sent.
The conversational interface into the same engine.
Smoke Alarm doesn't just find discrepancies. It investigates them, determines the safest correction, prepares the fix, explains exactly what it intends to change, and executes only after authorized human approval.
Ask Ivory why, and it answers from the records. Ask it to prepare the fixes, and the Remediation Engine prepares them the way Fix Me does: the evidence, the expected before and after, the risk class, and an approval card a manager presses before anything runs. Reconcile finds it. Autopilot fixes it.
Ask Ivory · Reconcile Pro with Autopilot
Preview- Ivory, why are we off by three units?
- I found three discrepancies. Two appear to be failed Metrc submissions and one appears to be a receiving error. I can prepare corrections for the first two. The receiving discrepancy requires a physical package count.from the findings, the Metrc queue and the manifest
- Prepare the fixes.
- Two corrections prepared, each with its evidence, its expected before and after, and the Metrc receipt it would submit. Both need manager approval. The receiving discrepancy is waiting on a count. Nothing runs until you approve.
- Approval needed · two correctionsReview
- FIX ME Metrc receipt for a sale that timed out · L3 · Manager approval required: an authoritative inventory quantity or a regulatory record would change.
- FIX ME Metrc receipt for a second sale that timed out · L3 · Manager approval required: an authoritative inventory quantity or a regulatory record would change.
- NEEDS INFORMATION Receiving discrepancy · a physical package count is needed before a correction can be prepared.
IllustrationA static illustration of the exchange. Every consequential change waits for a person: the manager reviews each prepared correction, then approves, and the approval is recorded with role, device and time.
Smoke Alarm investigates a discrepancy, determines the safest correction, prepares it, explains exactly what it intends to change, and executes only after a named person's approval, with six records kept for every fix.
Waiting on: Running on test and pilot locations; no customer location has used it yet.
On a discrepancy case: a planner model proposes the correction, a second model verifies it, a person approves it, and the approved actions run through the write ledger and are read back.
Waiting on: Running on test and pilot locations; no customer location has used it yet.
How Fix Me worksAI may investigate, reason, recommend, simulate and prepare. Humans authorize consequential changes. Smoke Alarm records both.
What Ivory will not do.
The limits are in the code, not in a policy document.
Never autonomous over regulatory records
Consequential actions require an explicit approval card and are written to the audit log. Ivory cannot approve its own proposal, and a declined card is recorded with the reason.
Never writes to Metrc
Nothing Ivory does can write to the state tracking system, and it never promises that something was reported to a regulator. Metrc writes have their own ledger and their own approvals.
Never a place for secrets
Ivory never asks for an API key or a password in conversation. It opens a secure form instead, and only ever learns that a key is stored and its last few characters.
Never a stronger claim than the source
Regulation is quoted as written and cited by document. Any question touching inventory-discrepancy rules carries a standing flag that a person must review the answer before acting on it.
Dictation shows the words first
Speaking instead of typing uses the browser’s own speech recognition; the words appear in the composer before anything is sent, and nothing spoken goes anywhere until the person sends it.
Not a data-entry robot
Ivory works at the package level with the records the operation already keeps. It does not track plants, enter records from photographs or bulk-import a grower’s upstream records.
When no model is configured or its quota is exhausted, Ivory says so plainly instead of guessing. Advisory explanations of findings are labelled advisory; the arithmetic behind every finding is deterministic and never done by a model.
Ask it something about a real manifest.
Twenty minutes with Ken and Charles. Bring a manifest or a finding that bothered you and watch Ivory answer from the record, then propose the fix for you to approve.