oregor-projects/trinity-demo-java

This system is a Java-based microservice scaffolding tool, generated by PolyGenesis, designed to produce Spring Boot applications with REST APIs for domain features like task management. It provides a complete project structure including Maven build configuration, CI integration, and database persistence via Spring Data JPA and Flyway. The generated code includes API contracts, service implementations, and DTOs to handle standard CRUD operations for defined aggregates.

This change introduces the backend API layer for task management in the Java demo application. It adds request and response models (such as CreateTaskRequest, FetchTaskRequest, and ModifyTaskRequest) to the demo-api module, defining the data structures for task operations. In the demo-api-detail module, it implements the TaskService and TaskQueryService interfaces, providing the logic to create, modify, fetch, and list tasks with pagination support, along with a TaskConverter to map internal entities to collection records.

demo-api, demo-api-detail · high confidence

The project now includes a Maven Wrapper configuration file that specifies the use of Apache Maven version 3.5.4, ensuring consistent build environments across different setups.

.mvn · high confidence

The repository has been initialized with a Java-based project structure, including Maven wrapper scripts (mvnw, mvnw.cmd) for consistent builds, a .gitignore file tailored for Java IDEs (IntelliJ, Eclipse, NetBeans), and a Travis CI configuration (.travis.yml) to automate testing and deployment. A README.md provides instructions for building and running the demo microservice, and a prepare-to-commit.sh script enforces code formatting and license validation before commits.

(repo-wide) · high confidence

The demo-app now includes a Spring Boot application entry point that defaults the system timezone to UTC, along with environment-specific configuration profiles for development (MySQL) and CI (H2 in-memory). The setup includes Flyway for database migrations, JPA validation, and Actuator endpoints for health, info, and metrics, providing a foundational structure for task management features generated by PolyGenesis.

demo-app · high confidence

This change introduces the foundational scaffolding for a task management feature, generated by the PolyGenesis platform. It defines the core domain model with a Task aggregate root (including description and done status) and its persistence layer using Spring Data JPA and Hibernate, backed by Flyway database migrations that create the \dmo\_task\ and \dmo\_domain\_message\ tables. On the API side, it exposes a Spring REST controller (\TaskRestService\) under \/api/demo\ that supports creating, modifying, fetching, and listing tasks via standard HTTP methods, along with the necessary request/response DTOs and service interfaces.

(repo-wide) · high confidence

The repository is initialized with a multi-module Maven structure for the 'trinity-demo-java' application, based on Spring Boot 2.1.3. The build configuration defines modules for the main application, API contracts, domain logic, and auxiliary services, while establishing dependency management for Trinity4J libraries, Spring Boot starters, and data persistence tools like Spring Data JPA, Flyway, and QueryDSL.

(dependencies) · high confidence

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

• CAI 54 → 49 (-5.4)
• Rubric changed (rubric-2026.08.17 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 99 (-0.6)
• Architecture 100 (new)
• Maturity 72 → 57 (-15.3)
• Readiness 41 → 35 (-5.6)
• Security 100 → 78 (-22.2)
• Domain Modelling 48 → 48 (-0.0)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — no supported dependency manifest was read
• No exposed public API
• Test reliability not included
• change coupling unreadable for .java — no production change history could be paired for this repository's own source
• early-stage repository — too little history to judge knowledge freshness
• git history depth insufficient
• single-maintainer — knowledge-concentration (bus factor) risk

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (59 lines × 3) (demo-api/src/main/java/com/oregor/trinity/demo/java/task/CreateTaskRequest.java)
• No SBOM
• No build provenance
• No dependency advisory monitoring
• Scanner failed to run — not a clean result
• Scanner failed to run — not a clean result
• TodoComment (demo-domain-details/demo-domain-detail-repository-springdatajpa/src/test/java/com/oregor/trinity/demo/java/task/TaskPersistenceImplTest.java)

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

oregor-projects/trinity-demo-java 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.