Run the statutory notification clock from when a reportable event is known, draft the notification against the regulator form, and keep the readiness record true — a named mine official makes the call.
An event occurs, and the record is pulled from supported control-room, dispatch, shift-log and roster sources.
02
A clock starts when the operator knew or should have known, not when somebody finished deciding.
Reason
03
A notification is drafted against the fields the regulator form asks for, and held for the official who makes it.
04
A scene is preserved, and the duty that attached at the event is surfaced with the record it has to leave behind.
05
A filing window opens, and the accident report and the quarterly return are tracked against the event that began them.
Decide
06
A drill falls due, and coverage is counted against the roster that actually worked, not the roster on the plan.
07
A physical expires, and the agent tracks the date on the form and never what the physician wrote inside it.
Out
08
A plan is approved, and the training window is counted from the approval date, not the date it was submitted.
09
A write action runs only inside the approval boundaries agreed during implementation.
→Product statement
The agent runs the clock and keeps the record; a named mine official notifies, and a record found wrong is corrected after it was relied on.
Example workflow
One event, first report to filing
AgentHuman
1First report receivedControl room, dispatch log, shift record and medical transport note
2Clock startedTime of first knowledge, candidate event classes and the duties that attach, each with its named source
3Notification draftedDraft notification, form fields, preservation checklist, open items and confidence
4Controls appliedForm-field completeness, clock checks, preservation and retention tests and confidence threshold
No human action required
Stages 1 to 4 run unaided, and nothing is notified at any of them — the agent is drafting, and the official lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the mine official.
Low confidence
Adds a safety manager read first.
Official review
The draft is held with its clock, its open items and the confidence.
Approve · Amend · Send to safety manager review
Approved — released to the record▼
6Notification record updatedOnly where write access and approval policy allow it
7Outcome evaluatedAmendment distance, open-item outcomes, regulator queries and post-filing corrections
Amendments
Every official amendment is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Declaring an emergency, or ordering an evacuation.
Deciding whether an event is reportable.
Making the notification to the regulator.
Taking charge on shift during a mine emergency.
Automation boundaryAgent acts unaided
✓Start the clock at the first record of the event, and show it running.
✓Draft the notification against the fields the form requires.
✓Surface the preservation and record duties that attach at the event.
✓Name what has expired in the readiness record, and hold the pack.
Writes run only inside the boundaries agreed at implementation, never ahead of a notification.
Certifying a drill, a team or an apparatus test.
Clearing a rescue team member as medically fit.
Judging a scene-preservation exception in real time.
Changes to event-class, clock or approval rules.
Example output
One notification, annotated
Everything the agent drafts is attached to the record it was drawn from.
Notification output · single eventIllustrative example
Event class
Notification drafted
Time to notification
Source of record
Confidence
Notifier of record
Underground fire, no injury
Fire underground not extinguished inside ten minutes
22 minutes
Control-room log on file
86%
Shift foreman, named on the roster
As receivedTaken from the control-room log and the shift record — nothing on this side is written by the agent.
Source facts usedControl-room event logShift and dispatch recordSuppression report
Why this is openThe log shows when the fire was called in, and nothing shows the official being told.
ActionApproveAmendSend to safety manager review
What the score decidesBelow the configured threshold the item picks up a safety manager read before the official sees it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every reportable eventFrom the first record
03Clock and pack
Start the clock on the record
The window opens when the operator knew or should have known, so the time spent deciding is already time elapsed.
01Approved path
Doubt resolves toward calling
In Canyon Fuel, decided 30 January 2026, the Commission held the window opened as soon as the foreman was told.
02Human review
Not the alarm, and not the response
Our maintenance planning agent carries equipment currency; our safety compliance assistant carries training and document currency. This page owns the clock that starts at an event.
04Build an evidence trail
The event, the clock it started and the official who notified stay on the notification.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Control room and dispatchSCADA · dispatch systems Shift logs and rosters
Regulator formsMSHA 7000-1 · 7000-2 Form 5000-3 records
Training and competencyPegasus · Onsite Track Easy Drill and training ledgers
Agent
Emergency notification
Reads the record Runs the clock Holds for the official
Rescue and equipment recordsApparatus inspection logs Self-rescuer test records
A site-level notification-timeliness figure can read as clean while a few event classes carry most of the returned items. Nestack reports the return rate by event class, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Underground fire and outburst
8.8%
3.7×
Review
Entrapment and hoist damage
6.1%
2.5×
Review
Metal and nonmetal surface
4.4%
1.8×
Watch
Reported injury events
2.0%
0.8×
Normal
Bar: return-rate lift vs. injury-event baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends when the suite grows by one
A cycle is done when the missed window has become a case the next release must pass. That suite is what the next notification drafted is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Return rate rises in one event class.
02Diagnose
The fifteen minutes that started while somebody drove out to look are read back until the cause narrows to one.
03Improve
Stamp the change; the events behind it are filed under that number.
04Verify
Each touched notification case runs once more, and one red holds it.
05Learn
It stays as a standing test, and the reporting rules move with it.
Learn → DetectThe return edge. Detection next time runs against one more case than last.
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, notification workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Notification workflow discovery and boundary mapping.
02Event-source and record assessment.
03Event-class, clock and record-retention mapping.
04Event ingestion and clock start.
05Notification drafting and form binding.
06Confidence scoring and exception routing.
07Official notification workflow.
08Control-room and forms integration.
09Clock and readiness cases.
10Guardrails and notification controls.
11Event-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal 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 mine, one event classProductionProduction control-room systemsAdvancedMultiple mines / regulators
Introduced at Pilot
Clock tracking and drafting✓✓✓
Mine-official approval✓✓✓
Readiness-currency baseline✓✓✓
Introduced at Production
Reporting by event class—✓✓
Exception workflow in your systems—✓✓
Approved write-back—✓✓
Control-room integration—✓✓
Introduced at Advanced
Multi-regulator form rules——✓
Multi-stage notification approvals——✓
High event volume——✓
Multi-regulator notification controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, event volume, approval controls and deployment requirements.
Separate from buildBuild 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.
You bringWe build with it
01Your event classes and notification paths→Event-class, clock and record-retention rule mappingWeek 1
02Representative prior notifications and forms→Event ingestion, clock start and the drafting baselineWeek 2
03Your emergency plan, drills and rescue records→Readiness-record mapping and automation-boundary definitionWeek 1
04Access to relevant APIs, feeds or exports→Event-source and record assessment, then integration setupWeek 2
05Notifications you would not want timed→Window cases and failure-mode testingWeek 4
06What no readiness record may skip→Confidence scoring, exception routing, guardrails and notification controlsWeek 3
07Named mine officials to make the call→Official notification workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The schedule reflects the weeks actually worked, which is why one band in week five is a doubled one.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Notification workflow discovery, rule mapping and the automation boundaryW2Source integration and the drafting baselineW3Clock logic, drafting workflow and notification controlsW4Evaluation suite, readiness-currency checks and failure-mode testingW5Control-room integration, a pilot event class and targeted correctionsW6One drill cycle run under the emergency response coordinator, then Agent Care handover
Reading the bandA bar covers only the weeks its own work is named in. The week 5 overlap is real, not padding.
At the end of W6The final checks clear on live drills and monitoring moves to Agent Care.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Mining AI agent
Build the notification clock before the fifteen minutes start.
Show us your event classes, your control-room records and the readiness ledger you keep. The record has to survive being read back years later by someone who already knows what happened and wants to know what you knew and when — so we build the clock, the pack and the ledger against that reading. During the event itself the agent is not in the loop, and the official keeps the call.
