Permissioned Records Layer

Meridian Chain

Authority→Identity→Write→Evidence

Meridian Chain is the trusted-memory layer of the Meridian Special District: a permissioned record foundation for receipt anchors, status continuity, settlement evidence and reviewable institutional events. It does not try to become a public network. Its capability is finite, identity-bound and purpose-limited. The boundary is the trust.

Within MSD, M Chain sits below services: it keeps the narrow, reviewable record memory that lets receipts, status and settlement facts be checked across time.

Review the Record Boundary See the Assurance Path

01Bounded memory 02Identity-bound write 03Reconciled evidence 04Formal publication

Review posture: concept and pilot framework, subject to public mandate, formal adoption, and jurisdictional approval.

RoleEvidence memory · status continuity

AdmissionPermissioned · identity-bound

BoundaryFinite classes · no open platform

Public proofReceipts · status · attestations

What it is A controlled memory layer beneath civic services. Receipts, status events, settlement evidence and governed changes land on one finite institutional record base.

Why it matters Public trust cannot rely on unreviewable technical claims. The narrower the record surface, the easier it is for governments, auditors and partners to read.

What it is not No open-network or speculative posture. No public programmable surface, no open-network campaign, no API service and no market story.

01RoleTrusted memory sits below services.

02AdmissionEvery writer is identity-bound.

03ReconciliationReserve, issue and ledger sum must agree.

04PublicationEvidence opens only through formal sequence.

MSD operating path

One institutional sequence, not a standalone chain.

Mandate sets the perimeter. Identity admits participants. Services create daily use. Meridian Chain preserves the narrow record memory underneath, so assurance can be reviewed later without asking anyone to trust the system blindly.

01MandateDefine what may be issued, accessed, paused and revoked.

02IdentityBind people, companies and writers to MID / MCID recognition.

03ServiceLet Meridian One, Mpay and related branches create usable workflows.

04MemoryRecord only finite receipt, status, settlement and governance facts.

05AssurancePublish evidence through reserve, ledger, attestation and verification paths.

Architecture — what may be recorded

Six public record classes, one finite audit surface.

A trusted memory layer earns trust not by how much it can do, but by what it cannot. This is not a feature tour; it is the public record taxonomy of the system.

A formal institutional record taxonomy hall with six governed evidence stations connected to one central civic record table. — Six governed routes into one institutional record. The illustration is conceptual; the control principle is literal: no public contracts, no anonymous write path, no seventh record class.

A layered institutional model showing civic authority, public services and a digital ledger foundation as one controlled infrastructure stack.

Institution above, memory below

Meridian Chain is the trusted memory layer, not the public face.

Residents and merchants should experience simple services. Regulators and auditors need a finite book of status, receipt and settlement facts. The record layer sits underneath both: narrow enough to govern, strong enough to reconcile.

PII stays off the ledger Mirror layers are read-only Write access is admission

Reserve discipline Issue and retire can only follow verified reserve movement.

Service settlement Transfer and conversion remain inside named, allowlisted accounts.

Public evidence Anchors and registry changes make proofs and rule changes reviewable.

Issue · reserve matched

Only after a reserve deposit is verified can an equal amount be issued to the same identity. If reserves do not move, issuance does not move.

Reserve in → verified → equal issue

Retire · reserve release

Redemption retires the same amount it pays out. What leaves the reserve is what leaves supply, so the books cannot quietly drift apart.

Redeem → equal retire → reserve out

Transfer · named movement

Value moving between allowlisted accounts. Every unit has an origin, a destination and a signature — value of unknown provenance does not enter the ledger record.

Identity → identity · fully traceable

Convert · approved rate

The ecosystem settlement asset and a jurisdiction's local digital currency convert as one ledger operation at the published rate: all or nothing, no in-between state.

USDM ⇄ local digital currency · single operation

Anchor · evidence commitment

The fingerprint of a receipt or credential is written into the ledger. From that moment anyone can verify it independently — including fully offline.

Receipt hash → ledger anchor → verifiable

Registry · governed change

Governed changes to the account allowlist and system parameters. Four-eyes principle, fully logged — changing the rules is itself an auditable transaction.

Propose → review → effect · traceable

