# Changelog

## Score

- CAI 59 → 59 (+0.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 73 → 73 (+0.0)
- Architecture 95 → 94 (-1.8)
- Maturity 86 → 90 (+4.0)
- Readiness 33 → 33 (+0.0)
- Security 100 → 100 (+0.0)
- Domain Modelling 85 → 85 (+0.0)

## Resolved (11)

- Consequences/trade-offs are not visible before the clip marker cuts the body mid-solution list (docs/architecture-decisions/0007-api-first.md)
- Context and decision are both present but the body is clipped mid-sentence ('We can add custom features to Spring functionality when it's needed.') before any consequences/trade-offs or a review link appear (docs/architecture-decisions/0002-integration-events-implementation.md)
- Context is a bare 'The idea from CQRS - do not return anything from command processing. But in some cases...' with no problem statement and decision body identical (returns generated identifiers after processing) then clipped (docs/architecture-decisions/0008-result-from-comand-handlers.md)
- Context lists only the two alternatives (same model vs separate models) and decision restates CQRS without explaining why it is chosen over them or what trade-offs exist (docs/architecture-decisions/0003-cqrs.md)
- Context lists two alternatives but the decision is restated verbatim ('rich domain model solution will be used...') with no rationale or trade-offs (docs/architecture-decisions/0006-rich-domain-model.md)
- Decision is narrow and consequences/trade-offs are absent: only "Natural keys or uuids should be used. Primary keys are forbidden..." with no trade-off on identifier uniqueness across modules (docs/architecture-decisions/0005-identifier-between-modules.md)
- Decision is stated but context and consequences fall below the clip marker; no trade-offs or alternatives are mentioned (docs/architecture-decisions/0010-use-axon-framework.md)
- Decision is strong but the consequences section (coupling reduction) is couched in vague 'higher bounded contexts independence' without quantifying trade-offs such as latency and duplication (docs/architecture-decisions/0001-bounded-contexts-communication.md)
- No consequences/trade-offs section describing the cost of adopting Axon (e.g. learning curve, tooling) and benefits versus Spring-event (docs/architecture-decisions/0011-use-axon-event-publishing-mechanism.md)
- No consequences/trade-offs section describing what happens when the application moves away from Spring (e.g., loss of Spring-specific features) and how Quarkus integration is verified (docs/architecture-decisions/0012-make-application-framework-independent.md)
- No context/problem framing and no consequences/trade-offs section (docs/architecture-decisions/0004-validation.md)

## New (2)

- Outdated (compile): net.minidev:accessors-smart
- Outdated (compile): net.minidev:json-smart
