Bring the interface
to the room.
Retained dashboards across TVs, phone and Kitchen Hub. Text, visuals and selected audio replies.
IMPLEMENTED · HOST-SPECIFIC LIMITS✳ CHAD’S WORKSPACE / NOVEMBER 2026
Hey Tai.
Here’s the
machine.
An idea can become software.
That software can reach the real world.
12 SLIDES · EXPLORE AT YOUR OWN PACE
INTENT → TOOLS → ACTIONFIG. 01 / CONNECTED BY DESIGN
01 / THE BIG IDEA
Software that reaches
beyond the screen.
START WITH INTENT
“Build this.”A conversation · Voice · Touch
“Show me.”
“Make it happen.”
→
⌘
Build somethingWrite code, test it, put it online.
▣
Use what’s connectedBrowsers, services and device capabilities.
↗
Put the result where it belongsA URL, a display, a phone or a watch.
THE SHIFT
From isolated apps to a workspace that can build, connect and act.
02 / THE ARCHITECTURE
Four parts.
One working loop.
Each has a clear job.
Together, they turn intent into something useful.
SELECT A LAYER TO EXPLORE ↙
A map of responsibilities. Tasks use the parts they need.
03 / IO — INPUT & OUTPUT
Hands.
Eyes.
A voice.
The bridge between an agent
and the things around us.
Authenticated devices. Explicit destinations.
Capabilities depend on the host and its permissions.
IOINPUT ↔ OUTPUT
PHONEVoice · Native controls
WATCHESPush to talk · Replies
DISPLAYSDashboards · Scenes
BROWSERS & HOMEWeb interaction · Selected controls
IN Voice & touchACT Native & browser commandsOUT Visuals, text & selected speech
04 / LUCITE — THE WORKSHOP
The workshop
behind the magic.
LUCITE /
REUSABLE PRIMITIVESBuild once.
Build once.
Compose everywhere.
Shared TypeScript utilities, service wrappers, authentication, state and infrastructure helpers.
HotStateHot contentService integrations
✳
Every project adds tools.
Those tools make the
next project faster.
The original monorepo. Reiterate has since become a standalone deployment engine.
05 / REITERATE — THE CLOUD ENGINE
A folder becomes
a live system.
A repeatable path from source to AWS.
Deploy the capabilities you need.
Keep the deployment state in the cloud.
your-domain/ SOURCE
├─ public/Website & assets├─ api/HTTP endpoints & state├─ io/WebSocket handlers├─ event/Queued & scheduled work├─ email/Incoming email handlers└─ private/Private objects⟶
↗
DOMAIN-ADDRESSABLE AWS SERVICESReachable.
Revisioned.
Repeatable.
S3 + CloudFront · Lambda + API Gateway
DynamoDB · SQS + Scheduler · SES
01 Validate→02 Review diff→03 Update→04 Live HTTPS
06 / CODEX — THE OPERATOR
From a sentence
to a verified change.
AN EXAMPLE WORKFLOW
“Make a presentation for Tai.
Deploy it with Reiterate.”YOU
Deploy it with Reiterate.”YOU
01 Read the workspace map & instructions
02 Inspect the relevant projects
03 Build the presentation
04 Check rendering & interactions
05 Deploy & verify the result
THE WORKFLOW BEHIND THIS DECK
REASONING + TOOLS + FEEDBACK
It can work
inside the workspace.
Read source. Write files. Run commands.
Use the integrations already built.
Check what actually happened.
Enrolled device inputs share a durable Codex conversation.
Desktop chats remain separate. Replies follow device routing.
07 / FOLLOW A REQUEST
Watch the pieces
work together.
FROM YOUR WRIST
“What can thisSTEP 1 / 5
workspace do?”
The selected audio mode determines whether speech plays on the watch, phone or nowhere.
08 / WHAT’S ALREADY HERE
Real projects.
Real capabilities.
Bring the interface
Work in an
existing session.
Snapback can inspect and interact with selected authenticated desktop browsers.
IMPLEMENTED · VERIFY TARGETMore than
a notification.
Signed commands, app controls, UI actions and bounded dynamic Java execution.
RECORDED DEVICE CHECKSBuilt here.
Running online.
Public apps migrated to Reiterate; connector and experience templates have cloud test deployments.
DEPLOYED · SCOPE VARIESA growing
toolbox.
Web products, market-data pipelines, agent tools and device experiments share one workspace.
MIX OF PRODUCTS & EXPERIMENTS09 / INSIDE THE WORKSPACE
Organised for
the next idea.
One workspace.
Independent projects.
Shared instructions and tools.
The index is the map.
Each project owns its implementation and operating guide.
workspace/PROJECT CONTAINER
WORKSPACE_INDEX.mdWhere to startlucite/Libraries, integrations & productsreiterate/Standalone AWS deployment enginedocs/device-io/Inventory, routing & discoverymachine-brain-codex/Shared device conversation & jobsmachine-launcher/Phone app & native bridgewatch-control/Wearable controls & repliestv-hello-webview/Displays, scenes & TV adapters+ agent-system · monster · funnel · other projects
10 / DESIGNED WITH BOUNDARIES
Powerful tools.
Clear boundaries.
01
Know the destination.
Authenticate the input. Select the physical output. Respect silent mode and shared-screen bindings.
02
Separate authority.
Public connector delivery does not grant native device control. Secrets stay in the designated vaults.
03
Verify the result.
Accepted is not the same as rendered. Configured is not the same as online. Keep evidence of the outcome.
STILL EVOLVING
Some integrations are prototypes. A unified local host bridge is planned.
Device sleep, permissions and connectivity remain real constraints.
✳
FOR TAI / BUILT IN CHAD’S WORKSPACE
The next idea
has a head start.
Codex helps build it. Lucite supplies the tools.
IO connects the world. Reiterate puts it online.
What would you build?
THIS DECK IS AN EXAMPLE OF THE WORKFLOW. DEPLOYED WITH REITERATE.