Platform Engineering

Six Engineering Phases — why haythix is built differently

8 min read

What it is

Before the seven Verticals, we shipped six platform-parity Phases that put haythix at level — or ahead — of every competitor in the activity-bot category. The phase that competitors don't run is Phase 4 — the QA Sweep that strips fabricated metrics. It's the most-important engineering decision in the platform's history.

How to think about it

These phases describe how the foundation was built. They don't correspond to single pages in the UI — they're cross-cutting decisions visible in the codebase and in every API response.

Step-by-step

  1. Phase 1 — Portfolio Rebalancer

    Real-position rebalancing across all your holdings. Hourly worker. Explicit "unpriced" status when CoinGecko has no feed for an asset — we never impute prices to make the dashboard look complete.

  2. Phase 2 — Grid Bot Variants

    Spot, futures, infinity, and reverse grids on one engine. Each rung knows its side and direction, so a futures grid behaves correctly when reserves invert.

  3. Phase 3 — Cross-Exchange Arbitrage

    5-state leg status (ok / partial / partial-leg / open-leg / unfilled). The operator always knows which leg of an arb fired and which didn't. Arbitrage that hides leg failures is the leading source of ghost P&L on every competitor.

  4. Phase 4 — QA Sweep (no fabricated metrics)

    Stripped 15+ hardcoded ROI/winRate values from the marketplace. Replaced Math.sin(seed) "scores" in the public token analyzer with explicit pending state. Nulled fabricated wallet P&L in Top Traders. The phase competitors do not ship.

  5. Phase 5 — Frontend Deploy Discipline

    Frontend deploys are batched intentionally. Never half-shipped pages, never live routes pointing at undeployed backends. Stripe live-mode flip is deferred to your real-money test, not auto-flipped at deploy.

  6. Phase 6 — Ops Cleanup with Safety Nets

    Destructive admin operations require explicit token (e.g. confirm: "YES_DELETE_<userId>") and snapshot prior state before mutating. Mistakes are reversible.

Tips & pitfalls

  • When you see "—" on a stat, that's Phase 4. It means we don't have real data for that field. Other platforms would fill it with an imputed estimate; we won't.
  • When you see "partial" status on a scan or worker run, that's the same discipline applied to long-running jobs. We won't pretend a partial run was complete.
  • These phases are why the seven Verticals work. The discipline is the foundation; each Vertical is built on top of it.