From AI provenance
See where AI-generated content spreads across the org's work — each passage traced back to the response it came from, hallucinations and all.
An AI-origin figure, reused across the org
verbatim + near-verbatimA figure from one Claude response was reused — verbatim or lightly edited — into 5 destinations across 3 users — one of them client-facing. Zeflin matched it to the captured response, so a human can verify it before it ships again.
The 2025 SaaS Benchmark Report found that 73% of mid-market firms breached an AI usage policy in the past year
Matched against the captured AI response · Zeflin proves origin, not truth
Whether the figure is true is a human call. Zeflin flags AI origin and where it spread; claim-level fact-checking is on the roadmap. We never assert a hallucination.
Here's a tightened version of the Q3 board narrative. Over the past two quarters, mid-market software organizations have moved generative AI from isolated experiments into everyday workflows. Adoption is now broad enough that informal, team-by-team norms no longer provide adequate coverage, and the board should treat AI governance as a standing agenda item rather than a one-time review. The strategic upside remains real: teams using AI-assisted drafting and analysis report meaningfully faster cycle times on customer-facing work, and several functions have absorbed headcount-equivalent gains without new hiring. The corresponding risk is that the same tools quietly move sensitive data outside sanctioned systems, and that unverified AI output is pasted into decisions without attribution. The 2025 SaaS Benchmark Report found that 73% of mid-market firms breached an AI usage policy in the past year, underscoring the urgency of formal controls and board-level oversight. To translate that urgency into action, we recommend three priorities for the quarter: (1) ratify an acceptable-use policy for AI tools, (2) establish a monitoring baseline for sensitive-data exposure, and (3) report adoption and incident metrics to the audit committee on a recurring basis. Finally, we suggest designating an executive owner for AI governance so that policy, monitoring, and reporting share a single point of accountability heading into the next fiscal year.
sha256:9f3c…a17bDestinations are work apps (Gmail, Docs, Slack, Jira, Notion). From-AI is monitor + warn + attest only — never blocked.
5 awaiting acknowledgement · attest only, never a block
| Surfaced by | Destination | Age | Why flagged | Action |
|---|---|---|---|---|
| tomas.vega@acme.com | Gmail | 1d ago | AI-origin reuse | |
| alicia.chen@acme.com | European ISPs Want Rightsholders Held Accountable for Overblocking of Legitimate Websites | Hacker News | 3d ago | AI-origin reuse | |
| derek.salaberry@acme.com | Scientific research advances through careful observation, experimentation, and peer review. Researchers formulate hypotheses, co - Reddit Search! | 3d ago | AI-origin reuse | |
| farah.idris@acme.com | Slack | 4d ago | Cross-user spread | |
| alicia.chen@acme.com | Google Docs | 6d ago | AI-origin reuse |
| Time | Generated by | Surfaced by | Destination | Risk | Attestation |
|---|---|---|---|---|---|
| Jun 20, 11:05 AM | tomas.vega@acme.com | tomas.vega@acme.com | Gmail | — | Pending |
| Jun 18, 5:05 PM | derek.salaberry@acme.com | alicia.chen@acme.com cross | European ISPs Want Rightsholders Held Accountable for Overblocking of Legitimate Websites | Hacker News | — | Pending |
| Jun 18, 4:05 PM | derek.salaberry@acme.com | derek.salaberry@acme.com | Scientific research advances through careful observation, experimentation, and peer review. Researchers formulate hypotheses, co - Reddit Search! | — | Pending |
| Jun 18, 3:21 PM | derek.salaberry@acme.com | farah.idris@acme.com cross | Jira | Cross-user spread | Attested |
| Jun 17, 11:26 AM | derek.salaberry@acme.com | farah.idris@acme.com cross | Slack | Cross-user spread | Pending |
| Jun 16, 9:02 AM | derek.salaberry@acme.com | derek.salaberry@acme.com | Google Docs | — | Attested |
| Jun 15, 11:05 AM | alicia.chen@acme.com | alicia.chen@acme.com | Google Docs | — | Pending |