What works, and what does not.

A local terminal agent that edits code and runs commands, with provider configuration, a doctor command, and hardened filesystem and terminal boundaries.

Designed but not yet implemented: account sign-in, device registration, the hosted model gateway and cloud task history.

The shared backend for identity, entitlements, credits, usage and tasks. It verifies Supabase tokens, owns no provider secrets on the client, and never executes privileged operations itself.

Billing holds no prices and no payment provider yet.

The layered Fedora bootc image, the capability layer, the safety layer and the AI Engineer control plane are being built.

Target: boot and desktop responsiveness within 5% of stock Fedora, with an offline-first reasoning path.

The voice pipeline, interaction routing and the desktop app are being built. The Aria-to-CLI contract does not exist yet.

When it does, voice approvals will route through the OS's real approval tiers.

Marketing pages are live. The account area is being migrated from a local store to Supabase Auth and the Beyonders-Backend.

Checkout stays honest: it will not take a payment until a provider is connected.