# Changelog

## Score

- CAI 47 → 48 (+0.9)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

## Lenses

- Code Health 82 → 82 (+0.0)
- Architecture 64 → 64 (+0.0)
- Maturity 66 → 69 (+3.2)
- Readiness 49 → 49 (+0.0)
- Security 34 → 34 (+0.0)
- Event-Driven 77 → 100 (+22.7)
- Performance 70 → 77 (+6.8)

## Resolved (62)

- Change coupling: Contract.cs ↔ TerminationIsPossibleOnlyAfterThreeMonthsHavePassedRule.cs (Chapter-4-applying-tactical-domain-driven-design/Fitnet.Contracts/Src/Fitnet.Contracts.Core/Contract.cs)
- Checkable ADR rule enforced only by prose: 0003-use-modules (Chapter-1-initial-architecture/Docs/ArchitectureDecisionLog/0003-use-modules.adoc)
- Decision is generic ('We decided to use Docker') with no context (why not a different container platform) or trade-offs beyond the listed consequences (Chapter-1-initial-architecture/Docs/ArchitectureDecisionLog/0006-use-docker.adoc)
- Duplicate command definitions. The `PrepareContractCommand` appears twice with identical signatures in the provided list (likely from different namespaces or versions in the dump). While not a runtime conflict, it pollutes the API surface.
- Duplicate domain method signatures with different parameters. One takes raw `DateTimeOffset` values, the other takes a `Signature` value object. This suggests the domain model has evolved or has two different ways to sign a contract.
- Duplicate interface definitions with conflicting return types for the same method signature. One version of `IContractsModule` returns `Task` (void-like), while the other returns `Task<ErrorOr<Unit>>`. This indicates two different versions of the interface or a copy-paste error in the API surface.
- Duplicate registration methods with inconsistent signatures. One takes a 'module' string parameter, the other does not. It is unclear if these are for different layers (API vs Internal) or if one is legacy.
- Duplicate service registration methods. `AddContracts` includes a `module` string parameter which is absent in `AddContractsApi`. This suggests confusion between registering the core application logic versus just the API endpoints.
- Inconsistent return types for equivalent operations. `IContractsRepository.GetByIdAsync` returns `Task<Contract?>` (nullable reference), while `IBindingContractsRepository.GetByIdAsync` returns `Task<ErrorOr<BindingContract>>` (Result pattern). This forces consumers to handle null checks in one case and error unwrapping in the other.
- No context/problem and no consequences for not recording decisions (e.g. lost change drift or lack of audit trail) are mentioned (Chapter-1-initial-architecture/Docs/ArchitectureDecisionLog/0001-record-architecture-decisions.adoc)
- The namespace for the IBusinessRule interface is spelled 'BussinessRules' (missing 'i') in one location and 'BusinessRulesEngine' in another. While the interface name is consistent, the namespace spelling inconsistency suggests a copy-paste error or lack of standardization in the namespace structure for business rules.
- XML-doc coverage: Fitnet (Chapter-1-initial-architecture/Src/Fitnet/Fitnet.csproj)
- XML-doc coverage: Fitnet (Chapter-2-modules-separation/Src/Fitnet/Fitnet.csproj)
- XML-doc coverage: Fitnet (Chapter-3-microservice-extraction/Fitnet/Src/Fitnet/Fitnet.csproj)
- XML-doc coverage: Fitnet (Chapter-4-applying-tactical-domain-driven-design/Fitnet/Src/Fitnet/Fitnet.csproj)
- XML-doc coverage: Fitnet.Common.Api (Chapter-2-modules-separation/Src/Common/Fitnet.Common.Api/Fitnet.Common.Api.csproj)
- XML-doc coverage: Fitnet.Common.Api (Chapter-3-microservice-extraction/Fitnet.Common/Fitnet.Common.Api/Fitnet.Common.Api.csproj)
- XML-doc coverage: Fitnet.Common.Api (Chapter-4-applying-tactical-domain-driven-design/Fitnet.Common/Fitnet.Common.Api/Fitnet.Common.Api.csproj)
- XML-doc coverage: Fitnet.Common.Core (Chapter-2-modules-separation/Src/Common/Fitnet.Common.Core/Fitnet.Common.Core.csproj)
- XML-doc coverage: Fitnet.Common.Core (Chapter-3-microservice-extraction/Fitnet.Common/Fitnet.Common.Core/Fitnet.Common.Core.csproj)
- …and 42 more

## API surface

- Unchanged — 1 HTTP endpoints

## Architecture

- Unchanged — 9 containers · 3 contexts · 3 edges
