Skip to content

Release: v0.29.5

Choose a tag to compare

@shinpr shinpr released this 02 Nov 06:51
· 12 commits to main since this release
5f8b2ed

What's Changed

  • When requirements leave a quality level unset (performance, freshness, consistency, availability, or protection beyond the required trust boundary), design selects the lowest level that still delivers the outcome and records it. ADR and Design approval stops show these selected levels.
  • Each added design surface is kept only when removing it breaks a requirement, an accepted decision, or a repository rule or contract. Criteria the workflow wrote for itself are narrowed instead of justifying more mechanisms.
  • Designers fix review findings by removing or narrowing first, then reusing, and add mechanisms last.
  • Review findings always applied regardless of cost now cover exploitable trust-boundary gaps rather than any security concern.
  • implementation-approach no longer lists project, budget, market, and operational-procedure items that fall outside the repository change.