Reacture/FoxOffice
60.0
Adequate · 8 November 2026
2.3k
lines of production code
C#
primary language
7
measurements over time
What this system is
Fox Office is a cinema management system that provides both a public-facing API and an administrative web interface for managing theaters, movies, and screenings. It utilizes an Azure-based infrastructure with a message bus and Cosmos DB for data persistence, supported by a .NET Core architecture that includes domain models, command handlers, and comprehensive unit testing.
Features
Initial release of the Fox Office cinema management system
The application is initialized with a complete set of core components. This includes the API controllers for managing theaters, movies, and screenings, alongside the domain models and command handlers that process these requests. The infrastructure layer is also introduced, featuring Azure-based message bus and Cosmos DB repositories for the read model, as well as an initializer that sets up the required storage queues and database collections on startup.
(repo-wide) · high confidence
Initial release of the FoxOffice.Admin application
The FoxOffice.Admin application is introduced, providing a web-based administrative interface for managing movies, theaters, and screenings. The update adds controllers and views for creating and listing movies, theaters, and screenings, along with the necessary view models and an API client to communicate with the backend services.
source/FoxOffice.Admin · high confidence
Behavioural changes
2 commits (0 fixes) modifying contents
A change to existing behaviour in contents — 2 commits, 3 files.
contents · medium confidence · unverified
Test coverage
Added unit tests for the FoxOffice admin and domain layers
Added comprehensive unit tests for the admin controllers (Movies, Theaters, Commands, and Queries), the ApiClient service, and the domain models (Movie, Theater, and their respective command handlers). These new tests verify controller actions return correct result types and models, ensure the API client correctly serializes commands and handles success/error responses, and confirm that domain aggregates raise the expected events and enforce validation rules.
source/FoxOffice.Tests · high confidence
Dependencies
Initial project structure and dependency configuration for FoxOffice
The FoxOffice solution is initialized with ten new .csproj files defining the build configuration for each project, including Admin, Api, Azure, Contracts, Domain, Modules, Processor, ReadModel, and the two test projects. These files establish the .NET Core 2.1 and .NET Standard 2.0 target frameworks and declare the initial set of NuGet package dependencies, such as Autofac, Khala libraries, StyleCop, and various Microsoft and third-party packages.
(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 53 → 60 (+7.0)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 74 → 74 (+0.0)
- Architecture 89 → 89 (+0.0)
- Maturity 75 → 78 (+2.9)
- Readiness 42 → 57 (+14.3)
- Security 62 → 71 (+9.3)
- Domain Modelling 60 → 60 (+0.0)
- Accessibility 63 → 64 (+0.9)
- Performance 60 → 60 (+0.0)
Resolved (9)
- Coverage not measured — no coverage collector is wired up
- Duplicate intent with confusing naming. 'AddNewScreening' and 'AddScreening' appear to be the same operation. 'AddNewScreening' omits the ScreeningId (likely server-generated), while 'AddScreening' requires it. This creates ambiguity about whether the client or server is responsible for ID generation, and the naming convention is inconsistent.
- Duplicate intent with confusing naming. 'CreateMovie' and 'CreateNewMovie' are semantically identical. 'CreateMovie' includes a MovieId, while 'CreateNewMovie' does not. This inconsistency suggests uncertainty about ID ownership and redundant types.
- Duplicate intent with confusing naming. 'CreateTheater' and 'CreateNewTheater' are semantically identical. 'CreateTheater' includes a TheaterId, while 'CreateNewTheater' does not. This inconsistency suggests uncertainty about ID ownership and redundant types.
- End-of-life runtime: .NET netcoreapp2.1 (source/FoxOffice.Tests/FoxOffice.Tests.csproj)
- Type duplication across namespaces. 'FoxOffice.Seat' and 'FoxOffice.ReadModel.Seat' have identical structures (Row, Column, IsReserved). This suggests a lack of clear separation between domain models and read models, or unnecessary duplication.
- Vulnerable: AutoMapper
- Vulnerable: Microsoft.AspNetCore.App
- Vulnerable: Microsoft.NETCore.App
New (4)
- End-of-life runtime: .NET netcoreapp2.1 (source/FoxOffice.Admin/FoxOffice.Admin.csproj)
- End-of-life runtime: .NET netcoreapp2.1 (source/FoxOffice.Api/FoxOffice.Api.csproj)
- End-of-life runtime: .NET netcoreapp2.1 (source/FoxOffice.Tests.Functional/FoxOffice.Tests.Functional.csproj)
- End-of-life runtime: .NET netcoreapp2.1 (source/FoxOffice.Tests/FoxOffice.Tests.csproj)
API surface
- Unchanged — 13 HTTP endpoints
Architecture
- Unchanged — 2 containers · 2 contexts · 1 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
Reacture/FoxOffice 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 872db55f323f7713b87d759bf1644a6ee8923a3b — 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.