FounderSignal

Repository Skill

Use FounderSignal as a Codex Skill.

FounderSignal is packaged so a judge or developer can use it as a reusable Codex workflow, not only as a hosted demo. The live app generates the artifacts; the repository explains how to carry those artifacts into a repo-level agent loop.

Clone-and-run path

  1. Use AGENTS.md as the Codex operating contract.
  2. Use eve-agent/skills/startup-validation.md for founder validation.
  3. Use eve-agent/skills/supabase-rls.md for database and RLS generation.
  4. Use eve-agent/tools/compile_intent.ts as the compile tool boundary.
  5. Copy the generated manifest.json tab from the live compiler into a Codex-ready project.

Skill invocation contract

FounderSignal_Bootstrap
{
  "founder_intent": "B2B AI document summarizer for law firms",
  "agent_validation_score": 84,
  "critical_risks": ["data privacy", "multi-tenant isolation", "workflow adoption"],
  "founder_corrections": ["Must support firm-level data isolation"],
  "outputs": ["spec.md", "schema.sql", "tasks.txt", "manifest.json"]
}

Vercel eve agent shape

The repository includes an eve-style durable agent directory with agent.ts, instructions.md, reusable tools/, reusable skills/, GitHub channels/, scheduled checks, and delegated subagents.

eve-agent tree
eve-agent/
  agent.ts
  instructions.md
  tools/
  skills/
  channels/
  schedules/
  subagents/

API proof

The public manifest endpoint exposes the active agent contract.

GET /api/eve-manifest
curl https://foundersignal-buildweek.vercel.app/api/eve-manifest

Guardrails

FounderSignal emits Supabase PostgreSQL primitives with explicit RLS policies, avoids unverified scale claims, and keeps ArkNet Digital Vault as a public handoff reference. This standalone Build Week project does not write into ArkNet OS or the arknet.digital project.