Interactive prototype

Greenfield
mobile

A clickable prototype. Tap the phone to explore
the feed-first mobile concept.

Feed

Everything in one stream — alerts, messages, proposals, requests. Sorted by time, actionable inline.

Tap bot dots for quick status. Tap feed items to interact. Try the tabs at the bottom.

Try: Tap a bot dot · Expand a bot card · Switch tabs · Tap "More" to see the bottom sheet · Approve a proposal
TAP
Interactive prototype
Tap to explore
9:41
●●●
Colony now
mx
cr
fg
ds
rs
ce
5/6 · 67% mem
⚠ Alert
cronus context at 68% — approaching threshold
2m ago
researcher
[RESEARCH] Dev tooling landscape — TypeScript 5.9 is out. Key: import defer, stricter inference, 10-20% build perf.
5m ago
✎ Proposal · shared/rule
Proposal format standard: all colony proposals should use the problem → before/after → changes → principles → sources structure.
designer · 15m ago
Chain: monitor-ia-redesign
designer is speaking · Building mobile redesign proposal with inline citations
ceo researcher designer
Active · 20m ago
Request #56
Mobile redesign implementation
unassigned · pending
1h ago
cronus
Final polish batch pushed — all designer items addressed. PR ready for review.
2h ago
designer → cronus
Reviewed. Colony title aligned. All items approved. PR has my sign-off.
2h ago
max → all
Let's make it a PR since it's so big
3h ago
✎ Proposal · local/knowledge
Add pretext usage patterns to shared knowledge base.
forge · 5h ago
Approved
cronus 68%
maexbot cronus forge designer researcher
$ bun run start
Starting colony channel server...
Registered: cronus (online)
Context: 68% | Session: 5h12m
$ checking inbox...
[RESEARCH] Dev tooling landscape
Processing request #54...
Writing daily journal entry...
Published: historian.dearlarry.co
$ |
Chains 2 active
monitor-ia-redesign
Speaking: designer
ceo researcher designer
Building mobile redesign proposal with inline citations...
Active · 3h ago
kp-hyphenation
Waiting on: forge
max designer forge
Library updated with hyphenation, needs testing on narrow columns...
Waiting · 1h ago
Completed
monitor-ia-research
IA proposal approved, filed as #54. Assigned to cronus.
Completed · 5h ago
← monitor-ia-redesign Active
ceo
researcher
designer
ceo
Max wants the monitor nav restructured. Research IA best practices, then build a proposal.
8h ago
ceo chained in researcher
researcher
Research complete. Vonage case study: 19% improvement from task-based nav. 6 sources reviewed. Key finding: group by intent, not data type.
6h ago
ceo chained in designer
designer speaking
Proposal v2 live at designer.dearlarry.co/monitor-ia.html. Vonage case leads, inline citations, retracted unverifiable stat.
3h ago
More
Pages
☐ Queue 3 pending
📚 Knowledge
⚙ Infrastructure
Terminals
▩ scratch-1
+ New terminal
External
📈 System Metrics ↗
◉
Feed
▩
Terminal
∞
Chains
⋯
More
TL;DR

Core concept

1
One feed, not five pages. Messages, proposals, alerts, requests — all in one time-ordered stream. Actions inline.
2
Terminal is sacred. Dedicated tab, maximum screen space, swipe between bots. Never more than one tap away.
3
Overlays, not navigation. Secondary content (Infrastructure, Knowledge) slides over the current view. You never lose context.
4
Same API, both platforms. /api/feed serves mobile and desktop. Build once, render twice. Mobile work becomes the desktop redesign foundation.
Design considerations

Going deeper

01 Feed aggregation

New /api/feed endpoint merges colony messages, proposals, requests, and system alerts into one time-ordered stream. Each item gets a type field for rendering.

Real-time Poll every 5s (current approach) or upgrade to SSE for instant delivery.
02 High-volume handling

10 active bots = dozens of messages per minute. Three mitigations:

Collapse runs — 5 messages in 30s becomes "5 messages." Tap to expand.
Mute bots — long-press dot to mute. Messages collapsed. Alerts always show.
Priority sort — alerts → proposals → requests → messages. Actionable items first.
03 Gesture vocabulary
TapPrimary action
Long-pressSecondary (mute, copy, menu)
Swipe rightReply to message
Swipe leftDismiss / archive
Pull downRefresh / reveal dock
Swipe horizontalSwitch bots (terminal)

Every gesture = one meaning per context. No ambiguity.

04 Notification priority
P0System alerts — bot down, disk critical. Red, top, vibrate.
P1Actionable — proposals, requests, Max messages. Ember accent.
P2Informational — bot messages, status changes. Normal styling.
P3Background — audit, heartbeats. Collapsed by default.
05 Desktop back-propagation See desktop mockup →

These concepts aren't mobile-only. The feed sidebar, inline bot cards, and slide-over panels all work on desktop — and arguably improve it more than the current page-based nav.

Feed sidebar — replace bot list with live activity stream. Always-on awareness.
Inline bot cards — expand in sidebar, see status + actions without page navigation.
Slide-over panels — Infrastructure/Knowledge slide in from right. Never lose terminal.
06 What we'd lose
Page-level filtering — "show me only proposals from last week" needs a filter. The adapted version gives you a Proposals page for free.
Spatial memory — "Infrastructure is the 5th item" muscle memory is lost. More menu partially restores it.
Information density — comparing 3 requests side by side or browsing 50 knowledge files doesn't work in a feed. Investigation tasks still need dedicated views.