No rule defines reach, share of voice or media value, so the agent stores the corpus, the query and the method behind each figure, and holds it for the owner who signs.
A figure is produced, and the corpus, the query and the window behind it sit beside it.
02
Share of voice is asked for, and the Code of Federal Regulations defines the term nowhere.
Reason
03
Reach is reported, and it is marked as modelled from outlet audiences, not counted from readers.
04
A self-defined metric reached a filing before, and Wells Fargo settled it: Exchange Act Rel. 34-88257.
05
A media-value line appears, and 17 CFR 244.101(a)(2) puts operating measures outside Regulation G.
Decide
06
The figure reaches a filing, and the definition, the method and any change to it go in with it.
07
A grant report asks for earned media information, and 23 CFR 1300.35(b)(4) defines none of it.
Out
08
A number cannot be rebuilt from the record, and that is written down as the finding.
09
Execute write actions only inside the boundaries approved at implementation time.
→Product statement
Counting and the method trail belong to the agent, and the corpus arrives from monitoring rather than being gathered here. Publication belongs to a named measurement owner, who owns the number there.
Example workflow
One figure, corpus to publication
AgentHuman
1Corpus receivedClip feeds, broadcast logs and wire pickups as the monitoring vendor delivered them this period
2Method fixed and versionedThe query, the outlet set, the date window, the duplicate rule and the day the method was set
3Counts raised against that methodThe volume, the modelled reach, the sentiment split and the share against a named competitor set
Stages 1 to 4 run unaided, and no figure meets a reader at any of them — the agent is counting, and the owner lane opens at the publication gate.
5DecisionSplits at the publication gate
Rebuilds from the stored method
Goes to the named measurement owner to publish.
Anything that will not rebuild
Adds an analytics-lead read first.
Owner review
The figure is held with its method, its corpus snapshot and the query that selected it.
Publish · Append source · Send to analytics review
Published — by the named measurement owner▼
6Dashboard and reporting records updatedOnly where write access and the records policy both allow it
7Figure evaluatedMethod stability, corpus continuity, owner corrections and what analytics review found
Owner corrections
Each correction the owner makes is scored in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Publishing a media figure to a board.
Deciding what counts as the competitor set.
Certifying earned media to a funder.
Signing a filing that carries the number.
Automation boundaryAgent acts unaided
✓Fix the query and the corpus before a count runs.
✓Snapshot the outlet list the vendor indexed this period.
✓Mark each reach number as modelled from an outlet audience figure.
✓Hold the count, the method and the corpus in one numbered record.
Nothing meets a reader except by a named measurement owner, inside the agreed boundaries.
Deciding a rise in coverage means anything.
Telling a board what the coverage was worth.
Choosing the competitor set a share is drawn against.
Changes to the figure, the method or the report.
Example output
One coverage figure, annotated
This serves a communications team whose sentiment scores sit, on the measurement body’s own 2026 reckoning, around the low-to-mid sixties for precision; below is one figure as the agent leaves it.
Coverage figure · one reporting periodIllustrative example
Figure
Recorded as
Method
Evidence of record
Confidence
Held for
Share of voice, named competitor set
Rebuilds from the record
Query and corpus, versioned
Corpus snapshot, 7 August 2026
Held unpublished
The measurement owner, by name
As receivedBuilt from one corpus snapshot and one stored query, and it claims nothing beyond what those hold.
What the figure record holdsCorpus snapshotStored queryMethod note
Why no publication herePutting a media number in front of a board is a call the owner makes.
ActionPublishAppend sourceSend to analytics review
What the score decidesBelow the configured threshold a figure gets an analytics 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
Each figure countedFrom the corpus that carries it
03Evidence
Where that evidence goes
The agent does not vouch for a number, only for its corpus, its query and its method — which is what Release 33-10751 and 17 CFR 229.303 turn on once the figure enters a filing.
01Approved path
A number nobody defines
One federal rule does name earned media: 23 CFR 1300.35(b)(4). A named state official certifies it by 11:59 p.m. EDT on 1 August, exposed under 18 U.S.C. 1001. That duty binds highway-safety grantees, not companies.
02Human review
Searched for, and not there
Full-text search of the Code of Federal Regulations returns nothing for advertising value equivalency, share of voice, earned media value or the Media Rating Council, against controls running to the hundreds; earned media itself returns seven hits, and the seven sit together in NHTSA grant rules.
04Build an evidence trail
The figure, the method that produced it and the person who published it stay together.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Coverage and clip feedsMonitoring vendor · clip exports Articles, broadcast and dates
Integration availability depends on the client's existing systems and API access.
Agent controls
Six checks between the model and the board
Six rules against one edge, the last the finest. What measures true is drawn in the map below.
L6 · Outermost — last line of defenceInward → L1 · closest to the model
L6Rollback / safe modeNarrow the agent to raw counting when evaluation or production signals degrade.Roll back
L5Version trackingTrack model, prompt and method rules, and note the version each figure was counted under.Track
L4Method trailRecord each figure, the corpus under it, the query it used and each read of the file.Record
L3Owner releaseHold the figure for a named owner; the hold governs publication, not whether the number is true.Gate
L2Definition guardrailsTest each figure against its stored method, and refuse to hang a money value on coverage; the industry guidance against that is voluntary and unenforced.Restrict
L1Confidence routingRoute a low-confidence count to an analytics read before the figure reaches the owner.Require review
Model coreFigure counted — the query, the corpus, the counts and the method behind them
L1 – L2Test whether a figure may stand
L3Leaves publication to a named owner
L4 – L5Keep the figure and the method behind it
L6Publishes the count and no valuation when signals degrade
How Nestack evaluates it
Evaluate the whole counting run — not only the figure that comes out.
Coverage runs the whole depth of the workflow, and every layer is cut by slice.
Surface — the figure a board pack carries
Depth of coverage ▼
E1Final-output evaluationDid the figure record the method it was actually counted under?
E2Step-level evaluationDid the agent read the right corpus, the right window and the live query?
E3Tool evaluationDid it read and write the correct period and the correct metric?
E4Confidence calibrationDo low-confidence counts actually attract more owner corrections?
E5Slice evaluationHow does performance change across specific metric classes?
E6Business outcomeHow many figures needed a correction before the owner published?
Floor — the corpus a figure rests on
Failure modes
Where each failure originates in the agent
Seven failure modes, each placed where it first becomes visible.
Agent lifecycleDirection of processing →
01 · Retrieval1 mode
UF-04
Corpus shifted, label held
The outlet list moved between one period and the next.
Stage gathersThe clips, the logs, the dates and the outlets
02 · Reasoning2 modes
UF-01
Query rewritten mid-series
The boolean changed and the volume changed with it.
UF-06
Hostile piece read as neutral
A damaging article quotes the company at length.
Stage proposesThe query, the counts, the split and confidence
03 · Tool / write2 modes
UF-02
Whole-site audience credited
One article is credited with a month of visitors.
UF-05
Valuation under a new name
The same rate-card multiplication, relabelled.
Stage writesOnly where write access and approval policy allow it
04 · Output1 mode
UF-03
Number crosses into a filing
A dashboard figure becomes one an officer certifies.
Stage returnsThe figure a board reads and an officer signs
05 · Change / Version1 mode
UF-07
Method changed without a note
The label holds while the arithmetic underneath moves.
Stage tracksModel, prompt, query rules and corpus dates
Sev-1 · a figure certified on no recordSev-2 · a stale corpus reaches the boardSev-3 · signals degrade, figure held back
A report-level correction figure can read clean while modelled reach figures carry most of the rework. Nestack reports the correction rate by metric class, not only across the report as a whole.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Modelled reach figures
8.8%
3.7×
Review
Share-of-voice ratios
6.2%
2.6×
Review
Sentiment splits
3.9%
1.6×
Watch
Raw clip counts
1.8%
0.8×
Normal
Bar: correction-rate lift vs. raw-count baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unset denominator costs
A cycle ends when the figure whose method changed without a note is a standing case. That suite is what the next period reported is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Correction rate rises on modelled reach figures.
02Diagnose
The share that climbed because a competitor quietly left the index is worked backwards until one cause is left standing.
03Improve
The report goes out numbered, and the methods beneath it ride with it.
04Verify
One method case still failing is enough to hold the report back.
05Learn
It is kept for good, and the method notes are amended in the same commit.
Learn → DetectThe return edge. The next report 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, counting logic, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Method-definition and automation-boundary controls.
02Corpus, query and audience sources.
03Query-to-figure trails and definition-coverage maps.
04Corpus snapshot ingestion.
05Query, window and method binding.
06Reproducibility scoring and review routing.
07Owner publication workflow.
08Reporting-system integration.
09Method and definition cases.
10Guardrails and valuation controls.
11Method-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 report, one cycleProductionProduction reporting workflowAdvancedMultiple markets / metric sets
Introduced at Pilot
Counting to your stored methods✓✓✓
Named owner publication✓✓✓
Definition-register baseline✓✓✓
Introduced at Production
Reporting by coverage class—✓✓
Analytics review workflow in your systems—✓✓
Approved dashboard write-back—✓✓
Corpus-and-warehouse integration—✓✓
Introduced at Advanced
Multi-corpus reconciliation——✓
Cross-market metric packs——✓
Dense coverage volumes——✓
Multi-market measurement controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, coverage volume, approval controls and deployment needs.
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 live metrics and the method each one is counted by→Method capture and definition versioningWeek 1
02Representative corpus, query and audience material→Source binding, counting logic and the definition registerWeek 2
03Your reporting calendar and the owners it names→Method mapping, corpus binding and the automation boundaryWeek 1
04Access to the relevant feeds, exports or vendor APIs→Corpus, query and audience-source assessment, then integration setupWeek 2
05Figures you would not want reconciled→Definition cases and the failure-mode roundWeek 4
06What no figure may be called→Reproducibility scoring, review routing, guardrails and release controlsWeek 3
07A named measurement owner who publishes→Release to the named 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
These bands are counted rather than evened; the fifth week holds two because those two truly coincide.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Method discovery, definition versioning and the automation boundaryW2Corpus and query integration, and the definition-register baselineW3Counting logic, reproducibility checks and release controlsW4Evaluation suite, definition cases and failure-mode testingW5Warehouse and reporting integration, pilot figures and targeted correctionsW6One reporting period run under the measurement owner, then Agent Care handover
Reading the bandNo bar runs past the weeks its own work is named for, and week five carries two by design.
At the end of W6When the method 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 · Measurement AI agent
Build a measurement agent around the method your last coverage report never wrote down.
Show us one number your team reports each quarter and the query and the corpus behind it. If nobody can rebuild that figure from the record, it is not a measurement but a claim. A number that will not rebuild comes back as a finding.
