PMFKit v1 Architecture
Documentation for production-ready v1: system architecture, agent contracts, evidence taxonomy, reasoning standards, and scope.
| Document | Purpose |
|---|---|
| agents-overview.md | What agents are; intern vs report agents; index to interns and report-agents |
| crawlers.md | Intern agents in technical detail (Discovery, Product, UI Capture, Competitor, pricing pass) |
| report-agents.md | Report agents in technical detail (CMO, BD, COO, CDO) |
| background-flow.md | End-to-end background flow (crawl → evidence → reports), entry points, step order, Evidence Layer in detail |
| system-architecture.md | High-level flow, Evidence Layer, orchestration, single entry, dependency map |
| agent-contracts.md | Input/output schemas per agent, versioning, shared artifact; no re-crawl/re-interpret |
| evidence-taxonomy.md | Categories (Product Surface, Documentation, Pricing, etc.), storage, tagging, traceability |
| reasoning-standards.md | Evidence → Inference → Judgment; claim types; no undocumented logic |
| pmf-stage-definition.md | Official PMF stages (0–5 / Idea Validation → Growth), mapping to DRL and UI |
| release-scope.md | What is in v1 and what is explicitly out |
| post-v1-roadmap.md | Phase 2–4 expansion (no implementation in v1) |
| output-narrative.md | CMO: recommendation templates, one thing this week, narrative alignment |
| diagnostic-examples.md | CMO: 5 real startup URLs and coherent-output criteria for release |
Rule: If it’s not documented, it doesn’t exist.
Documentation maintenance and versioning
Before merging a release to main: Add or update the release report for that version (docs/vX.Y/release-report.md) with what shipped, then merge.
When you launch a new version and change behavior:
- Update the relevant architecture doc pages (e.g. new intern or report step → crawlers.md or report-agents.md).
- If I/O or contracts change, update agent-contracts.md and bump
AGENT_CONTRACT_VERSIONincore/agents/types.ts. - Add an entry to the project changelog or release changelog (e.g. docs/v1.9/changelog.md).
- If entry points or pipeline order change, update background-flow.md.
Optional: add a "Last updated" or "Doc version" line at the top of changed docs for credibility and tracking.