Projects
What distinguishes a project
Section titled “What distinguishes a project”Unlike apps/* (deployed products) or packages/* (shared libraries), projects/* entries are data-science/analytics deliverables: DVC-versioned data pipelines and notebooks, generally scoped to a single client engagement or research question. Most follow a projects/<name>/{data,notebooks,src} layout, with data/{raw,preprocessed,out} tracked via DVC (.dvc pointer files, data/registry.yml) rather than committed directly. Some are excluded from the root uv workspace (see root pyproject.toml’s [tool.uv.workspace] exclude) when they need a divergent dependency set (e.g. GPU/CUDA packages).
Projects
Section titled “Projects”| Project | Status |
|---|---|
| 2025 Permit Ratification | Notebook-driven: CFDI v4.0 modeling + Voronoi geospatial influence-zone analysis |
| 2026-05-11 Axfaltec Variance Validation | Full DVC pipeline: ingestion → mass-balance/variance EDA → audit workbook & exec summary |
| Diesel Storage Tanks | Ingestion only: GeoJSON → PostGIS loader |
| EIA 861 | Not started — empty scaffold |
| MX COM Reporting | Full DVC pipeline: historical CRE filing cleanup & consolidation |
| Presidential Effect | Data acquisition only: yfinance market data fetch |
| Solar & Wind Generation | Most complete: load → clean → transform → visualize, incl. reusable Plotly style module |