Architecture Decision Records

This folder captures why key technical decisions in cpp.js were made — the reasoning, the tradeoffs, and what alternatives were rejected. AI agents and human contributors should read the relevant ADR before changing the affected area.

ADRs are immutable. When a decision is overturned, write a new ADR that supersedes the old one (and update the old one's "Status" header to point at the supersession).

Index

#	Title	Status	Affects
0001	AI agents are first-class consumers of cpp.js	Accepted	Plugin, MCP, AGENTS.md, playbooks
0002	Use pnpm workspace dependencies for transitive C++ build order	Accepted	All cppjs-packages/*/*/package.json
0003	Allow env values in cppjs.config.js to be functions of (state, target)	Accepted	cppjs-core/cpp.js/src/state/, plugin authors
0004	Distribute agent integration in 3 layers: Claude Code plugin, MCP server, AGENTS.md snippet	Accepted	cppjs-agents/, cppjs-core/cppjs-mcp/, website/src/pages/agents.mdx
0005	Add platform: 'wasi' as a first-class build platform (wasm32-wasip3 command components)	Accepted	buildWasiCommand.js, -wasi/-bin-wasi packages, CI
0006	Bind plain Rust through a flat C ABI; the engine never depends on the binding layer	Accepted	cppjs-core-embind-rust/, rustBridgeGen.js, bundler plugins
0007	Prefix direct crate imports with cargo:	Accepted	getDependFilePath.js, bundler plugins, cargoDependencies
0008	Govern published binaries with a derived Bin & License Contract (K1-K4)	Accepted	cppjs-packages/README.md, buildBinTools.js, check-publish-hygiene.js

Writing a new ADR

1. Copy 0000-template.md to <next-number>-<kebab-title>.md.
2. Fill in Context (the forces at play), Decision (what we chose), Consequences (what this means going forward — both good and bad), and Alternatives considered (what we rejected and why).
3. Add a row to the index above.
4. Status starts as Proposed; flip to Accepted once merged. Use Superseded by ADR-NNNN if a newer ADR overturns it.

When to write one

You should write an ADR when:

• The decision will be load-bearing for many future changes (build order, plugin contract, runtime adapters).
• You picked option A over B+C and the next person will reasonably wonder why.
• The decision sets a constraint that's hard to undo (file layout, public API shape, dependency choice).

You don't need one for:

• Bug fixes (the commit message + linked issue is enough).
• Cosmetic refactors that preserve behavior.
• Code-level patterns already documented in AGENTS.md or per-package conventions.

Reference

ADR pattern from Michael Nygard's "Documenting Architecture Decisions". Format kept minimal — four sections, plain Markdown.