Glossary

The delivery engine of this toolkit: ft-developer detects the repo and stack, grades the task (architecture-led vs TDD-led), delegates to the coding agents, and runs audit/review behind the same gates.

Per-repo inventory used to onboard the agents fast: a deterministic COMPONENT-MAP.md skeleton (modules, Spring beans, JPA entities, DB tables, Angular counts) plus an AI-authored COMPONENT-MAP.semantic.md layer. Both are CI-gated.

OMA device-management protocol over CoAP/DTLS for constrained IoT devices (v1.0–v2.0). A sibling to the BBF protocols; parameter paths are validated against the spec, like TR-* work.

SLF4J’s thread-local context map. FT deliberately does not use it — flows hop across thread pools, queues, and sessions, so MDC context silently vanishes mid-flow; ids are carried explicitly as key=value on the session/command object instead.

Vendor-neutral application-metrics facade (with Spring Boot Actuator), scraped by Prometheus. FT uses low-cardinality tags only — the serial belongs in logs, not metric tags.

Redux-style reactive state management for Angular. In FT it is the client-side cache: read from selectors, never re-fetch what the store can already answer.

Angular ChangeDetectionStrategy.OnPush — change detection runs only on input-reference change or an async pipe emission. The FT default for every component.

OpenAPI is the machine-readable description of a REST API; springdoc generates it (and Swagger UI) from Spring controllers via @Tag/@Operation/@Schema. It is the living contract for external APIs.

The internal UI↔BE wire style: POST /{controller}/{action} with the filter/id carried in the JSON body — not REST. Reads use POST; create/update use PUT. Distinct from the external REST surface.

Vector database that indexes a repo’s code (the ft_code collection) for deep semantic search by the agents; re-indexed on merge to main.

Writing and approving a one-page design before coding an architecture-led task — the counterpart to TDD for bounded work. The CTO signs off before implementation starts.

Library that starts real services (databases, brokers, protocol emulators) in Docker for integration tests (*IT). FT never mocks the DB.

BBF data model defining the parameter tree (Device.) managed over TR-069 / TR-369. Validate paths against the spec before writing code or tests.

BBF’s successor management protocol to TR-069 — multi-controller and transport-agnostic (MQTT / WebSocket / CoAP / STOMP).