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.
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
AgentHuman
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.
5DecisionDivides at the completeness gate
Record sufficient
Goes to the Chief Dam Safety Engineer to sign.
Anything thin
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 required8 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 boundaryAgent 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 projectIllustrative example
Project
Recorded as
Classification
Evidence of record
Confidence
Held for
Role designation, § 12.62(a)
Chief Dam Safety Engineer designated
High hazard potential
Programme revision, 6 August 2026
Held unsigned
The Owner and the named engineer
As receivedTaken from the programme document and the licence record — it reaches as far as those sources do.
What the record holdsDesignation letterAnnual review minuteAudit acceptance, dated
Why no safety call hereConformance rests with the Owner under § 12.62(d)(3), not with the agent.
ActionSignAppend recordSend to dam safety
What the score decidesBelow the configured threshold the set picks up a dam safety read before the engineer 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 projectFrom the programme that covers it
03Record
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.
01Approved path
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.
02Human review
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.
04Build 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 licenceProgramme document · licence articles Role designation records
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 aggregateIllustrative 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 threshold2 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 stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on delegated programme scopes.
02Diagnose
The emergency plan that named an engineer who retired two winters ago is read back until one cause remains.
03Improve
Number the change; the projects that drove it are filed underneath it.
04Verify
Each touched project case is run once more, and one red holds it back.
05Learn
It stays on as a standing test, and the review rules move with it.
Learn → DetectThe 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.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Dam-safety-programme discovery and boundary work.
02Programme, review and inspection sources.
03Role-designation and review-cycle coverage mapping.
04Programme record ingestion.
05Project, section and record binding.
06Completeness scoring and staff routing.
07Signature workflow.
08Inspection and plan-system integration.
09Role-currency and review cases.
10Guardrails and sealing controls.
11Programme-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 project, one yearProductionProduction programme workflowAdvancedMultiple 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 priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction 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 projects and their hazard classifications→Project mapping and role-designation captureWeek 1
02Representative reviews, audits and inspection reports→Record binding, cycle logic and the programme baselineWeek 2
03Your emergency action plan and its call list→Programme mapping, project binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Programme, inspection and plan-source assessment, then integration setupWeek 2
05Programmes you would not want signed→Review cases and failure testingWeek 4
06What no dam safety programme may assume→Completeness scoring, staff routing, guardrails and signature controlsWeek 3
07A named Chief Dam Safety Engineer to sign→Signature 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
Each band is the honest working time a phase takes, and the fifth is shared because the work is.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Programme workflow discovery, project mapping and the automation boundaryW2Source integration and the role-designation baselineW3Programme assembly, cycle logic and signature controlsW4Evaluation suite, review cases and failure-mode testingW5Record integration, pilot projects and targeted correctionsW6One review year run under the chief dam safety engineer, then Agent Care handover
Reading the bandEach bar sits across only the weeks its own work is named for. The fifth week doubles because the work does.
At the end of W6When the programme record validates, Agent Care takes the agent on.
DurationSix-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.
