Skip to content
CAI
Software that uses CAICheck a score

haxnted/pet-family-backend-new

51.7

Adequate · 8 November 2026

18.7k

lines of production code

C#

primary language

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is a .NET 10 microservices architecture for a PetFamily platform, centered around managing pet adoptions and user accounts. It provides core domain capabilities for handling species, pets, shelters, and volunteers, alongside user profile management. The infrastructure layer supports reliable messaging and observability, while the codebase enforces consistent coding standards and centralized dependency management.

Features

Adds shared domain, contracts, and infrastructure monitoring configurations

This update introduces the core shared kernel for the PetFamily microservices architecture. It adds the \PetFamily.SharedKernel.Domain\ layer with a structured \Error\ and \ErrorType\ system for consistent error handling, alongside custom exceptions like \DomainException\, \EntityNotFoundException\, \ForbiddenException\, and \UseCaseException\. The \PetFamily.SharedKernel.Contracts\ layer is introduced, defining integration events (e.g., \UserCreatedEvent\, \UserDeletedEvent\) and MassTransit commands for the pet adoption saga (e.g., \StartPetAdoption\, \ReservePet\). Additionally, infrastructure configuration files are added for observability and monitoring: OpenTelemetry settings, Prometheus scrape configs for all services, Grafana dashboard definitions for ASP.NET Core, PostgreSQL, RabbitMQ, and Redis, as well as Kibana and RabbitMQ plugin configurations.

Shared · high confidence

Introduce account profile management with read/write capabilities

Users can now create, update, and retrieve their account profiles. This change adds the domain model for the Account aggregate (including phone number, age experience, description, and photo), along with the application layer commands and handlers for creating an account, updating profile details, and updating a profile photo. The infrastructure layer provides the database context, entity configuration, and migrations for the Accounts table, while also integrating MassTransit outbox/inbox state tables for reliable messaging. Caching is introduced to store account data by user ID for 5 minutes, and dependency injection is configured for the repository and service layers.

Solution · high confidence

Behavioural changes

Added project-wide code style and build configuration

The repository now enforces consistent C\# code formatting and style through a new .editorconfig file, which defines rules for blank lines, brace placement, 'var' usage, and indentation. Additionally, a Directory.Build.props file has been added to set the default .NET 10.0 target framework, enable implicit usings and nullable reference types, and integrate StyleCop.Analyzers for static code analysis. A stylecop.json configuration file is also included to customize analyzer behavior.

(repo-wide) · high confidence

Test coverage

Added integration tests for domain handlers

Added integration tests for the following domain handlers: Species, Pet, Shelter, and Volunteer. These new test files verify the correct behavior of command and query handlers for managing species, pets, shelters, and volunteers, including operations like adding, updating, deleting, and querying these entities.

(repo-wide) · high confidence

Dependencies

Centralized package version management and .NET 10.0 upgrade

The project has adopted centralized package version management via a new Directory.Packages.props file, which defines versions for all dependencies including OpenTelemetry, Ocelot, MassTransit, and various Microsoft libraries. Additionally, all .csproj files in the solution have been updated to target the net10.0 framework, standardizing the runtime version across the microservices and shared kernels.

(dependencies) · high confidence

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 52 → 52 (-0.6)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 89 → 89 (-0.0)
  • Architecture 85 → 85 (+0.0)
  • Maturity 64 → 70 (+6.5)
  • Readiness 53 → 53 (+0.0)
  • Security 43 → 41 (-2.4)
  • Domain Modelling 67 → 71 (+3.4)
  • Event-Driven 80 → 77 (-2.9)
  • Performance 60 → 60 (-0.5)

