ClearConnect Headless component and script review¶

Status: Review draft | Last reviewed: 2026-10-15

The interactive review prepares the conversational ClearConnect story before a full Scene is produced. It shows seven workspace arrangements, fifteen reusable A2UI components, a brand board and a six-chapter script. Every record, dialogue and outcome is synthetic.

The selected runtime direction is now OpenAI Decisions for Headless presentation: choose behavior, component composition and placement from validated plans. The hosted review still uses authored arrangements; no Decisions API integration is active in it.

Rendering and ownership¶

The review imports the current apps/ai-manager/components/director/workspace/HeadlessShell.tsx, its original scoped stylesheet and its shared workspace reducer. The component registry is the catalogue's real registerA2UIComponent entrypoint. The shell and catalogue are bundled into a static review; no retired Headless runtime is started.

Source owners:

Asset	Location
Components, manifests and tools	`apps/catalog-builder/catalogs/tenant/clearconnect-headless/`
Color/font specification	Catalogue `branding.json`
Scoped Headless adaptation	Catalogue `branding.css`
Script source	`apps/ai-manager/scripts/clearconnect-headless/script.json`
Generated readable script	Same directory, `SCRIPT.md`
Review, build, install and verification	`apps/ai-manager/scripts/clearconnect-headless/`
Generated site	`apps/clearconnect/review/dist/`

The existing Clear Connect leaf wordmark is retained. A cropped leaf supplies the narrow navigation mark. Forest green and sage derive from the supplied ClearConnect app; Figtree and Poppins come from the Headless base. Font licences are packaged with the catalogue. Embedded font CSS makes the native catalogue preview independent of cross-origin font requests.

Interaction contract¶

The catalogue emits semantic actions such as cc.work.focus, cc.preferences.confirm and cc.callback.confirm. An async dispatcher receives case context and, where applicable, reviewed form values. If only the legacy handleAction is available it can request work, but the component still does not claim the work completed. Missing action transport disables the button. Dispatcher rejection produces an inline retry message.

The review dispatcher changes sample views and returns authored preview outcomes. It performs no HTTP mutations. The ActionReceipt component renders the status supplied by the host; it does not derive success from a click. Choices preserve explicit refusal. Evidence can be expanded independently.

Proactive entry and document evidence¶

Workspace entry supplies the morning briefing, Renee's priority, Ashley's scheduled call and earlier intake summary immediately. It does not wait for a typed question or suggestion click. The script's first assistant message is automatic; the composer offers follow-up actions rather than an opening request for priorities.

The supplied PSP archive includes EnrollmentFormView.tsx, DocumentReviewPane.tsx, the fax extraction service/router and frontend/public/demo-assets/clearconnect-enrollment-form-ashley.pdf. The extraction service includes PDF text extraction with LLM field mapping and an image-fax vision path. Their presence in the archive does not establish a running OCR integration in this review.

DocumentInsight summarizes earlier processing and emits cc.document.open with caseId and documentId. The review resolves a fixed Ashley attachment; it does not load caller-supplied URLs. The native dialog shows three rasterized pages of the original PDF, extracted field provenance, later-record context, page navigation, enlargement and the unchanged downloadable PDF. The source is loaded on demand. Escape closes the reader and restores keyboard focus.

prepare-document.py uses build-time PyMuPDF to produce review assets under apps/ai-manager/scripts/clearconnect-headless/documents/. document.json records archive/member provenance and the PDF hash. No OCR service is invoked. The PDF is stamped September 29, 2026, so it represents intake before the fictional October 13 workday. Its blank member ID remains blank on the paper; the later coverage lookup and separately captured consent are authored story records. The unsigned consent sections and blank assistance application are preserved. This document belongs to Ashley; Renee's missing note stays separate.

Story¶

The fictional workday is Tuesday, October 13, 2026, with Eastern times and explicit time jumps. Maya coordinates exceptions; Pacey supplies on-screen assistance. The patient-facing ClearConnect AI answers Jordan's chat and Renee's call, makes Ashley's scheduled welcome and owns her agreed Friday follow-up. Routine actions proceed after applicable patient confirmation and successful tool results. They do not become a coordinator approval queue.

Jordan's preference chat completes with AI. Renee explicitly asks for Maya; the handoff includes identity state, completed work, provider-outreach context and the missing note. AI retains ownership until Maya accepts. Ashley's AI welcome completes without escalation, retaining accepted and declined choices. The updated briefing reports outcomes automatically and keeps Renee's exception visible. The script is approximately seven minutes, with optional document and provider-takeover beats adding 20–30 seconds.

The script has separate speaker/mode fields, screen directions, component references and outcomes. Pacey text must not be mixed into patient audio. See the generated script for the complete dialogue and review decisions.

Delegated outreach and call supervision¶

From EvidenceAnswer, Delegate provider outreach opens the AIOutreach example. Maya assigns a goal, and the AI contacts the approved provider. The component shows the task, recipient, active call state, transcript and remaining document dependency. It emits cc.outreach.direct with reviewed instruction text and cc.outreach.takeover with case/task identities.

The review acknowledges direction and demonstrates Takeover requested before Maya on call. Its 650 ms transition is deliberately authored; it is not a Genesys/media result. Switching examples invalidates a pending transition. A live host must authorize the task, resolve the active call and await actual human media acceptance, retaining AI ownership on failure or uncertainty.

The Awaiting document variant records the provider commitment without claiming the note arrived. Provider conversation, receipt, extraction and case validation are separate events. AIServiceUpdate provides optional inspection of routine AI conversations. ConversationArrival is displayed as Conversation Handoff and represents an escalation, not every new contact.

Draft assets and publication boundary¶

The native installer creates a tenant catalogue named ClearConnect · Conversational workspace and a branding profile named ClearConnect · Headless review, then builds the catalogue as a draft. These are review assets and are not attached to any live agent.

The complete custom Headless appearance is applied in the static review through the scoped brand adapter. Scene's existing branding selector maps its supported colors/logo; it does not automatically consume arbitrary css_overrides for the Headless shell. Full Scene assembly must carry the approved adapter into the host and pin published catalogue versions. No complete Scene is produced at this review stage.

Commands and repeatable installation are in the catalogue README. The review deploy changes only the static /review/ directory on the existing ClearConnect host.

Verification¶

The browser check validates every manifest sample, all fifteen renderers, seven workspace arrangements, evidence expansion, explicit decline, edited preference payloads, callback outcomes, pending/error variants, host branding changes, script download and mobile layout. It checks automatic initial content with no user message, all three document pages, the unchanged PDF hash, keyboard focus return, document enlargement and mobile containment. It verifies AI-only routine resolution, selective handoff, AI outbound ownership, delegated outreach, instruction payloads and pending takeover before human ownership. It also rejects JavaScript errors, failed asset requests and any browser HTTP mutation. Screenshots and reports are stored privately in .local-data/clearconnect-headless.

See the presenter review guide.