Agentic Landmark · The Brief
Briefs on the infrastructure, authorization architecture, and commerce strategy of the agentic web: what brands need so agents can find, evaluate, and transact with them.
Anthropic now marks Claude output with an embedded text watermark and C2PA metadata. The documentation is candid about what that proves, which is very little. Provenance and authorization are different records, and only one of them is being built for you.
Both agent readiness instruments produce a weighted composite, and an average is a claim about the whole. A break is a claim about one link. Those do not commute. Why the score tells you what your exposure costs, and only an ordered read can tell you where you stop.
An agent and a seller want the same things right up until the recommendation, which is the one moment that decides the sale. Whoever funds the agent decides what happens there. For the agents that earn the highest-value delegation, there is no rate card, and there was never going to be one.
Agent selection is a funnel with its own stages and its own success event, and almost nobody instruments it. Winning upstream and winning downstream produce the same blended number, which is why the single-funnel view sends you to fix the wrong half.
A category of agent software now ships the org chart as the interface for running agents. It is intuitive, and it is the wrong unit of analysis. A reporting line records who answers to whom. It does not bound what may be committed, on which workflow, by which principal.
Over 40% of agent programs will be canceled by 2027. Blast radius decides which survive: how much a wrong action costs, and whether you can take it back.
Pull the audit log for the last purchase order your agent placed. Whose name is on it? In most enterprises, the answer is a person, sometimes one who was on vacation that week. What the log will not say is that an agent did this.
A demand-side agent that gets you wrong costs you a recommendation, and it self-corrects tomorrow. An operational agent that gets it wrong has already placed the order. Recommendations are reversible. Actions are not. Why agent readiness takes two instruments, not one.
Most agent-ready advice collapses two different problems into one. Being cited and being usable run on different infrastructure, fail in different ways, and must be fixed in a fixed order. A map of the four-standard stack, from robots.txt to WebMCP, and why the sequence is the argument.
In March 2026, AI-sourced retail traffic converted 42% better than everything else. Now try to find it in your analytics. Agent revenue lands in direct, organic, and unassigned, so the best-converting channel looks unproven and gets defunded. Not a reporting problem. A budgeting problem.
