WordloopLearn the Platform
Conceptual guides to Wordloop's architecture, services, and the vocabulary we use to talk about them.
Learn the Platform
This section is for understanding — the why and how behind Wordloop. It is not a tutorial (see Start Here) and it is not a reference (see Reference). It is the narrative layer that turns a repository of code into a system you can reason about.
What you will find here
Concepts
The vocabulary of Wordloop: Meetings, People, Transcriptions, Syntheses, Tasks, and the entities that carry them.
Architecture
System topology, data flow, authentication, workflows, and the infrastructure under them — visualised with C4 diagrams.
Services
Per-service handbooks: wordloop-core (Go API), wordloop-ml (Python AI runtime), wordloop-app (Next.js frontend).
How to read this section
Start with Concepts if the domain is new to you — understanding what a Meeting, Person, and MeetingSynthesis mean in code matters for every change downstream. Move to Architecture to see how services compose into a platform, then drop into a Service handbook when you need implementation-level depth.
If you want to know what we believe about building software at this scale and why, read Engineering Principles. If you want to do something, see Guides. If you want to look something up, see Reference.