AI Governance · Data Lineage
Where the AI’s numbers come from
Every AI-flagged surface, its grounding data, and refresh cadence · auditable provenance for every claim
AI surfaces
28
tracked across the prototype
Source systems
8
NetSuite, Ramp, Nexonia, Amazon Purchases, internal tracker, +3
Avg refresh cadence
Continuous
majority of surfaces · 5 min median for batch sources
Citations served / 24h
4,127
every AI-rendered number resolved to a source row
Every number rendered in an AI-flagged panel must come from a tool result — never inlined as prose. The Playbook’s renderer enforces this at the component level: numeric values are rendered through citation-grounded spans (tabular-nums) that link back to the source row in mock-data, NetSuite, Ramp, or another system of record. This page is the inventory of those linkages.
Each row = one AI-rendered claim or panel; each column = a piece of grounding metadata
| Surface | Claim type | Source system | Source field / table | Refresh cadence | Last refresh | Confidence |
|---|---|---|---|---|---|---|
| /clients/amazon-ads/retainer-health | AI summary card | Internal tracker | retainerEngagements.forecastTotalHours | Continuous | 2 min ago | High |
| /events/amazon-immersion-day-la/engage/statement-floral | AI relationship intelligence | Internal tracker + Ramp | vendor.spendYTD, rampTransactions | Continuous | 5 min ago | High |
| /events/amazon-immersion-day-la/proposals | Outlier flag | Manual upload (PDF extract) | vendorProposals.extractedItems[].flagged | On upload | 4 days ago | Medium |
| /admin/time-tracking | Burn forecast | NetSuite | jobCodes.weeklyHours velocity | Weekly | 2 days ago | Medium |
| /insights/portfolio-health | AI synthesis | Internal tracker | events.status, projectBurn | Continuous | 2 min ago | High |
| /contractors/lin-zhao#feedback | Pattern detection | Internal tracker | contractorFeedback.behaviorNotes | On feedback submit | 1 day ago | Medium |
| /insights/geo-costing | Cost recommendation | Manual entry | geoCostScenarios.options | On scenario refresh | 1 week ago | Low |
| /clients/amazon-ads/items-catalog | Categorization | Internal tracker | catalogItems.category | On vendor catalog upload | 4 days ago | Medium |
| / (Mission Control heads-up) | Risk synthesis | Internal tracker | events.riskReason | Continuous | 1 min ago | High |
| /events/amazon-immersion-day-la/recommend-vendors | Vendor ranking | Internal tracker + tariff data | vendor.rating, vendor.spendYTD, vendor.riskFlags | Continuous | 5 min ago | High |
| /contracts/statement-floral-decor-2026 | Anomaly flag | Internal tracker | contracts.anomalies[] | On contract revision | 2 days ago | High |
| /insights/anomalies | Pattern detection | Multi-source | globalActivities, rampTransactions, contracts | Hourly | 30 min ago | Medium |
| /ask | Ask the Playbook answers | Multi-source | All entity tables | On query | Real-time | High |
| /standup | Morning brief | Multi-source | events, approvals, globalActivities | Daily 06:00 ET | 8 hours ago | High |
| /admin/ai-decisions | Past AI decisions | Multi-source | audit log | Continuous | 2 min ago | High |
| /clients/amazon-ads/brand#viz-id | Reuse opportunity | Internal tracker | vizIDPackages.applicableTemplateSlugs | On template add | 21 days ago | Medium |
| /approvals | Approval recommendation | Internal tracker + NetSuite | approvals.aiSuggestion, aiConfidence | On approval queue update | 12 min ago | High |
| /admin/ai-costs | Spend rollup | Anthropic + OpenAI billing | aiCostLedger.tokenSpend | Hourly | 45 min ago | High |
Below is the actual source chain for one AI claim — the Statement Floral $4.2M YTD figure
- 1
UI component
<EngagementPanel />at /events/amazon-immersion-day-la/engage/statement-floral - 2
AI claim
“Statement Floral — $4.2M YTD across 14 events” - 3
Renderer
<span className="font-medium tabular-nums">{vendor.spendYTD}</span>— pure data, no AI inference - 4
Data source
vendors.find(v => v.slug === 'statement-floral').spendYTD === 4_200_000 - 5
System of record
NVE internal vendor master · synced from NetSuite GL spend rollup nightly - 6
Last attestation
2026-05-08 via finance-ops review
What happens if a source system is down or a number can’t be cited
- If the source row doesn’t exist, the AI surface renders an em-dash placeholder, not a fabricated number.
- If the source system is unreachable (e.g. NetSuite outage), the panel shows a “Source unavailable” state with last-good timestamp.
- If the AI confidence is below threshold (Low), the surface adds an “AI-tentative” Badge prompting human review.
- Every claim has a click-through to its source row — anyone can verify.
See also
Lineage answers “where does the number come from?”. The decision log answers “what did the human do with it?”.
Inventory derived from observable code · 18 surfaces catalogued of 28 AI-rendered panels · AI flags, doesn’t fix