# Meridian Montserrat / 领境通 Super App Function Map

Date: 2026-05-08

Purpose: provide a complete national-super-app function map for Meridian Montserrat, organized so product, design, government, and engineering teams can review the app as one coherent system.

## Product Definition

Meridian Montserrat is the national digital identity, payment, communication, government-service, digital-company, credential, and trusted-asset app for Montserrat.

The product should not be presented as a wallet. Wallet, chat, credentials, government services, and DC registration are all modules inside a larger identity-first national operating app.

## Core Principle

People are real-name verified. Conversations are private. Money and formal records are auditable.

- Real-name people: MID / DID / verified identity anchors the account and counterparty trust.
- Private conversations: normal resident chat is end-to-end encrypted.
- Auditable money: payment requests, transfers, receipts, refunds, disputes, and service events are structured records.
- Stateful services: government and DC applications always show status, next step, responsible office, and required action.

## Navigation Model

Recommended first product navigation:

Home / Chat / Pay / Services / ID

This avoids reducing the app to a wallet while keeping the highest-frequency actions close to the user.

## Functional Map

### 00. Meridian System Overview

Role: explain the whole national super-app in one view.

Core functions:

- Map the relationship between Home, ID, Chat, Pay, Services, Vault, Card, Security, Business/DC, Chain, and Operator Console.
- Show that MID identity controls permissions.
- Show that Chat and Pay create daily use.
- Show that Gov, DC, and Vault create institutional stickiness.
- Show Meridian Chain, MRD, USDM, and MXCD as trusted infrastructure rather than front-stage complexity.

### 01. Meridian Home / 领境首页

Role: daily command center.

Core functions:

- Identity status summary.
- Residency / MID validity.
- USDM available balance and local XCD display.
- Recent chats and payment requests.
- Pending government or DC tasks.
- Official notifications.
- Quick actions: Send, Request, Chat, Scan, Services.

Design requirement: the first screen should say "this is my Montserrat digital life", not "this is my crypto wallet."

### 02. Meridian ID / 领境身份

Role: sovereign digital identity surface.

Core functions:

- MID profile and real-name verified status.
- DID binding and verifiable credentials.
- QR verification.
- Residency / digital residency status.
- Identity state: active, pending, restricted, frozen, revoked.
- Credential renewal and recovery entry.
- Minimal disclosure proof.

Design requirement: official and trusted, but still simple for ordinary residents.

### 03. Meridian Chat / 领境聊天

Role: resident payment messaging.

Core functions:

- One-to-one real-name resident chat.
- MID Verified counterparty display.
- End-to-end encrypted normal messages.
- Pay and Request inside chat.
- Structured payment request card.
- Completed receipt card.
- Block and report.
- Disable new payments when identity is restricted.

Design requirement: private chat bubbles must look different from formal payment records.

### 04. Meridian Pay / 领境支付

Role: daily resident and service payment layer.

Core functions:

- P2P send and request.
- QR scan payment.
- USDM stable payment rail.
- MRD native asset support for network value / gas.
- MXCD future sovereign rail placeholder.
- Payment confirmation with verified identity.
- Receipt generation.
- Refund, cancel, dispute, and transaction detail.

Design requirement: consumer-simple on the surface; identity-verified and receipt-backed underneath.

### 05. Meridian Vault / 领境凭证库

Role: personal trusted records library.

Core functions:

- ID credentials.
- Residency credentials.
- Payment receipts.
- Government service documents.
- DC documents and certificates.
- Offline credential.
- Downloadable or shareable proof where permitted.
- Search, filters, categories, validity status.

Design requirement: feel like a secure archive, not a cloud-drive file dump.

### 06. Meridian Gov / 领境政务

Role: official digital service entry.

Core functions:

- Government service catalogue.
- Signed official notices.
- Service applications.
- Renewals, permits, certificates, fees.
- Status tracking.
- Supplementary document requests.
- Service payment through Meridian Pay.
- Receipt and proof stored to Vault.

Design requirement: every government service must be clear about source, status, required action, and responsible office.

### 07. Meridian Business / DC / 领境商务

Role: Digital Company pathway and business services.

Core functions:

- DC / Digital Company registration.
- MID-holder fast track.
- Company name reservation.
- Directors, shareholders, beneficial owners, PSC records.
- Document upload and signature.
- Company payment and receipts.
- Digital company certificate.
- Annual renewal and filing.
- Company status and compliance tasks.

Design requirement: make DC feel transparent, compliant, and modern; avoid legacy offshore-company branding.

### 08. Meridian Card / 领境卡

Role: physical and offline trust touchpoint.

Core functions:

- Physical ID card.
- NFC verification.
- Offline credential.
- Emergency identity proof.
- Merchant or government counter verification.
- Optional offline payment or access flow when approved.

Design requirement: card should feel like official infrastructure, not a novelty accessory.

### 09. Meridian Security / 领境安全

