Contact

Contact.

Meridian Verity is the short brand for Meridian Verity Group. Route licensing, procurement, security review, or privacy through the same signed public state.

Procurement-grade routing for Security and Counsel. Email only (no embedded form vendors).

Truth strip Reviewer routing v80.5

Single-source reviewer navigation. If any page text conflicts with a signed receipt, treat it as HOLD and follow the receipt.

/trust/reviewer-index/ Reviewer Index Key roles Site‑release latest

/.well-known/mvg-reviewer-index.json Machine index Signature

Canonical pointer /.well-known/mvg-prod.json (+ .asc) is the single signed production pointer. Determine state from signature validity (fail‑closed): missing ⇒ HOLD; invalid ⇒ FAIL; valid signature ⇒ proceed to verify referenced receipts offline.

Key roles site_release_verification_keyring_url = /trust/site-release/latest/pgp.asc · security_contact_encryption_key_url = /pgp.asc · security.txt

Verifier states PASS: all required proofs verify · HOLD: proof is missing, withheld, or unverifiable (fail‑closed) · FAIL: proof is present but invalid or inconsistent.

Licensing: NDA diligence → pilot → license terms. Fastest routing: include (1) action surface and (2) evidence consumer.

Routing role aliases no backend

Where to email

Route by artifact or agreement type. If unsure, start with licensing@meridianverity.com.

Licensing & pilots — licensing@meridianverity.com (NDA diligence · pilot · license terms)
Procurement & acceptance — procurement@meridianverity.com (acceptance criteria · auditor attachments)
Security — security@meridianverity.com (security review · disclosure)
Privacy — privacy@meridianverity.com (DPA · retention/deletion)
Legal — legal@meridianverity.com (terms · publication boundaries)

Verifiable routing: contact channels (pinned) · mvg-contact.json

Secure contact (PGP)

For encrypted reports: import pgp.asc and verify pgp.fingerprint.

What to include (routing)

Highest‑risk action surface (egress / privileged I/O / accelerator dispatch)
Evidence consumer (Security / Audit / GRC / procurement / regulator)
Constraints (cloud/on‑prem; kernel/driver/hypervisor; air‑gap)

Auditors attach (optional)

Audit summary (PDF)
Receipt / manifest (JSON)

Structured intake structured offline

Structured intake (optional)

Generates a structured mailto message. No analytics or embedded form vendors by default.

Preferred: Security present

For licensing and pilots, include Security: align acceptance criteria and ship offline‑verifiable artifacts your reviewers can replay.

HALTSEAL Procurement Trust posture