Turn M Wallet into a product system the whole team can understand.

This site is not a loose document archive. It is a role-based workbench with clear questions, deliverables, and review standards for each team.

Use this as the meeting map. It tells each team where to start, which sections to use next, and what output they should produce before work moves forward.

This section turns the product vision into a working release board. A module is not ready until the page, policy rule, backend object, receipt or audit event, and team handoff are all clear.

Do not reduce M Wallet to an asset list. First help users understand their MID status, account context, and recovery posture. Assets, payments, IBC, credentials, and services should then appear as verified account capabilities.

FCA, USDF, MXCD Future, and external assets serve different product roles. The interface should make those roles obvious instead of treating everything as a flat token list.

This is the core module map for development. Every module must answer: who is the user, which account is active, which actions are allowed, and what record is produced.

Use this as the bridge between product design and engineering. If a row is incomplete, the feature is not ready for implementation.

This layer turns the guide into a release-quality checklist. It helps product owners decide what can enter sprint planning, helps engineering see contract boundaries, and helps QA know what must be verified.

This layer gives design and frontend teams a shared component language. Every screen should express identity, account context, trust status, risk state, and record outcome in a consistent way.

The interface should feel fresh, light, and trusted. It should not feel like an exchange, a heavy government portal, or a speculative crypto app.

The core engineering objects are not tokens alone. They are user, MID, account, MPC policy, recovery case, credential, invoice, receipt, policy, and audit event.

These cards are the working checklist for each team when reviewing this guide.

These journeys show how identity, account context, payment, credentials, and records work together. They are also a practical checklist for product, design, backend, QA, marketing, and customer experience teams.

External storytelling can be simpler, but it must not drift away from the internal product logic: MID-first, verified account, trusted payment, official records.

This is not a signal to build every feature at once. First prove the product logic with a working loop, then expand into complex assets and advanced security.

This log keeps unresolved questions visible without letting them blur the product direction. Each item has a recommended default, risk, owner, and next action.

This is no longer a plain file list. It is the working navigation for the M Wallet team, giving product, design, engineering, brand, market, government, and customer experience teams a shared way into the same product logic.