What problem does it solve? When proposing changes or reviewing code in the Envilder project, contributors often lack context on why specific tools, patterns, and infrastructure were chosen, leading to inconsistent decisions and repeated debates. ## Core Features & Use Cases - ADR Index: Provides a searchable table of ten Architecture Decision Records covering acceptance test infrastructure, test tooling per stack, SDK architecture patterns, code quality tooling, monorepo structure, and trunk-based development. - Quick Reference Tables: Summarizes test double patterns per stack (Vitest, NSubstitute, unittest.mock) and container testing packages for AWS LocalStack and Azure Lowkey Vault. - Decision Rules: Lists concrete checks to perform before adding testing tools, changing SDK public APIs, modifying formatters, or altering acceptance test infrastructure. - Use Case: Before proposing a new mocking library for the TypeScript SDK, consult ADR-0002 to confirm Vitest is the established choice and avoid re-litigating a settled decision. ## Quick Start Ask the AI to check the architecture decision records before proposing a new testing tool or SDK design change.