Current Status

Status Terms

Term	Meaning
Runtime-verified	Verified with real Core, provider, worker, native app, device, ledger, trace, log, or artifact evidence.
Phase-test pending	Code or UI is wired, but real end-to-end validation is still missing.
Source-ready	Source, protocol, or project wiring exists and may build, but user runtime use is not verified.
Design-only	Product or architecture design exists, but implementation has not landed.

Public Release vs Development Evidence

The public release path is being reworked around native app assets. The private source tree has newer development evidence for native apps, Core management, mobile pairing, Android, and iOS Chat speech input. This documentation calls out those boundaries instead of presenting development evidence as a public release guarantee.

Current Snapshot

Area	Status
Core and CLI	Runtime-verified on the current development host; CLI is now an operator path, not the main public installer.
Manager tool planning	Runtime-verified with a real provider producing structured tool calls.
macOS native app	Runtime-verified in source/dev evidence for Core management, Workbench, Chat, Local Gateway, and native node work.
iOS native app	iPhone/iPad simulator runtime-verified for several paths; real iPhone install/launch/Core status verified; speech permission/live transcription still pending.
Windows native app	Source-ready + build/static verified; Windows host runtime validation pending.
Android native app	Source-ready + build verified; signed APK/AAB release packaging is now part of the native release path.
Gateway and Channels	Source-ready with selected runtime-verified slices; broader media and recovery parity still pending.
Talents	Registry/runtime projection foundations exist; full marketplace experience is not complete.

Why This Matters

Aegis can operate real tools and devices. That makes honest status labels part of the product safety model. If a feature is source-ready but not runtime-verified, the docs should say so.