Codex-first thinking
The output is not a conversation. It is a repo-ready packet with boundaries, files, tasks, and correction memory.
Builder Proof
Inspect the work, not the pitch.
FounderSignal is a standalone Build Week project that demonstrates product judgment, agent workflow design, API discipline, deployment verification, documentation, and GitHub handoff from one public system.
Codex-ready proof surface
Agent loop, compiler, correction, GitHub packet, eve shape, Vault handoff.
What to inspect
One builder, multiple proof points.
01Live Agent Workflow
Mission packet -> runtime processing -> VC, security, and growth specialist cards.
02Codex Artifact CompilerGenerates `spec.md`, `schema.sql`, `tasks.txt`, and `manifest.json` from founder intent.
03GitHub LoopTurns the corrected execution packet into an implementation issue packet.
04eve Agent ShapeShips agent files, tools, skills, channel, schedule, and delegated subagents.
05API ContractDocuments public endpoints and response contracts for the workflow.
06Vault ContinuityCommits final artifact state with a content hash and session id.
Builder signal
The project demonstrates the kind of work Codex makes possible.
Production surface
Vercel functions, Cron, headers, live routes, static docs, image assets, and deployment verification are all public.
Engineering handoff
The system creates GitHub issue packets so useful intelligence enters an actual implementation queue.
This is the proof path for serious reviewers.
Run the workflow, compile the artifacts, apply a correction, generate the GitHub packet, then inspect the repo. The product is the evidence.