Skip to content
CAI
Software that uses CAICheck a score

Ahoo-Wang/wow-project-template

66.3

Adequate · 9 November 2026

1.2k

lines of production code

TypeScript

with Kotlin

7

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

Features

Added use case diagram for DemoService

The documentation now includes a new use case diagram illustrating the interactions between the User actor and the DemoService, specifically detailing the CreateDemo and UpdateDemo use cases. This visual aid is provided in both PlantUML source format and a rendered SVG image to help users understand the system's functional scope.

document · high confidence

Generated client code for the Demo bounded context

The client now includes auto-generated TypeScript code for the 'demo' bounded context, providing type-safe access to its API. This adds a \DemoCommandClient\ for executing commands (create, update, delete, recover, and apply resource tags) and a \demoQueryClientFactory\ for querying aggregate state and handling domain events. The generated types define the \DemoState\, command bodies (\CreateDemo\, \UpdateDemo\), and event interfaces (\DemoCreated\, \DemoUpdated\), exposing endpoints under \/tenant/{tenantId}/demo\.

client/src · high confidence

Initial client library setup with Vite build and fetcher dependencies

The client directory has been initialized as a TypeScript library project. It uses Vite for building, configured to bundle the library entry point while externalizing the \@ahoo-wang/fetcher\ family of packages (fetcher, decorator, eventstream, cosec, wow) to be provided at runtime. The project includes ESLint configuration for TypeScript, a tsconfig targeting ES2020, and a .gitignore file. Documentation is provided in the README for generating client code from OpenAPI specs and building the library.

client · high confidence

Initial project template scaffolding with documentation and tooling

The repository is initialized as a Wow framework microservice template implementing DDD, Event Sourcing, and CQRS. This entry establishes the foundational project structure and tooling: it adds the Gradle wrapper scripts (gradlew, gradlew.bat) and configuration (.gitattributes) for consistent builds, introduces .editorconfig to enforce Kotlin coding standards (trailing commas, import-on-demand rules), and sets up Renovate (renovate.json) to manage dependency updates with specific groupings for Spring and Kotlin/KSP ecosystems. It also includes comprehensive documentation in README.md (module descriptions, usage guides, CI/CD steps) and CLAUDE.md (AI assistant guidance, build commands, architecture patterns), alongside an updated .gitignore to exclude build artifacts and IDE files.

(repo-wide) · high confidence

Initial server application and demo projector setup

The server module now includes a Spring Boot application entry point (Server.kt) that scans the demo bounded context, and a DemoProjector that logs incoming DemoCreated events.

server/src/main/kotlin · high confidence

Introduce demo and review domain models with HTTP command routing

The API layer now defines the core domain contracts for a demo-and-review workflow. It registers the \demo-service\ bounded context with \DemoService.kt\, exposing \CreateDemo\ and \UpdateDemo\ commands via HTTP POST routes, while \PublishDemo\ and \RejectDemo\ are kept internal (HTTP routes disabled). A \DemoView\ query model implements \IDemoState\ to expose demo state (id, data, status) to callers. The review side adds \CreateReview\ (internal), \ApproveReview\, and \RejectReview\ commands with specific HTTP actions, along with \ReviewStatus\ and \DemoStatus\ enums. Tests verify that \DemoView\ correctly implements the \IDemoState\ contract.

api · high confidence

Introduces Demo domain with review workflow and saga orchestration

The domain module now includes the core domain model for the Demo bounded context, featuring the Demo aggregate root (handling creation, updates, publishing, and rejection) and its state management via event sourcing. It also introduces a Review aggregate to manage the approval lifecycle and a DemoReviewSaga that orchestrates the cross-aggregate workflow: automatically creating a review upon demo creation, and triggering publish or reject commands on the Demo aggregate based on the review outcome. Additionally, a BoundedContext annotation is registered to support framework metadata resolution and component scanning.

domain · high confidence

New type-safe API client and standardized build conventions

This change introduces a new type-safe client, DemoClient, for the DemoService, allowing other services to interact with the API contract without depending on the underlying infrastructure. It also establishes a comprehensive set of Gradle build conventions in the build-logic module, standardizing Kotlin compilation (JVM 17), static analysis with Detekt, code coverage reporting via Kover, and Maven publishing with signing support for CI environments.

api-client, build-logic · high confidence

Test coverage

Added basic server integration test

A new \ServerTest\ class has been added to verify that the Spring Boot application context loads successfully, ensuring the server's core dependencies and configuration are valid at startup.

server/src/test · high confidence

Dependencies

Gradle wrapper updated to version 9.7.1

The Gradle wrapper configuration has been updated to use Gradle version 9.7.1. This ensures that builds will consistently use this specific version of the Gradle build tool, downloaded from the official distribution URL, providing a stable and reproducible build environment.

gradle · high confidence

Initial dependency management and module scaffolding

The project introduces a centralized dependency management strategy by adding a BOM module and a new API module. The API module (\api/build.gradle.kts\) declares its dependencies against a shared platform (\:dependencies\), integrating core libraries such as \wow-api\, \wow-apiclient\, \coapi-api\, and \swagger-annotations\, while also configuring the KSP plugin for code generation. This establishes the foundational build structure and dependency graph for the application.

(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 68 → 66 (-1.8)
  • Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.

Lenses

  • Code Health 100 → 100 (+0.0)
  • Architecture 65 → 65 (+0.0)
  • Maturity 67 → 74 (+7.5)
  • Readiness 66 → 66 (+0.0)
  • Security 69 → 61 (-7.7)
  • Domain Modelling 100 → 100 (+0.0)

New (2)

  • Medium CVE: [GHSA redacted] (client/pnpm-lock.yaml)
  • Medium CVE: [GHSA redacted] (client/pnpm-lock.yaml)

Changes since last survey

  • 9 commits — 0 feature/other, 9 fixes

By area

  • .github/workflows — 3 commits
  • gradle/libs.versions.toml — 3 commits
  • client/package.json — 2 commits
  • gradle/wrapper — 1 commit

Notable commits

  • fix: fix(deps) Update Gradle to v9.8.2 (#1245)
  • fix: fix(deps) Update com.google.devtools.ksp:symbol-processing-gradle-plugin to v2.3.13 (#1253)
  • fix: fix(deps) Update eslint to ^10.13.0 (#1248)
  • fix: fix(deps) Update me.ahoo.cosec:cosec-bom to v6.1.2 (#1235)
  • fix: fix(deps) Update node to v24.22.2 (#1250)
  • fix: fix(deps) Update org.springframework.boot:spring-boot-dependencies to v4.1.2 (#1249)
  • fix: fix(deps) Update renovatebot/github-action action to v46.3.12 (#1254)
  • fix: fix(deps) Update renovatebot/github-action action to v46.3.9 (#1246)
  • fix: fix(deps) Update vite to v8.3.5 (#1247)

Architecture

  • Unchanged — 0 containers · 1 contexts · 0 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

Ahoo-Wang/wow-project-template 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 9 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 e91ffd055374da669930e04925f6b16d1ea498be — 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-bb0cb800cd0f.