Two deadlines. Twenty days apart. Both reshape the advertising infrastructure that determines People Inc's revenue trajectory. Neither includes People Inc's voice.
The Shrinking Room Gets Fixed
October 2 is the deadline for Google and the DOJ to submit their jointly proposed final judgment in the ad tech antitrust case. Judge Brinkema's remedies, unsealed September 16, are behavioral: Google must integrate AdX and DFP with Prebid within 12–15 months, share real-time bid data with publishers, stop Google Ads from favoring AdX, and submit to a six-year technical monitor with full access to employees, systems, and source code.
For People Inc, this is unambiguously good. D/Cipher runs on GAM (Google Ad Manager, formerly DFP). The Prebid integration requirement means D/Cipher's auctions get exposed to open competition. Real-time bid data sharing means the contextual intelligence D/Cipher provides can be measured against what competitors offer. The playing field gets leveled in the infrastructure that carries D/Cipher's display revenue.
But here is the number that defines the scope: open web display fell from 40% to 11% of Google Ads volume between 2019 and 2025. Brinkema's remedies fix the plumbing in a room that is emptying. Video, CTV, in-app advertising, retail media, and agentic transactions are all explicitly outside the judgment's scope. The monitor watches for six years. The market it monitors has been shrinking for six years already.
The Growing Room Gets Standardized
October 22 is the close of public comment on AAMP 3.0, which introduces OpenProposal — the specification that standardizes how seller agents describe advertising products to buyer agents. This is the agentic equivalent of what DFP's auction logic does for display: it determines how inventory gets discovered, evaluated, and transacted. Except it is open, standards-based, and agent-readable from the start.
What OpenProposal enables: a buyer agent at WPP or Omnicom queries available inventory against a brief. Seller agents at participating publishers respond with structured proposals — pricing, packages, audience parameters, creative specs. The buyer agent compares, ranks, and moves toward commitment. No RFP email chains. No media planner spreadsheets. No phone calls.
The Seller Agent SDK is being built into reference implementations during the comment period itself. By October 22, the default codebase that publishers fork to participate will be hardened. After that, the standard moves from proposal to production.
D/Cipher is not in the comment process. D/Cipher is not in the Seller Agent SDK. D/Cipher is not among the registered agents. When the comment period closes, the specification that governs how buyer agents discover publisher inventory will finalize without People Inc's input on how D/Cipher's contextual intelligence should be represented.
The Asymmetry
People Inc benefits when openness is imposed on its supplier.
People Inc declines when openness is invited from its own infrastructure.
This is the structural paradox of October. The Brinkema remedies give D/Cipher better competitive data in display auctions — more transparency into Google's bid routing, real-time pricing signals, Prebid interoperability. People Inc did not ask for this openness. A federal judge imposed it on Google. And it helps.
AAMP 3.0 offers D/Cipher representation in the agentic advertising pipeline — the ability to describe its contextual intelligence to buyer agents, participate in automated proposal evaluation, receive queries from the Omnicom and Horizon buyer agents that are already executing live campaigns. People Inc was invited to participate. The comment period is open. The SDK is documented. The barrier, as I wrote in The Sandwich, is not engineering. It is organizational.
What October 2 Actually Fixes
The remedies are significant but narrow. A technical breakdown:
| Remedy | D/Cipher Impact | Market Covered |
|---|---|---|
| AdX integrates with Prebid | D/Cipher bids compete on neutral ground | Display only (11% of Google Ads) |
| Real-time bid data shared | D/Cipher can measure its contextual premium | Display only |
| Google Ads stops favoring AdX | Fair routing for D/Cipher supply path | Display only |
| DFP auction logic documented | Transparency into yield mechanics | Display only |
| 6-year monitor | Enforcement mechanism | Display only |
Every remedy helps D/Cipher. Every remedy applies only to the market segment that has been declining for six years. The remedies make the shrinking room fairer. They do not address the room that is growing.
What October 22 Actually Decides
OpenProposal is not theoretical. It connects to AdCOM (the common vocabulary), OpenDirect (transaction standards), and the Deals API. A publisher who implements the Seller Agent SDK can have its inventory discoverable by every buyer agent registered in the AAMP ecosystem — currently including Amazon Ads, PubMatic, Equativ, Optable, Dstillery, and others.
The specification being finalized right now determines:
- How buyer agents discover publisher inventory — if D/Cipher is not represented, buyer agents cannot discover it
- How proposals are structured — if D/Cipher's contextual intelligence has no OpenProposal schema, it cannot be evaluated alongside competitors
- How transactions flow from brief to commitment — if D/Cipher is outside the pipeline, there is no automated path from buyer query to D/Cipher response
The comment period is not a formality. It is when the default implementation gets built. The Seller Agent SDK that ships after October 22 will define the minimum viable publisher integration. Publishers who adopt it will be discoverable. Publishers who do not will be invisible — not by exclusion, but by default.
The Engineering Decision
There is a concrete action available to People Inc before October 22: submit a public comment to AAMP 3.0 describing how D/Cipher's contextual intelligence should be represented in the OpenProposal schema. Not build an MCP server. Not register an agent. Just — comment. Describe what D/Cipher offers in the vocabulary the standard is defining. Ensure that when buyer agents evaluate contextual targeting capabilities, D/Cipher's approach is representable in the specification.
CIO Jon Roberts is a founding participant in CoMP, IAB Tech Lab's compliance program. He has standing. He has the relationship. The same standards body that runs CoMP runs AAMP. The door is the same door.
A public comment is not a commitment to build. It is a signal that you intend to participate — that the specification should accommodate your capabilities. It costs one engineer reading the spec and one executive approving a submission. It buys time without committing resources. And it ensures that when the SDK ships, the default implementation does not exclude the very kind of intelligence D/Cipher provides.
The alternative is silence. The comment period closes. The SDK ships. The default implementation reflects whoever showed up. And D/Cipher's contextual intelligence — the anti-identity approach that is genuinely differentiated — gets no representation in the standard that governs how buyer agents evaluate publisher inventory.
One deadline imposes openness on People Inc's supplier. The other invites openness from People Inc itself. October will answer whether the company can only receive openness — or whether it can practice it.