The Context Assembly Problem Has One Fix — Here's Where to Apply It

Key takeaways
✦ One knowledge architecture solves three distinct problems: internal agent access, agentic commerce readiness, and LLM visibility
✦ Most organizations are solving each separately. They're the same context assembly problem wearing different clothes
✦ The OKF (Open Knowledge Format) domain primitive is the infrastructure layer underneath all three

In my last post, I discussed the opportunity to start building OKF-structured domain primitives from any file format. Now I want to discuss what you do with them.

Use case 1: Internal knowledge democratization

Every organization has a proprietary knowledge problem. A database nobody outside the data team can query. Strategy docs in a shared drive nobody opens. Tribal knowledge that walks out when someone quits.

The OKF domain primitive turns that repository into something any internal agent can navigate. Drop in the source files. The agent extracts the concepts, encodes the relationships, and outputs a bundle any downstream agent can load as grounded context. A live knowledge layer for your employees. Not a wiki nobody updates.

Use case 2: Agentic commerce readiness

When a shopping agent hits your brand's front door, it isn't browsing. It's evaluating and on a mission. It needs to know what you sell, how it's structured, and whether it can transact without a human in the loop.

Most brand websites are built for human browsing. An agent can't do much with a hero image and a navigation menu.

An OKF-structured product bundle gives the agent what it needs: taxonomy, attributes, pricing logic, and transactional parameters structured for machine retrieval. The brand becomes transactable, not just visible. The brands building this now own the agentic channel. The ones waiting will be retrofitting when volume is already flowing elsewhere.

Use case 3: LLM visibility and citability

llms.txt tells frontier models what your site contains. Table stakes. OKF goes deeper.

A domain primitive encodes not just what your content says, but why it matters: the concepts, the relationships, the authoritative definitions your organization owns. That's the metadata that improves recall, citability, and attribution inside ChatGPT, Claude, and Gemini.

Most GEO strategies stop at content formatting. OKF gives LLMs a richer surface and a clearer signal about which concepts you own.

The unifying thread

Internal agents. Shopping agents. Frontier model visibility. Three problems, one architecture.

The context assembly problem shows up the same way every time: the knowledge exists, the agent can't reach it, and the human fills the gap manually.

Build the infrastructure once. Apply it everywhere it creates leverage.

That's the plumbing. And most organizations haven't started.

What's the highest-leverage knowledge problem in your organization right now? Let me know if I can help?

Building Knowledge Infrastructure That Actually Travels With Your Workflow

Key takeaways
✦ Google just formalized a pattern most AI builders have been solving informally: how agents find and use organizational knowledge
✦ The problem isn't the model. It's context assembly: scattered docs, siloed wikis, no portable format
✦ Domain primitives built on OKF become durable infrastructure, not one-off prompt hacks

Most AI agents fail before they start.

Not because the model is wrong. Because the knowledge it needs is scattered across a nested shared drive, a Confluence page, a shared wiki, or an important KPI framework someone emailed a while back.

What Google just shipped

On June 12, Google Cloud published the Open Knowledge Format (OKF) v0.1: an open spec for packaging organizational knowledge so agents can actually use it. Plain markdown files. YAML frontmatter. No proprietary SDK required.

The core insight: the context assembly problem is the same one every agent builder solves from scratch. OKF bets the fix is a format, not another platform.

The problem it surfaces

I've been building what I call domain primitives: structured knowledge stores encoding not just data, but the decisions, definitions, and business logic surrounding it. Agents need that metadata. Raw data alone isn't enough.

OKF gives that work portable architecture. It formalizes a pattern emerging informally across Obsidian vaults, agent markdown repos, and llms.txt files, pinning down the conventions that let knowledge written by one producer be consumed by a different agent without translation.

What I built on top of it

I built an ingestion agent that takes any file format and produces an OKF-structured domain primitive. Drop in a PDF brief, a CSV, a strategy doc, a campaign taxonomy. The agent extracts the concepts, structures them as OKF bundles, and outputs something any downstream agent can consume as grounded context. A knowledge layer that travels with the workflow.

What most orgs miss

The context assembly problem doesn't get solved by a better model. It gets solved by unglamorous knowledge engineering done before the agent runs. OKF doesn't do that work for you. It gives the work a home.

The organizations pulling ahead aren't prompting harder. They're building knowledge infrastructure agents can actually navigate.

That's the plumbing. And the bill is coming due for every org that skipped it.

This is a pretty clean demonstration of how I typically work: convert frontier AI concepts into organizational leverage before they become conventional wisdom. If your team is wrestling with the context assembly problem, reach out.

Link to the OKF repo: https://github.com/GoogleCloudPlatform/knowledge-catalog/tree/main/okf

From Local and Fragmented to Global and Governed: The Prerequisite Many Have Avoided

✦ Your AI strategy is only as strong as the data underneath it.
✦ Most organizations do not know how strong or weak that foundation actually is.
✦ That gap is about to get expensive.

Before you deploy another AI workflow, answer this question honestly.

The data foundation question nobody wants to ask:
How confident are you that the data feeding your AI right now is clean, centralized, consistently defined, and actively monitored for quality every single day?

Not "mostly." Not "we're working on it." Right now. Today.

The AI Readiness Self-Score:
🔴 Fragmented: data lives across local platforms, manual feeds, and spreadsheets with no unified view. Different teams define the same KPIs differently. No one is monitoring quality systematically.

🟡 Partially centralized: some consolidation exists but significant gaps remain. Quality issues surface reactively, usually when something breaks visibly.

🟠 Mostly standardized: a global framework exists but local exceptions still require manual intervention. Quality checks run but not daily, not against defined thresholds.

🟢 Fully governed: one source of truth for every metric. Daily automated quality assurance. Standardized taxonomy enforced across all markets and partners. AI agents run against this foundation with confidence.

The uncomfortable truth

Most organizations deploying AI today are 🔴 red or 🟡 yellow on data foundation and 🟠 orange on ambition. That gap is not a technology problem. It is a governance problem that technology will not solve on its own.

Most automated AI workflows do not improve your data. They execute against it. Every quality flaw, every inconsistency, every ungoverned pipeline becomes an input the agent treats as truth.