Role: trust, recovery, and protection.

Core functions:

- Passkey / biometric authentication.
- Device binding and device management.
- MPC / key protection.
- Recovery contacts.
- Emergency access.
- Fraud monitoring.
- Account freeze and restore.
- Risk prompts before high-value or official payments.

Design requirement: strong security without making ordinary users feel like they are operating a complex crypto wallet.

### 10. Meridian Chain & Asset Family / 领境链与资产体系

Role: settlement and verification infrastructure.

Core functions:

- Meridian Chain account.
- MRD / Meridian Coin native asset.
- USDM stable settlement asset.
- MXCD future sovereign rail.
- External assets secondary where supported.
- Chain confirmation, receipt hash, audit-safe payment record.
- Explorer-like detail hidden behind user-friendly receipt surfaces.

Design requirement: show credibility and traceability without overexposing chain jargon.

### 11. Merchant & Institution Console / 商户与机构工作台

Role: business, merchant, and government operating layer.

Core functions:

- Verified customer lookup.
- Payment request and receipt issuing.
- Refunds and reconciliation.
- Service request handling.
- DC workflow review.
- Official notice sending.
- User identity status check where permitted.

Design requirement: practical operations console, dense and clear, not a marketing dashboard.

### 12. Governance, Privacy & Audit Layer / 治理、隐私与审计层

Role: cross-system trust architecture.

Core functions:

- Separate private chat from auditable payments.
- Payment and receipt audit trail.
- Government service event log.
- Consent and purpose limitation.
- Role-based access control.
- Freeze, revoke, blacklist, and restricted-state propagation.
- Compliance export for authorized roles.

Design requirement: make the privacy boundary visible and credible: government trust does not mean government access to private chats.

### 13. Onboarding & Activation / 注册与激活

Role: turn an approved person into an active Meridian user.

Core functions:

- Invitation or eligibility entry.
- Phone/email/passkey setup.
- MID verification and liveness where required.
- Device binding.
- Wallet and Meridian Chain account activation.
- Recovery setup.
- First receipt / first chat / first service guidance.
- Restricted activation state if identity review is incomplete.

Design requirement: activation should feel like opening a national digital account, not setting up a crypto wallet. The user should understand what is active now and what still requires verification.

### 14. Notifications & Activity / 通知与动态

Role: unify all cross-module events into one understandable timeline.

Core functions:

- Payment requests.
- Completed transfers.
- Government notices.
- Service status updates.
- DC registration and filing tasks.
- Credential expiry and renewal reminders.
- Security alerts.
- Receipt creation and Vault save events.
- Filters by personal, payment, government, DC, security, and system.

Design requirement: notifications should be actionable and stateful. The user should know whether each item is informational, waiting for action, completed, expired, or high-risk.

## Role And Journey Matrix

Meridian should be reviewed by role, because the same app surface exposes different permissions and workflows.

### Local Resident / 本地居民

Journey: activate MID -> chat/pay -> receipts -> services -> card.

Primary modules: Home, ID, Chat, Pay, Vault, Gov, Card, Security.

### Digital Resident / 数字居民

Journey: apply or activate -> credentials -> services or DC -> USDM payments -> renew.

Primary modules: Onboarding, ID, Vault, Gov, DC, Pay, Activity.

### DC Founder / 数字公司创办人

Journey: MID verified -> DC name -> ownership records -> filing/payment -> certificate.

Primary modules: ID, DC, Pay, Vault, Gov, Activity.

### Merchant / 商户

Journey: verify customer -> request payment -> issue receipt or refund -> reconcile.

Primary modules: Pay, Merchant Console, Vault, Chain/Audit.

### Government Officer / 政府人员

Journey: signed notice -> service case -> fee/payment -> status update -> record.

Primary modules: Gov Console, ID status, Pay records, Vault documents, Activity.

### Compliance Auditor / 合规审计

Journey: authorized query -> receipt/service logs -> restricted state review -> export.

Primary modules: Governance, Privacy & Audit, Chain proof, Console.

## Rollout Roadmap

The product should activate in phases so adoption and institutional trust grow together.

## Phase Logic

### V1

Home, ID, Pay, Chat, Vault receipts, basic Security, onboarding, activity, and initial Services.

Objective: create daily resident usage through real-name payment chat.

### V2

Gov service catalogue, DC application, merchant payment requests, richer Vault, offline credential, and richer official notifications.

Objective: make Meridian the default official service entry.

### V3

MRD/USDM/MXCD maturity, merchant console, government consoles, expanded DC lifecycle, advanced compliance and audit.

Objective: turn the app into a full national digital economy platform.

### V4

Cross-jurisdiction Meridian pattern, API ecosystem, banking/payment partner integrations, sovereign rail expansion, compliance exports, and multi-country app variants.

Objective: turn Meridian from a Montserrat product into a repeatable sovereign digital infrastructure pattern.