Resolved (47)

  • Duplicate event types with identical structure and intent. Both events carry a FileId and BucketName, suggesting they represent the same domain concept (a request to delete a file/photo) but are split into two distinct types without clear differentiation in the signature.
  • Inconsistent event naming and lifecycle representation. CreateAdoptionChat appears to be a command/intent (contains AdopterName, PetNickName), while AdoptionChatCreated and AdoptionChatCreationFailed are outcomes. However, AdoptionChatCreated lacks the ChatId in its signature (only has CorrelationId, ChatId, PetId), whereas CreateAdoptionChat does not have a ChatId. More critically, AdoptionChatCreated has a ChatId property, but CreateAdoptionChat does not, which is correct for command vs event, but the naming convention mixes 'Action' (Create) with 'State Change' (Created). A more consistent pattern would be AdoptionChatRequested (command) vs AdoptionChatCreated (event). The current mix of Create... (command-like) and AdoptionChat... (event-like) is slightly inconsistent with other pairs like ReservePet/PetReserved.
  • XML-doc coverage: Account.Domain (Solution/Account/Account.Domain/Account.Domain.csproj)
  • XML-doc coverage: Account.Handlers (Solution/Account/Application/Account.Handlers/Account.Handlers.csproj)
  • XML-doc coverage: Account.Hosts.Consumers (Solution/Account/Hosts/Account.Hosts.Consumers/Account.Hosts.Consumers.csproj)
  • XML-doc coverage: Account.Hosts.DI (Solution/Account/Hosts/Account.Hosts.DI/Account.Hosts.DI.csproj)
  • XML-doc coverage: Account.Hosts.Endpoints (Solution/Account/Hosts/Account.Hosts.Endpoints/Account.Hosts.Endpoints.csproj)
  • XML-doc coverage: Account.Infrastructure (Solution/Account/Account.Infrastructure/Account.Infrastructure.csproj)
  • XML-doc coverage: Account.Services (Solution/Account/Application/Account.Services/Account.Services.csproj)
  • XML-doc coverage: ApiGateway (Solution/ApiGateway/ApiGateway/ApiGateway.csproj)
  • XML-doc coverage: Auth.Application (Solution/Auth/Auth.Application/Auth.Application.csproj)
  • XML-doc coverage: Auth.Contracts (Solution/Auth/Auth.Contracts/Auth.Contracts.csproj)
  • XML-doc coverage: Auth.Core (Solution/Auth/Auth.Core/Auth.Core.csproj)
  • XML-doc coverage: Auth.Endpoints (Solution/Auth/Hosts/Auth.Endpoints/Auth.Endpoints.csproj)
  • XML-doc coverage: Auth.Infrastructure (Solution/Auth/Auth.Infrastructure/Auth.Infrastructure.csproj)
  • XML-doc coverage: Conversation.Domain (Solution/Conversation/Conversation.Domain/Conversation.Domain.csproj)
  • XML-doc coverage: Conversation.Handlers (Solution/Conversation/Application/Conversation.Handlers/Conversation.Handlers.csproj)
  • XML-doc coverage: Conversation.Hosts.Consumers (Solution/Conversation/Hosts/Conversation.Hosts.Consumers/Conversation.Hosts.Consumers.csproj)
  • XML-doc coverage: Conversation.Hosts.DI (Solution/Conversation/Hosts/Conversation.Hosts.DI/Conversation.Hosts.DI.csproj)
  • XML-doc coverage: Conversation.Hosts.Endpoints (Solution/Conversation/Hosts/Conversation.Hosts.Endpoints/Conversation.Hosts.Endpoints.csproj)
  • …and 27 more

New (5)

  • doc comments repeat the names (Shared/PetFamily.SharedKernel.WebApi/Extensions/OpenTelemetryExtensions.cs)
  • doc comments repeat the names (Solution/Auth/Auth.Application/Services/IAuthService.cs)
  • doc comments repeat the names (Solution/Auth/Auth.Infrastructure/Services/Keycloak/IKeycloakAuthorizationClient.cs)
  • doc comments repeat the names (Solution/Notification/Notification.Infrastructure/BackgroundJobs/NotificationLogCleanupService.cs)
  • doc comments repeat the names (Solution/VolunteerManagement/VolunteerManagement.Infrastructure/Common/Contexts/VolunteerManagementDbContextFactory.cs)

API surface

  • Unchanged — 64 HTTP endpoints

Architecture

  • Unchanged — 16 containers · 4 contexts · 3 edges

Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

haxnted/pet-family-backend-new was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 8 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit 4aa0c08333341074d10cec92b34f6252ae2aedfc — the exact code this score is about.
  • Scored under rubric-2026.11.2 — the same rubric and the same method as every other entry in this index.
  • Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.3+preprod-45ab2cab63de.