The Blueprint: making any platform readable by agents

The PrestaShop module isn't an end in itself. It's the first implementation of a reusable pattern: how to open any e-commerce platform to AI agents, without inventing a protocol. We call it the Blueprint.

The problem isn't the protocol, it's the coupling

The temptation, when implementing UCP or MCP, is to code everything in the module. The result: throwaway, non-transposable code. At the next platform (WooCommerce, a Symfony API, a closed SaaS), you start over.

The Blueprint sets a different architecture: a decoupled core + adapters, hinged on a pivot format.

AI agents
   ▲  discover /.well-known/ucp, then query
ADAPTERS (UCP REST · UCP MCP · later WebMCP, feeds)
   ▲  pure functions: Capability Graph → protocol surface
CAPABILITY GRAPH (versioned JSON Schema, neutral, unbranded)
   ▲  produced by introspection, through a PORT
PLATFORM (PrestaShop · Sylius · an API · a proxy)

The Capability Graph: the only thing to write

The pivot describes "what this system can expose" — products, variants, public prices, stock, languages, currencies — independent of any protocol. It's a versioned JSON Schema.

A platform that can produce this graph inherits every adapter for free. That's the only platform-specific work. The manifest, the UCP mapping, the MCP server: reused as-is.

Three deployment modes, one core

• Embedded (coded): the core inside the app, which implements the ports with its classes. That's the PrestaShop module.
• Library: the core as a Composer dependency of an existing app — e.g. a FondoukBundle for Sylius/Symfony. A second reference implementation proving transposition.
• Proxy: the core in front of an untouchable system, wired to its API, exposing the agent surface on its behalf.

What makes modes 2 and 3 possible: the core depends on no framework. Hence the strict physical split capability-core/ ↔ prestashop-module/.

The red line

The Blueprint is a playbook for implementing existing standards, not a competing spec. The day it describes a concept UCP or MCP already defines, we delete it and point to their spec. Authority comes from being the best implementation, not one more standard.

Read the Blueprint

Four artifacts, extracted from real code: the Capability Graph schema, the adapter contract, the discovery pattern, the deployment modes. Entry point: ARCHITECTURE.md. All open (MIT).

The Fondouk team — Synapsea