Customer Data Architecture
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.
Current positions
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, Jul 21, 2026
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, Aug 3, 2026
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, Jul 7, 2026
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, Jun 19, 2026
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, Jul 16, 2026
Showing 27 of 27 positions
No positions match these filters.
The timeline — newest first
- Aug 3, 2026 Claim 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”
Status: current — no change since Aug 3, 2026.
- Aug 3, 2026 Claim 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.”
Status: current — no change since Aug 3, 2026.
- Jul 21, 2026 Verdict 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.”
Status: current — no change since Jul 21, 2026.
- Jul 16, 2026 Framework 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.”
Status: current — no change since Jul 16, 2026.
- Jul 13, 2026 Claim 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.”
Confirmed: Jul 21, 2026 (On the Record →)
Status: current — no change since Jul 13, 2026.
- Jul 13, 2026 Framework Superseded 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.”
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.”
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 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.”
Status: current — no change since Jul 13, 2026.
- Jul 13, 2026 Claim 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.”
Status: current — no change since Jul 13, 2026.
- Jul 7, 2026 Framework 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.”
Status: current — no change since Jul 7, 2026.
- Jul 7, 2026 Framework 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”
Status: current — no change since Jul 7, 2026.
- Jul 5, 2026 Framework 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.”
Status: current — no change since Jul 5, 2026.
- Jul 5, 2026 Claim 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.”
Status: current — no change since Jul 5, 2026.
- Jul 5, 2026 Coinage 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”
Coins the term “Custody Partition”.
Status: current — no change since Jul 5, 2026.
- Jun 19, 2026 Claim 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”
Status: current — no change since Jun 19, 2026.
- Jun 19, 2026 Call 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”
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 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”
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 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.”
Status: current — no change since Jun 19, 2026.
- Jun 19, 2026 Claim 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.”
Status: current — no change since Jun 19, 2026.
- Jun 19, 2026 Framework Superseded 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.”
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 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."”
Coins the term “Signal Containerization” — supersedes “segment” as the operative term.
Status: current — no change since Jun 7, 2026.
- Jun 7, 2026 Coinage 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.”
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 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.”
Status: current — no change since Jun 7, 2026.
- Jun 7, 2026 Claim 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.”
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 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”
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.” (On the Record →)
Status: current — no change since Jun 7, 2026.
- Jun 7, 2026 Claim 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.”
Status: current — no change since Jun 7, 2026.
- Jun 7, 2026 Framework 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”
Status: current — no change since Jun 7, 2026.
27 of 108 total verified ledger rows shown here, filtered to
Composable CDP + Agentic CDP + Customer data architecture + Identity resolution + Signal containerization. Built against corpus revision aa6c54d —
every row on this page passed verification.state === 'verified' before it was allowed
to render. Receipts are verbatim; superseded and retracted rows are marked, never presented as current.
Methodology: Evolution of Thinking.