landscape/systems.md

Capability and system map

System / repository	Responsibilities	Data ownership	Deployment
Agile Dancers	Current school administration, import/export, scheduling and show planning	Owns its application PostgreSQL data	Existing frontend/backend application deployment; project-owned Compose configuration
landscape	ADRs, specifications, capability/system map, onboarding	Owns landscape documentation	Documentation repository; no application runtime
engineering	Shared engineering mechanisms, standards, skills, templates and generator	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.