Agentic orchestration
Interview generation, answer coaching, report creation, retrieval context, and traceable orchestration boundaries are implemented in the backend.
Technical diligence room
Investor review flow for the Android product, AI orchestration layer, release system, observability, load evidence, and cost controls.
Start with the public proof, then use the protected deep dive for source files, run outputs, and limits.
Inspect the APK, Play screenshots, metadata packet, and deterministic Android release gates.
Review Python orchestration, retrieval boundaries, report generation, and the LangSmith trace smoke.
Separate deterministic load testing from tiny live-model sampling so throughput and spend are governed independently.
Keep iOS, AWS execution, and live-model stress tests as gated next proofs until those runs exist.
Current claims are tied to code, generated artifacts, smoke reports, or live public-safe endpoints.
Interview generation, answer coaching, report creation, retrieval context, and traceable orchestration boundaries are implemented in the backend.
Android release gates cover deterministic states across setup, chat, post-answer, completed sessions, and review/history flows.
Load testing runs on deterministic runtime. The first live-model trace sample is capped, small, and separate from stress testing.
Codex Spark remains the alpha proof path; OpenAI API is now a config-switchable serving path for future Google Play traffic.
LangSmith tracing is proven by deterministic and live-model public-scenario smokes, separate from stress tests so traces stay readable.
Repo/release evidence shows 94 commits since May 18, 50 release/play/site-related commits, and current launch gates passing.
The deep dive is gated separately: public pages stay open, protected evidence is Basic Auth scoped, and secret/raw-data classes stay out of git and static pages.
The protected answer map links each role requirement to current proof and explicitly marks roadmap items.
Public-safe endpoints stay open; sensitive traces, raw data, and deeper test artifacts belong behind the protected deep dive.