Skip to content

Engineering log

Open notebook. Closed source.

Dated entries for what shipped and what broke. The failures are here on purpose — a log that records only wins is marketing, and everyone reading this can tell the difference.

  1. SuryaSetu

    Bounded reconcile to a time window — it resurrected deleted data

    The tool built to recover leads the Demand Engine never delivered had no time bound, so re-running it restored records that had been deliberately removed. Recovery tools need a window, or they are an undelete nobody asked for.

  2. SuryaSetu

    Wrote up the four silent failures of the first campaign day

    Every one of them reported success while doing the wrong thing. The pattern is worth more than the fixes: a pipeline that cannot fail loudly will fail quietly instead.

  3. SuryaSetu

    Fetched lead answers from the Graph API — every lead was arriving empty

    The answers were never in the webhook payload. The ingest path had been reporting healthy while writing blank rows for an entire campaign day.

  4. SuryaSetu

    Stopped hiding broken leads

    Malformed leads were silently skipped so the dashboard stayed clean. Now they surface as errors. A dashboard that is quietly wrong is worse than one that looks bad.

  5. Infrastructure

    Health watchdog, and the real shape of the idle-reclamation risk

    Free-tier compute can be reclaimed when it looks idle. The watchdog exists because the failure mode is not a crash — it is a machine that quietly stops being yours.

  6. Infrastructure

    Hourly backups with a verified restore drill

    A backup that has never been restored is a hypothesis. This one has been restored end to end, off-site, and the drill is part of the routine.

  7. SuryaSetu

    Phone-is-identity auth with role-bound invite codes

    Vendors and advisors hold 30-day sessions; admin holds 7. The people using this portal are installers on a phone in the field, not operators at a desk.

  8. SuryaSetu

    Wired three controls the code claimed but did not have

    Found during a review pass. Documentation asserting a control that does not exist is worse than documentation admitting the gap.

  9. SuryaSetu

    Lead-distribution portal — vendor, employee and admin consoles

    Three roles, one data model, row-level scoping so a vendor can never see another vendor’s leads.

  10. Substrate

    First-run guided tour across the frontend

    A spotlight walkthrough of every feature. Software nobody can find their way around has no features.

Cadence

Updated as things ship, not on a content calendar. If this page has not moved in a while, that is information too.