Main site

Operations AI agent · Obligation tracking

Compliance Obligation Tracking AI Agent

Diarise a recurring obligation the day it lands, file the evidence under it as the evidence arrives, and hand the whole register to the named owner or operator who certifies it.

Typical delivery
4–6 weeks
Deployment
Your stack
Owner certifies
Evidence filed
After launch
Agent Care

What this agent does

Tracks the obligation, never certifies it

In

  1. 01

    An obligation lands from a rule such as 40 CFR 68.79, and it enters the register with an owner.

  2. 02

    A deadline recurs whether anybody is watching or not, so the clock runs off the rule, not the diary.

Reason

  1. 03

    A five-year revalidation falls due under 68.67(f), and the evidence is checked before the date.

  2. 04

    A change forces a revised hazard analysis, and 68.190(b)(5) sets six months from that change.

  3. 05

    An incident occurs, and 68.81 starts a clock on beginning the investigation, not on finishing it.

Decide

  1. 06

    An owner leaves, and each obligation filed under that name shows as unheld until somebody takes it.

  2. 07

    An emergency contact changes, and 68.195(b) opens a one-month window nobody else is watching.

Out

  1. 08

    An obligation lapses, and the lapse is written up as a finding rather than quietly closed out.

  2. 09

    Execute write actions only inside the approval boundaries agreed during implementation.

Product statement

Tracking, evidencing and clock-keeping belong to the agent. The certification belongs to a named owner or operator, who makes the reasonable inquiry and signs.

Example workflow

One obligation, rule to certification

  1. 1Obligation identifiedRegulatory text, permit conditions, corporate standards or an existing compliance register
  2. 2Clock set from the ruleThe interval, the trigger that starts it, the next date it falls due and the owner who holds it
  3. 3Evidence assembledThe audits, revalidations, investigations and change records filed against the obligation
  4. 4Controls appliedRegister checks, evidence-age checks, owner checks and completeness confidence

No human action required

Stages 1 to 4 run unaided, and nothing is certified at any of them — the agent is tracking, and the owner lane opens at the completeness gate.

5DecisionSplits at the completeness gate
Evidence complete

Goes to the named owner or operator.

Anything missing

Adds a process safety lead read first.

Owner review

The obligation is held with its evidence, its gaps and the date it next falls due.

Certify · Add evidence · Send to safety review

Certified — by the owner or operator

  1. 6Compliance records updatedOnly where write access and records policy allow it
  2. 7Outcome evaluatedClock accuracy, evidence currency, owner corrections and what review found

Corrections

Each owner correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required

8 items

  • Certifying that a submission is true and complete.
    • Deciding that an obligation applies to this company.
    • Conducting the reasonable inquiry behind a signature.
    • Declaring a compliance audit adequate.

  • Automation boundary

    Agent acts unaided

    • ✓Set the clock from the rule that creates the duty.
    • ✓File the evidence under the obligation it answers.
    • ✓Show which obligations are unheld, unevidenced or overdue today.
    • ✓Raise the next date due, and name the owner who must answer it.

    Nothing is certified except by a named owner or operator, inside the agreed boundaries.

    • Judging whether a hazard analysis needs revising.
    • Accepting a declined recommendation as justified.
    • Telling a regulator what a record means.
  • Changes to the register, the clocks or the owners.

Example output

One obligation, annotated

This serves an operations team whose owner or operator has to certify under 40 CFR 68.185; below is one obligation exactly as the agent leaves it.

Obligation record · single duty

Illustrative example
Obligation
Compliance audit, covered process
Recorded as
Due, evidence incomplete
Interval
Three-year cycle
Evidence of record
Audit report, 6 May 2026
Confidence
Held uncertified
Held for
The named owner or operator

As received

Assembled from the audit report and the change records on file, and it asserts nothing beyond them.

What the record holds

  • Audit report
  • Revalidation record
  • Change record

Why no certification here

Certifying after inquiry is a judgement the owner or operator makes.

What the score decides

Below the configured threshold the obligation gets a safety-lead read before the owner.

Action

CertifyAdd evidenceSend to safety 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 obligation

From the rule that creates it

03Evidence

Where the register sits

Horizon scanning watches instruments and the stage each has reached; this tracks the obligations you already have, the evidence filed against each and the clocks that recur.

01Approved path

The clock runs without you

A recurring duty comes round again and nothing in the stack says so, because the deadline lives in 40 CFR 68.190 and not in your calendar.

02Human review

