Enter each instrument at the stage it has actually reached — proposed, applying, stayed, vacated or withdrawn — with the date and source that establishes it, and hold it for a named owner.
2Instrument context assembledThe instrument, the body standing behind it, the regime it belongs to and the stage its source establishes
3Register entry draftedThe stage, the source under it, the gaps and currency
4Controls appliedSource checks, duplicate-instrument checks, stage checks and currency confidence
No human action required
Stages 1 to 4 run unaided, and no instrument is accepted at any of them — the agent is only staging, and the owner enters at the currency gate.
5DecisionSplits at the currency gate
Source authoritative
Passes to the register owner for acceptance.
Anything stale
Adds a regulatory counsel read first.
Regulatory counsel review
The entry is held with its stage, its gaps and the sources they came from.
Accept · Append source · Send to regulatory counsel
Accepted — by the named register owner▼
6Register and watchlist records updatedOnly where write access and records policy allow it
7Outcome evaluatedSource currency, stage coverage, counsel corrections and what review found
Corrections
Every regulatory counsel correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Deciding that an instrument applies to this company.
Ruling on what a vacated rule leaves in force.
Treating a proposal as a live obligation.
Accepting an instrument into the register unaided.
Automation boundaryAgent acts unaided
✓Watch the configured official sources for each regime.
✓Record the stage an instrument reached, with its date and its source.
✓Re-confirm currency on the cadence each regime sets.
✓Flag a stage change and route the entry to the owner who holds it.
No instrument is accepted and no digest goes out except by a named person, on approval.
Judging whether a deferral changes your plan.
Telling a board that the estate is compliant.
Setting the cadence at which a regime is watched.
Changes to the register, the watchlist or the digest.
Example output
One register entry, annotated
Our shipped market-research agent traces commercial sources for an insights function; this one tracks instruments and the stage each has reached, for a strategy team deciding whether to act.
Register entry · single instrumentIllustrative example
Stage
Recorded as
Instrument
Source of record
Confidence
Held for
Deforestation, Regulation (EU) 2025/2650
In force, and not yet applying
Stage recorded, not judged
Application from 30 December 2026
Held unaccepted
The register owner, by name
As receivedTaken from the Official Journal text and the watch record — it reaches no further than those sources.
What the record holdsOfficial Journal textStage and its dateLast currency check
Why nothing is settled hereWhether a deferred rule changes your plan is a judgement for counsel.
ActionAcceptAppend sourceSend to regulatory counsel
What the score decidesBelow the configured threshold an entry picks up a counsel read before the owner 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 instrumentFrom the source that establishes it
03Stage
Where the stage is used
No general obligation binds an ordinary company to monitor regulatory change: this page shows what was watched and the stage each instrument reached, and it settles nothing beyond that.
01Approved path
Proposed is not in force
Release 33-11414 was announced on 5 May 2026 and its comments closed on 6 July 2026, with no adopting release since, so Form 10-Q stands.
02Human review
What was checked, and not found
No duty of general application to scan the horizon was located in statute or rule; no penalty figure is published on this page; and the OCC heightened standards and the fund compliance rule were not read in primary text, so neither is cited.
04Build an evidence trail
The instrument, the stage it has reached and the owner who accepted it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Gazettes and official registersFederal Register · EUR-Lex Proposals and adoptions
Courts and appellate docketsDocket entries · opinions Vacaturs, stays and remands
Regulators and supervisorsAgency bulletins · portals Guidance, withdrawals and pauses
Agent
Regulatory horizon register
Watches the sources Records the stage Holds for the owner
Legislatures and parliamentsBill trackers · legislative feeds Bills, adoptions and repeals
Integration availability depends on the client's existing systems and API access.
Agent controls
Six vaults between the model and the owner
Six vaults opened one inside the next, the last the heaviest. What is inside is set out in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeNarrow the agent to instrument listing when evaluation or production signals degrade.Roll back
L5Version monitoringTrack model, prompt and staging rules; 16 CFR Part 425 was vacated on 8 July 2025 and the pre-2024 rule restored on 12 February 2026.Track
L4TraceabilityRecord each instrument, the stage under it, the source it came from and every read of the entry.Record
L3Owner releaseHold the entry for the named register owner; the hold governs acceptance, not what the instrument turns out to require.Gate
L2Source guardrailsTest each entry against its official source; the LkSG reporting duty stayed law after BAFA closed its portal on 3 September 2025.Restrict
L1Confidence thresholdsRoute a stale entry to a counsel read first; the HSR form of 2024 was vacated on 12 February 2026 and a stay refused on 19 March 2026.Require review
Model coreInstrument staged — the stage, its source, the date and currency
L1 – L2Test whether an entry may stand
L3Leaves the acceptance to a named person
L4 – L5Keep the instrument and the stage behind it
L6Falls back to instrument listing when signals degrade
How Nestack evaluates it
Evaluate the whole assembly — not only the register entry that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the digest a strategy team reads
Depth of coverage ▼
E1Final-output evaluationDid the entry record the stage its source actually establishes?
E2Step-level evaluationDid the agent read the right source, the right instrument and the live text?
E3Tool evaluationDid it read and write the correct register entry and the correct stage?
E4Confidence calibrationDo low-confidence entries actually attract more counsel corrections?
E5Slice evaluationHow does performance change across specific regimes?
E6Business outcomeHow many entries needed a correction before the owner accepted?
Floor — the decision the company answers for
Failure modes
Where each failure originates in the agent
Seven failure modes, each fixed at the stage where it first surfaces.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
MI-03
Stale source read
The text read is not the version now in force.
Stage gathersThe regimes, the sources, the dates and stages
02 · Reasoning2 modes
MI-04
Stage asserted, not sourced
A stage is recorded with no source under it.
MI-06
Vacated rule read as live
A struck-down rule is worked as the operative one.
Stage proposesThe instruments, their stages and currency
03 · Tool / write2 modes
MI-02
Stale entry passed forward
An entry moves on without the counsel read.
MI-05
Stage bound to wrong instrument
The date is filed against a different measure.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
MI-01
Accepted, source unrecorded
The entry shows acceptance but not the text under it.
Stage returnsThe entry an owner accepts and a board reads
05 · Change / Version1 mode
MI-07
Silent stage drift
A source updates while the register keeps the old stage.
Stage tracksModel, prompt, staging rules and stage fields
Sev-1 · an instrument accepted on no sourceSev-2 · a vacated rule reaches the digestSev-3 · source degrades, entry held back
A regime-level currency figure can read clean while litigated and vacated rules carry most of the rework. Nestack reports the correction rate by regime, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Litigated and vacated rules
7.4%
3.6×
Review
Proposed rules and consultations
5.3%
2.6×
Review
EU regulations in force
3.2%
1.6×
Watch
US federal final rules
1.6%
0.8×
Normal
Bar: correction-rate lift vs. US federal final rule baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What a stale stage costs
A loop ends when the vacated rule read as live has become a case the next release must pass. That suite is what the next digest issued is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on litigated and vacated rules.
02Diagnose
The click-to-cancel rule a renewals plan still assumed, vacated on 8 July 2025, is read back until a single cause remains.
03Improve
Number the change; the instruments that drove it are filed underneath it.
04Verify
Each touched instrument case is run once more, and one red holds it back.
05Learn
It stays on as a standing test, and the staging rules move alongside it.
Learn → DetectThe return edge. The next digest 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, register assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Acceptance-boundary and watchlist-coverage work.
02Gazette, docket and bulletin sources.
03Instrument-to-stage and currency-cadence mapping.
04Instrument source ingestion.
05Instrument, stage and date binding.
06Currency scoring and review routing.
07Owner acceptance workflow.
08Register and watchlist integration.
09Stage and currency cases.
10Guardrails and staging controls.
11Instrument-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 regime, one yearProductionProduction register workflowAdvancedMultiple regimes / jurisdictions
Introduced at Pilot
Stage assembly to your sources✓✓✓
Register owner release✓✓✓
Watched-instrument baseline✓✓✓
Introduced at Production
Reporting by regime—✓✓
Owner acceptance workflow in your systems—✓✓
Approved write-back—✓✓
Official-source integration—✓✓
Introduced at Advanced
Multi-jurisdiction registers——✓
Cross-regime digest packs——✓
Large watchlists——✓
Multi-jurisdiction staging controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, instrument 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 regimes and the sources you already trust→Source mapping and instrument captureWeek 1
02Representative gazette, docket and bulletin records→Source binding, stage logic and the register baselineWeek 2
03Your standing watchlist and the owner it names→Regime mapping, cadence binding and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Gazette, docket and bulletin source assessment, then integration setupWeek 2
05Digests you would not want relied on→Currency cases and the evaluation runWeek 4
06What no horizon digest may establish→Currency scoring, review routing, guardrails and release controlsWeek 3
07A named owner who accepts an instrument into the register→Release to the register owner, 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
You are reading effort, not spacing, which is why the fifth of these bands has two phases inside it.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Register workflow discovery, regime mapping and the automation boundaryW2Source integration and the watched-instrument baselineW3Stage assembly, currency logic and release controlsW4Evaluation suite, currency cases and failure-mode testingW5Docket integration, pilot instruments and targeted correctionsW6One legislative year run under the regulatory counsel, then Agent Care handover
Reading the bandEvery band runs the weeks its own work is named for, and one of them doubles up because the work does.
At the end of W6When the instrument 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 · Strategy AI agent
Build a horizon register around the rule your plan still assumes is law.
Show us one instrument and the source that fixes its stage. Which regime puts a general duty to scan on you? None does: the nearest analogues, 17 CFR 275.206(4)-7 and FINRA Rule 3130, reach investment advisers and a member firm CEO, never an ordinary company.
