Roadmap
Three lanes for the app. One more for the hardware. Every milestone lives in content/roadmap.ts — edit one object, the page reflects it on the next build.
Where we started
Native Android app shell in Kotlin. Jetpack Compose UI, intro boot animation, onboarding flow, user-selected assistant name with persistence, voice style selection, Command Deck + Living Companion layout, central animated orb with identity plate, bottom navigation shell.
Completed
Natural command input converts to safe, inspectable skill previews before any live action runs. Rule-based intent routing with AI Intent Brain fallback, parameter extraction, dry-run preview, missing-field detection, step preview, and irreversible-step markers.
Completed
Nine built-in known skills run through controlled Android intents and AccessibilityService: email drafting, reminders, search, Maps, text messages, calendar events, notes, app launching, and browser/website search. Final send/save/confirm always stays under user control.
Completed
Known skills become trustworthy and inspectable. Step result objects, success/failure states, retry and fallback logic, timeout handling, risk classification, irreversible-action confirmation, and the green-pin criteria that mark a skill stable enough for normal use.
Completed
Known-skill execution moved beyond a test harness into a product flow: voice and typed command input, safe direct handoff for trusted known skills, staged values, recent run and diagnostics surfaces, parser/source visibility, missing-field handling, and user-controlled protected final actions.
Learn by Doing records private on-device Accessibility action metadata and OpenCV screen-state fingerprints only while explicitly enabled. Users can demonstrate workflows, test them, re-learn, accept them, give them icons, and remove learned skills. Protected final actions remain manual.
Approved learned skills can be listed, staged, invoked by shortcut or voice, guarded by replay/testing, and removed with confirmation. Learned-skill awareness is reflected in Silver Prime's local self-knowledge without exposing private learned steps or payloads.
The production Aetheric V2 asset family, measured action controls, bounded raster cache, responsive Prime Nexus header apertures, and source-measured title/status masks are merged. The v122 build is the latest founder-tested development baseline; later v124 header polish is merged and still awaits device verification.
Where we are
Current merged Android code baseline: versionCode 124, versionName 1.0-mainc-council-layout-polish-r1. MAINC R1 provides a full-screen, local-first council for two to four ready providers, blind opening positions, rotating later rounds, human interventions, stop/end recovery, partial-failure isolation, plain-text export, and a transcript-first responsive layout. Automated gates passed with 110 tests, zero lint errors, and an assembled debug APK; founder device and real-key verification remains pending.
Verify two-, three-, and four-provider councils with real keys on founder devices, then add Council History and deletion, retry/skip controls, richer provider metadata and usage, explicit privacy disclosure polish, conclusion/synthesis, Markdown and JSON export, accessibility and reduced-motion coverage. MAINC remains a human-guided discussion workspace and does not execute Android tools directly.
Silver Prime now has local runtime self-knowledge, learned-skill awareness, a redacted tool manifest, and System Health Audit logs. Full user-facing backup/restore, profile transfer, and optional cloud or network-device backup remain future release work.
Settings is evolving into the control centre. Implemented surfaces include provider configuration, voice controls, health audit, account links, diagnostics, and Aetheric collapsed-first operational cards. Finalized pricing, subscription controls, purchase/restore, and release-policy polish are not live yet.
Voice input/output is active through Android TTS fallback plus optional downloadable Piper SP Male and SP Female packs. Conversation Mode can transition into known and learned skills. Continuous background listening and a completed wake-word engine remain unfinished future work.
The app now supports provider configuration for Groq, Anthropic, OpenAI, and Gemini, with one selected conversational provider active at a time and provider context grounded in the local tool manifest. Offline local-model packaging and final local/cloud routing policy remain future work.
Where we're headed
Future phone-camera vision, visual memory, and recognition scope. The plan calls for explicit camera permission, manual capture, object/place/person memory, 'What is this?' curiosity prompts, face enrollment, and deletable local-first vision memories, with no always-on camera in the first Vision milestone. Final entitlement is not set.
The AIPC informational surface already exists as the future home for hardware integration. Later work would add validated Wi-Fi Direct pairing, a Perception Brain camera stream, and shoulder-platform support. Hardware, app integration, pricing, and entitlement remain future decisions.
Prepare Silver Prime for public users: final permission onboarding, privacy and policy work, verified billing and entitlement controls, regression coverage, release signing, stable app bundles, device acceptance, website alignment, About links, and Play Console submission. No public Google Play release is live yet.
Hardware track
A future hardware track within the same Silver Prime product roadmap. The Android phone remains the AI brain; AIPC is the planned sensor and actuator peripheral. No hard dates: phases advance only when prototype and manufacturing evidence supports them.
Define the ring/toroid form factor, hidden-rotor housing geometry, and palm-size target weight. Specify the Wi-Fi Direct protocol between drone and Silver Prime app. Design the RTSP video pipeline, microphone array routing, and speaker integration. Specify the shoulder platform harness: magnetic landing pad, wireless charging coil, USB-C backup port, slim carbon fibre cross-body strap. No physical hardware — software architecture and interface contracts only.
Build and validate a first physical unit against the target ring geometry, guarded rotors, camera, GPS, flight-control, battery, and weight assumptions. Prototype the planned phone link and shoulder platform before publishing final specifications or commercial terms.
Flight-test the sub-250 g target and measure endurance, altitude hold, return behavior, phone-link recovery, and safety controls. Define supported markets from certification and local drone requirements before any external validation group or delivery promise is announced.
Select a manufacturing path, complete applicable certification, validate packaging and fulfillment, and publish campaign terms only after prototype readiness. No launch date, reward order, pricing, bundle entitlement, or subscription commitment is finalized.
Hardware phases are indicative only. No dates, prices, allocations, supported markets, or delivery estimates are committed; joining the interest list creates no reservation.