Hosted MCP service and stores · 8 October 2026 · Customer access appears in the combined architecture
Guided views
Explore this system
Step through curated paths without changing the source diagram.
Beat
Next
ReadyChapter 01 / 01
Guided chapter
Diagram guideExplore this system
Inspecting compiled semantics
E ExportT ThemeS Style0 Reset+ Zoom in- Zoom outEsc Close
Find a node
⌕/
No matching nodes
Semantic passport
Verified source
Authored reach
Route probeChoose a start node
Pick two semantic nodes on the diagram
Choose the source, then the destination. Direction matters.
Semantic lensCompare system roles
Choose up to two semantic kinds. One reveals its real traffic; two compare only direct authored relationships.
Choose a kind to inspect its nodes and touching relationships.
Semantic radar
Building overview
Click nodeDrag to pan
GECX owns the MCP connection
• Your agent calls /mcp with its CES service-agent ID token. The app checks the signed identity again.
• Bind experienceSessionId to X-Trueserve-Session-Id. get_session_info resolves it before form tools run.
The browser submits; GECX reads
• Your backend creates an experience with POST /v1/sessions. The customer browser receives A2UI over SSE and posts a ui-action through the public web entry.
• GECX receives the submission through await_auto_change. A later call can read the retained result.
SMS and customer access need setup
• The source includes AWS SMS and link redemption. This pilot has no SMS credentials or origination identity.
• A customer mobile browser needs a public HTTPS web entry that adds Google ingress authentication and preserves the browser session JWT.
Pilot limits
• One warm instance; replacement clears experience and submission state. The app image retains its catalogues.
• Synchronous GECX form calls passed validation. ANI, SMS delivery and voice interruption need a channel integration test.
Architecture diagram • Built with Archify • Create yours ↗ • Hover to trace • R route • Click to focus • +/− zoom • M radar • T theme • E export