Homer is a production-grade VoIP/SIP telemetry capture, storage, and analytics platform. It ingests HEPv3 packets over UDP/TCP/TLS/HTTP, plus OpenTelemetry traces/metrics/logs and InfluxDB line protocol, decodes SIP and RTCP/VQ-RTCPXR/SIPREC, and stores everything in a DuckDB/DuckLake lakehouse with Parquet files and a SQLite catalog. The system provides tiered hot/cold storage, compaction, retention, time-travel queries, Arrow FlightSQL access for Grafana/BI tools, a REST v4 API, a React dashboard, live WebSocket stream views, a CLI, and a Lua scripting engine for correlation. Although it is fundamentally an operational application, it contains a sophisticated data-lake/ETL layer, so it is hybrid in character; the dominant personality is an application service. The architecture is a modular Go monolith that can run as an all-in-one process or split into writer, node, and coordinator roles via configuration. Ingest listeners feed a zero-copy SIP/HEP decoder into batched DuckLake writers; background compaction and tiering move data across volumes; queries route through an Arrow FlightSQL server or the coordinator's search API. The embedded React/TypeScript UI is extensive, with dashboards, settings, user auth (internal, LDAP, OAuth2), alerting, and even isolated mini-games such as Chess, Tetris, and Doom. External dependencies include DuckDB and its DuckLake extension, S3/Azure object storage, LuaJIT, and optional log shipping to Loki/Elasticsearch. The codebase is well-tested and modular, with several genuinely reusable components such as a zero-copy SIP parser, a generic Go-Lua bridge, a pub/sub broker, and a CIDR-trie alias map. However, there is meaningful technical debt: hand-rolled SQL string interpolation, some duplicate CRUD patterns, a few known failing/skipped tests, pinned DuckDB extension versions, and scope creep from dashboard games. The project is actively developed and the drift is manageable rather than severe.