Honest Status

• ✓Public landing page with hero, problem, capability passport overview, prompt-vs-native explainer
• ✓Public registry preview with 10 seed packages
• ✓Capability Passport detail pages for all 10 seed packages
• ✓Manifest Spec v0.1
• ✓Capability Passport Spec v0.1
• ✓Install Receipt Spec v0.1
• ✓Policy Pack Spec v0.1
• ✓Prompt-URL-Install Spec v0.1
• ✓LLM-readable site install card at /llms.txt (text/plain)
• ✓LLM-readable per-package install cards at /packages/[slug]/llms.txt (text/plain)
• ✓Machine-readable registry endpoint declaration at /.well-known/apai.json
• ✓Honest status page (this page)
• ✓Security baseline page
• ✓Pricing preview page
• ✓Private registry beta and waitlist pages
• ✓Publisher application page
• ✓JSON Schemas for manifest, passport, receipt, policy
• ✓CLI scaffold under packages/cli/ (commands print stub output and write local receipts)
• ✓Install Card Verification: per-package install cards include a SHA-256 Checksum line. Agents echo it back; POST /api/install/verify validates. Catches LLM fabrications about which card was loaded. Does NOT enforce runtime behavior - that is the Policy Pack story.
• ✓Provenance Chain structural verification: three-step (publish / retrieval / install) chain with prev_hash linking + payload_sha256 hash-of-payload. POST /api/provenance/verify returns chainIntegrity (verified | broken | missing), stepsPresent, stepsVerified, and warnings. The chain LINKING is cryptographically verified; the chain IDENTITIES are not (see stubbed).

Exists in code; not yet functional in the way the spec describes.

• ~CLI install behavior: apai search/install/passport/audit/rollback commands exist but print placeholder output and do not yet fetch real packages
• ~Scanner: lib/scanner.ts checks suspicious patterns and hidden Unicode only; real prompt-injection, OAuth-scope, and dependency scanning lands in Phase 5
• ~Waitlist form: submits to /api/waitlist but persistence is in-memory only; Phase 4 adds Neon Postgres + Resend confirmation email
• ~Audit API: /api/audit/package returns the scanner stub findings; real audit pipeline lands in Phase 5
• ~Install preview / receipt API: /api/install/preview and /api/install/receipt return example payloads; real install flow lands in Phase 1
• ~Provenance Chain cryptographic signature verification: at v0.1 the ed25519 signatures embedded in each chain step are placeholder strings prefixed 'stub-ed25519:'. There is no key authority, no sigstore, no fulcio, no rekor, no publisher enrollment, no key rotation. The trustRoot literal everywhere is 'stub-v0.1-no-trust-root'. Chain LINKING is structurally verified; chain IDENTITIES are not. Real signing lands in v0.2.

Roadmap items. Not present in any form yet.

• ○User accounts, sessions, authentication, billing (Phase 4)
• ○Real CLI install behavior (Phase 1)
• ○Remote MCP gateway at mcp.apai.run (Phase 6)
• ○Private workspaces and approval queue (Phase 5)
• ○Publisher verification and package signing (Phase 6)
• ○Audit log export (Phase 5)
• ○Real prompt-injection, OAuth-scope, and dependency scanning (Phase 5)
• ○Multi-tenant database (Phase 4)
• ○Stripe billing integration (Phase 4)
• ○Workspace policies and runtime enforcement (Phase 5)
• ○Trademark clearance for APAI name (legal track, not engineering)