Groening: Portland Open-Data Explorer
Groening is a Portland port of Elvis: the same architecture, a DuckDB warehouse modeled with dbt, aimed at free public data for the Portland metro across Multnomah, Washington, and Clackamas counties. The design goal was reproducibility. The warehouse is baked fresh at build time, and everything city-specific is isolated to a single config file, so pointing the whole thing at a new city is a small, contained change.
What it proves
A reproducible dbt warehouse baked fresh at build time, with the city-specific config isolated to one file.
How it was built
Claude Code, a reproducible ELT-plus-dbt warehouse baked at build time, with the city-specific config isolated to one file.
What is real, and where I was learning
What is real: the build is reproducible, and the config isolation actually holds, which is the point I was testing. Where I was learning: it reuses the Elvis pattern deliberately, so the novelty is in the portability, not a from-scratch design.