Skip to main content

​
Context

Earlier repositories made dozens of framework design decisions: how definitions are declared, how bindings are keyed, how modules compose, how configuration is namespaced. Stackra’s framework packages do not exist yet. Copying those decisions as accepted ADRs would describe packages that are not built, and a standard for nothing teaches people standards are optional.

​
Decision

  1. No framework design ADR is written before its package lands. When a package is created, its design decision is written as its own ADR in the same change, and the package’s README.md links to it.
  2. Until then this page is a reading list, not a rule. The topics, and where the earlier thinking lives:
  3. Product compiler and definition-tier designs are out of scope for Stackra.

​
Consequences

  • The ADR index stays honest about what is built.
  • Writing a package’s ADR becomes part of creating the package.

​
Enforcement

Planned: the package scaffold (pnpm new package) prompts for the ADR link in the new package’s README.md; the architecture-guardian agent blocks a new framework package without one.

​
Supersedes and sources

Supersedes: none. Sources as listed in the table; the origin repositories are informational only.