Energy AI agent · Dam safety programme
Dam Safety Program AI Agent
Follow the programme against the organisation it describes — who holds the named role today, whether the call list is current — and hold the record for the two people who sign it.
- Typical delivery
- 4–6 weeks
- Deployment
- Your stack
- Named engineer
- Programme-bound
- After launch
- Agent Care
What this agent does
Tracks the programme, not the dam
In
- 01
A named role changes hands, and § 12.62(b) has the Owner and that engineer both sign the programme.
- 02
A dam is high hazard potential, and § 12.62(a) forces an engineer, not a coordinator.
Reason
- 03
An annual review falls due, and § 12.64 sends the result to the Regional Engineer.
- 04
A five-year audit is planned, and § 12.65 wants the Regional Engineer to accept the auditor first.
- 05
An emergency plan is reviewed yearly, and § 12.24 still wants the call list updated continually.
Decide
- 06
An assessment year lands, and § 12.37 adds a failure mode analysis and a risk analysis to it.
- 07
A consultant team is proposed, and § 12.34 has FERC approve it before the work begins.
Out
- 08
A verification is executed, and § 12.13 requires a notary — the FERC financial reports require none.
- 09
Execute write actions only inside the approval boundaries agreed during implementation.
Product statement
The agent assembles and tracks cycles. A named Chief Dam Safety Engineer signs the programme with the Owner, and each independent consultant signs and seals the report.
Example workflow
One programme, record to signature
- 1Programme record receivedRole designations, review minutes, audit acceptances or inspection reports
- 2Programme context assembledThe project, its hazard classification, the section it answers to and the date the cycle last closed
- 3Programme set draftedThe role held, the cycles, the gaps and completeness
- 4Controls appliedCurrency checks, record-sufficiency checks, date checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is signed at any of them — the agent is assembling, and the dam safety lane opens at the completeness gate.
Goes to the Chief Dam Safety Engineer to sign.
Adds a dam safety staff read first.
Dam safety review
The set is held with its designations, its gaps and the projects they sit on.
Sign · Append record · Send to dam safety
Signed — by the Owner and the named engineer
- 6Project and inspection records updatedOnly where write access and records policy allow it
- 7Outcome evaluatedRecord completeness, role currency, staff corrections and what review found
Corrections
Each staff correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required
8 items
- Signing the Owner's Dam Safety Program.
- Sealing an independent consultant report.
- Performing a periodic inspection or assessment.
- Verifying a document before a notary public.
Automation boundary
Agent acts unaided
- ✓Hold the role designation with the date it was last confirmed.
- ✓Track the § 12.40(c) beat: ten years to an assessment, five to an inspection.
- ✓Chase the annual readiness test § 12.25 wants of responding personnel.
- ✓Flag a call list still carrying a name the personnel record has dropped.
Nothing is signed or sealed except by a named person, inside the agreed boundaries.
- Judging whether a dam is safe to operate.
- Telling the Regional Engineer a programme conforms.
- Requiring a public safety plan under § 12.52(b).
- Changes to designations, plans or inspection records.
Example output
One programme, annotated
Our grid asset maintenance copilot holds a condition finding for the engineer who dispositions it; this record is a statutory programme with named roles.
Programme record · single project
Illustrative example- Project
- Role designation, § 12.62(a)
- Recorded as
- Chief Dam Safety Engineer designated
- Classification
- High hazard potential
- Evidence of record
- Programme revision, 6 August 2026
- Confidence
- Held unsigned
- Held for
- The Owner and the named engineer
As received
Taken from the programme document and the licence record — it reaches as far as those sources do.
What the record holds
- Designation letter
- Annual review minute
- Audit acceptance, dated
Why no safety call here
Conformance rests with the Owner under § 12.62(d)(3), not with the agent.
What the score decides
Below the configured threshold the set picks up a dam safety read before the engineer sees it.
Action
SignAppend recordSend to dam safetyValue
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 project
From the programme that covers it
Where the programme is used
Our compliance reporting assistant drives a register and names no regime; this page is Part 12, with its own cycles and its own named signers.
A programme two people sign
Part 12 sets no deadline for telling FERC that the named engineer has changed — §§ 12.61 through 12.65 carry none — so that currency is yours to keep.
Checked, and not found
The FERC civil penalty actions published for 2025 carry no Part 12 dam safety violation; the lever here is the compliance order and the Regional Engineer directive.
Build an evidence trail
The programme, the role held against it and the consultant who sealed stay on the record.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Programme and licence
- Programme document
- licence articles
- Role designation records
Inspection and assessment
- Part 12D reports
- consultant files
- Regional Engineer letters
Emergency planning
- Emergency action plan
- call list
- Notification contact records
Agent
Dam safety programme record
- Reads the programme
- Tracks the cycles
- Holds for the signers
Training and personnel
- HR feed
- training records
- Readiness test records
Observability & evaluation
- OpenTelemetry
- Langfuse
- Supported monitoring/evaluation sources
Integration availability depends on the client's existing systems and API access.
Agent controls
Six gates between the model and the signature
Six gates, and no two shut on the same thing. What passes all six is named in the map below.
L6 · Outermost — last line of defence
Inward → L1 · closest to the model
- L1 – L2
- Test whether a set holds up
- L3
- Leaves the signature with a person
- L4 – L5
- Keep the programme and the role behind it
- L6
- Narrows to programme assembly when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the programme set that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the set a Regional Engineer reads
- E1Final-output evaluationDid the set record who holds the named role, and since when?
- E2Step-level evaluationDid the agent read the right project, the right section and the live programme?
- E3Tool evaluationDid it read and write the correct project record and the correct cycle?
- E4Confidence calibrationDo low-confidence sets actually attract more dam safety corrections?
- E5Slice evaluationHow does performance change across specific project types?
- E6Business outcomeHow many sets needed a correction before the engineer signed?
Floor — the outcome the Owner answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, placed at the stage in the agent where each starts.
Agent lifecycle
Direction of processing →
01 · Retrieval
1 mode
- IZ-03
Stale programme read
The programme read is not the revision now in force.
Stage gathers
The projects, the roles, the cycles and the dates
02 · Reasoning
2 modes
- IZ-04
Role currency assumed
A designation is treated as current on no record.
- IZ-06
Guideline read as rule
A Chapter 18 method is cited as though § 12.37 named it.
Stage proposes
The programmes, the roles held and completeness
03 · Tool / write
2 modes
- IZ-02
Thin set passed forward
A set moves on without the dam safety read.
- IZ-05
Record bound to wrong project
A review is filed against the wrong dam.
Stage writes
Only where write access and approval policy allow it
04 · Output
1 mode
- IZ-01
Signed, cycle unrecorded
The record shows a signature but not what stood behind it.
Stage returns
The set two people sign and an auditor reads
05 · Change / Version
1 mode
- IZ-07
Silent cycle regression
A programme revision moves the cycle, not the record.
Stage tracks
Model, prompt, cycle rules and record fields
- Sev-1 · a programme signed on no record
- Sev-2 · a stale call list reaches the plan
- Sev-3 · source degrades, set holds unsigned
Affected slices
Delegated scopes absorb the corrections
A project-level role-currency figure can read clean while delegated programme scopes carry most of the corrections. Nestack reports the correction rate by project, not only in total.
Slice performance — reported separately, not only in aggregate
Illustrative example| Slice | Failure rate | Lift | Lift vs. threshold | Status |
|---|---|---|---|---|
| Delegated programme scopes | 8.7% | 3.7× | Review | |
| Newly licensed project works | 6.2% | 2.6× | Review | |
| Multi-dam single licences | 3.8% | 1.6× | Watch | |
| High hazard potential dams | 1.4% | 0.6× | Normal |
Bar: correction-rate lift vs. high-hazard-project baseline · scale 0–4.0× · tick marks the 2.0× review threshold
2 of 4 slices over threshold
Evidence-linked improvement
What a stale call list costs
A cycle is done when the lapsed call list has become a case the next release must pass. That suite is what the next review run is measured against.
Improvement cycle · five stages
Switchback — the path turns at Improve and returns at Learn
- 01
Detect
Correction rate rises on delegated programme scopes.
- 02
Diagnose
The emergency plan that named an engineer who retired two winters ago is read back until one cause remains.
- 03
Improve
Number the change; the projects that drove it are filed underneath it.
- 04
Verify
Each touched project case is run once more, and one red holds it back.
- 05
Learn
It stays on as a standing test, and the review rules move with it.
Learn → Detect
The return edge. The next programme is measured 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, programme assembly, evaluation, integration, then production validation and handover.
Workstream
Week 1Week 2Week 3Week 4Week 5Week 6
- 01Dam-safety-programme discovery and boundary work.Week 1
- 02Programme, review and inspection sources.Week 1, Week 2
- 03Role-designation and review-cycle coverage mapping.Week 1, Week 2
- 04Programme record ingestion.Week 2
- 05Project, section and record binding.Week 2, Week 3
- 06Completeness scoring and staff routing.Week 3
- 07Signature workflow.Week 3, Week 4
- 08Inspection and plan-system integration.Week 5
- 09Role-currency and review cases.Week 4, Week 5
- 10Guardrails and sealing controls.Week 4
- 11Programme-trail instrumentation.Week 5, Week 6
- 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 tier | PilotOne project, one year | ProductionProduction programme workflow | AdvancedMultiple projects / licences |
|---|---|---|---|
| Introduced at Pilot | |||
| Programme assembly to your cycles | ✓ | ✓ | ✓ |
| Named engineer signature | ✓ | ✓ | ✓ |
| Role-designation baseline | ✓ | ✓ | ✓ |
| Introduced at Production | |||
| Reporting by project | — | ✓ | ✓ |
| Signature workflow in your systems | — | ✓ | ✓ |
| Approved write-back | — | ✓ | ✓ |
| Inspection-record integration | — | ✓ | ✓ |
| Introduced at Advanced | |||
| Multi-licence portfolios | — | — | ✓ |
| Cross-project programme packs | — | — | ✓ |
| Large dam portfolios | — | — | ✓ |
| Multi-project review controls | — | — | ✓ |
| Build price | From $5,000 | From $8,000 | Custom 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.
You bring
We build with it
01Your projects and their hazard classifications
→Project mapping and role-designation capture
Week 102Representative reviews, audits and inspection reports
→Record binding, cycle logic and the programme baseline
Week 203Your emergency action plan and its call list
→Programme mapping, project binding and the automation boundary
Week 104Access to relevant APIs, feeds or exports
→Programme, inspection and plan-source assessment, then integration setup
Week 205Programmes you would not want signed
→Review cases and failure testing
Week 406What no dam safety programme may assume
→Completeness scoring, staff routing, guardrails and signature controls
Week 307A named Chief Dam Safety Engineer to sign
→Signature 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
Each band is the honest working time a phase takes, and the fifth is shared because the work is.
Phase
W1
W2
W3
W4
W5
W6
- DiscoveryW1
- BuildW2 – W3
- EvaluateW4 – W5
- Pilot & LaunchW5 – W6
Week focus
W1Programme workflow discovery, project mapping and the automation boundary
W2Source integration and the role-designation baseline
W3Programme assembly, cycle logic and signature controls
W4Evaluation suite, review cases and failure-mode testing
W5Record integration, pilot projects and targeted corrections
W6One review year run under the chief dam safety engineer, then Agent Care handover
- Reading the band
- Each bar sits across only the weeks its own work is named for. The fifth week doubles because the work does.
- At the end of W6
- When the programme record validates, Agent Care takes the agent on.
- Duration
- Six-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Energy AI agent
Build a dam safety programme agent around the roles your licence already names.
Show us your programme and the two names on it. Part 12 sets no clock for replacing the named engineer, so that currency stays yours. Storm and water analytics return a score with its bounds; a tailings impoundment answers to another regulator on another cycle.
- Typical delivery
- 4–6 weeks
- Deployment
- Your programme document
- Named engineer
- Programme-bound
- After launch
- Agent Care available
Nestack Agents · Dam safety programme
AGT-EN-12 · Agent Care available after launch