Concierge surfaces.
Client-facing assistants that stay inside scope, cite their sources, and hand off to humans on defined triggers.
Layer 04 — The ArchitectureQ3 2026
Application.
User-facing surfaces and integrations — concierge widgets, intake interfaces, and operator consoles tuned for regulated workflows.
Application is Layer 4 of the ism3 stack. User-facing surfaces and integrations. Concierge widgets, intake interfaces, and operator consoles tuned for regulated workflows.
The application layer is where your teams and your clients actually touch the system — and where regulated workflows diverge hardest from consumer chat. An intake interface that collects protected information, a concierge that must decline out-of-scope questions, an operator console that shows a reviewer exactly what the model saw: these are purpose-built surfaces, not skins on a chatbot.
Layer 4 surfaces inherit everything below them — tenancy from Layer 1, routing from Layer 2, retrieval permissions from Layer 3 — and expose the audit trail above them. The result is an interface your compliance team can reason about.
Inside Layer 4.
Intake interfaces.
Structured collection tuned for regulated data — what is captured, what is redacted, and what is refused is explicit.
Operator consoles.
Reviewers see the query, the retrieved context, and the generated answer side by side — the unit of review, not a transcript fragment.
System integrations.
Connections into the case-management, records, and scheduling systems you already run, with idempotent writes that reject replays.
Reference architecture
Whitepaper — Q3 2026.
The Layer 4 whitepaper will document the surface patterns — concierge, intake, and operator console — and the integration architecture that connects them to existing enterprise systems.
FAQ
Layer 4, answered.
Yes. Each engagement is custom-built for the workflows it serves — the surfaces above are patterns we deploy and operate, not products you license.
That is its job. Integrations into case-management, records, and scheduling systems are part of the layer, with idempotent writes so a flaky downstream API cannot double-post.
Scope enforcement at the surface, retrieval grounding from Layer 3, and defined human-handoff triggers. The assistant answers from your sources or it hands off — those are the two paths.