Repository navigation
Home
The GTS wiki explains how the product model becomes software structure. Start with the system architecture, then follow a bounded context or delivery concern into its detailed page.
GTS is a modular monolith with several Docker applications around one PostgreSQL database. Domain-driven design defines the language and bounded contexts. Hexagonal architecture separates ports from adapters. Onion architecture makes dependencies point towards the domain. A canonical relational model preserves ownership and consistency across HTTP requests and asynchronous work.
flowchart TB
Product["Product model<br/>DI track, signal chains and shootout"]
Contexts["Bounded contexts<br/>Core, Audio, T3K source and parked Video"]
Domain["Domain model<br/>aggregates, values, rules and ports"]
Applications["Applications<br/>web, synchronisation, orchestration and workers"]
Adapters["Adapters<br/>HTTP, PostgreSQL, pgmq, files and source APIs"]
Runtime["Runtime<br/>Docker Compose, nginx and Traefik"]
Product --> Contexts
Contexts --> Domain
Domain --> Applications
Applications --> Adapters
Adapters --> Runtime
- GTS-Technical-Architecture explains the system from product concepts to deployment.
- REFERENCE-ARCHITECTURE states the rules that implementation must satisfy.
- IMPLEMENTATION separates delivered capability from accepted target and parked work.
- Audio-Processing describes the Audio bounded context and its Core port.
- Frontend-Architecture describes the public Astro surface and authenticated React app.
- Jobs-Architecture-and-Operations describes pgmq, leases, finalisation and failure handling.
- GTS-Video-Architecture records the parked video boundary and its reopening conditions.
- SignalChainUIPlan describes the accepted signal-chain interface and current scaffold.
- static-typing describes the enforced Python and TypeScript type boundaries.
The repository ADRs hold decision history. The development guide holds commands and operator procedures.
The backend model, source synchronisation, audio processing, orchestration and manifest publication exist. The public comparison experience and authenticated app workflows remain in active development. Video composition is parked and has no deployed worker.