# Customer Data Architecture — Position Record Why customer data stopped moving — the composable/warehouse-native shift, the fourth generation it set up, what an agentic layer is (and isn’t) allowed to hold, and — one layer downstream — how signal containerization applies the same governed-movement discipline to a signal that has to travel without anyone losing control of it. > Markdown twin of https://nofluffadvisory.com/thinking/customer-data-architecture/ — the Position Record for Composable CDP + Agentic CDP + Customer data architecture + Identity resolution + Signal containerization. Generated from the verified position ledger; methodology: https://nofluffadvisory.com/thinking/ ## Current positions **Composable CDP** — The suite-versus-pipe dichotomy missed a third option that is now real: the warehouse vendor itself becoming the suite and selling the warehouse-to-platform seam clean. > “The suite-versus-pipe dichotomy failed to price the third option: the warehouse vendor itself becoming the suite.” — [On the Record — Entry № 1](https://nofluffadvisory.com/on-the-record/), Jul 21, 2026 **Agentic CDP** — Fourth-generation agentic-CDP claims are currently vendor-claimed and architecturally reasoned, not operationally demonstrated. > “The fourth-generation products making this argument are early — much of it is vendor-claimed and architecturally reasoned rather than operationally demonstrated.” — [standards/composable-cdp-vs-reverse-etl-vs-packaged-cdp](https://nofluffadvisory.com/standards/composable-cdp-vs-reverse-etl-vs-packaged-cdp/), Aug 3, 2026 **Customer data architecture** — An agentic decision layer should hold governed working memory only — never a duplicate customer record — reading from source and pointing back to source. > “So it keeps governed working memory and nothing else. No duplicate customer record. It reads from source, holds only what it needs to reason, act, audit, and measure” — [building/ai-growth-operator](https://nofluffadvisory.com/building/ai-growth-operator/), Jul 7, 2026 **Identity resolution** — In-warehouse identity ownership still requires a bridge to a shared ID or clean-room match at the activation edge; the shared spine becomes a component you call, not the system of record. > “A warehouse-native stack still usually bridges to a shared ID at the activation edge — a universal ID, or a clean-room match — because your internal keys do not reach the open web on their own” — [The Composable CDP: How Customer Data Stopped Moving](https://nofluffadvisory.com/writing/the-composable-cdp-how-customer-data-stopped-moving/), Jun 19, 2026 **Signal containerization** — Curation and containerization are the same packaging move at different maturity stages: curation is packaging that learned to charge, containerization is packaging that learned to answer. > “Curation is packaging that learned to charge. Containerization is packaging that learned to answer.” — [The Great Repackaging](https://nofluffadvisory.com/writing/the-great-repackaging/), Jul 16, 2026 27 positions tracked · held since Aug 3, 2026 · record spans Jun 7, 2026 – Aug 3, 2026 **Verified tensions:** none currently recorded between the positions on this page. That is a statement about what the ledger has verified — not the result of an exhaustive contradiction analysis. ## Coverage gap, disclosed Every verified position below is either still holding or was confirmed by a later event — no unresolved open call yet. That's not because Evgeny's thinking never reverses or leaves a question open elsewhere on this site; this topic's own record simply hasn't reached one yet. Rather than manufacture a loss or an open call to look complete, this page stays visibly partial until a real one earns its place. ## The timeline — newest first ### Aug 3, 2026 — Claim — Current · Agentic CDP The agentic CDP is an overlay on the three existing customer-data architectures, not a fourth procurement alternative — it shifts the weights in the comparison rather than adding a column. > “Not yet. "Agentic CDP" names an overlay on the three architectures compared here, not a fourth procurement alternative” — [standards/composable-cdp-vs-reverse-etl-vs-packaged-cdp](https://nofluffadvisory.com/standards/composable-cdp-vs-reverse-etl-vs-packaged-cdp/), Aug 3, 2026 - Status: current — no change since Aug 3, 2026. ### Aug 3, 2026 — Claim — Current · Agentic CDP Fourth-generation agentic-CDP claims are currently vendor-claimed and architecturally reasoned, not operationally demonstrated. > “The fourth-generation products making this argument are early — much of it is vendor-claimed and architecturally reasoned rather than operationally demonstrated.” — [standards/composable-cdp-vs-reverse-etl-vs-packaged-cdp](https://nofluffadvisory.com/standards/composable-cdp-vs-reverse-etl-vs-packaged-cdp/), Aug 3, 2026 - Status: current — no change since Aug 3, 2026. ### Jul 21, 2026 — Verdict — Current · Composable CDP The suite-versus-pipe dichotomy missed a third option that is now real: the warehouse vendor itself becoming the suite and selling the warehouse-to-platform seam clean. > “The suite-versus-pipe dichotomy failed to price the third option: the warehouse vendor itself becoming the suite.” — [On the Record — Entry № 1](https://nofluffadvisory.com/on-the-record/), Jul 21, 2026 - Status: current — no change since Jul 21, 2026. ### Jul 16, 2026 — Framework — Current · Signal containerization Curation and containerization are the same packaging move at different maturity stages: curation is packaging that learned to charge, containerization is packaging that learned to answer. > “Curation is packaging that learned to charge. Containerization is packaging that learned to answer.” — [The Great Repackaging](https://nofluffadvisory.com/writing/the-great-repackaging/), Jul 16, 2026 - Status: current — no change since Jul 16, 2026. ### Jul 13, 2026 — Claim — Current · Confirmed · Agentic CDP Agents acting on customer data need a governed truth, which strengthens the warehouse-native case and raises packaged-CDP exit stakes. > “An agent needs a governed truth to act on — memory, permissions, and audit live wherever the customer copy lives.” — [CDP vs. Reverse ETL Is the Wrong Question](https://nofluffadvisory.com/writing/cdp-vs-reverse-etl/), Jul 13, 2026 - Confirmed: Jul 21, 2026 - Status: current — no change since Jul 13, 2026. ### Jul 13, 2026 — Framework — Superseded (refined) · Composable CDP Comparing CDPs to reverse ETL is a category error: a CDP is a suite, reverse ETL is a pipe, and the deciding question is where the governed copy of the customer lives. > “A CDP is a suite — a place customer data lives, plus the machinery around it. Reverse ETL is a pipe — a mechanism that moves data from where it lives to where work happens.” — [CDP vs. Reverse ETL Is the Wrong Question](https://nofluffadvisory.com/writing/cdp-vs-reverse-etl/), Jul 13, 2026 - Refined by: “The suite-versus-pipe dichotomy missed a third option that is now real: the warehouse vendor itself becoming the suite and selling the warehouse-to-platform seam clean.” (Jul 21, 2026) ### Jul 13, 2026 — Call — Retracted · Composable CDP The hybrid of warehouse ownership plus sub-second personalization is a seam buyers must engineer themselves because no vendor sells it clean. > “Expect to engineer the seam yourself; nobody sells it clean.” — [CDP vs. Reverse ETL Is the Wrong Question](https://nofluffadvisory.com/writing/cdp-vs-reverse-etl/), Jul 13, 2026 - Correction: this call was retracted — the corrected position is “The suite-versus-pipe dichotomy missed a third option that is now real: the warehouse vendor itself becoming the suite and selling the warehouse-to-platform seam clean.” (Jul 21, 2026). AUDIT'S BIGGEST CATCH: retracted on-the-record 07-21, yet the retracted sentence ships VERBATIM on the standards page stamped LAST_VALIDATED 2026-08-03. True state is 'contested-stale' — per-surface status, unrepresentable in v0. Lint finding, fires today. Retraction window: 8 days. ### Jul 13, 2026 — Claim — Current · Signal containerization Everything the stack currently carries -- identity graphs, contextual signals, Agentic Audiences vectors, signal containers -- encodes only the who and the what of a moment; where and when have no native representation yet. > “Identity graphs, contextual signals, the dense vectors inside Agentic Audiences, the signal containers this site has argued for — all of it encodes the who and the what.” — [The Context Economy Has a Governance Problem](https://nofluffadvisory.com/writing/the-context-economy/), Jul 13, 2026 - Status: current — no change since Jul 13, 2026. ### Jul 13, 2026 — Claim — Current · Signal containerization The policy layer inside a signal container -- not the activation logic -- is what separates a context economy from a surveillance economy running on the same rails. > “The policy layer is not paperwork stapled to the signal. It is the thing that separates a context economy from a surveillance economy running on the same rails.” — [The Context Economy Has a Governance Problem](https://nofluffadvisory.com/writing/the-context-economy/), Jul 13, 2026 - Status: current — no change since Jul 13, 2026. ### Jul 7, 2026 — Framework — Current · Agentic CDP There is a fourth agentic-CDP implementation cell the category skipped — federated over the merchant's existing SaaS stack, for buyers with no warehouse and no data team — and Ev is building it. > “This product takes the fourth cell: federated. The decision layer sits over the merchant's existing SaaS stack and keeps only governed working memory — context, a versioned constitution, a ledger, holdout state.” — [building/ai-growth-operator](https://nofluffadvisory.com/building/ai-growth-operator/), Jul 7, 2026 - Status: current — no change since Jul 7, 2026. ### Jul 7, 2026 — Framework — Current · Customer data architecture An agentic decision layer should hold governed working memory only — never a duplicate customer record — reading from source and pointing back to source. > “So it keeps governed working memory and nothing else. No duplicate customer record. It reads from source, holds only what it needs to reason, act, audit, and measure” — [building/ai-growth-operator](https://nofluffadvisory.com/building/ai-growth-operator/), Jul 7, 2026 - Status: current — no change since Jul 7, 2026. ### Jul 5, 2026 — Framework — Current · Customer data architecture Generation four of customer data architecture begins after data stops moving: the record stays put and everything else moves instead. > “Generation four is what happens once it has stopped: the record stays put, and everything else moves instead.” — [Adtech and Martech Were Never Two Industries. They Were Two Copies of the Customer.](https://nofluffadvisory.com/writing/the-agentic-cdp-two-industries-one-table/), Jul 5, 2026 - Status: current — no change since Jul 5, 2026. ### Jul 5, 2026 — Claim — Current · Composable CDP Lock-in migrates again in the agentic era: from rewriting SQL to an organization's accumulated institutional memory held by the agent — an exit cost CustomerLake does not document as exportable. > “The composable era's exit cost was rewriting SQL. This era's exit cost is an organization's institutional memory.” — [Adtech and Martech Were Never Two Industries. They Were Two Copies of the Customer.](https://nofluffadvisory.com/writing/the-agentic-cdp-two-industries-one-table/), Jul 5, 2026 - Status: current — no change since Jul 5, 2026. ### Jul 5, 2026 — Coinage — Current · Customer data architecture Adtech and martech were never two industries but two custodies of one customer record — the Custody Partition — and one governed customer memory dissolves it. > “the Custody Partition — a divide born of who held the customer record” — [Adtech and Martech Were Never Two Industries. They Were Two Copies of the Customer.](https://nofluffadvisory.com/writing/the-agentic-cdp-two-industries-one-table/), Jul 5, 2026 - Coins the term **“Custody Partition”**. - Status: current — no change since Jul 5, 2026. ### Jun 19, 2026 — Claim — Current · Identity resolution In-warehouse identity ownership still requires a bridge to a shared ID or clean-room match at the activation edge; the shared spine becomes a component you call, not the system of record. > “A warehouse-native stack still usually bridges to a shared ID at the activation edge — a universal ID, or a clean-room match — because your internal keys do not reach the open web on their own” — [The Composable CDP: How Customer Data Stopped Moving](https://nofluffadvisory.com/writing/the-composable-cdp-how-customer-data-stopped-moving/), Jun 19, 2026 - Status: current — no change since Jun 19, 2026. ### Jun 19, 2026 — Call — Current · Confirmed · Agentic CDP The governance built for the customer profile becomes the governance needed for the agent — a June call productized by the Snowflake loop five weeks later. > “the governance you built for the profile becomes the governance you need for the agent” — [The Composable CDP: How Customer Data Stopped Moving](https://nofluffadvisory.com/writing/the-composable-cdp-how-customer-data-stopped-moving/), Jun 19, 2026 - Confirmed: Jul 21, 2026 — “the same role-based access, masking, and audit controls that govern your data govern the agent automatically. Same sentence, productized.” - Status: current — no change since Jun 19, 2026. ### Jun 19, 2026 — Call — Current · Confirmed · Composable CDP The activation layer becomes the obvious execution surface for advertising agents — vindicated in operation, still premature in architecture as of the July verdict. > “the activation layer becomes the obvious execution surface for advertising agents” — [The Composable CDP: How Customer Data Stopped Moving](https://nofluffadvisory.com/writing/the-composable-cdp-how-customer-data-stopped-moving/), Jun 19, 2026 - Confirmed: Jul 21, 2026 — “three weeks in, that prediction is vindicated in operation and still premature in architecture.” - Status: current — no change since Jun 19, 2026. ### Jun 19, 2026 — Framework — Current · Composable CDP The warehouse-native model's defining bet is to own the substrate instead of renting the spine — the identity-utility trade in one line. > “The warehouse-native model makes the inverse bet: own the substrate instead of renting the spine.” — [The Composable CDP: How Customer Data Stopped Moving](https://nofluffadvisory.com/writing/the-composable-cdp-how-customer-data-stopped-moving/), Jun 19, 2026 - Status: current — no change since Jun 19, 2026. ### Jun 19, 2026 — Claim — Current · Composable CDP Composable does not escape lock-in; it relocates and arguably deepens it onto the warehouse, the hardest layer to leave. > “Composable reduces application-layer lock-in while concentrating, and arguably deepening, the dependency on the one component hardest to leave: the warehouse.” — [The Composable CDP: How Customer Data Stopped Moving](https://nofluffadvisory.com/writing/the-composable-cdp-how-customer-data-stopped-moving/), Jun 19, 2026 - Status: current — no change since Jun 19, 2026. ### Jun 19, 2026 — Framework — Superseded (refined) · Composable CDP The composable CDP is not a product but the third generation of customer data architecture, defined by refusing to move data. > “It is the Composable CDP, and it is best understood not as a product but as the third generation in a lineage.” — [The Composable CDP: How Customer Data Stopped Moving](https://nofluffadvisory.com/writing/the-composable-cdp-how-customer-data-stopped-moving/), Jun 19, 2026 - Refined by: “Generation four of customer data architecture begins after data stops moving: the record stays put and everything else moves instead.” (Jul 5, 2026) ### Jun 7, 2026 — Coinage — Current · Signal containerization A signal container is a governed, executable decision object — not a segment ID — that packages buyer intent, meaning, provenance, policy, and activation logic together so intent can be discovered, matched, scored, activated, and audited across systems. > “A segment says, "Here is a group of users." A signal container says, "Here is the governed logic for how this intent should be discovered, matched, scored, activated, and audited across systems."” — [Signal Containerization: The Next Abstraction Layer for Agentic Advertising](https://nofluffadvisory.com/writing/signal-containerization-agentic-advertising/), Jun 7, 2026 - Coins the term **“Signal Containerization”** — supersedes “segment” as the operative term. - Status: current — no change since Jun 7, 2026. ### Jun 7, 2026 — Coinage — Current · Signal containerization The most powerful activation pattern is a dual-gate model, requiring both audience match and contextual alignment before an impression qualifies — this changes data from a pre-built segment into a live decision object. > “The most powerful version is a dual-gate model: the user is in the matched audience and the impression context is aligned with the signal.” — [Signal Containerization: The Next Abstraction Layer for Agentic Advertising](https://nofluffadvisory.com/writing/signal-containerization-agentic-advertising/), Jun 7, 2026 - Coins the term **“Dual-Gate Activation”** — supersedes “identity path”, “contextual path” as the operative term. - Status: current — no change since Jun 7, 2026. ### Jun 7, 2026 — Framework — Current · Signal containerization A signal container's value comes from packaging six things that normally travel separately and lose meaning at every hop — intent, meaning, provenance, policy, execution, and evaluation. > “A signal container packages six things that normally travel separately — and lose meaning at every hop.” — [Signal Containerization: The Next Abstraction Layer for Agentic Advertising](https://nofluffadvisory.com/writing/signal-containerization-agentic-advertising/), Jun 7, 2026 - Status: current — no change since Jun 7, 2026. ### Jun 7, 2026 — Claim — Current · Confirmed · Signal containerization The market's dependence on identity-based matching for activation is too brittle for modern privacy constraints, CTV, retail media, and fragmented data environments. > “That "identity or nothing" model is too brittle for modern privacy, CTV, retail media, and fragmented data environments.” — [Signal Containerization: The Next Abstraction Layer for Agentic Advertising](https://nofluffadvisory.com/writing/signal-containerization-agentic-advertising/), Jun 7, 2026 - Confirmed: Jul 21, 2026 — “hashed-PII match against a walled garden's identity spine — the exact dependence signal containerization was designed to relieve” - Status: current — no change since Jun 7, 2026. ### Jun 7, 2026 — Claim — Current · Confirmed · Signal containerization Missing standards layers always begin as private plumbing before they become open standards -- the pattern the industry defaults to when a governed object (like a closed-loop feedback layer) does not yet exist. > “which is how missing layers always begin: private plumbing first, standards later” — [Signal Containerization: The Next Abstraction Layer for Agentic Advertising](https://nofluffadvisory.com/writing/signal-containerization-agentic-advertising/), Jun 7, 2026 - Confirmed: Snowflake x Meta governed loop — Jul 21, 2026 — “named the failure mode of this transition over a month ago... Today's blueprint is that failure mode executed well.” - Status: current — no change since Jun 7, 2026. ### Jun 7, 2026 — Claim — Current · Signal containerization In the contextual-path activation pattern, a leading SSP stops being pure supply pipe and becomes part of the decision runtime itself, comparing bidstream context against a semantic prototype in real time. > “In this model, a leading SSP is not just a supply pipe. It becomes part of the decision runtime.” — [Signal Containerization: The Next Abstraction Layer for Agentic Advertising](https://nofluffadvisory.com/writing/signal-containerization-agentic-advertising/), Jun 7, 2026 - Status: current — no change since Jun 7, 2026. ### Jun 7, 2026 — Framework — Current · Signal containerization A signal container must be a governed, executable object rather than a segment fetched on the fly because it executes a decision already reasoned about upstream -- the line between an agent that plans and a runtime that acts. > “The container executes a decision that was reasoned about before the impression arrived. That is the line between an agent that plans and a runtime that acts” — [Signal Containerization: The Next Abstraction Layer for Agentic Advertising](https://nofluffadvisory.com/writing/signal-containerization-agentic-advertising/), Jun 7, 2026 - Status: current — no change since Jun 7, 2026. ## Where the verified record ends The verified record for Composable CDP + Agentic CDP + Customer data architecture + Identity resolution + Signal containerization currently ends at **Aug 3, 2026**. No unverified candidate rows are pending for these concepts. Nothing beyond that date, and nothing outside these verified rows, is claimed here. --- 27 of 111 total verified ledger rows shown here, filtered to Composable CDP + Agentic CDP + Customer data architecture + Identity resolution + Signal containerization. Built against corpus revision `d5aebe0` — every row passed `verification.state === 'verified'` before it was allowed to render. Receipts are verbatim; superseded and retracted rows are marked, never presented as current. Methodology: https://nofluffadvisory.com/thinking/