Identity
Who published this state and which keys are authoritative.
Meridian State Layer
Decision before action.
Five checks—identity, scope, freshness, integrity, and policy—resolve to PASS, HOLD, or FAIL before a sensitive action is allowed. Signed state decides first; local verification and independent replay confirm the same outcome.
- 15 secSee what checks action before it happens.
- 60 secVerify the same public state locally under the published path.
- 5 minRoute leadership, security, procurement, or licensing to the right next step.
Pages explain. Signed state decides. Independent replay confirms. Need the replay appendix? Open Proof.
Five checks set the verdict
Five checks set the verdict.
Identity, scope, freshness, integrity, and policy resolve the outcome before action.
Scope
Which subject, action, and route are covered by the state.
Freshness
Whether the declared state is still within published time bounds.
Integrity
Whether pointer, signatures, digests, and witnesses still verify.
Policy
Which published rule resolves PASS, HOLD, or FAIL before action.
Decision and receipt follow from those five checks.
Claim graph
Every public claim resolves from the same state layer.
The mechanism stays legible because claims, dependencies, freshness rules, and reason codes are rendered as one graph instead of hidden across pages.
Evidence
Rule
Decision
Trust Center, Verify, Procurement, Licensing, and Proof are different views over the same signed public state.
60-second verification
Verify the live public state in under 60 seconds.
Use the same published verifier already exposed on Verify. Do not introduce a second toolchain or a second command.
Use the published path.
Download the current bundle, run the published offline verifier, then confirm the current public status, canonical production pointer, and signed evidence manifest.
python3 public_verify_site_release_v50_4.py --evidence-bundle MVG_SiteRelease_Evidence_Bundle_MVG-SITE-PROD-20260227.3.zip --trust-mode prod
What should match
- Current public status — matches the published state.
- Canonical production pointer — resolves to the same authority path.
- Manifest + signatures — verify locally under the published trust mode.
- Decision rule — missing, withheld, or unverifiable proof stays HOLD.
5-minute next step
Choose the right path for your role.
A serious buyer should not have to guess where to go next. Route leadership, security, procurement, and licensing directly from this page.
Understand posture fast
Review the brief, public status, and authority rule.
Open ExecutiveInspect signed evidence
Start with the reviewer bundle and the canonical pointer.
Open VerifyOpen the buyer-ready packet
Use the procurement pack, evidence manifest, and policy mapping.
Open ProcurementMove into scoped diligence
Use the licensing path and partner checklist.
Explore LicensingNeed the replay appendix?
Controls explains the mechanism. Proof collects the buyer-run replay path, acceptance scenes, and audit questions that support deeper review.
State resolves locally. Independent replay confirms the same verdict.
Falsification Receipt is the standards name for the replay object behind local verification, independent replay, and challenged outcomes.
Front-door trust asset: independently witnessed HOLD. Public spec text remains subject to revision as witnessed replay matures.
Ready to review MVG with one public diligence system?
Start at the live public state, verify it locally, then compare the witness quorum status before you move into procurement, licensing, or executive review.