WordloopReference
Structured lookup surfaces — CLI flags, API contracts, database schema, configuration keys, error codes, and glossary.
Reference
Reference material is information-oriented: terse, complete, and predictable. If you are returning to Wordloop after a break and need to remember the exact ./dev flag, the JSON shape of an event, or what error code 4003 means — you are in the right section.
Contract surfaces
CLI
Every ./dev command in one table, with flags, defaults, and examples.
API
Core and ML HTTP APIs — OpenAPI-rendered, with live examples.
Events
WebSocket and Pub/Sub event schemas from our AsyncAPI specs.
Database
Schema, tables, columns, indexes, and foreign keys.
Configuration
Every environment variable, config key, and feature flag, organised by service.
Errors
Error codes with HTTP status, meaning, and operator action.
Glossary
The canonical definition for every domain term and acronym.
A note on sources of truth
Wherever possible, reference pages are generated from the same specs the code is generated from. The API reference is rendered directly from specs/*-openapi.json, the events reference from specs/*-asyncapi.yaml, and the database schema from the live migrations. If a reference page seems to drift from reality, the spec is the canonical source — open an issue, then fix the spec, and the page will follow.