Design sheets
Everything drawn for channels-manager, newest first. The folders hold a lot of superseded studies; this page hides those and shows only what is current.
Each one opens with the direction it is drawn against and ends with the forks it raises. React to the direction first — if that is wrong, the pixels do not matter.
Nothing gets built from any of them until you rule its direction.
Waiting on youround 4 · authored 2026-08-05, one hand
Drawn on the shell that shipped the same day, so what you see is the real chrome.
Answers "is the bot okay" in a sentence at the top, instead of asking it as a heading and making you work the answer out.
The fork: the five channel gate cards are gone from this screen, because the Dashboard already owns that concept. Keep them here and thin the Dashboard instead?
ContactsReact contacts.htmlOne list of people instead of two. Five dropdowns become one Filter button and a row of removable conditions, and "last heard from" finally gets a column.
The forks: does Segments stop being a tab and become a saved view? And is unrecorded consent "Not asked" or "Unknown"?
SettingsReact settings.htmlOne section at a time now that the ten tabs are the shell's panel. Two shapes drawn: a form section (Alerts) and a list section (Connections). The last uppercase is taken off.
The forks: does a connection row say "Working" (a claim needing a real check) or "Active"? And should every row carry a what-breaks-if-you-delete-it sentence, or only n8n?
Knowledge documentReact knowledge-doc.htmlThe only screen where what you write and what the bot uses differ: you edit prose, the bot searches the chunks it was cut into. This puts them side by side.
The forks: are chunk boundaries read-only, or can you move one by hand? And the KB rewrite-from-zero is still open, which may change what a document even is.
Analytics — the definition roundYour call analytics-definition.htmlNot a proposed screen. An inventory of the six questions the data can already answer, plus one arrangement drawn only so the choices are concrete.
Four answers needed: which questions stay, is cost-per-lead the headline, does Analytics own "per situation", and is the time-range control furniture?
Built and livefor reference — these are settled
Compare the running app against these; they are what was approved and shipped.
The screen at /. Its health foot line is now built too.
The two-level shell: icon rail plus a panel of screens. Five states.
Flow canvasLive flows-canvas.htmlThe automation canvas and its trigger wizard.
The Activity and Posts lanenot this lane's work
Another session owns these. Activity's design is reacted to and its logic is built; the Posts sheet is authored and awaiting a glance.
The full screen, assembled from its registry. Filter menu, facets, chips, sorting and the detail panel.
PostsAwaiting a glance sweep-activity-posts/posts.htmlNewly authored by that lane.
Activity matrixReference sweep-activity-posts/activity-matrix.htmlThe registry rendered as one reviewable page — 6 kinds, 8 outcomes.