Qpoint Design

Pages

Session View — Transcript as Chat

Source: c77 session-view — chat-grammar bake-off over scenario fixtures, 2026-08-20

Anatomy v1 proved the ladder; this pass borrows existing chat grammars — messenger, team channel, agent console — so the transcript feels familiar before it feels novel. The question each candidate must answer: does the borrowed grammar carry machinery, violations, and cost without breaking the chat illusion? Every candidate renders the same fixture from the same mechanically derived beats.

Churn analysis — prod warehouse blocked, rerouted

Messenger

candidate

The iMessage/WhatsApp grammar — you on the right, the agent on the left, everything else whispered as centered system lines (the "Missed call" register).

· 4 MCP lifecycle ·

Summarize last quarter's customer churn from the warehouse — monthly rate and top three cancellation reasons.

09:31Z

I'll query the warehouse for Q2 churn events grouped by month and reason.

09:31Z

· 1 tool call ·

⃠ block — postgres-prod · query

The production Postgres server is blocked by policy for agent access. The snowflake-readonly replica is approved — rerunning the analysis there.

09:31Z

· 2 tool calls ·

Reasons should exclude involuntary churn — payment failures.

09:32Z

Re-querying with involuntary churn filtered out.

09:32Z

· 1 tool call · 1 file ·

Q2 voluntary churn: 2.1% → 1.8% → 2.4% monthly. Top reasons: missing SSO/SCIM (31%), price at renewal (24%), unused seats (17%). Summary written to reports/q2-churn-summary.md. Note: the prod warehouse remains blocked for agents; the readonly replica covered everything needed.

09:32Z

Verdict — instantly warm; the dialogue reads itself. But the grammar has no register for machinery beyond a whisper: bursts and violations become the small print, cost has no home at all, and the CISO's evidence is typeset as an afterthought. Familiarity here is too domestic for a governance surface.

Team channel

candidate

The Slack grammar — avatar rows, names, timestamps, and its best borrowed idea: machinery and policy speak as an app. Tool bursts arrive as attachment cards with the colored side-bar; a violation is the red-bar alert engineers already know from every #security channel.

Qpointapp09:31Z

4 MCP lifecycleinit postgres-prodlist_tools postgres-prod — 6 toolsinit snowflake-readonlylist_tools snowflake-readonly — 4 tools

Devon09:31Z

Summarize last quarter's customer churn from the warehouse — monthly rate and top three cancellation reasons.

Claude Code09:31Z

I'll query the warehouse for Q2 churn events grouped by month and reason.

Qpointapp09:31Z

1 tool callmcp postgres-prod·query — BLOCK — SELECT … FROM churn_events — server not approved for agents

Qpointapp09:31Z

Blocked by policy — block — postgres-prod · query

Claude Code09:31Z

The production Postgres server is blocked by policy for agent access. The snowflake-readonly replica is approved — rerunning the analysis there.

Qpointapp09:31Z

2 tool callsmcp snowflake-readonly·query — ok — churn by month, Q2mcp snowflake-readonly·query — ok — cancellation reasons, Q2, top 10

Devon09:32Z

Reasons should exclude involuntary churn — payment failures.

Claude Code09:32Z

Re-querying with involuntary churn filtered out.

Qpointapp09:32Z

1 tool call · 1 filemcp snowflake-readonly·query — ok — reasons excl. payment_failedcreate reports/q2-churn-summary.md

Claude Code09:32Z

Verdict — the discovery of the pass: policy as a persona. When enforcement speaks as an app in the thread, violations stop being metadata and become utterances — with the exact visual weight engineers already grant Slack alerts. Machinery is first-class but bulky: every burst costs a full row, and long sessions will scroll forever.

Agent console

candidate

The Claude Code / ChatGPT grammar — the engineer's own daily surface: full-width prompt blocks, assistant prose, tool calls as collapsed mono rows, cost as a per-turn footnote. For the person who ran the session, this is replay in their native tongue.

▸init postgres-prod

▸list_tools postgres-prod — 6 tools

▸init snowflake-readonly

▸list_tools snowflake-readonly — 4 tools

Devon

Summarize last quarter's customer churn from the warehouse — monthly rate and top three cancellation reasons.

I'll query the warehouse for Q2 churn events grouped by month and reason.

▸mcp postgres-prod·query — BLOCK — SELECT … FROM churn_events — server not approved for agents

✗ block — postgres-prod · query

The production Postgres server is blocked by policy for agent access. The snowflake-readonly replica is approved — rerunning the analysis there.

▸mcp snowflake-readonly·query — ok — churn by month, Q2

▸mcp snowflake-readonly·query — ok — cancellation reasons, Q2, top 10

Devon

Reasons should exclude involuntary churn — payment failures.

Re-querying with involuntary churn filtered out.

▸mcp snowflake-readonly·query — ok — reasons excl. payment_failed

▸create reports/q2-churn-summary.md

Verdict — the most literal familiarity for the primary audience: it looks like the tool that produced the session. Machinery is native, cost footnotes land naturally. But it flattens the oversight reading — every tool row carries equal weight, so violations rely on color alone, and there is no skim layer at all: you re-live the session at 1×.

Chat wearing the spine

carries forward

The composed candidate: channel-grammar rows, but the avatar rail becomes the beat spine — dialogue keeps faces, machinery keeps glyphs, bursts stay one line until asked. Familiar at reading distance, scannable at arm's length.

▸

activity09:31Z

Devon09:31Z

Summarize last quarter's customer churn from the warehouse — monthly rate and top three cancellation reasons.

Claude Code09:31Z

I'll query the warehouse for Q2 churn events grouped by month and reason.

▸

activity09:31Z$0.02

✗

blocked09:31Z

block — postgres-prod · query

Claude Code09:31Z

The production Postgres server is blocked by policy for agent access. The snowflake-readonly replica is approved — rerunning the analysis there.

▸

activity09:31Z$0.02

Devon09:32Z

Reasons should exclude involuntary churn — payment failures.

Claude Code09:32Z

Re-querying with involuntary churn filtered out.

▸

activity09:32Z$0.02

Claude Code09:32Z

Verdict — the channel's warmth with the anatomy page's spine: one rail serves both readings. Dialogue stays a conversation between faces; machinery, violations, and errors become named speakers in the same thread; the glyph column survives squinting. Cost rides the row edge without ceremony. This is the transcript grammar to carry into the composed session page — pending Mark's read.

Laws

What the borrowing taught

Grammar	Borrows	Reveals	Breaks
Messenger	Bubbles, sides, system whispers	Dialogue warmth — the session as a conversation you were in	Machinery demoted to small print; cost homeless; evidence reads as gossip
Team channel	Avatar rows, app personas, alert attachments	Policy as a speaker — violations land with #security-alert weight	Row-per-burst bulk; long sessions scroll without a skim layer
Agent console	Prompt blocks, collapsed tool rows, per-turn cost footnotes	The engineer's native tongue — replay looks like the tool that ran	No altitude: every row equal weight, violations lean on color alone
Chat + spine	Channel rows for dialogue, anatomy glyph rail for everything else	One rail, two readings — conversation up close, spine at a squint	Slightly heavier gutter; avatars and glyphs must share a column width

Three laws carried forward.Familiarity is the ramp, not the destination — borrow the chat register for dialogue, but the session is testimony, not conversation; the spine is what we add. Policy is a speaker — enforcement rendered as an utterance in-thread (the channel grammar's gift) makes violations legible to every audience at the weight they deserve. Machinery stays one glance away, never zero — collapse bursts, but a transcript that hides the machinery entirely is a chat log again, and the compliance reading dies.