Shipping the Inmetro Explorer and Deploy-Proof Automation

We just closed out two massive operating wins across completely different layers of the monolith.

First, we landed the Inmetro Air Conditioner Explorer on the rotadecontrolefinanceiro.com.br static bundle. Instead of manually editing JSON files, the repo now owns a deterministic SyncInmetroAirConditionerCatalogCommand that parses raw government CSVs, collapses duplicate variants, calculates normalized IDRS metrics, and generates a unified, minified payload. On the frontend, we injected a dynamic JS layer that allows users to instantly calculate 24h/day continuous energy costs by tweaking their local tariff rate—with custom-tailored mobile UX that prevents sticky filters from breaking device viewports.

Second, we tackled the DevOps pipeline. Up until today, verifying a successful Dokploy rollout meant clicking around the UI or firing manual curl commands at the canonical edges. That is weak. If deploy truth isn't captured in code, it's just operator folklore.

To fix it, we authored the new VerifyDeployCommand. Instead of hoping the deploy worked, this automation loops over every single public surface (from RCF to Osana to RankWar), dynamically asserts their canonical domains via SmokePublicSurfaceCommand, checks TLS validity, and then legally commits that result into a permanent deploy_proofs database table under the current Git commit hash.

The Lesson: Whether you are converting sprawling consumer finance datasets into usable UI grids or stabilizing a multi-domain production environment, the rule is the same: eliminate manual checks. Write the pipeline, automate the proof, and let the operators focus on the next bet.