Building Blocks → Palettes

Concept: every application in the fleet is a typed building block. Blocks get assembled into palettes (purpose-built panels), viewed through lenses (need / want / use), and served according to roles. One composition model from your morning briefing to a recruiter's demo.

← Mockups home · Picker · Signal · Direct Line

The infographic — four layers, one flow

BLOCKSapps as typed parts
in ▸ out ports

Signalout: briefing · audio Dictateout: intents Benchmarksout: evals Photolibout: images Brandingout: posts Notifyin: events Spend Guardout: alerts Gia Chatin/out: dialog Fleet Auditout: health

▼ ▼ ▼

PALETTESblocks assembled
for a purpose

🌅 MORNING OPSSignal + Calendar + Spend + Notify 🎨 CREATOR DESKBranding + Photolib + Voice + LinkedIn 🛠 FLEET ROOMAudit + Spend + Dispatch + Logs 🎬 DEMO STAGEGallery + Benchmarks + Trust artifacts

▼ ▼ ▼

LENSESreorder everything
by intent

NEED — act now WANT — explore USE — daily tools

▼ ▼ ▼

ROLESwho sees what,
at what power

OWNEReverything · admin FAMILYchosen palettes · use COLLABORATORdemo stage · use VISITORgallery · view

The control panel — what assembling feels like

BLOCK LIBRARY

SOURCES

Signal briefing Fleet health Spend guard Photo stream

ACTIONS

Dictate Dispatch job Publish post

BRAINS

Gia chat Benchmarks

🌅 MORNING OPS — Byron's palette

SIGNAL BRIEFING

EP 15 ready · 4 stories · ▶ play · park topics → feeds Notify

SPEND GUARD

All quiet · $4.10 today · alert only on class-change

NOTIFY FEED

2 events overnight · access request (pending you)

DICTATE

tap → capture intent → OB1 consumer · destination chips

GIA — DIRECT LINE

"Morning. EP 15 rendered clean…" · same session as Telegram

drag from library · wires = feeds · every tile answers "why am I seeing this"

INSPECTOR — Signal briefing

typesource · audio+cards

feedsNotify · Gia context

freshnessupdated 6:15 today

cost$0.11 / episode

PERMISSIONS

OWNER · admin FAMILY · listen COLLAB · — VISITOR · —

LENS TAGS

WANTUSENEED (only on alert)

Role & permission model

Capability level → Role ↓	SEE tile visible	USE consume/play/read	WIRE rearrange, connect feeds	ADMIN grant, configure, spend
Owner (keyed device)	all blocks	all	all	all
Family (invited key)	granted palettes	granted blocks	—	—
Collaborator (share link, expiring)	Demo Stage	demo blocks only	—	—
Visitor (public)	Gallery only	public cards	—	—

How it hangs together

Blocks are typed. Each declares what it emits (briefings, alerts, images, evals) and what it accepts (events, intents, dialog). A palette is just a subscription graph — Signal's "parked topic" feeds Notify; Dictate's intent feeds Gia; everything Gia knows shows up in chat. Wires are visible: every tile can answer "why am I seeing this."
Permissions attach to the block capability, not the page. A palette shows a role only the tiles it's granted — same palette, different completeness per viewer. The grant primitives already exist in the fleet: keyed devices (you), invited keys (family), expiring share links (the stack-share mechanism, reused), public (registry visibility rules).
Lenses are orderings, not pages. NEED surfaces anything demanding action (approvals, alerts) across all palettes; WANT surfaces the explorable (briefings, new cards); USE pins daily verbs (dictate, chat, dispatch). Time-aware: mornings lead with Morning Ops, workday with Fleet Room.
Consumption is audited, not surveilled — same count-only, no-PII posture as the gallery.
Growth path: the gallery IS the visitor palette already; Direct Line (Phase ④) is the first owner block. This concept is the roof over both — each future build just adds a block, not an app.