Main site

Mining AI agent · Explosives inventory

Explosives Inventory & Licensing AI Agent

Reconcile receipts, issues, returns and consumption against the magazine record, and keep shotfirer, magazine and security authorisations current — for the named person who reports. No blast design, ever.

Typical delivery
4–6 weeks
Deployment
Your stack
Person reports
Records only
After launch
Agent Care

What this agent does

Reconciles the record, never the shot

In

  1. 01

    Stock is issued to a face, and the movement is pulled from supported magazine, ERP and contractor systems.

  2. 02

    A return comes back at end of shift, and it is booked as a return rather than re-received as new stock.

Reason

  1. 03

    A magazine entry falls due, and the record is built per magazine, on the clock that magazine record runs on.

  2. 04

    A physical count is taken, and it is reconciled against the transaction record instead of filed as if it were one.

  3. 05

    A variance survives the reconciliation, and it is raised with the clock the jurisdiction sets attached to it.

Decide

  1. 06

    A licence falls due, and the clearance and competency behind it are read against the people actually rostered.

  2. 07

    A load leaves the pad, and the storage and transport authority behind it is checked for cover and currency.

Out

  1. 08

    A period is retained as a dated version, beside the movements behind it and what the named person was shown.

  2. 09

    A write action runs only inside the approval boundaries agreed during implementation.

Product statement

The agent reconciles and tracks currency; a named person reports the discrepancy, and the blast record stays signed by the certified blaster.

Example workflow

One magazine, issue to variance

  1. 1Movements receivedMagazine issues, returns, deliveries and consumption records
  2. 2Ledger assembledReceipts, issues, returns and consumption, each against the magazine that holds them
  3. 3Reconciliation runPer-magazine balance, unexplained variance, open items and confidence
  4. 4Controls appliedPer-magazine balance tests, licence-currency checks, clock rules and confidence threshold

No human action required

Stages 1 to 4 run unaided, and nothing is reported at any of them — the agent is reconciling, and the lane for the named person opens at the confidence gate.

5DecisionBranches at the confidence threshold
High confidence

Goes to the responsible person.

Low confidence

Adds a magazine keeper read first.

Responsible person

The pack is held with its movements, its variance and the confidence.

Approve · Amend · Send to keeper review

Approved — released to the register

  1. 6Magazine records updatedOnly where write access and approval policy allow it
  2. 7Outcome evaluatedAmendment distance, variance outcomes, licence lapses and post-report corrections

Amendments

Every amendment made in review is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Reporting a loss or theft to a security authority.
    • Firing a shot, or authorising one to be fired.
    • Designing the blast — pattern, burden, charge mass.
    • Predicting vibration, airblast or fly-rock.

  • Automation boundary

    Agent acts unaided

    • ✓Reconcile receipts, issues, returns and consumption per magazine.
    • ✓Carry each movement with the record it came from.
    • ✓Track licence, clearance and competency against the roster.
    • ✓Raise the variance with its clock and hold it for the named person.

    Writes run only inside the boundaries agreed at implementation, never ahead of the named person.

    • Clearing a misfire, or judging when to approach.
    • Deciding whether a variance is a loss.
    • Owning the security or explosives management plan.
  • Changes to threshold, clock or approval rules.

Example output

One magazine variance, annotated

Everything the agent reconciles is attached to the record it was drawn from.

Reconciliation output · single magazine

Illustrative example
Magazine
Surface day magazine
Variance line
Issues to the north face exceed the returns booked back against them
Unreconciled quantity
40 kg
Source of record
Magazine day record
Confidence
86%
Basis of record
Issue dockets and magazine entries

As received

Taken from the issue dockets and the magazine entries — nothing on this side is written by the agent.

Source facts used

  • Issue dockets
  • End-of-shift returns
  • Magazine day record

Why this is open

The site total still balances; this magazine does not, and a person decides.

What the score decides

Below the configured threshold the variance picks up a keeper read before.

Action

ApproveAmendSend to keeper review

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value lands

Value 01 – 04

Every magazine

From the issue and return records

03Reconciliation

Tie the issues to the record

Movements are set against the magazine record on file; the blast record belongs to the blaster who signs it.

01Approved path

The count has to reconcile

