24 lines
1.9 KiB
Markdown
24 lines
1.9 KiB
Markdown
# Capability and system map
|
|
|
|
| System / repository | Responsibilities | Data ownership | Deployment |
|
|
| --- | --- | --- | --- |
|
|
| [Agile Dancers](http://192.168.2.28:3000/wanjakrah/agiledancers) | Current school administration, import/export, scheduling and show planning | Owns its application PostgreSQL data | Existing frontend/backend application deployment; project-owned Compose configuration |
|
|
| [Waterpolo Coaching](http://192.168.2.28:3000/wanjakrah/waterpolo-coaching) | Interactive visualization of waterpolo training and player positions | Owns its application state; no production data store documented yet | Local frontend/backend development; no production deployment configured |
|
|
| landscape | ADRs, specifications, capability/system map, onboarding and shared agent skills | Owns landscape documentation and agent workflows | Documentation repository; no application runtime |
|
|
| [engineering](http://192.168.2.28:3000/wanjakrah/engineering) | Shared build mechanisms, standards, templates and generator; shared runner setup | Owns versioned engineering source | Immutable versioned releases consumed by applications |
|
|
|
|
S19 separates engineering and governance repositories. It does not extract a
|
|
business capability or change runtime/data boundaries. Scheduling and school
|
|
administration remain candidates for future examination under ADR1. Any later
|
|
system extraction must specify contracts, enforced data ownership and failure
|
|
behavior before migration.
|
|
|
|
Waterpolo Coaching uses Three.js (https://threejs.org/) with TypeScript and Vite
|
|
instead of the Angular frontend used by Agile Dancers. Its npm lint, test, build
|
|
and container contracts still follow the common engineering recipe.
|
|
|
|
The physical mini-pc provides the shared host runner labelled `mini-pc`, registered
|
|
at Gitea user scope for `wanjakrah`. Existing and new repositories of that owner
|
|
use the same runner. Builds share one execution slot; deployment settings and
|
|
registry credentials remain project-owned.
|