A review of everything living in iEnergia AI Apps — and a concrete, low-cost plan for David, Sven, Daniel and Sebastian to build at the same time without stepping on each other.
The folder holds a fast-moving product suite organised into six pillars. Status today: 12 live, 7 shipped, 13 building, 3 parked, 3 tech-debt, 1 idea.
Vault (6-month fleet archive, live) · Iris Local Agent feature store · Fleet Forensic drill-down · Hidden-signal sweep · per-vendor ingest v2.
Prism monthly report · Lens owner-reporting product · PR audit · Lens Parker watchlist · Verona spatial foundation · cierre_mes.php.
Anatomía (canonical plant record) · Helix backend · TV portafolio display · Margin → iAM asset-management · three-tier data arch (LOCKED).
BEAM Reporte (field daily-report app) · iFleet / Tracklink vehicle GPS (SOLUS Flota).
GRIDvault CRM — PMGD industry chessboard (72 orgs / 184 contacts) · GRIDvault freemium concept.
CEN PRMTE API → TV · GPM key switch · CIMA (EPC) · LUMEN brand · Tracker PdM · Magnetar / Pluto / EnnoIA vision briefs.
The evidence is already in the folder: versioning is being done by hand, and 2.9 GB of data is mixed in with a few MB of actual source code.
prism_report.php.bak2…bak8, cen_check.php.bak-truncated, Spark Central.html.bak4-corrupted. This is exactly git's job..pyc, .venv/, __pycache__/, .idea/..bak file becomes one line in the timeline; roll back instantly.DEPLOY-NOW.md ritual.Git is for code. Object storage is for data. Keep the repos small and fast; move the 2.9 GB to Cloudflare R2. A good .gitignore alone removes ~95% of the bulk.
The GitHub org ienergia already exists (the Solus repo is live). Not 40 repos, not one giant monorepo — group by deploy target, which is how the apps actually ship.
| Repository | Holds | Deploys to |
|---|---|---|
ienergia/idata | PHP apps — Prism, Lens, Vault, cen_*, vcom_tick | cPanel idata.ienergia.cl via FTP Action |
ienergia/spark-dashboards | Standalone HTML — Spark Central, GRIDvault, Iris forensic, TV | Cloudflare Pages |
ienergia/data-pipelines | Python — CEN / VCOM / GPM harvesters | Local / scheduled |
ienergia/Solus (exists) | The Next.js app build | Cloudflare Pages |
ienergia/briefs (optional) | Vision & strategy .md / .html docs | — |
A simple GUI — no command line needed. Clone once, done.
sven/iris-rules, daniel/beam-reporte. Isolated work, zero "we both edited it" conflicts.
Open a PR → quick look → merge to main. The review takes seconds.
GitHub Actions publishes to Cloudflare Pages or FTPs to cPanel. The zip ritual disappears.
Move API CEN/, Lens/incident_corpus/, Json Test Data/ and the PLABACOM zips to Cloudflare R2 (you already use Cloudflare). A tiny data/README.md in git tells people where it is. Dropbox stays only as the human drop-zone for raw exports.
The expensive mistake would be committing the data — files over 100 MB are blocked by git outright. Keep data in R2 and the cost stays near zero.
Pricing is approximate and current as of early 2026 — verify on GitHub's pricing page before committing.
Each person owns their work on their own branch and merges through a pull request — so David, Sven, Daniel and Sebastian can all build at once without ever overwriting each other.
Owns the vision and the roadmap. Reviews and approves merges to main; sets product priorities across the pillars.
Red-pens specs and rules (Iris & Kepler), shapes the briefs. Drives the data-platform direction.
Builds the pipelines and backends — CEN / VCOM / GPM ingest, reporting, deploy automation.
Field-facing apps — BEAM Reporte, iFleet/Tracklink, plant intake and O&M surfaces.
Roles are a starting suggestion — easy to adjust. Add anyone to the ienergia org in two clicks.