Changelog
PitBridge is in development. This log records build milestones, not public releases. Every entry here is real. When something is in dogfood and not live, it says so.
Public site, docs, and design system
The marketing site went public: the product pages, the safety pages, the learn cluster, and the first comparison pages.
The security model doc is up, covering the localhost bind, pairing tokens, the arm-live ritual, and the kill switch.
The design system reached v1.1. Color stays semantic: green means an order is permitted to proceed, red means it was refused, and nothing decorative uses either.
- site
- docs
Local-first daemon and guardrail engine in dogfood
The local-first daemon runs the frozen order pipeline: schema check, permission check, guardrails, confirmation, submit, audit. No MCP or REST path skips it.
The guardrail engine enforces the twelve v0 guardrails, including the kill switch, the daily loss halt, and the max position cap. Limits load from a config file the agent cannot read or write.
Every decision writes to a hash-chained append-only audit log, so a dropped or altered line is detectable after the fact.
This runs in shadow mode against a NinjaTrader 8 simulation account. It is not public yet, and no account is armed for live orders.
- daemon
- guardrails
- audit
NinjaTrader 8 add-on and local MCP server paired
The NinjaTrader 8 add-on pairs with the daemon over the local network. The add-on connects out to the daemon, so there are no inbound firewall rules on the Windows side.
The daemon serves an MCP server over stdio for a local client; custom agents get a localhost REST API and WebSocket event feed. MCP over streamable HTTP is on the roadmap. Tool names are still settling.
Reduce-only order verbs (close, flatten) stay reduce-only even under the kill switch, so de-risking is always possible while opening intent is not.
- addon
- mcp
PitBridge is in development. NinjaTrader 8 is first.
Tell us your platform and we email you when your setup is supported. Nothing else.