What isn't built yet
One page, stated plainly, instead of ten hedges scattered across the docs. Everything below is a genuine gap, not a roadmap teaser softened into a maybe. If you're evaluating Northsun for production, plan around what's on this page.
The validation gate is not publicly callable
Every agent proposes. Northsun governs. is the product thesis. It does not mean every current action already passes through a governed decision boundary today. A Stage-1 deterministic evaluator exists in source, but the complete gate — the server-owned checkpoint between a proposed agent action and an external effect — is not exposed through the frozen public API. Nothing outside that frozen surface (recall_and_enrich, calls/end, caller) is a public contract you can call. Full detail, including what graduation would require: Validation gate.
Policy-bundle authoring is not shipped
Versioned rule bundles that a validation gate would evaluate against — the intended shape is documented, illustrative examples exist internally — are architecture guidance, not a callable contract. You cannot create, version, or deploy a policy bundle through any public interface today. Full detail: Policy bundles.
There is no self-serve signup
The early-access form collects your email into a waitlist; it does not mint a key on submission. Its own confirmation says what actually happens: a person reaches out within 24 hours with a working key. See Installation for both ways to ask for one. If you were expecting an instant "create account, get key" flow, that doesn't exist yet.
There is no self-serve billing or checkout
Hobby is free. Paid plans are quoted and invoiced directly, by a person, not through a checkout flow — the billing dashboard states this plainly and routes you to email rather than a card form. Usage-based limits and invoices are not yet a self-serve product surface. See Pricing for the current Hobby/paid split.
Why this page exists
Every one of these gaps is real and none of them block using the frozen public API today — Get a key, make your first call, and wire it to Vapi or Bland all work now. This page exists so you plan a production launch around the substrate that's actually shipped, not around a capability that reads like it's live because it's mentioned somewhere hopeful. If something you need isn't here and isn't in the rest of the docs, ask — hello@mnemix.ai — rather than assume.
Next steps
- Production readiness — the launch checklist for what is shipped.
- Validation gate and Policy bundles — the full design detail behind the first two gaps above.
- Troubleshooting — diagnose issues with what's actually live.