# TrooIDs — Digital DNA: one real problem, one practical walkthrough

Transcript of the episode as synthesised. Every factual line names the passage it comes from (source ids refer to files of this site's knowledge bundle). Hosts: Giovanni (A, cloned voice with consent) and Co-host (B, synthetic voice).

**[00:00] Co-host:** Why do the apps and algorithms we use every day seem to serve advertisers, platform retention and corporate metrics, rather than what we actually want?
Sources: none (a question or challenge, no factual claim)

**[00:10] Giovanni:** Because of what the source calls the principal-agent problem. The flow today is you, then a platform, then an algorithm, then an outcome. The algorithm looks as if it serves you, but it also serves advertising revenue, engagement and third-party interests.
Sources: [src:agency-conflict.md](https://trooids.com/knowledge/agency-conflict.md)

**[00:28] Co-host:** So if we generate all the data, how do we become the actual principal in that chain?
Sources: none (a question or challenge, no factual claim)

**[00:34] Giovanni:** Digital DNA's answer is the Agent of One: a private digital intelligence that represents an audience of exactly one person, you. The flow becomes you, your agent, the outcome. The agent knows only the information you authorise; it understands your objectives, preferences and permissions; and it works for you, not for the company providing the interface.
Sources: [src:agent-of-one.md](https://trooids.com/knowledge/agent-of-one.md), [src:agency-conflict.md](https://trooids.com/knowledge/agency-conflict.md)

**[00:58] Co-host:** Let me put my skeptic's hat on. Concepts are easy. How is that control actually enforced, without your so-called agent leaking my information everywhere?
Sources: none (a question or challenge, no factual claim)

**[01:09] Giovanni:** The site has a live, supported example: the permission workbench, at troo-ids dot com slash workbench. It uses fixture data, a week of calendar events, one private note and three fictional contacts, created in your browser tab. Nothing leaves the tab.
Sources: [src:workbench.md](https://trooids.com/knowledge/workbench.md)

**[01:27] Co-host:** And what happens in it?
Sources: none (a question or challenge, no factual claim)

**[01:29] Giovanni:** Three steps. First, you grant a scheduling assistant one field only, calendar availability, under a rule called R-1. Second, it proposes three time slots from that one permitted read; its optional request for your calendar titles is refused, and the function still completes. Third, you revoke R-1, run it again, and it fails with "R-1 revoked". A policy engine sits between every function and the data: there is no default allow, and a readable trace, what was used, the objective, the rule, the result, is written before any data is returned.
Sources: [src:workbench.md](https://trooids.com/knowledge/workbench.md)

**[02:09] Co-host:** Fair. But that workbench runs in a browser tab with sample data. Is this a product I can download today, or is it theory?
Sources: none (a question or challenge, no factual claim)

**[02:17] Giovanni:** A bounded, honest answer: it is architecture, designed, not a finished product. What exists today is the website, the knowledge bundle, the workbench and a contact facility. There is no Agent of One you can download or use yet.
Sources: [src:digital-dna.md](https://trooids.com/knowledge/digital-dna.md), [src:today-and-next.md](https://trooids.com/knowledge/today-and-next.md), [src:workbench.md](https://trooids.com/knowledge/workbench.md)

**[02:34] Co-host:** I appreciate the reality check. So what is the next step?
Sources: none (a question or challenge, no factual claim)

**[02:38] Giovanni:** Register your interest on the site; the team replies within two working days, and individuals are invited when a first cohort opens. And one thought to leave you with, from the same bundle: the pull economy. Permissionless sending, consensual receiving. A sender no longer buys permission from a platform to reach you; your agent decides whether a message gets your attention. Addressability is not delivery, and delivery is not attention.
Sources: [src:today-and-next.md](https://trooids.com/knowledge/today-and-next.md), [src:pull-economy.md](https://trooids.com/knowledge/pull-economy.md)