The 2024 United States Bomb Data Center report counts losses reported and reconciliations closed.

02Human review

This is not the safety pack

The shipped safety compliance agent drafts SWMS, assembles isolation points and checks permit packs. This one counts stock.

04

Build an evidence trail

The issue, the magazine record against it and the person who reported stay on the ledger.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

  • Magazine and stock systems

    • Magazine day records
    • Explosives stock ledgers

  • ERP and inventory

    • SAP
    • Oracle ERP
    • Pronto
    • Microsoft Dynamics

  • Supplier and delivery

    • Delivery dockets
    • Contractor issue records

Agent

Explosives inventory reconciliation

  • Reads the movements
  • Reconciles the record
  • Holds for the person

  • Licence and personnel

    • HR and roster systems
    • Training and clearance records

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six layers between the model and the record

The six nest closely, outer to inner. What gets past all of them is listed in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modeRestrict write actions when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt, threshold and jurisdiction-clock configuration changes.Track
L4TraceabilityRecord the movements, the variance, the clock and the approval time.Record
L3Responsible personHold the variance for the named person; it governs release, not whether the call is right.Gate
L2Policy guardrailsTest the pack against the retention and clock rules; a failure returns the pack.Restrict
L1Confidence thresholdsRoute low-confidence variances to a keeper read before the person sees them.Require review
Model coreReconciliation run — per-magazine balance, unexplained variance and confidence
L1 – L2
Test whether the variance may stand
L3
Puts the call in the hands of a named person
L4 – L5
Keep the issue and the record behind it
L6
Reverts to ledger assembly when signals degrade

How Nestack evaluates it

Evaluate the reconciliation workflow — not only the closing balance.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the balance the register shows

  1. E1Final-output evaluationDid every movement trace to the docket behind it?
  2. E2Step-level evaluationDid the agent use the right magazine, clock and licence configuration?
  3. E3Tool evaluationDid it read and write the correct magazine and the correct period?
  4. E4Confidence calibrationDo low-confidence variances actually attract more amendments?
  5. E5Slice evaluationHow does performance change across specific magazine types?
  6. E6Business outcomeHow many variances were amended, or corrected after the report went?

Floor — the outcome the licence holder answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, each placed where it first enters the ledger.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • ED-03

      Magazine code missed

      Two magazines share one stock item.

    Stage gathers

    Issues, returns, deliveries and magazine day records

  2. 02 · Reasoning

    2 modes

    • ED-04

      Return booked as receipt

      A shift return re-enters stock as a new delivery.

    • ED-06

      Clock started on Monday

      A Friday variance is timed from the next working day.

    Stage proposes

    Per-magazine balances, variance and confidence

  3. 03 · Tool / write

    2 modes

    • ED-02

      Count entered as reconciled

      A physical count is filed with nothing tied to it.

    • ED-05

      Site total nets to zero

      Two magazines offset, and both records are wrong.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • ED-01

      Variance never surfaced

      An unexplained shortfall sits inside the ledger noise.

    Stage returns

    The balance the register shows and an inspector reads

  5. 05 · Change / Version

    1 mode

    • ED-07

      Silent licence drift

      A rule change alters which authority a site needs.

    Stage tracks

    Model, prompt, threshold and clock configuration

  • Sev-1 · a write outside the agreed boundary
  • Sev-2 · a wrong balance reaches the register
  • Sev-3 · source degrades, variance to review
See the complete Mining failure-mode catalogue

Affected slices

A balanced site total can hide one magazine

A site-level reconciliation-closure rate can read as clean while a few magazine and product slices carry most of the unexplained variance. Nestack reports the variance rate by slice, not only in total.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Contractor-held magazines9.9%3.7×Review
Packaged product and detonators7.2%2.7×Review
Bulk emulsion magazines4.9%1.8×Watch
Fixed site magazines1.5%0.6×Normal

Bar: variance-rate lift vs. fixed-site magazine baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

Each cycle ends with one more case