The path from local and fragmented to global and governed is not glamorous. Daily quality assurance checks. Standardized taxonomy enforced at ingestion. A single metric definition every market, every partner, every platform aligns on.

But when that foundation is in place, the AI deployment conversation changes entirely. You stop asking whether the output is trustworthy. You start asking what you want to build on top of it.

A clean data foundation is what separates an AI strategy from an AI result.

Consider taking the AI Readiness Diagnostic - it will frame up your data foundation, governance, and workflow readiness in under 15 minutes: https://lnkd.in/gw4UB-KZ

What the Cannes Creative Brand Lion Is Actually Scoring (And Why Most Brands Aren't Ready)

✦ Cannes Lions just introduced an award for organizational systems, not campaigns.
✦ The jury is scoring the infrastructure that makes creative excellence repeatable.
✦ Most marketing organizations are not ready for that question.

For 70 years, the Palais has rewarded the work. Next week, it starts rewarding what makes the work possible.

What Cannes just signaled

The Creative Brand Lion, new for 2026, does not judge campaigns. It judges systems, cultures, and capabilities. The jury chair is the Global CMO of AB InBev. Cannes Lions CEO Simon Cook framed it simply: what are the inputs that make breakthrough ideas possible?

Seven subcategories. Talent. Operations. Technology. Customer experience. All of them judging the same thing: whether the capability exists beyond the campaign.

That is a different question than the industry has been asked before. And it has a very uncomfortable answer for most organizations.

The real problem underneath

Creative teams spend years building a brand. The identity. The standards. The distinctiveness that makes the work recognizable before anyone reads the copy.

And then an algorithm decides what the brand looks like at scale.

Most organizations have no governance layer between their brand standards and the platforms executing against them. No systematic review before creative goes live. No scoring against the brand's own rubric. The brand exists in a PDF that no deployment process actually enforces.

One poorly governed deployment can erode in an instant what took years to build. That is not a creative problem. It is an organizational design problem. And the Creative Brand Lion is now scoring it directly.

The Palais just started scoring the plumbing. Most organizations are still only polishing the faucet.

How I approach this

If your team is deploying AI-driven creative without a governance layer upstream - concepts like Brand Guardian are built for exactly this gap. Creative governance infrastructure trained on your brand bible, scoring every format against a calibrated rubric built on brand fidelity, distinctiveness, emotional impact, and authenticity before the first ad is made, before a campaign goes live, before an algorithm decides what your brand looks like at scale.

Your brand doesn't belong to the algorithm. Brand Guardian makes sure it never will.

For information on Brand Guardian visit: https://lnkd.in/gHrhsF9d

You Bought the Science. Did You Fix the Data First?

Key takeaways:
✦ Measurement vendors sell methodology. They cannot sell you the data foundation required to support it.
✦ Incrementality testing and MMM are only as rigorous as the data environment they run on.
✦ Nobody in the sales process has an incentive to name the real problem.

Cannes Lions (June 22–26) will be full of measurement vendors.

Incrementality platforms. MMM providers. AI-native attribution tools. All of them selling the same promise: buy the science, get the answer.

The promise is real. The assumption underneath it is not.

The real problem nobody names in the sales process

Incrementality testing built on inconsistently tagged campaigns returns confidently wrong lift numbers. MMM fed by fragmented, agency-siloed data optimizes against a fiction. The model runs. The outputs look precise. The deck gets built.

The methodology is not the problem. The data environment is.

And nobody in the room has an incentive to say that out loud. The vendor wants the deal. The agency wants to look capable. The brand team wants to hand the CMO a number. So the number gets produced, the methodology gets a panel at the Palais, and the data problem stays buried until the results do not hold.

This is not a critique of the measurement category. The science these platforms are building is serious. But rigorous methodology applied to a broken data environment does not produce better answers.

It produces more sophisticated wrong ones.

So before you invest in the science, be honest about what you are feeding it.

What would your team honestly say about the data environment your measurement tools are running on?

The AI Readiness Self-Score:
🔴 Fragmented. Campaign data is siloed across platforms, agencies, and spreadsheets. No unified taxonomy. Measurement outputs reflect that fragmentation back at us.
🟡 Partially centralized. Inconsistencies remain across partners and platforms. We use the numbers but quietly discount them.
🟠 Mostly centralized with known gaps. Measurement is directionally reliable but we know where the weak points are.
🟢 Governed, standardized, and monitored. We trust the data environment our measurement tools are running on.

The measurement investment is only as strong as the foundation underneath it.

My AI Readiness Diagnostic surfaces exactly where that foundation stands before you build on it.
👉 https://lnkd.in/gw4UB-KZ

Your Media Data Can Now Talk to AI. Does It Have Anything Worth Saying?

Key takeaways:
✦ MCP servers now let marketers query media performance via AI chat. The interface problem is solved.
✦ The bottleneck was never the interface. It was always the data underneath it.
✦ Connecting AI to fragmented, ungoverned data does not surface insight. It surfaces confusion faster.

Your media performance data can now talk to AI. The question is whether it has anything worth saying.

Last month, Measured launched an MCP server that lets marketers ask ChatGPT, Claude, or Gemini the question every CMO asks in QBR: "Where should I spend my next dollar?" The answers draw from 30,000+ incrementality tests across 200+ brand clients.

The infrastructure to query your media performance via AI conversation is live.

What is not live, in most organizations, is the data quality that makes that conversation trustworthy.

The real problem underneath

MCP connectivity solves the interface problem. It does not solve the data problem.

If your campaign taxonomy is inconsistent across platforms and partners, if the same KPI is defined differently depending on who pulled the report, connecting an AI interface to that foundation does not surface insight. It surfaces automated confusion with a better UX.

The real value comes from the unglamorous work that happened first. Standardized KPI definitions. Resolved taxonomy inconsistencies. Monitoring built to catch data quality failures before they reach a decision. That work does not get announced at Cannes. But it is the reason the AI answer is trustworthy when it arrives.

So before you connect the server, be honest about what you are connecting it to. Most organizations already know the answer.

The AI is not the variable. Your data is.

What color would your team honestly assign your measurement data?
The AI Readiness Self-Score:
🔴 Fragmented. No unified taxonomy or standard definitions across platforms and partners. Any AI answer reflects that chaos back at us.
🟡 Partial standardization. Meaningful inconsistency remains. We would not fully trust an AI recommendation built on our current data.
🟠 Mostly standardized with known exceptions. Monitoring exists in some areas. AI recommendations are directionally useful.
🟢 Governed and standardized across internal teams and partners, with proactive monitoring in place. We trust the foundation our AI reasons from.

---

My AI Readiness Diagnostic tells you exactly where your data foundation stands before you trust it to power a decision.
👉 https://lnkd.in/gw4UB-KZ

You Are Not Sending a Campaign. You Are Sending Instructions.

Key takeaways:
- Autonomous agent-to-agent media buying is already live. PubMatic, Viant, and Yahoo are running it now.
- Once you hand off to an autonomous DSP agent, the constraint envelope you send is your only control surface. There is no execution review.
- The organizations that govern the input will govern the outcome. Everyone else is a passenger.

The infrastructure is not coming. It is already running.

PubMatic's AgenticOS is live with WPP Media, MiQ, and Wpromote. Viant's Lattice Brain is explicitly no-human-in-the-loop. The Ad Context Protocol is being adopted across PubMatic, Scope3, and Yahoo to let AI systems transact across the advertising ecosystem without manual intervention at each step.

Most marketing leaders are treating this as a future state conversation.

It is a procurement decision happening right now.

The AI readiness self-score:
When your organization hands a campaign brief to an autonomous DSP agent, what governs what it is allowed to do?

🔴 Nothing formal. The platform runs against whatever parameters were entered. No constraint envelope. No audit trail.
🟡 Standard platform brand safety settings are applied but there is no documented logic connecting the brief intent to the execution boundaries.
🟠 Guardrails exist but they were written for a human review workflow. No one has tested whether they translate to autonomous execution.
🟢 A governed constraint envelope is produced before every activation, validated against brand standards and GARM floors, and the autonomous system operates inside it with monitored compliance.

The governance gap nobody is naming:

With a traditional DSP campaign, you can audit what was built before it runs. A human reviewed the line items. A human approved the targeting. The payload was deterministic.

With an autonomous DSP agent, you are not sending a campaign. You are sending instructions. The agent decides execution inside those instructions. What you send is the only control surface you have.

That is not a workflow efficiency story. That is a fiduciary one.

The organizations that will operate confidently in an agent-to-agent buying environment are not the ones who figured out the platform fastest. They are the ones who built governance around the input before the autonomous system asked for it.

The constraint envelope is your brief, your brand standards, and your guardrails — serialized into a form an autonomous agent can act on. Most organizations have not built that. Most do not know they need to.

Source: https://lnkd.in/gFnhmn9f

Your Brand Bible Is Not Enough. Google's AI Needs It Structured.

Google Marketing Live 2026 made something clear that most marketing organizations are not ready to hear.

Starting in September 2026, Dynamic Search Ads automatically upgrade to Google AI Max. The platform no longer accepts keyword lists as the primary input. The AI generates ad copy dynamically, matching the specific query and the AI-generated answer sitting above it in real time. Google's VP of Ads put it plainly on stage: "You can't choose keywords anymore."

Then Google introduced AI Brief.

AI Brief is a plain-language pre-execution tool that lets advertisers tell AI Max who they are before it runs. Brand voice. Tone. Approved messaging. What the AI should say and what it should not. The concept is straightforward. The execution requirement is not.

For AI Brief to work, your brand standards have to exist in a form the AI can actually act on. Not a 60-page PDF that lives in a shared drive. Not a slide deck from the last rebrand. A structured, queryable brand standard that can be translated into machine-readable constraints before the platform fires.

Most organizations do not have that. And that gap is about to become expensive.

What Google Is Actually Asking For

When Google says "guide the AI with plain-language instructions," what it means in practice is this: your organization needs to have already done the work of codifying your brand standards into structured inputs before the campaign launches.

That means:

• A defined brand voice with enough specificity that an AI can distinguish on-brand from off-brand copy

• Approved messaging hierarchies, not just taglines

• Creative constraints that go beyond "stay on brand" into actual rubric-level criteria

• Platform-specific guardrails that translate those standards into what Meta Advantage+ or Google AI Max can act on

This is not a creative brief. It is infrastructure. And it lives upstream of every campaign, every asset, every AI-generated output your organization produces.

The brands that build this infrastructure now own the AI-first advertising channel. The ones that wait will spend the next 18 months cleaning up what the algorithm decided their brand should say.

Why Brand Guardian Was Built for This Moment

Brand Guardian is Chuck Schultz Consulting's creative governance capability, designed specifically for the age of algorithmic creative. It sits between your production process and your deployment layer, scoring every asset against a structured brand standard before anything goes live.

It is built on three components that are directly relevant to what Google is now requiring.

• The Brand Bible is not a static document. It is a structured, queryable brand standard built once and maintained in your project files. It captures the criteria an AI evaluation system needs to distinguish on-brand from off-brand: identity standards, voice parameters, messaging hierarchy, campaign mandatories, and platform specifications. This is the foundation everything else builds on.

• The Static and Video Guardians evaluate your creative assets against five brand dimensions: brand identity, message and tone, campaign alignment, visual complexity, and platform fit. Every asset receives a numeric score, a verdict lane, flagged risks, and structured output. The verdict is governance-grade, not subjective. Flagship Ready means deploy. Hold means restart.

• The Platform Guardrail Producer is the capability that connects directly to what Google introduced at Marketing Live 2026. It takes your Brand Bible and translates your brand standards into Google AI Max and Meta Advantage+ constraints before the first ad is generated. Not after the AI runs and the copy comes back wrong. Before.

This is what AI Brief assumes you already have. Most organizations are building it after the fact.

The Five Evaluation Dimensions

Every asset Brand Guardian scores is evaluated across five dimensions:

• Brand Identity (25 pts) — Logo, color, typography, visual signature

• Message and Tone (25 pts) — Headline, copy, voice alignment to brand standards

• Campaign Alignment (20 pts) — Brief compliance: objective, proposition, mandatories

• Visual Complexity (15 pts) — Cognitive load, hierarchy, readability at format size

• Platform Fit (15 pts) — Format compliance, safe zones, spec adherence

A perfect score is 100. The verdict lanes run from Flagship Ready (90 to 100) down to Hold (below 60). The CD stays in control. Brand Guardian evaluates. It does not produce creative or replace judgment. That is by design.

The Readiness Question Most Orgs Are Avoiding

Here is the diagnostic question Google Marketing Live 2026 just made urgent:

If your team had to produce an AI Brief for Google tomorrow, brand voice, approved messaging, KPI priorities, creative constraints, could you do it? Not in three weeks after a brand governance sprint. Tomorrow.

Most organizations will land somewhere between "the guidelines are in a PDF" and "we have some standards but they are written for humans, not platforms." Neither of those answers meets the bar Google just set.

The organizations pulling ahead are not waiting for the September upgrade. They are building the Brand Bible now. They are running the Platform Guardrail Producer now. They are treating brand standards not as a creative reference document but as the input architecture the AI stack requires to function correctly.

What This Means for Your Organization

If you are a marketing leader at a brand or an enterprise organization running paid media at scale, the Google AI Max transition is not a platform update you can configure around. It is a signal that brand governance has moved from a creative operations function to a performance marketing requirement.

The AI will execute whether your inputs are ready or not. The question is whether it is executing against your brand standards or improvising them at the moment of purchase intent.

Brand Guardian puts your brand at the center before the algorithm decides what your brand looks like at scale.

If you want to understand what it looks like in practice for your organization, the full Brand Guardian capability overview is available at chuckschultzconsulting.com/services-content.

Or if you want to understand how your organization scores across AI readiness before going deeper on creative governance, the AI Readiness Diagnostic is a 10-minute assessment that gives you an instant readiness score across AI usage, workflow ownership, and data foundation: chuckschultzconsulting.com/ai-readiness-assessment.

The AI is running. The question is what it is running on.

You Don’t Have an AI Problem. You Have a Clarity Problem.

Every marketing leader I talk to wants to move faster on AI. Most of them are already moving — experimenting with tools, greenlighting pilots, asking their agencies what’s possible.

But when I ask them where they actually stand — scored, specific, honest — almost none of them can answer.

That’s the real problem. Not the technology. The diagnosis.

The Gap Between Believing and Knowing

AI adoption in marketing organizations follows a predictable pattern. There’s a burst of early experimentation — ChatGPT prompts, vendor demos, a pilot here and there. Then a plateau. The tools are running, but the outcomes aren’t compounding. Teams are busy but not building.

The reason is almost always the same: no one has done the hard work of mapping current state to future capability. What AI are people actually using, and how? Where are the workflows still running on human effort that could be orchestrated? Is the data infrastructure ready to support anything more ambitious than a one-off use case?

Without answers to those questions, every AI investment is a guess.

What a Diagnostic Actually Looks Like

The AI Readiness Assessment I run scores organizations across three dimensions:

AI usage — not just “are we using it,” but how deliberately, how systematically, and with what level of governance. There’s a significant difference between a team running ad hoc prompts and a team with documented workflows, quality checks, and consistent outputs.

Workflow orchestration — where human effort is still doing work that could be automated, and where automation is already in place but not connected to anything that compounds. The gap between task-level AI and system-level AI is where most organizations are stuck.

Data readiness — the infrastructure question most people avoid because it’s uncomfortable. If the data isn’t clean, connected, and accessible, the AI layer sitting on top of it will underperform regardless of which model you’re using.

What Comes Out

The output isn’t a report. It’s a roadmap — 30/60/90-day priorities, scored and sequenced, based on where you actually are rather than where you’d like to be.

The 30-day priorities are almost always the same: stop the bleeding, document what’s running, identify the two or three workflows worth automating first. The 60 and 90-day work depends entirely on the diagnostic. That’s the point.

Why Free

I make the assessment free for the same reason I lead with it in every engagement: organizations that don’t know where they are make bad decisions about where to go. A paid engagement built on a shaky foundation is bad for both of us.

The assessment takes about 10 minutes. The clarity it produces is worth considerably more than that.

If you’ve been circling AI without traction — take it. It’s the right starting point.

[Take the free AI Readiness Assessment]

Your AI Pipeline Is a Suggestion Box. Here’s How to Turn It Into a System.

*Most organizations have more AI ideas than they can handle. Almost none have a system for deciding what gets built.*

-----

Here’s a scene playing out in marketing organizations everywhere right now.

Someone attends a conference. Someone watches a demo. Someone reads a case study. They come back with an idea: *we should use AI to do X.* It goes into a slide, or a Slack thread, or a Notion doc labeled “AI opportunities.” Three months later, one of those ideas gets approved — usually based on who championed it loudest, not which one would have the highest impact. It gets built by whoever was available. It goes to production without a formal review. Six months after that, nobody can find the documentation, the original prompt logic has drifted, and the person who built it has moved on.

This is not an AI problem. This is a governance problem. And it is nearly universal.

-----

## The Cost of Building Without a System

When organizations build AI capabilities without a governing structure, a few things happen reliably.

**Duplication.** Two teams build similar automations independently, neither knowing the other exists. Both work well enough that nobody consolidates them. Now you’re maintaining two systems, two sets of prompts, two failure modes.

**Invisible drift.** AI systems — especially prompt-based ones — are sensitive to upstream changes. A data schema update, a platform API change, a shift in business rules. Without systematic monitoring and documentation, these changes silently degrade performance. Nobody notices until something goes visibly wrong.

**Governance debt.** Every AI system that goes to production without a formal review creates a liability. Who approved it? Against what criteria? What are the guardrails? What happens when it fails? When an issue surfaces — and it will — the absence of answers to these questions turns a manageable incident into an expensive one.

**Organizational distrust.** Teams that have been burned by ungoverned AI deployments don’t become cautious adopters. They become skeptics. The credibility damage from one bad launch can set an organization’s AI program back by a year.

The irony is that the solution isn’t slower or more bureaucratic. A well-designed governance system actually accelerates deployment — because every idea moves through a consistent, predictable process instead of getting stuck in ad hoc approval loops.

-----

## What a Governed AI Innovation System Actually Looks Like

The word “governance” tends to make people think of committees and checklists. That’s the wrong mental model. Think of it instead as a pipeline — a structured sequence that every AI idea moves through, with clear criteria at each stage and a clear artifact at the end.

Here’s the architecture I would recommend installing.

### Stage 1: Intake and Scoring

Every idea enters through a single front door. Not Slack. Not a meeting. A structured intake form that captures: the business outcome this is supposed to influence, the workflow it touches, the data it needs, and the risk profile of the output.

The intake feeds an AI-assisted scoring model that evaluates each idea against four dimensions: strategic alignment, technical feasibility, data readiness, and governance complexity. High scores on all four move forward immediately. Low scores on feasibility or data readiness go to a backlog with a documented reason. The scoring is transparent and consistent — which means no more decisions made by whoever shouted loudest.

### Stage 2: Governed Build

Approved ideas move into a structured build process with defined artifacts required at each milestone: a workflow map, an agent design canvas, a system prompt with version history, and a test log. Nothing moves to the next stage without the artifact from the previous one.

This sounds like overhead. In practice it takes less time than the undocumented build process most teams are already running — because you’re not spending hours reverse-engineering what was built when something breaks.

### Stage 3: Review Board Evaluation

Before any AI capability goes to production, it passes through a Review Board evaluation. Five lenses: business alignment, technical integrity, data quality, ethical and compliance risk, and operational sustainability. Each lens is evaluated independently. The output is a written finding with a deployment recommendation.

The Review Board doesn’t exist to slow things down. It exists to catch the three or four things that always get missed when a team is excited about shipping — and to create an artifact trail that protects the organization if questions arise later.

### Stage 4: Deployment and Tracking

Approved capabilities go to production with a deployment record: what it does, what data it uses, who owns it, when it was last reviewed, and what the performance baseline is. This record lives in a central registry — not in someone’s Google Drive.

The registry is how you know, six months from now, what AI systems are running in your organization and whether they’re still performing as designed.

-----

## The Capability You’re Actually Building

The goal of all of this is not process for its own sake. It’s organizational capability — the ability to evaluate, build, govern, and scale AI systems faster and more reliably than your competition.

Organizations that build this capability now will have a compounding advantage. Every governed deployment adds to an institutional knowledge base. Every Review Board finding sharpens the organization’s judgment about what works. Every documented failure becomes a training asset, not a liability.

The organizations that skip this step don’t stand still. They accumulate governance debt — a growing backlog of ungoverned systems, undocumented decisions, and invisible risks that eventually requires expensive remediation.

You don’t need a large team to do this. You need a system. And the right system can be stood up, calibrated, and handed off to your team in a matter of weeks.

-----

## Where to Start

If your organization has more than five AI projects in flight — or more than five ideas in a backlog — you probably need this more than you realize.

The diagnostic question is simple: *If I asked you right now to list every AI system running in your marketing organization, along with who owns it, what data it uses, and when it was last reviewed — could you do it?*

If the answer is no, you don’t have a governance system. You have a collection of individual efforts that nobody has connected.

That’s fixable. But it’s easier to fix before the first incident than after.

Consider Blueprint Studio.

https://www.chuckschultzconsulting.com/services-content

-----

Your Brand Standards Were Built for Humans. Here’s What Machines Need Instead.

Your brand guidelines aren’t the problem. The fact that your AI agents can’t read them is.

The problem hiding in plain sight

Most marketing organizations have invested years building brand standards — voice guides, messaging frameworks, visual systems, approval hierarchies. All of it lives in PDFs and slide decks. All of it was designed for humans to read and interpret.

When an AI agent executes a campaign, it doesn’t open a PDF. It works from whatever structured context you’ve given it. If that context is incomplete, inconsistent, or absent — the agent executes confidently against the wrong foundation.

This is the ungoverned gap most organizations haven’t named yet.

The AI Readiness Self-Score:

🔴 Brand standards exist — in decks and documents humans reference loosely. No AI-accessible version exists.

🟡 Some elements are documented in structured form, but it’s inconsistent and not connected to live workflows.

🟠 A working version exists and some workflows reference it — but it isn’t maintained or governed as active infrastructure.

🟢 A machine-readable brand code exists, is actively maintained, and is the governing input for every AI-assisted workflow across the organization.

The real shift

A piece published in Harvard Business Review this week put a name to what’s missing: the “brand code.” A machine-readable knowledge base that encodes brand strategy, customer insights, and business rules — structured so both humans and AI agents can act on it consistently.

That’s not a rebranding exercise. That’s infrastructure.

The creative brief was designed for humans. It assumes context, judgment, and interpretation. AI agents don’t interpret. They execute. Feed them an ambiguous brief and they’ll produce confident output that misses the point.

The brand code is the brief that works for machines. Without it, every agent in your stack is operating on incomplete instructions — and you won’t know until the outputs tell you something went wrong.

Most organizations are deploying agents before they’ve built this foundation. That’s not a technology problem. It’s a sequencing problem.

Build the foundation first. The agents will run better because of it.

Source: “Redesigning Your Marketing Organization for the Agentic Age” — HBR, May 8, 2026

Agents Don't Browse: What the OpenAI Phone Means for How Brands Get Found

Key Takeaways:
- The app era assumed customers would come to your brand. The agent era doesn't.
- If your product data isn't structured for agent retrieval, your brand won't exist in the next interface layer.
- Agentic readiness isn't a tech project — it's a data architecture decision you're making right now by default.

The app on your customer's phone has a front door.

A URL. An icon. A deliberate tap.

The agent replacing it doesn't.

Analyst Ming-Chi Kuo reported last week that OpenAI is developing a smartphone where AI agents replace apps entirely. No icon grid. An agent that understands context, executes tasks, and surfaces your brand only if it can find, trust, and transact with your product data.

This isn't a 2028 thought experiment. The architecture decision is being made right now — in how your product catalog, pricing, and availability data is structured today.

What changes when the interface disappears

In the app era, brand presence was a distribution problem. Build a great app. Win the home screen.

In the agent era, it's a data architecture problem. Agents don't browse. They retrieve, evaluate, and execute. If your product data isn't structured and machine-readable at the field level — pricing, availability, attributes — the agent skips you. Not because it chose a competitor. Because it never found you.

The AI Readiness Self-Score:
🔴 Product data is scattered across platforms and spreadsheets. No unified, machine-readable layer exists.
🟡 Structured data exists in some channels but it was designed for human browsing — not agent retrieval.
🟠 Data is mostly structured but hasn't been audited against what an agentic transaction actually requires.
🟢 Product data is centralized, governed, and structured for agent-readable consumption — we've mapped what a purchasing agent needs to transact without a human in the loop.

Most brands are 🟡. Their data was built for search crawlers and display ads — not for autonomous agents making purchase decisions.

The bottom line

Your SEO team optimized for Google's crawler. Your dev team built for human thumbs.

Nobody optimized for an agent that doesn't click, doesn't browse, and won't wait for a page to load.

The brands that win aren't the ones with the best app experience. They're the ones whose data lets an agent find them, trust them, and buy from them — no human required.

Where does your product data stack sit today? Drop your color in the comments.

Ming-Chi Kuo post on X Platform was inspiration for this post:
https://lnkd.in/ewPgumnr

The Brief Is Now the Product: Creative Governance in the Age of AI-Native Advertising

Your creative team is producing ads for a consumer journey that platforms are quietly retiring.

Google's Q1 results told the real story. $110B in revenue. Google Cloud up 63%. Buried in the same report: Google Network ad revenue down 4% year over year. Not a soft market. AI Overviews, AI Mode, and agentic commerce features are resolving queries inside Google's own interfaces. Fewer clicks. Less open-web traffic.

Snap and X both launched AI-native ad platform overhauls this week. Not AI-assisted. AI-native. The platform generates the execution. Your team provides the inputs.

Every major platform is rebuilding around AI-mediated interaction. The click-through journey your creative was built for is being structurally dismantled.

The AI Readiness Self-Score:
🔴 Creative is produced and uploaded by the team. The platform serves it as-is.
🟡 AI tools are in production but creative strategy and brand governance are still output-focused.
🟠 Starting to think about briefs as the strategic layer but no governance model in place yet.
🟢 Brand standards, messaging taxonomy, and creative governance are structured as upstream inputs the AI executes against.

Most brand teams are 🔴 or 🟡. Built for a world where they controlled the final execution.

The brief is now the product

When the platform generates the ad, your creative team's role shifts entirely. What your brand stands for. What claims you'll make and in what context. The constraints you set on tone and format. Those inputs are what the AI executes against at scale, in real time, without asking first.

Sloppy brand standards don't disappear in this model. They get industrialized.

And if users are completing purchases inside Google's AI interfaces without ever reaching your landing page, your attribution breaks. The conversion happened. You just can't see it through the funnel you built.

The advertisers who navigate this well will treat the creative brief as infrastructure. Not output.

The ones who don't will keep optimizing for a journey their customers have already left.

Creative teams spend years building a brand. One poorly governed AI deployment can erode it faster than any bad campaign ever could.

Where does your creative governance sit today? Drop your color in the comments.
---
Have you considered what creative governance infrastructure in the age of AI and algorithmic creative might look like? Trained on your brand bible, scoring every format against a calibrated rubric built on brand fidelity, distinctiveness, emotional impact, and authenticity. Your brand doesn't belong to the algorithm. If curious - reach out.
---

Agentic Commerce Is the Mobile Moment. The Window Is Open. Are You Building?

Special Series: Agentic Shopping (5 of 5)

Key Takeaways:
⏵ The brands that own agentic commerce in 2028 are making infrastructure decisions right now — not in 2027.
⏵ The window to build ahead of the curve is open. It won't stay open.
⏵ Five posts. One argument: structure your data for machines before the agents arrive — or react to losses you can't explain.

This series started with a simple provocation.

Your next customer might not be human.

Over four posts we mapped what that actually means — not as a futurist thought experiment, but as a set of infrastructure decisions every brand needs to make right now.

The Arc, Compressed
Part 1: Is your data ready to be shopped by an agent?
Part 2: llms.txt — one file, two jobs. GEO citability and agentic transaction readiness. Build it once.
Part 3: The receiving stack — orchestrator, intake, retrieval, reasoning. A coordinated team serving every visiting agent.
Part 4: The audit — five layers, a scored gap map, a sequenced action plan.

Every post. Same conclusion.

The Strategic Imperative

The infrastructure is being standardized in 2026. The protocols are live. The agents are already being deployed by early movers.

This is the same window that existed with mobile in 2010. The brands that acted early built structural advantages that compounded. The ones that waited spent years catching up — and most never fully closed the gap.

Agentic commerce is that window. And it is open right now.

What the Winners Will Have Built
→ A machine-readable llms.txt serving both citability and transaction
→ Product catalog, pricing, and inventory structured for machine consumption
→ Data taxonomy governed consistently across every system an agent queries
→ A receiving architecture designed for visiting agents — not just human visitors
→ Agentic readiness audited before the agents arrived — not after the losses showed up

None of these are technology decisions. Every one is a leadership decision.

The agents are coming. The only question is whether your brand is ready to receive them — or scrambling to catch up when they arrive.

That's the series. Five posts. One argument.

Is agentic readiness on your radar? If you market/sell online - it should.

The Agentic Readiness Audit: The Five-Layer Framework Every Brand Needs Before the Agents Arrive

Special Series: Agentic Shopping (4 of 5)

Key Takeaways:
⏵ Agentic readiness can be audited today — before the agents arrive.
⏵ The gaps aren't where most brands expect them. They show up in taxonomy, accessibility, and transaction logic — not design or content.
⏵ A scored readiness framework gives you a gap map and a sequenced action plan. That's the starting point.

In Part 3 we mapped the receiving stack — the coordinated team of agents that serves a visiting agentic shopper.

Now the obvious question: how ready is your stack right now?

A New Kind of Audit

The marketing industry has SEO audits. GEO audits. UX audits. Conversion audits. None of them answer the question an agentic shopper is actually asking. Can I navigate this brand's data environment, evaluate options, and complete a transaction — without a human in the loop?

That's a different question. It requires a different audit. And it produces a different kind of score.

The Agentic Readiness Scoring Rubric

An agentic readiness audit evaluates five layers — each one a potential failure point in the receiving stack:

1. Discoverability
🔴 No machine-readable index exists → 🟢 llms.txt published, structured for citability and transaction

2. Data Structure
🔴 Fragmented across platforms and spreadsheets → 🟢 Structured and accessible without analyst intervention

3. Taxonomy Consistency
🔴 Inconsistent definitions across platforms → 🟢 Unified taxonomy governed across all data sources

4. Transaction Accessibility
🔴 Purchase pathway requires human navigation → 🟢 Transaction logic structured and agent-accessible end to end

5. Response Integrity
🔴 Data gaps produce incomplete agent responses → 🟢 Data quality governance ensures recommendations reflect reality

The Gap Map

Most brands auditing against this rubric will cluster at 🔴 or 🟡 across all five layers — not because of bad decisions, but because none of these systems were designed with a non-human visitor in mind.

That's the gap map. And it's more useful than a single score.

Each layer that scores 🔴 or 🟡 is a sequenced action item — prioritized by which failure point sits earliest in the receiving stack. Discoverability first. Transaction accessibility last. Fix the handshake before you fix the handoff.

An agentic readiness audit doesn't tell you how good your website is. It tells you how ready your data infrastructure is to serve a visitor who doesn't have eyes.

Where This Is Headed

Agentic readiness scoring is an emerging category. The rubric doesn't exist as a standard yet. The audit methodology is being defined right now — by brands and practitioners willing to ask the question before it becomes urgent.

The ones who audit now will have a gap map, an action plan, and a head start. The ones who wait will be reacting to agent traffic they can't explain.

Part 5 is the strategic imperative — why brands that build this infrastructure in 2026 own the channel by 2028.

The Visiting Agent Never Knew It Was Talking to Five AIs. It Just Got a Clean Answer.

Special Series: Agentic Shopping (3 of 5)
Key Takeaways:
⏵ When an agentic shopper arrives at your brand, a single AI isn’t handling the request. A coordinated team of agents is.
⏵ The brands that win agentic commerce aren’t just building better data — they’re building a receiving architecture designed to serve visiting agents well.
⏵ This infrastructure exists today. The question is whether your brand is designing for it — or waiting until it’s table stakes.

In Part 2 we talked about the handshake — the llms.txt file that tells a visiting agent what your brand offers and how to navigate it.

Now the agent is inside. What happens next?

It’s Not One AI. It’s a Team.

Most people imagine agentic commerce as a single AI having a conversation with your website. That’s not how it works.

What actually happens is closer to a well-run organization. Different agents handle different jobs. Each one specialized. Each one passing context to the next. The visiting agent never talks to your database directly — it talks to a receiving architecture your brand has designed to serve it.

The Receiving Stack

The Orchestrator is the front door — a Chief of Staff that greets the visiting agent, interprets intent, and decides who handles what. It doesn’t do the work. It directs it.

The Context-Intake Agent grounds the request against your brand’s data environment — translating intent into something your catalog, inventory, and pricing systems can respond to. This is where your llms.txt and data taxonomy do their heaviest lifting.

The Retrieval Agent surfaces the two or three closest matches from your structured data. Not everything you sell — a curated shortlist built from real data.

The Reasoning Agent evaluates fit — scoring options against budget, availability, specifications, and proximity — and synthesizes a recommendation.

The Orchestrator closes the loop — packaging the recommendation and handing it back to the visiting agent.

The visiting agent never knew it was talking to five agents. It just got a clean answer.

Why This Matters

Every layer depends on your underlying data. Fragmented, ungoverned data doesn’t fail loudly. It fails quietly — incomplete recommendations, lost transactions, visiting agents that don’t come back.

What’s missing isn’t technology. It’s organizational intent — designing the receiving architecture before the agents arrive.

One file. One stack. Built once. Ready for whatever agent shows up.

This is Part 3 of a 5-part series on agentic data readiness. Part 4 is the readiness audit — how to test your own site with AI today and find every gap before the agents do.

Have you started thinking about your receiving architecture yet?

The Difference Between Being Cited and Being Shoppable

Special Series: Agentic Shopping (2 of 5)

Key Takeaways:
⏵ Most marketers think llms.txt is a GEO tool. It's also the front door for agentic shoppers. Same file. Two very different stakes.
⏵ Two readiness layers: being cited by AI, and being transactable by AI. The infrastructure that serves both is the same.
⏵ Build a machine-readable interface now. Rebuilding under pressure later costs more.

In Part 1 - I asked whether your data was ready to be shopped by an agent.

Before an agent can shop you — it has to know you exist. And know what you can do. That's the handshake.

Two Problems. One File.

Most marketing leaders think of llms.txt as a GEO tool — the AI equivalent of SEO metadata. A way to help ChatGPT, Claude, or Perplexity cite your brand when someone asks a relevant question.

That's real. And it matters. AI-generated answers are already cannibalizing search clicks. If your brand isn't structured for LLM citability, you're losing visibility you can't measure yet.

But llms.txt is also something else entirely. It's the file an agentic shopper reads before it ever interacts with your site.

Two very different problems. Two very different stakes. One file — if you build it right.

The Difference Between Being Cited and Being Shoppable

GEO is a visibility problem. When someone asks "what's the best midsize SUV for a family of five," you want your brand in the answer.

Agentic readiness is a transaction problem. When an agent arrives at your site with configured intent — specific product, budget, availability window — it isn't reading your content. It's querying your data. It needs to know what's available, how it's structured, and whether it can transact on behalf of the human who sent it.

---
Being cited gets you into the consideration set. Being shoppable gets you the transaction.
---

Most brands aren't ready for either. The ones investing in GEO are solving half the problem.

The Markdown Principle

Humans organize content for humans. Machines need content organized for machines. The gap between those two structures is where AI fails — whether it's a knowledge base, a product catalog, or a brand's entire digital presence.

llms.txt is essentially a markdown file. Structured, consistent, machine-consumable. It tells a visiting agent what your brand offers, how it's organized, and what actions are available — whether that agent is retrieving a citation or executing a purchase.

The brands that win the agentic era aren't the ones with the most sophisticated AI. They're the ones whose data is structured for machine consumption before the agents arrive.

One file. Two jobs. Build it once.

Agentic Data Readiness: The Infrastructure Question Nobody is Asking Yet

Special Series: Agentic Shopping (1 of 5)

Key Takeaways:
⏵Agentic shoppers don't experience your website — they parse your data. If it isn't structured for machine consumption, they move on.
⏵The brands winning agentic commerce won't have the best AI. They'll have the best data infrastructure.
⏵The readiness question isn't "are we building agents?" It's "can agents shop us?"

Your next customer might not be human.

They won't browse your homepage. They won't respond to your hero banner. They won't notice your redesign.

They'll arrive with intent already formed, query your product data, evaluate fit, and either complete a transaction — or leave. In seconds. Without rendering a single pixel of your UI.

The Agentic Shopper Is Already Here

Mondelez is hiring a global lead for agentic commerce. Their own retail partners project 30% of site traffic will be agentic by 2028. McKinsey puts the global market at $3–5 trillion by 2030.

The infrastructure is being built right now. Google. Amazon. OpenAI. The question isn't whether agentic shoppers are coming to your brand's digital properties. The question is whether your data is ready to receive them.

The AI Readiness Self-Score: Agentic Data Readiness
🔴 Product catalog, pricing, and inventory data is fragmented — an agent couldn't navigate it reliably.
🟡 Some structured data exists but it's inconsistent across SKUs, categories, or regions — partial information at best.
🟠 Core product data is structured, but the connective tissue — policies, promotions, inventory logic — isn't machine-readable.
🟢 Data is structured, governed, and accessible enough that a non-human agent could navigate, evaluate, and transact reliably.

Most brands land at 🔴 or 🟡 — not because of bad decisions, but because no one has asked the question in these terms before.

The Uncomfortable Truth
Agentic commerce doesn't fail because of bad AI. It fails because the data is locked inside analyst queues, fragmented across platforms, and structured for human dashboards — not machine consumption. An agent hits the same walls your internal team hits every day. The difference: your team works around it. The agent doesn't.

The next wave of lost conversions won't show up in your bounce rate. Agents don't bounce. They just never come back.

This is Part 1 of a 5-part series on agentic shopping and data readiness. What's your gut reaction to the idea that agents will be shopping your brand before your team is ready for them?

Google's AI Max Doesn't Break Campaigns. It Exposes Them.

Key Takeaways:
► Google AI Max shifted search from keyword-based to intent-based bidding this week — your AI now interprets meaning, not just match types
► Intent-based systems expose data taxonomy gaps across teams and partners that keyword campaigns could quietly absorb
► Organizations without a governed taxonomy don't lose control gradually — they lose it at the moment the AI picks a winner

Google AI Max just went live. Your search campaigns are no longer keyword-based. They're intent-based.

That distinction matters more than most teams realize — and it has nothing to do with the bidding mechanics.

The Problem No One Is Naming

Google's AI now reads your landing pages, interprets your headlines, and infers the intent behind your audience's queries in real time. It connects signals across placements your team never explicitly mapped. By September, Dynamic Search Ads are gone. The system decides.

Here's the gap: intent-based execution is only as coherent as the data structure feeding it.

When your media team defines a conversion differently than your brand team — when your agency uses one attribution window and your internal analytics team uses another — keyword campaigns could absorb that ambiguity. They operated inside guardrails you set.

Intent-based AI doesn't split the difference. It resolves ambiguity by picking one interpretation. And it does that at scale, continuously, before anyone reviews the output.

The AI Readiness Self-Score:
🔴 No shared taxonomy — everyone defines KPIs differently.
🟡 Informally aligned — rough consistency, but nothing enforced.
🟠 Mostly governed — taxonomy exists, but legacy exceptions still exist.
🟢 Fully governed — one definition, enforced across teams, partners, and platforms.

Most organizations are 🟡. Many believe they're 🟠.

The Real Cost:
On The AI Readiness Maturity Spectrum, data taxonomy isn't a technical problem. It's a governance decision that predates your AI investment.

Google's AI Max will optimize against whatever signal you give it. If your conversion definitions conflict across your stack, you won't see a configuration error. You'll see a performance report that looks reasonable — until someone asks why the agency numbers don't match the internal dashboard.

That gap used to be a reporting problem. With intent-based AI running your campaigns, it becomes a budget allocation problem.

---
The diagnostic no platform runs before selling you automation is whether your organization is ready to be automated.
---

Source: Digiday, April 15, 2026 https://lnkd.in/gMNpRNAF

What Would Your AI Say About You?

What would your AI say about you?

Not what you say you can do with AI.
What it would actually say — based on how you work with it every day.

Most people can't answer that question cleanly. Neither can their managers.
That's the talent gap no one is talking about yet.

► The Problem No Performance Review Has Caught Up To ◄

Every organization is building AI into daily workflows. Tools are deployed. Training is checked off. Adoption metrics look fine.

But no one has defined what good looks like at the individual level.

You can see someone's outputs. You can measure their deliverables. You cannot see whether they're working with AI with discipline and judgment — or just accepting whatever the model hands back.

That invisible variable is about to become the most important one on your team.

What does your organization actually know about how well your team works with AI — not just whether they're using it?
🔴 No way to assess it — AI skill is assumed or inferred from tool usage, not evaluated
🟡 Managers have a general sense of who's good with AI but no framework to assess or develop it
🟠 Some informal recognition of AI capability differences across the team but nothing formal or repeatable
🟢 AI competency is defined, assessed, and incorporated into development goals and performance reviews

Most organizations are 🔴 or 🟡. Which means the team members doing the most sophisticated AI work are invisible to the talent system. And the ones producing mediocre AI outputs are invisible too — for a different reason.

What This Actually Costs You
You can't develop what you can't see.

If AI competency isn't defined, it can't be coached. It can't be rewarded. It can't be set as a goal. It can't be tracked year-over-year. And it can't be used to make better hiring decisions.

The organizations that get this right in the next 18 months will build compounding advantage — because their people will get measurably better at AI, not just more familiar with it. The ones that don't will wonder why their AI investments keep underdelivering despite widespread adoption.

---

The gap between using AI and using it well is real. And right now, there's no organizational system to measure it.

---