BafGo PortBafGo PortA direction, not a schedule. No dates, no promises. Just the areas we intend to keep growing, and why they matter.
Early access means it works today, still early. Exploring means it's where we're heading next.
Rules, the trace, and verify are the foundation, and they ship today. We keep growing them: sharper link integrity, a calmer editor, and more ways to catch drift before it reaches production.
One command from the npm registry today. Next we fold that into a single self-contained binary, so there's no Node to install and updates are one fetch.
Local tamper-evidence ships today: manifest.json fingerprints, a hash-chained event log, and optional signing keys for approvals. What's next is the offsite witness and archive, for teams that have to prove it to a third party. The witness is pluggable: a public log by default, swappable for a self-hosted one, so teams that can't ship hashes offsite can run the whole thing on-prem. Your code never leaves your repo: only fingerprints do.
Drafting and suggestions already run on your own model with your own keys. We grow this without ever routing, holding, or billing your usage.
One read-only board across every repo, for product leads and auditors who need the whole picture instead of one repo at a time.