The Governance Layer for Agentic Payments. Policy, compliance, and audit above every agentic-payment rail.
Rail-neutral. Policy-opinionated. Design specification — not production capability.
- mnnr-standard — the open specification. Schemas, adapter contracts, 11 first-class product objects, brand kit. Apache 2.0.
- mnnr-platform — the reference implementation. Private.
If you're evaluating MNNR for procurement, security, or compliance sign-off — start at mnnr.app/trust/. It's the single index for everything an auditor, CISO, or legal team needs:
- Contract templates (direct-download PDFs, EU/UK + US variants) — MSA · SOW · DPA · AUP
- Security pack — Threat model · Data flow · Sub-processors · IRP · VDP · SOC 2 tracker
- Live cryptographic attestation — ML-KEM-768 + ML-DSA-65 (FIPS 203 + FIPS 204, signed 2026-06-14)
- Positioning honesty — Claims Register tracks what's design spec vs built
- Reconciliation event schema
- Payment-rail adapter integration guide
- 11 domain objects + relationship graph
- Brand kit
/llms.txt— AI-crawler site map/.well-known/ai-agents-manifest.json— agent capability manifest/.well-known/security.txt— RFC 9116
Marketing surface: mnnr.app · A50 Emergency Retrofit: mnnr.app/#a50
MNNR is a design specification for governance infrastructure. We do not own, operate, or guarantee any payment rail. See individual repository READMEs and the Claims Register for authoritative status per component.