How clients experience everything: conversational UI, voice, embedded in the tools people already work in (email, Excel, deal systems), proactive notifications, with one conversation following the user across channels rather than living in one app.
Channels, in the order clients ask for them: chat, web app, desktop, mobile app, voice, phone and call center, embedded in work tools, and MCP hosts
Output & format renderer, DETERMINISTIC: an immutable, versioned template merged with approved structured data (structures from Knowledge, house templates from the Plane); corrections land as data updates and the artifact regenerates
Channel mix configuration per client
MCP hosts (Claude, Copilot, custom apps) are a first-class channel, client-side; just beneath them the NORTH-FACING Platform MCP Gateway exposes the whole platform as an MCP server, so all code stays server-hosted
P1Z-built client surfaces (web app, desktop shell, mobile, voice) are thin shells over ONE shared UI core, render tree, streaming message views, conversation state machine; shells hold no business logic and enter through the same north gateway
Feedback capture: every edit, rejection and correction routes to the eval store, the richest eval signal there is
Boundary test: nothing rendered here is hardcoded, channels, formats and templates are all plane parameters.
Plane parameters: channels · formats · templates
Client-specific configuration for this layer is specified band by band in Client Delivery, C1 spec: every input with its binding key, generated artifact, and verifying check.
Component reference
Chat (Conversational UI)
The conversational surface where users work with the platform in natural language; the default channel for interactive judgment work.
ImplementationServed to hosts through the north gateway as UI resources; no business logic lives client-side. Activation per audience is the C1 channel_mix value.
Voice
Spoken interaction for hands-busy and mobile moments; the same conversation in a different modality.
ImplementationA channel adapter in front of the same gateway session; enabled through channel_mix. There is no separate logic path for voice.
Phone & Call Center
Telephony as a channel: inbound and outbound calls, interactive voice response, and call-center assist where an operator console surfaces the same platform.
ImplementationA channel adapter: speech in and out at the edge, the same gateway session behind it. Activation, routing and escalation rules are C1 values; no telephony-specific business logic exists anywhere.
Embedded in Work Tools
The assistant surfaced inside the tools people already use: email, spreadsheets, deal systems.
ImplementationEmbedded surfaces are selected through the C1 embedded_surfaces value; every embedded call still enters through the north gateway.
Proactive Notifications
Platform-initiated messages: a report is ready, a gate is waiting, an exception fired.
ImplementationTriggered by workflows and escalation timers. What may be sent, to whom, over which channel is governed by notification_rules (C1); nothing is sent outside those rules.
Cross-Channel Continuity
One conversation that follows the user across channels and devices instead of living in one app.
ImplementationSession and memory machinery (L7) keys the conversation to the person, not the channel; each channel attaches to the same session through the gateway.
MCP Hosts
The applications users sit in: Claude, Copilot, custom apps. Client-side; P1Z serves hosts and never builds them.
ImplementationHosts connect to the per-tenant north endpoint; admission is by host allow-list; identity passthrough carries the person into every downstream permission check. Distinct from the P1Z-built client surface shells: hosts are third-party applications P1Z serves but never builds.
Client Surface Shells
The P1Z-built surfaces: the web app in the browser, the desktop shell (native plus webview), mobile on iOS and Android, and voice as a future surface. Each is a thin shell: it renders and captures, nothing more.
ImplementationShells hold no business logic and no state machine of their own; they compose the shared UI core and speak to the platform only through the north gateway, exactly like a third-party host. A new channel is a new shell, never a new codebase.
Shared UI Core
The one presentation package every P1Z-built shell reuses: the render tree, the streaming message views, and the conversation state machine.
ImplementationBuilt once and versioned as a single package; a new surface is a thin shell over the same core, never a re-implementation. Client-side conversation state lives here and reconciles with the session and memory machinery (L7) through the gateway.
North-Facing Platform MCP Gateway
The platform exposed as an MCP server to any host: agents, use cases and UI resources offered as tools, with all code and business logic staying server-hosted.
ImplementationOne endpoint template, stamped per tenant (setup step 15). Tenant auth, host allow-list, identity passthrough, rate limits and per-host quotas; the tool listing is generated from the registry, never hand-registered.
Output & Format Renderer
The deterministic engine that turns approved structured content into finished deliverables.
ImplementationA pure function of an immutable, versioned template plus approved data. Templates come from C1 house_templates, document structures from Knowledge; no agent ever touches layout, and corrections regenerate the artifact.
Channel Mix Configuration
The per-client record of which channels are switched on, for which audiences.
ImplementationPlane values only (C1); changes land on config deploy with no code path.
Feedback Capture
Every edit, rejection and correction captured as evaluation signal, the richest labeled data the platform receives.
ImplementationRoutes to the eval store with the source data's classification inherited; drives the evals and self-improvement pattern (P5).