What was checked, and not found

Checked in the current text: the 2024 accident prevention rule is in force and codified, not stayed and not vacated, its challenge sits in abeyance and the rollback is proposed only, so the 68.10 date in May 2027 stands.

04

Build an evidence trail

The obligation, the evidence filed against it and the owner who holds it stay together.

Integrations

Typical integrations

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

  • Regulatory sources

    • eCFR
    • Federal Register
    • Permit conditions and corporate standards

  • Process safety records

    • Hazard analyses
    • revalidations
    • Management-of-change and incident records

  • EHS and compliance systems

    • Intelex
    • Enablon
    • Sphera
    • Cority
    • VelocityEHS

Agent

Compliance obligation tracking

  • Reads the obligations
  • Files the evidence
  • Holds for the owner

  • Audit and document stores

    • Audit reports
    • corrective actions
    • Document management and records archives

  • Observability & evaluation

    • OpenTelemetry
    • Langfuse
    • Supported monitoring/evaluation sources

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

Agent controls

Six locks between the model and the signature

Six locks on one door, the last the heaviest. What opens it is drawn in the map below.

L6 · Outermost — last line of defence

Inward → L1 · closest to the model

L6Rollback / safe modeNarrow the agent to listing obligations when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and calendar rules, and note the version each obligation was tracked under.Track
L4TraceabilityRecord each obligation, the evidence under it, the clock it ran on and every change to the file.Record
L3Owner releaseHold the obligation for a named owner; the hold governs release, not whether the file is complete.Gate
L2Register guardrailsTest each obligation against the rule text it was drawn from, and refuse a clock with no rule under it.Restrict
L1Confidence thresholdsRoute a thin evidence file to a safety-lead read before the obligation reaches the owner.Require review
Model coreObligation tracked — the rule, the clock, the evidence filed and what is missing
L1 – L2
Test whether an obligation may stand
L3
Leaves the certification to a named owner
L4 – L5
Keep the obligation and the evidence behind it
L6
Holds the obligation open when signals degrade

How Nestack evaluates it

Evaluate the whole register — not only the obligation that comes due.

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

Surface — the obligation an inspector asks about

  1. E1Final-output evaluationDid the obligation record the rule and the clock it was actually tracked on?
  2. E2Step-level evaluationDid the agent read the current rule text, the right interval and the live register?
  3. E3Tool evaluationDid it read and write the correct obligation and the correct evidence file?
  4. E4Confidence calibrationDo low-confidence obligations actually attract more owner corrections?
  5. E5Slice evaluationHow does performance change across specific obligation types?
  6. E6Business outcomeHow many obligations needed a correction before the owner certified?

Floor — the evidence a certification rests on

Failure modes

Where each failure originates in the agent

Seven failure modes, each pinned to the stage where it starts.

Agent lifecycle

Direction of processing →

  1. 01 · Retrieval

    1 mode

    • NK-03

      Stale rule text read

      The rule read is not the one that now applies.

    Stage gathers

    The rules, the clocks, the owners and the files

  2. 02 · Reasoning

    2 modes

    • NK-04

      Clock set on the wrong trigger

      A duty is dated from filing, not the event.

    • NK-06

      Obligation entered without basis

      A duty is carried that no rule creates.

    Stage proposes

    The rule, the clock, the evidence and the gaps

  3. 03 · Tool / write

    2 modes

    • NK-02

      Thin evidence file passed on

      An obligation moves on without the safety read.

    • NK-05

      Evidence bound to wrong duty

      The file is stored against another obligation.

    Stage writes

    Only where write access and approval policy allow it

  4. 04 · Output

    1 mode

    • NK-01

      Certified, gap unrecorded

      The record shows a signature but not the missing evidence.

    Stage returns

    The obligation an owner signs and an auditor reads

  5. 05 · Change / Version

    1 mode

    • NK-07

      Silent register decay

      An owner leaves and the clock keeps running unheld.

    Stage tracks

    Model, prompt, clock rules and owner records

  • Sev-1 · a certification signed on a gap
  • Sev-2 · a recurring deadline passes unmet
  • Sev-3 · source degrades, obligation held open
See the complete Operations failure-mode catalogue

Affected slices

Event-driven clocks absorb the corrections

An obligation-level evidence figure can read clean while event-driven six-month clocks carry most of the corrections. Nestack reports the correction rate by obligation type, not only in total.

Slice performance — reported separately, not only in aggregate

