Skip to main content

July–August 2026 — Safety gates, latency visibility, and BYOK

· 2 min read
AlphaSwarm Platform Team
Platform Engineering

The July–August development cycle focused on auditability and safety before capital: statistically honest promotion gates, expiring human approvals, per-segment order-latency visibility, and vendor credentials that never sit in process environments.

Every behaviour listed here ships default-off behind a feature flag (with one deliberate exception: latency metrics auto-enable in paper and development environments). Your deployment does not change until an operator opts in.

Safer promotions​

  • Trial ledger — every research trial is recorded, so the deflated-Sharpe and overfitting statistics that gate promotion use an honest experiment count. A lucky 1-in-10,000 backtest no longer looks like skill. Concept →
  • Evidence-gated promotion — promotion requests fail closed without a complete statistical evidence bundle, and paper execution refuses artifacts that lack an approval token.
  • Approvals now expire — pending human approvals (orders, promotions, ingestion) carry a TTL; stale requests lapse instead of firing late. Concept →

See where every millisecond goes​

Six named clocks measure each segment of the order path — market-data lag, strategy think time, risk gate, ledger write, broker acknowledgement, fill apply — with a ready-made Grafana dashboard. Auto-on in paper/dev environments. Concept →

Bring your own keys​

Market-data and brokerage credentials (Alpaca, IBKR, Databento, Alpha Vantage) now resolve through the platform credential vault at the moment of use — organizations can bring their own vendor keys, and worker processes no longer carry vendor secrets in their environment. Concept →

Governed streaming​

Kafka messages carry schema ids that consumers verify (refusing to guess on unknown schemas), and stream consumers address topics through the governed data catalog rather than hard-coded names. Concept →

Also in this cycle​

  • CLI sign-in fix: alphaswarm-cli auth login device flow now works against hosts that previously only advertised the web app's OIDC client.
  • Clearer readiness: /readyz distinguishes "database migrations pending" from "database down", and surfaces auth-service reachability advisorily.
  • License + customer management APIs for enterprise/BYOC deployments.
  • dbt semantic layer (preview): named, governed business metrics for agents and dashboards. Concept →

The full engineering detail is in the 2026-08-13 changelog.