The loudest story in agent infrastructure as AGNTCon opens this week is not what arrived, but what remains missing from the ledger. On October 22, 2026, as AGNTCon and MCPCon open in San Jose, the industry faces a fundamental gap: while individual governance stacks are shipping, the connective tissue that would make them interoperable remains a series of drafts and blueprints. This announced-but-not-shipped ledger is the primary bottleneck to enterprise agent adoption and the defining cost of Q4 agent budgets.
The Shipped Perimeter
For builders with immediate needs, the perimeter is buildable, but it is proprietary. On October 21, NVIDIA pushed agent enforcement into the silicon with the release of the OpenShell Reference Architecture. The release provides a buildable blueprint and documentation for industrial-scale agent operations, but it anchors the control point in NVIDIA’s own hardware. Similarly, Rhapsody Guardian shipped this week as a healthcare-native gatekeeper, providing the scoped access and audit trails required for regulated clinical environments. These products are available now, and for organizations in regulated verticals, the audit trail is increasingly becoming the product itself.
The Money20/20 show floor in Las Vegas provided a third example of the shipped perimeter. Proof and Circle joints demonstrated an end-to-end identity-gated purchase using x401 credentials and x402 settlement. The demo showed machine-speed settlement without a human clicking approve, using verifiable credentials to gate stablecoin purchases. This approach decouples trust from centralized intermediaries, but like the NVIDIA and Rhapsody perimeters, it relies on a specific set of tools rather than a ratified industry standard.
The Roadmap Ledger
The gap between these shipping perimeters and true interoperability is mapped in the roadmap ledger. The Personal Agent Protocol (PAP) remains in v0.1 draft form, as detailed in our analysis of the unshipped specs. While Sierra and Meta announced the initiative on October 6, the reference implementation and finalized standard are still pending. Okta’s agent identity framework and its associated gateway are likewise in a pre-general-availability state, offering a vision of identity-governed short-lived tokens that builders cannot yet fully deploy into production.
This delay is not merely academic; it carries a direct cost for Q4 budgets. Builders are currently forced to choose between waiting for a standard that may not land this year or committing to an individual governance stack that may create future “agent debt.” As noted in Okta’s framework analysis, the market is building around standards before they are ratified, which risks further fragmentation as vendors ship extensions that embed proprietary assumptions.
Interoperability at the Wait
The consequence of this gap is visible in the AGNTCon agenda. Tracks on governing agent calls and permissions carrying across tools describe patterns rather than protocols. One day-one session prescribes intercepting every call an agent makes to swap in short-lived credentials—a necessary workaround for the absence of a shared origin-verification standard. Until the specifications under discussion are ratified, builders cannot buy interoperability; they can only buy individual bridges. For enterprise architects, the watch remains on whether the programs in San Jose produce a mechanism or stay at framing, and whether the gap between the shipped perimeter and the roadmap ledger begins to close before the 2027 budgets are locked.