> [!question] Lingering Questions > - Does agent-based permission auditing find a different error distribution than conventional scanning, since it traverses as a user rather than enumerating as a tool? > - What is the actual cost of duplicated preparation work in decentralized AI pilots, versus a coordinated programme? > [!tip] Article Ideas > - "Your permissions were fine because nobody looked" — enterprise agent-readiness piece built on the practical-obscurity mechanism this clip names. > [!link] Cross Reference > - **Strong sibling to [[3. Resources/Permanent Notes/Practical Obscurity Is an Economic Property Not a Technical One]]** — that note is about cost collapse making mass deanonymization viable; this clip is the same mechanism inside the enterprise, where the collapsing cost is *search*. Two independent instances of one claim. > - One of six sibling clips from the same Trail of Bits talk in this batch. > [!quote] Vocabulary > - **agent legible** — data prepared such that an agent can search and reason over it, which is what forces the permissions question > - **forced permission audit** — the framing that agent-readiness makes a deferred governance task unavoidable rather than merely advisable ## Metadata - Source: [[3. Resources/Readwise/Articles/All of It’s Becoming Due at the Same Time|All of It's Becoming Due at the Same Time]] - Category: Video (YouTube short-form clip) - Published: 2026-07-31 ## Author's thesis Making enterprise data legible to agents forces a permissions audit that was always advisable and now can't be deferred, and it simultaneously raises the cost of every existing permission error, because an overshared file that survived on practical obscurity gets found the instant something searches everything instantly. ## Key arguments 1. **Agent-readiness is a forced permissions audit**, not a recommended one — the agent surfaces whatever permissions actually permit, not whatever anyone intended. 2. **The cost inversion is precise**: nothing about the permission changes, only the probability of discovery — practical obscurity was doing real security work that nobody accounted for. 3. **Deferred technical debt collapses onto one schedule** when something encounters everything concurrently instead of serially, which is why agent adoption feels disproportionately disruptive. ## Claim atoms ### Agent-readiness is a forced permissions audit > [!quote] ID:rw_01kywpa93s32mkm7fx0z24nq8w > Making data agent legible is a forced permission audit. You have to actually go through and figure out who can access what, how do we access stuff, where are the permissions on things. *Where:* ~00:00:00. *Why:* reframes an AI-enablement task as a governance one — the audit happens either deliberately or by disclosure. ### Oversharing stops being survivable when discovery becomes instant > [!quote] ID:rw_01kywpa93s32mkm7fx0z24nq8w > this also raises the stakes for permissions errors. If uh you overshare the information, now an AI agent within your company's going to find it instantly. *Where:* ~00:00:30. *Why:* the permission doesn't change, only the probability of discovery does — practical obscurity was carrying more security load than anyone accounted for. ### Uncoordinated adoption duplicates the expensive prerequisite > [!quote] ID:rw_01kywpa93s32mkm7fx0z24nq8w > they'll have various pockets of like no coordination... And that process leads to a lot of repeated work. *Where:* ~00:01:00. *Why:* a bounded argument against decentralized AI experimentation, specific to the shared data-access setup cost that each uncoordinated pocket rebuilds from scratch. ## Permanent candidates - The core practical-obscurity claim should **extend the existing [[3. Resources/Permanent Notes/Practical Obscurity Is an Economic Property Not a Technical One]]** rather than duplicate it — same mechanism, enterprise-search instance. - **Uncoordinated agent adoption duplicates the shared data-access prerequisite** — a distinct, narrower claim worth its own Permanent note. ## Processing checklist - [ ] Compare against Microsoft's published Copilot oversharing guidance - [ ] Audit access scopes on shared infrastructure before enabling agent tooling - [x] Connect into the relevant MOC — [[3. Resources/MOCs/AI Agent Safety MOC]] ## Links - [[3. Resources/MOCs/AI Agent Safety MOC]] — agent-driven permission exposure is core agent-security territory. - [[3. Resources/Permanent Notes/Practical Obscurity Is an Economic Property Not a Technical One]] — the general mechanism this clip instantiates inside the enterprise. - [[3. Resources/Permanent Notes/Uncoordinated Agent Adoption Duplicates the Shared Data-Access Prerequisite]] — the new Permanent note this Literature note generated.