What is JoinedWorkz?
JoinedWorkz is a model-driven engineering platform. You describe a system in the Canonical Model Notation (CMN), select a target platform and let reusable Facilities transform that model into implementation artifacts.
The canonical model can describe domain types, APIs, components, persistence and user-interface structure. Depending on the selected Facility, JoinedWorkz can derive OpenAPI documents, diagrams, Java types, Spring Boot APIs and persistence code, Flyway migrations, or experimental Quasar frontend fragments from that shared source.
How generation works
CMN model -> platform -> cartridges -> generators -> outlets- A platform selects the generation behavior for a model.
- A Facility packages platforms, profiles, cartridges and reusable model definitions.
- A cartridge applies one area of generation, such as OpenAPI, persistence or frontend output.
- An outlet routes generated artifacts into the appropriate directory or Maven module.
CMN models and project configuration remain authoritative input. Generated files have explicit ownership rules: some output is replaceable, some is created only once and then becomes manual source, and versioned schema migration history must be preserved.
Product components
- CMN language — the canonical, mostly platform-independent system model.
- JoinedWorkz Studio — an interactive editor with syntax support and model diagnostics.
- Maven plugin — build-time model loading, validation, transformation and generation.
- Facilities — reusable generation capabilities for Base, Java and Spring Boot, plus experimental Quasar support.
JoinedWorkz is not an application runtime and does not replace every manual integration task. A runnable application can still require a project-owned application shell, dependencies, runtime configuration and handwritten business logic. The selected Facility defines that boundary.