Build the deal file behind each agreement — the clock from execution, the payor, the standard in force when it cleared — then hand each signer the pack they attest to.
An agreement is executed, and the clock runs from that moment, not from the day compliance received it.
02
A payor is evidenced deal by deal — the institution's own rights-holder included — never taken as read.
Reason
03
A threshold moves, and the file keeps the memorandum version that was in force on the day that deal cleared.
04
A deal is filed with what is sold to the general public for profit and what the activation obligations fix.
05
A running Associated-deal total is held per athlete per academic year, and never summed across a trigger change.
Decide
06
A revenue-share agreement runs on its own clock into CAPS, and the cap position is kept on the academic year.
07
A state duty follows the instrument that binds — Texas, California and Colorado each set a different one today.
Out
08
A pack is built for each signer, and the file holds the submissions, the outcomes and the standard behind each.
09
Execute write actions only inside the approval boundaries agreed during implementation.
→Product statement
The agent assembles the file and keeps the standard of record; the Commission clears, and the president, the athletics director and each head coach attest.
Example workflow
One deal, execution to signature
AgentHuman
1Agreement executedThird-party contract, revenue-share agreement or agreed payment terms
2File assembledPayor, counterparty relationship, activation obligations and the running total, each with its source
3Standard recordedThe band, the methodology version and the memorandum date in force
4Controls appliedClock checks, payor-evidence checks, state-duty checks and completeness confidence
No human action required
Stages 1 to 4 run unaided, and nothing is cleared or attested at any of them — the agent is assembling, and the compliance lane opens at the completeness gate.
5DecisionBranches at the completeness gate
File complete
Goes to the compliance director to release.
Anything thin
Adds a general-counsel read first.
Compliance review
The file is held with its clocks, its standard of record and its gaps.
Release the file · Append evidence · Send to counsel
Released — submitted by a named person▼
6Compliance systems updatedOnly where write access and disclosure policy allow it
7Outcome evaluatedClock margin, evidence completeness, counsel corrections and what a later review found
Corrections
Each counsel correction is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Determining fair market value, or any range of it.
Clearing a deal, or predicting that it will clear.
Completing or signing any attestation.
Submitting or affirming a deal for an athlete.
Automation boundaryAgent acts unaided
✓Assemble the deal file from the agreement and the evidence behind it.
✓Run each disclosure clock from the execution date, per instrument.
✓Record the standard in force on the day the deal cleared.
✓Hold the running total and flag before the live trigger.
Nothing leaves the file except by a named signer, inside the agreed boundaries.
Making the associated-entity determination itself.
Deciding whether a violation must be self-reported.
Negotiating, restructuring or repricing a deal.
Changes to thresholds, clocks or signer packs.
Example output
One deal, annotated
A year after the signatures this file is the evidence, and it reads for you or against you.
Deal file · single agreementIllustrative example
Deal
Filed as
Clock
Standard of record
Confidence
Released by
Local retailer, Olympic sport
Appearance and merchandise activation, dated and fixed
Day 2 from execution
23 June 2026 memorandum
Held unreleased
The compliance director, in person
As receivedTaken from the executed agreement and the memorandum in force that day — nothing here is valued by the agent.
What the file holdsThe executed agreementPayor-relationship proofActivation obligations
Why no valuation hereThe range runs against a dataset the Commission revises as deals clear.
ActionRelease the fileAppend evidenceSend to counsel
What the score decidesBelow the configured threshold the file picks up a counsel read before.
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 dealFrom the executed agreement
03Evidence
Evidence the price, not the player
Our scouting agent evidences a player for a scout; this evidences a figure for a regulator.
01Approved path
Which standard cleared it
Five standards in fourteen months, so a file recording only cleared cannot be read back.
02Human review
Where the exposure now reaches
Executive Order 14400 made an unsupportable figure a debarment question on 1 August 2026; its reporting limb only directs consideration.
04Build an evidence trail
The deal, the standard in force when it cleared and the signer who attested stay on the file.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Disclosure platformsNIL Go · CAPS Institutional submission portals
A programme-level standard-provenance figure can read clean while one deal type absorbs most of the corrections. Nestack reports the counsel-correction rate by deal type, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Collective and associated deals
9.7%
3.7×
Review
Multimedia-rights routed deals
7.5%
2.8×
Review
Football and basketball deals
4.5%
1.7×
Watch
Olympic-sport local deals
1.7%
0.6×
Normal
Bar: counsel-correction-rate lift vs. Olympic-sport local baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
What an unreconstructable file costs
A cycle closes when the unreconstructable file is a regression case. That suite is what the next deal recorded is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Counsel-correction rate rises in one deal type.
02Diagnose
The two contracts with four regulatory statuses in five months are read back until one cause remains.
03Improve
The change ships numbered, and the deals that forced it ride with it.
04Verify
Nothing releases while one touched deal case is still red.
05Learn
It is kept for good, and the threshold rules are amended in the same commit.
Learn → DetectThe return edge. The next deal 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, file assembly, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Deal workflow discovery and boundary definition.
02Contract, roster and ledger sources.
03Threshold, methodology, clock and state-duty mapping.
04Agreement ingestion and file normalisation.
05Standard-of-record and evidence binding.
06Completeness scoring and counsel routing.
07Signer pack workflow.
08Compliance and ledger integration.
09Threshold and rationale cases.
10Guardrails and attestation controls.
11Deal-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 sport, one payor typeProductionProduction compliance systemsAdvancedMultiple sports / systems
Introduced at Pilot
File assembly to your rules✓✓✓
Named-signer release✓✓✓
Standard-provenance baseline✓✓✓
Introduced at Production
Reporting by sport—✓✓
Release workflow in your systems—✓✓
Approved write-back—✓✓
Compliance-system integration—✓✓
Introduced at Advanced
Multi-state disclosure duties——✓
Cross-sport signer packs——✓
High deal volume——✓
Multi-signer attestation 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 deal intake and record structure→Agreement ingestion and file normalisationWeek 1
02Representative executed agreements→File baseline, clock binding and standard-of-record captureWeek 2
03Your thresholds, clocks and state duties→Threshold, clock and state-duty mapping and the automation boundaryWeek 1
04Access to relevant APIs, feeds or exports→Compliance, roster and ledger assessment, then integration setupWeek 2
05Files you would not want reconstructed→Threshold cases and failure-mode testingWeek 4
06What no attestation may cover→Completeness scoring, counsel routing, guardrails and release controlsWeek 3
07Named signers and a compliance director→Signer release 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
These bands are the weeks each phase honestly costs, which is why the fifth one carries a pair.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Deal discovery, threshold mapping and the automation boundaryW2Source integration and the file baselineW3Assembly workflow, clock logic and release controlsW4Evaluation suite, threshold cases and failure-mode testingW5Compliance integration, pilot deals and targeted correctionsW6One attestation year run under the compliance director, then Agent Care handover
Reading the bandA bar covers only the weeks its own work is named in. The doubled fifth week is real work, not padding.
At the end of W6Validation closes on live deals, and Agent Care picks up the watch.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Sports & Fitness agent
Build a NIL disclosure agent around the people who have to sign.
Show us how a deal reaches you today and who signs on 1 September. If your file records that a deal cleared but not which standard cleared it, then the person signing for it cannot reconstruct it, and no OMB guidance we could find says otherwise.
