Architecture Constraints

Constraint	Source	Architectural consequence	Negotiable
Node.js 22 or newer; ESM TypeScript monorepo	Root package.json, workspace configuration	Packages target a shared Node runtime and use pnpm workspaces	Runtime baseline changes require a deliberate compatibility decision
Product definition is authored in repository files	CON-MARKDOWN-001	No external system of record; outputs are rebuildable from authored files	No
No hosted product authoring or approval UI	CON-NO-WEB-UI	Public HTML is informational or a generated read-only projection; changes remain in files, CLI and review	No
Public framework content must not reveal private product information	CON-PUBLIC-GENERIC	Examples and adoption learnings must be generic or sanitized	No
Keep the deterministic core independent of providers	ADR 0007 and package boundaries	Provider behavior belongs in integration packages; core has no AI provider dependency	No
Avoid architectural weight that is not needed by a repository-first CLI	Documented limitations and architecture decisions	No web framework or graph database in the CLI runtime; public pages are generated as static files	Revisit only with an explicit architecture decision

The authoritative runtime and development dependency declarations live in the root and package package.json files; this view records the architectural constraint rather than duplicating their evolving inventory.