Understand the system without exposing the private runtime.

What Project KAI is, what local-first means here, and where the owner remains in control.

A build-time snapshot of real public system counts—not a live uptime dashboard.

Git-sourced engineering history with evidence attached to each public entry.

Observe, understand, plan, govern, act, review, and learn—with the action boundary stated clearly.

The governed path from owner intent to domain action, evidence, and multiple persistent memories.

The 13 declared technical roles with underlying capability and autonomous-agent status separated.

The public system map and status-aware navigation across KAI's current surfaces.

Conversation, memory, content, trading research, analytics, and governance status in one view.

Local spoken responses, English/Hindi routing, fallback behavior, and the neural-voice roadmap.

A real local keyword-search capability over the engineering report corpus—not semantic universal memory.

The approval-first control architecture and the honest boundary around live desktop execution.

Topic, script, claims review, scenes, visuals, narration, captions, music, assembly, thumbnail, compliance, review, and publishing.

The real channels, deterministic content router, and public discovery surfaces fed by the production system.

Why production automation stops before publishing and how that boundary shapes the system.

Market observation, strategy evaluation, governance, risk, and Alpaca Paper integration status.

A tightly bounded Alpaca Paper observation baseline is active; AI-directed and live-money execution remain disabled.

Strategy research, simulation, backtesting, reporting, and the distinction between research and advice.

Human checkpoints, paper-first validation, pause and emergency controls, and auditable operation.

Default-deny capability authorization, revocation, kill switches, rate limits, and fail-closed policy handling.

What the public site collects, what it does not, and how public-safe disclosure is handled.

Current foundations, next controlled milestones, and longer-term governed expansion.

The current owner contact path while dedicated project channels remain unresolved.