Illustrative example
SliceFailure rateLiftLift vs. thresholdStatus
Event-driven six-month clocks11.8%3.7×Review
Newly registered obligations8.4%2.6×Review
Obligations with shared owners5.3%1.7×Watch
Established annual obligations2.1%0.7×Normal

Bar: correction-rate lift vs. established-obligation baseline · scale 0–4.0× · tick marks the 2.0× review threshold

2 of 4 slices over threshold

Evidence-linked improvement

What a lapsed clock costs

The cycle shuts when the missed recurring deadline is a regression case. That suite is what the next obligation review is measured against.

Improvement cycle · five stages

Switchback — the path turns at Improve and returns at Learn

  1. 01

    Detect

    Correction rate rises on event-driven six-month clocks.

  2. 02

    Diagnose

    The three-year audit that was four years old because the owner had left is worked backwards until one cause is left standing.

  3. 03

    Improve

    Number the change; the obligations that drove it are filed beneath it.

  4. 04

    Verify

    Nothing ships while one obligation case remains red.

  5. 05

    Learn

    The case is kept, and the calendar rules are amended in that same commit.

  6. Learn → Detect

    The return edge. The next obligation review runs against 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, obligation tracking, evaluation, integration, then production validation and handover.

Workstream

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

  1. 01Obligation-register and automation-boundary work.Week 1
  2. 02Regulatory, permit and internal sources.Week 1, Week 2
  3. 03Rule-to-obligation and clock-derivation mapping.Week 1, Week 2
  4. 04Obligation and evidence ingestion.Week 2
  5. 05Clock, evidence and owner binding.Week 2, Week 3
  6. 06Completeness scoring and review routing.Week 3
  7. 07Owner certification workflow.Week 3, Week 4
  8. 08EHS-system integration.Week 5
  9. 09Obligation and evidence cases.Week 4, Week 5
  10. 10Guardrails and attestation controls.Week 4
  11. 11Obligation-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 register, one siteProductionProduction compliance workflowAdvancedMultiple sites / regimes
Introduced at Pilot
Obligation tracking to your register✓✓✓
Named owner certification✓✓✓
Obligation-register baseline✓✓✓
Introduced at Production
Reporting by obligation—✓✓
Owner review workflow in your systems—✓✓
Approved write-back—✓✓
Obligation-source integration—✓✓
Introduced at Advanced
Multi-regime obligation sets——✓
Cross-site evidence packs——✓
Large obligation registers——✓
Multi-regime calendar controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build price
Confirmed after discovery based on integrations, workflow complexity, register size, 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 live obligations and the rule each one comes from

    Obligation capture and clock derivation

    Week 1

  2. 02Representative audits, revalidations and change records

    Evidence binding, clock logic and the register baseline

    Week 2

  3. 03Your compliance calendar and the owners it names

    Obligation mapping, clock derivation and the automation boundary

    Week 1

  4. 04Access to relevant APIs, feeds or exports

    Regulatory, permit and record-store assessment, then integration setup

    Week 2

  5. 05Registers you would not want inspected

    Deadline cases and failure-mode testing

    Week 4

  6. 06What no obligation register may certify

    Completeness scoring, review routing, guardrails and release controls

    Week 3

  7. 07A named owner or operator who certifies

    Release to the named owner, 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

Each band is as wide as its phase costs, so week five carries a pair rather than an empty column.

Phase

W1

W2

W3

W4

W5

W6

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

Week focus

W1Obligation discovery, clock derivation and the automation boundary

W2Source integration and the obligation-register baseline

W3Evidence binding, completeness logic and release controls

W4Evaluation suite, deadline cases and failure-mode testing

W5EHS-system integration, pilot obligations and targeted corrections

W6One audit cycle run under the accountable owner, then Agent Care handover

Reading the band
Each bar covers only the weeks its own work is named for, and week five is shared by design.
At the end of W6
When the evidence record validates, Agent Care assumes the agent.
Duration
Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Operations AI agent

Build a compliance obligation agent around the clocks that recur without anybody starting them.

Show us one recurring obligation and the evidence filed against it since it last came round. The owner or operator signs, on knowledge, information, and belief formed after reasonable inquiry, and the agent keeps the register that inquiry is run against.

Typical delivery
4–6 weeks
Deployment
Your obligations
Owner certifies
Evidence filed
After launch
Agent Care available

Nestack Agents · Obligation tracking

AGT-OP-05 · Agent Care available after launch

Build a compliance obligation agent

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

About you
Your obligations

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