stdio-only transport — index.ts uses StdioServerTransport. Cannot be called remotely by Claude, ChatGPT, or any external AI agent. The MVP requires an HTTP endpoint (SSE or Streamable HTTP).
Manifest-server contradiction — manifest-generator.ts advertises protocol: 'streamable-http' but the server is stdio. The manifest lies.
Gateway is a stub — gateway.ts is 10 lines of placeholder comments. No actual multi-tenant routing.
Schema is incomplete — schema.ts has a single businesses table with no tenant/location model, no freshness/telemetry fields, no badge state, no portal data. Doesn't support the strategy.
No polling, no freshness, no assessment — None of the critical Day 2-N mechanics from the strategy (polling, content hashing, JIT refresh, assessment gates, badge ladder) are implemented.
No downstream handoff — Cal.com/Stripe/Square integration is a config string, not real integration.
No HTTP server — fastify is in package.json but never wired up. No routes, no transport, no deployment target.

What replaced it

The strategy and product design live in docs/:

docs/strategy/CANONICAL_STRATEGY.md — Operating strategy
docs/product/ — Use cases, SSP spec, genre packs
docs/engineering/technical-roadmap.md — Technical architecture
docs/gtm/ — GTM, ICP, competitive analysis

Future engineering code will live in apps/ (per the monorepo structure) with proper HTTP MCP transport, multi-tenant gateway, polling infrastructure, and portal.

Action

This directory is preserved for reference only. Do not extend it. Future work happens in apps/.