Email-first routing for licensing, procurement, security, privacy, and legal — backed by signed public state, local verification, and offline-reviewable artifacts.
Published channels: contact channels (pinned) · mvg-contact.json
Clear routing upfront shortens serious review. If the lane is unclear, start with licensing@meridianverity.com for commercial diligence. Security issues should go directly to security@meridianverity.com.
NDA diligence, pilot scope, commercial path, and license terms.
Acceptance criteria, reviewer artifacts, offline review packs, and auditor attachments.
Security review, responsible disclosure, encrypted reporting, and reviewer coordination.
DPA, retention or deletion, jurisdiction-specific privacy review, and data handling questions.
Terms, publication boundaries, counterparty routing, and counsel coordination.
For licensing and pilots, copying Security early helps align acceptance criteria and shortens the path to offline-reviewable reviewer artifacts.
For encrypted disclosure, import the public key, verify the fingerprint, and use security.txt as the canonical security route.
Create a reviewer-ready email without embedded form vendors or analytics. Inspect the draft before sending.
For security, procurement, and counsel that need machine-readable or signed routing materials.
Human-readable reviewer routing and release references.
/.well-known/mvg-prod.json (+ .asc) is the single signed production pointer. Missing proof implies HOLD; invalid proof implies FAIL; a valid signature means the referenced receipts can be verified offline.
site_release_verification_keyring_url = /trust/site-release/latest/pgp.asc
security_contact_encryption_key_url = /pgp.asc · security.txt
