Public development status · 2026
Making space for
better conversations.
A live view of the work turning saved ideas into private, audience-specific conversation decks and deliberately shared Libraries—without exposing the private content itself.
Codex work status
Not blockedCodex is actively working. Temporary phone use does not stop independent implementation. iOS is green at 31/31 simulator tests, Android checks pass, role email is live, and the physical Safari share round trip is parked until Mark returns.
Flight path
From archive to private beta
-
01
Source archiveShipped
Catalog merged and validated.
-
02
Cloudflare runwayShipped
Worker, D1, R2, and this public status center.
-
03
Native shellShipped
SwiftUI model, persistence, and share extension.
-
04
The tactile ritualShipped
Deck physics, reveal, postpone, history, filters.
-
05
Multi-platform flightActive
TestFlight 3 → 5 → 6, Android, web, search, and incremental setup.
Priority 1 · blocking
Mark action required to unblock
Only actions that Codex could not solve with Computer Use, saved credentials, retries, or another safe path belong here.
- None Codex is actively working and does not need Mark to unblock it.
Priority 2 · not blocking
Mark attention required
Decisions, useful real-world checks, or reversible choices worth seeing early. Work continues regardless.
- Physical Safari share when the test phone is unlockedVerify Safari → share sheet → Agenda! extension → saved card on TestFlight build 6. The connected, locked phone does not block other work.
- Instagram importer769 unique “For Maya” saves are audited to a stable bottom. The first offline import preserves all existing enriched cards, and an immediate overlap rerun makes no changes.
Theme mix
The conversation terrain
Future flight paths
Ideas stay visible without blocking launch.
Public status, private content
No password. No private cards.
Anyone can view this development status. Raw relationship context never appears here; the repository stays private, R2 has no public bucket endpoint, and card/media/sync APIs still require revocable credentials.