Files
docs/index.md
T
julian 22b1b069df Bootstrap LLM-maintained wiki with TRM architecture knowledge
Initialize CLAUDE.md schema, index, and log; ingest three architecture
sources (system overview, Teltonika ingestion design, official Teltonika
data-sending protocols) into 7 entity pages, 8 concept pages, and 3
source pages with wikilink cross-references.
2026-04-30 13:20:17 +02:00

2.3 KiB

Index

Content catalog for the TRM wiki. Maintained by the LLM on every ingest. See CLAUDE for schema and conventions.

Sources

Entities

  • directus — Business plane: schema owner, REST/GraphQL/WSS, admin UI, permissions, Flows.
  • postgres-timescaledb — Durable storage: positions hypertable + business schema. The system's only single point of failure.
  • processor — Domain-logic service consuming Redis Streams; per-device hot state in memory; sole writer for telemetry tables.
  • react-spa — End-user UI; talks exclusively to Directus; role-based views in a single bundle.
  • redis-streams — Durable in-flight queue between Ingestion and Processor; Phase 2 transport for outbound commands.
  • tcp-ingestion — Per-vendor TCP listener service; parses binary protocols and emits normalized records.
  • teltonika — GPS hardware vendor; Codec 8/8E/16 telemetry today, Codec 12/14 commands deferred (13/15 one-way, 15 out of scope).

Concepts

  • avl-data-format — Canonical Teltonika packet structure: envelope, AVL record, GPS element, IO element layouts per codec.
  • codec-dispatch — Flat registry keyed on codec ID; the seam that makes Phase 2 additive.
  • failure-domains — Independent component failure behavior; database is the only SPOF.
  • io-element-bag — The pass-through principle for model-specific telemetry inside AVL records.
  • phase-2-commands — Deferred design for server-to-device commands via Teltonika codecs 12/14.
  • plane-separation — Three-plane architecture (telemetry / business / presentation) split by data velocity and failure domain.
  • position-record — Boundary contract between vendor adapters and the rest of the system.
  • protocol-adapter — Vendor-abstraction interface (bytes in → normalized Position out) at the Ingestion layer.

Synthesis

None yet.