Updates
as at 16 November 2026
- 16 Nov
Progress Demo storefront on commercetools and a pick-and-pack mock-up
Pat's first progress update. An end-to-end demo storefront is live against commercetools, the pick-and-pack app is ported to web and mobile on the Experience API, and ten next steps are named.
Step 1 · Catalogue load into commercetools and CoveoStep 2 · Thirsty Camel storefront on the Experience APIStep 3 · Cart and checkout with CyberSourceStep 5 · Pick-and-pack app on a phoneThe Experience API on Container Apps in the sandboxVercel and the edgecommercetools development projectCatalogue data (Thirsty Camel extract)
- 17 Sept
Document Endpoint Catalogue
The working inventory of Experience API endpoints across all three audiences — shopper, admin, and trade — route, method, purpose, success status, authentication, store context, and endpoint-specific rules.
- 11 Sept
Document Edge and Gateway Boundary
The access-platform boundary in front of the Experience API — CDN, WAF, load balancer, reverse proxy, and API gateway responsibilities, and the trusted-context handoff.
- 11 Sept
Document Contract Requirements
The public contract and governance entry point — what consumers receive and the rules that govern it. Implementation detail lives in the companion specifications below.
- 11 Sept
Document Decision Register
The single index of unresolved Experience API architecture decisions — proposed defaults, owners, and status, across contract, runtime, capability, error, cache, and multi-brand decisions.
- 11 Sept
Document Error Catalogue
The internal application error model, code registry, provider-error translation, HTTP mapping, and catalogue governance behind the public error contract.
- 11 Sept
Document Runtime Design
How the Experience API process resolves context, executes composition, handles failure, and emits telemetry after the trusted gateway handoff.
- 8 Sept
Document Multi-Brand and Multi-Client Composition Strategy
How one Experience API supports multiple brands and client types through a shared composition core and isolated variation points, without a per-brand/per-client BFF fleet — including caching, response-model, and policy-externalisation patterns.