C3 Mobile 0.1.2
Android control surface for paired Herdr hosts: Signal, sessions, workspaces, terminals, pairing, revocation, and reconnect recovery.
C3 / Delivery map · July 2026
This roadmap separates downloadable software from platform qualification and future intent. A build existing is not the same as a path being fully qualified.
Launch beta
Android control surface for paired Herdr hosts: Signal, sessions, workspaces, terminals, pairing, revocation, and reconnect recovery.
Unsigned Linux, macOS, and Windows builds with guided roles, verified runtime downloads, C3Sync operations, agent control, and terminals.
Encrypted native agent-session and working-tree continuity, durable offline catch-up, conflict preservation, and commit-aware fast-forwarding.
Standalone Linux, macOS, and Windows runtimes connecting the C3 control plane to Herdr. Linux is the physically qualified host path.
Next gates
Exercise install, start, stop, restart, persistence, and uninstall on macOS LaunchAgents and Windows Task Scheduler.
Qualify visible ANSI snapshot refresh, input forwarding, reconnect behavior, and long-output handling against a real Herdr session.
Add platform signing, macOS notarization, stable update channels, and store-ready mobile builds after the unsigned beta proves the workflow.
Complete an external review of the E2EE protocol, enrollment and recovery ceremonies, native secret storage, and relay threat model.
After launch
End-to-end FCM/APNs delivery, physical iOS qualification, and spoken screen-reader audits are outside the current launch gate.
The current Mobile installation enrolls with one hub that can reach many bridges. Fast switching between unrelated hubs comes later.
Plugins, worktrees, Herdr configuration editing, and integration administration remain separate from core orchestration.
C3 remains centered on a user-owned hub. Any future convenience layer must preserve endpoint encryption and explicit infrastructure ownership.
Start with evidence