From Protocol to Product

What this means for you

FNP did not start as a product. It started as a protocol the team published openly, then hardened into a server other teams could deploy. The launch narrative follows that order: spec, server, deployments, integrations.

The pitch

The promise of a document the host cannot read is old. What changed is that the math now runs in time a real user will tolerate, on hardware a real cloud already runs. FNP is the moment that promise crosses the line into something a team can actually ship to customers.

Who it’s for

Anyone telling the launch story to an outside audience: press, investors, prospective partners, or the first wave of regulated buyers who will not buy a beta but will champion a v1.

Proof points

• Specifications, reference circuits, and server are all in the open at github.com/aphelion-craft, with an explicit cross-repo docs source-of-truth in meta/platform-docs
• Production server already ships with persistence, auth, multi-region replication, observability, and cost controls. Not a research prototype
• Mobile and browser proof verification are part of the same release line, not a roadmap promise. Edits stay verifiable on the device that made them

timeline
  title FNP from idea to v1
  Spec : Three locks published as one architecture
       : Reference circuits open sourced
  Server : Production binary in Rust
         : PostgreSQL persistence and JWT auth
  Deploy : Multi-region Kubernetes topology
         : Observability and cost controls in the same release
  Edge : Browser and mobile verification
       : Same proofs end-to-end