"There is no seventh record class." This chain opens no public programmable surface and carries no third-party code. It is a trusted memory layer, not a platform — what it cannot do is its hardest promise.

Who can write

Address is identity; writing is admission.

Three controlled institutional gateways converging into a central ledger core, representing source screening, identity binding and permissioned ledger writes. — Admission is not an account feature. It is the boundary between reviewed sources, verified identity and the right to write settlement facts.

There are no anonymous addresses on this ledger. Behind every account that can hold value stands a verified MID (personal) or MCID (institutional) identity; every write carries a signature with a name behind it.

This is not forensics after the fact — it is a structural precondition. The right to write and the right to enter are the same right. At the funds gateway, "arrival ≠ admission" source screening comes first; at the ledger layer, the allowlist enforces "no identity, no entry." Two doors, guarding one boundary.

01Source screenedArrival is reviewed before reserve entry.

02Identity boundMID / MCID maps to the account perimeter.

03Ledger writesOnly admitted accounts can write settlement facts.

The funds gateway · M Gateway → The identity framework · Meridian SD →

How it works Concept preview

Three numbers that must always agree.

How much sits in the reserve pool, how much has been issued on the ledger, and how much all accounts hold in total — reconciled daily, and they must be equal. The ledger figure is this equation's public end.

A formal audit reconciliation hall with three equally weighted proof surfaces representing reserve pool, total issued and ledger balance sum.

Reserve pool = Total issued = Ledger balance sum

Reserve poolPublished at pilot

Total issuedPublished at pilot

Ledger balance sumPublished at pilot

Reconciliation discipline: daily checks; any discrepancy triggers an alert and freezes issuance; independent reserve attestations are published periodically. The ledger books corroborate the M Gateway transparency panel, and anchored receipts can be verified offline on the independent verification domain.

Transparency panel → Meridian Verify →

Assurance path Institutional sequence

Evidence moves in order, or it does not become public.

Meridian Chain is designed around a simple public rule: reserve movement, ledger entry, attestation and verification must form one reviewable path. Confidence comes from sequence, not spectacle.

A formal civic archive corridor with four sequential evidence stations leading toward a public verification aperture. — Four institutional surfaces, one evidence path: source control, ledger reconciliation, independent review and public publication.

01 Source control

Reserve movement and identity admission are reviewed before a settlement fact is allowed to enter the record.

02 Ledger reconciliation

Issued value, retirement, transfer and conversion remain within the finite six-class transaction surface.

03 Independent review

Reserve attestations and anchored receipts give auditors a bounded evidence set instead of an open-ended technical maze.

04 Formal publication

Public evidence data, verification records and governance archives open through formal pilot announcements.

Boundary & publication Published at pilot

Public by design, formal by sequence.

Operator structure, governance charter and public evidence surfaces will be published with the pilot, per formal announcements. This page promises what will be made public — not what has not yet been formally opened.

Who may operate Named institutions, admitted under a published governance charter.

What becomes visible Issuance, retirement, anchoring and block-status evidence.

How it is reviewed Reserve attestations and archived records remain available for audit.

A formal public governance publication chamber with archive walls, evidence tables and a central ledger console for official review records.

At pilot openingOperator set & governance charter published · public evidence surface opens

ContinuouslyIssuance, retirement & anchoring records queryable · block status in seconds

Each periodArchived alongside independent reserve attestations · permanently traceable

Formal sourceOfficial pilot announcements

Evidence surfacePublic evidence data, attestations, verification domain

BoundaryNo service, API or registration on this page

Public-status discipline: until the pilot is formally opened, the page remains an institutional concept surface. It marks the evidence to be published, the controls to be governed and the boundaries that are already fixed.

Memory layer, not platform

One record layer, holding up a city.

Six record classes are all it does — and all the foundation the floors above it need: institutions, identity, receipts, economy, hardware, all resting on one reviewable memory layer.

01Finite capabilitySix transaction classes; no public platform surface.

02Named admissionEvery account and writer has an identity behind it.

03Daily reconciliationReserve pool, total issued and ledger balance sum must agree.

04Independent proofReceipts and public records can be verified outside the business flow.

No open-market posture No public programmable surface No anonymous write access

Controlled scope Reviewed admission Public proof

The ecosystem · Meridian SD → M Gateway → Mpay → Meridian Verify →