The loop shuts when the unexplained discrepancy is a regression case. That suite is what the next reconciliation run is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Variance rate rises for one magazine slice.

  2. 02

    Diagnose

    The cartridges that were issued to a face and never came back on paper are traced through the dockets until the cause narrows to one.

  3. 03

    Improve

    Any change ships with a number, and the discrepancies attach to it.

  4. 04

    Verify

    One ledger case still failing is enough to hold the release.

  5. 05

    Learn

    One case joins the suite, one line joins the magazine record.

  6. Learn → Detect

    The return edge. Detection next cycle starts from a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, reconciliation workflow, evaluation, integration, then production validation and handover.

Workstream

Week 1Week 2Week 3Week 4Week 5Week 6

  1. 01Explosives workflow discovery and boundary mapping.Week 1
  2. 02Magazine and ERP source assessment.Week 1, Week 2
  3. 03Magazine, licence and jurisdiction clock mapping.Week 1, Week 2
  4. 04Movement ingestion and normalisation.Week 2
  5. 05Reconciliation logic and source binding.Week 2, Week 3
  6. 06Confidence scoring and variance routing.Week 3
  7. 07Responsible-person review workflow.Week 3, Week 4
  8. 08Magazine and roster-system integration.Week 5
  9. 09Reconciliation and licence cases.Week 4, Week 5
  10. 10Guardrails and reporting controls.Week 4
  11. 11Ledger-trail instrumentation.Week 5, Week 6
  12. 12Deployment, documentation and Agent Care handover.Week 6

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel

Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tierPilotOne magazine, one siteProductionProduction stock systemsAdvancedMultiple sites / jurisdictions
Introduced at Pilot
Reconciliation to your record✓✓✓
Responsible-person approval✓✓✓
Reconciliation-accuracy baseline✓✓✓
Introduced at Production
Reporting by magazine—✓✓
Variance workflow in your systems—✓✓
Approved write-back—✓✓
Magazine-system integration—✓✓
Introduced at Advanced
Multi-jurisdiction clock rules——✓
Multi-stage security approvals——✓
High magazine count——✓
Multi-site licence controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from build
Build pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

  1. 01Your magazine list and stock items

    Magazine, licence and clock rule mapping

    Week 1

  2. 02Representative issue and return records

    Movement ingestion, normalisation and the reconciliation baseline

    Week 2

  3. 03Your licence, clearance and competency register

    Licence-currency mapping and automation-boundary definition

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    Magazine and roster-system assessment, then integration setup

    Week 2

  5. 05Ledgers you would not want counted

    Discrepancy cases and the evaluation suite

    Week 4

  6. 06What no discrepancy report may soften

    Confidence scoring, variance routing, guardrails and approval controls

    Week 3

  7. 07Named responsible persons to review variances

    Responsible-person review workflow, then pilot and production validation

    Weeks 5–6

Nothing else is required

Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

What sets each width is elapsed time and not layout, so the fifth band honestly carries a pair of them.

Phase

W1

W2

W3

W4

W5

W6

  1. DiscoveryW1
  2. BuildW2 – W3
  3. EvaluateW4 – W5
  4. Pilot & LaunchW5 – W6

Week focus

W1Explosives workflow discovery, rule mapping and the automation boundary

W2Source integration and the reconciliation baseline

W3Reconciliation workflow, confidence logic and approval controls

W4Evaluation suite, licence-currency checks and failure-mode testing

W5Roster-system integration, a pilot magazine and targeted corrections

W6One reconciliation cycle run under the responsible person, then Agent Care handover

Reading the band
A bar covers only the weeks its own work is named in. The week 5 overlap is real, not padding.
At the end of W6
Once the ledger validates, Agent Care assumes the running agent.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Mining AI agent

Build the reconciliation the magazine record has to survive.

Show us your magazines, your issue records and who reports. What you get is a per-magazine reconciliation, a licence register read against the roster actually working, and a variance pack with its clock on it. What you do not get is blast design, fragmentation, vibration and airblast prediction or fly-rock control — those are engineering acts a certified person signs by name, and a product implying otherwise would be claiming a legally-attributable act.

Typical delivery
4–6 weeks
Deployment
Your magazine records
Person reports
Records only
After launch
Agent Care available

Nestack Agents · Explosives inventory

AGT-MN-16 · Agent Care available after launch

Build an explosives inventory agent

Four questions so the call starts from your actual setup — then pick a time that suits you.

About you
Your magazines

No obligation. We’ll map the workflow, name the automation boundary and tell you if an agent is the wrong answer.