Glossary

The authoritative vocabulary of Wordloop. When code, docs, or conversation refers to one of these terms, this page is what the term means. The domain-level concepts also appear in Learn / Concepts, where they are explained with more narrative context.

A

ADR — Architecture Decision Record. An append-only document capturing a significant, hard-to-reverse decision, with explicit debt annotations. See Decisions.

Adapter. A component that implements a port, bridging the domain to an external dependency (database, message broker, HTTP framework). Part of the hexagonal architecture vocabulary.

AsyncAPI. The machine-readable specification format we use to document event streams — the asynchronous counterpart to OpenAPI. See Core Events Reference.

B

Backpressure. The explicit control signal by which a producer is slowed when a consumer cannot keep up. In Wordloop, backpressure is designed into every real-time flow — we shed, coalesce, or block rather than buffering unbounded. See Real-Time.

C

Canary. A release shape where a small fraction of traffic reaches a new revision before it is promoted to 100%. See Progressive Delivery.

Clerk. The third-party authentication provider we use for user identity. JWTs from Clerk are verified by wordloop-core on every request.

Core (wordloop-core). The Go HTTP and WebSocket API that is the source of truth for Meetings, People, Transcriptions, Tasks, and real-time session state.

D

DORA metrics. Deployment frequency, lead time for changes, change failure rate, and mean time to recover — the four research-backed metrics we use to measure delivery performance. See DevEx.

E

Error budget. The quantity of "bad" events allowed by an SLO over a rolling window. Consumed by outages; restored by uptime. See Reliability.

Eval. A scored comparison of model output against a reference. We run evals in CI to catch regressions in AI-driven behaviour. See AI Engineering.

H

Hexagonal architecture. The structural pattern — domain core, ports, adapters — that every non-trivial Wordloop service follows. See Hexagonal Architecture.

I

Idempotency key. A client-supplied identifier that lets the server recognise and safely handle retried writes. Every write endpoint in Wordloop accepts one. See API Design.

IDP — Internal Developer Platform. The set of shared tooling, runtimes, and golden paths engineers use to build on Wordloop. See Platform.

J

JIT — Just-in-Time provisioning. The pattern by which Wordloop creates a local User and Person record the first time a user signs in via Clerk. No webhooks, no seeding. See Quickstart.

L

llms.txt. The machine-readable index of a documentation site, consumed by AI agents. See /llms.txt and Agent-Native Systems.

M

MCP — Model Context Protocol. The interoperable protocol we use to expose tools and resources to AI agents. See Agent-Native Systems.

Meeting. The primary entity in Wordloop — a bounded session that is captured in the system, attended by People, and producing a Transcription, a MeetingSynthesis, and Tasks. The meetings table and /meetings routes are the centre of the domain.

MeetingSynthesis. The AI-generated summary attached to a Meeting. Contains a headline, prose summary, key points, Topics, and TalkingPoints. Produced by the ML service after the Transcription finalises.

ML (wordloop-ml). The Python FastAPI runtime responsible for transcription, synthesis generation, and embedding.

N

Note. A free-form annotation attached to any entity via a polymorphic subject_type / subject_id pair.

O

OpenAPI. The machine-readable specification format we use to document HTTP APIs. Our server handlers and clients are generated from it. See API Design.

OTel — OpenTelemetry. The vendor-neutral observability framework we use for traces, metrics, and logs. See Observability.

Outbox pattern. The transactional pattern by which a database write and an event emission are committed together, via an outbox table. See Integration Patterns.

P

Person. A contact record representing someone who appeared in a Meeting, with or without a Wordloop account. Carries identity fields and an optional voice model for speaker attribution.

pgvector. The Postgres extension we use as our production vector store. See Postgres.

Port. An interface declared by the domain describing a capability it needs, implemented by an adapter. Part of the hexagonal architecture vocabulary.

R

RAG — Retrieval-Augmented Generation. The pattern of enriching a model call with retrieved context from our own data. See AI Engineering.

Runbook. A step-by-step recovery procedure for a known failure mode. See Operations / Runbooks.

S

SLO — Service Level Objective. A per-journey target for latency and success rate, measured over a rolling window. The foundation of Reliability.

T

Tag. A user-defined label applied to Meetings, People, or Tasks for organisation.

TalkingPoint. A specific point or claim within a Topic, surfaced as a bullet in the MeetingSynthesis view.

Task. An action item extracted from a Meeting. Tasks are assignable, hierarchical, and tracked through to completion. Statuses: pending, in_progress, completed, canceled.

Topic. A thematic cluster extracted from a Meeting's TranscriptSegments, carrying a name, summary, and the contributing segments.

Transcription. The speech-to-text record attached to a Meeting, aggregating TranscriptSegments as they arrive from the ML service.

TranscriptSegment. The atomic unit of a Transcription — one speaker turn, carrying speaker label, attributed Person, text, timestamps, confidence score, and a is_final flag.

U

User. A Wordloop account holder, identified via Clerk and JIT-provisioned on first sign-in. Each User has an associated Person record.

V

Voice model. The speaker-identification vector attached to a Person, built from verified TranscriptSegments and used to attribute future segments to a specific Person.

W

WebSocket. The default transport for real-time streams in Wordloop. See Real-Time.