Mayomu
Open menu

Help & Support

Help & Support

Product guidance for the current Mayomu MVP surface. Use this route to understand what the page system does today, where public discovery ends and Dashboard work begins, and which surfaces remain intentionally deferred.
Public discovery
Project-first
Private shell
Dashboard
Public SubProject route
/projects/[projectDisplayId]/subprojects/[subProjectDisplayId]
Legacy route status
Redirect compatibility
Launch claim
Founder review only

Current posture

This surface explains current product truth. It does not claim public-launch readiness, staffed support operations, legal approval, or hosted-environment proof.

Public routes

Public discovery and public-safe review remain readable without a Dashboard session.

Discovery starts with Projects

Use Home, Explore, and Search to browse public Projects first. Active SubProjects stay visible through each Project narrative and its published SubProject matrix.

HomeExploreSearch

Public SubProject review is Project-rooted

The canonical public-safe SubProject route is /projects/[projectDisplayId]/subprojects/[subProjectDisplayId]. Old /sub-projects/* frontend pages are temporary compatibility redirects during migration; backend /sub-projects/:id/* API endpoints remain unchanged.

Trust boundaries

Launch-facing copy must stay faithful to current MVP scope and mechanism truth.
  • Mayomu is not an investment product and does not promise return on funding support.
  • Mayomu does not provide wallet, custody, clearing, or settlement functionality in the current MVP.
  • Threshold crossing before deadline is not by itself funding success; funding outcomes remain deadline-based.
  • Published does not auto-open funding.
  • Accepted is a lifecycle outcome, not settlement.
  • Publish confirmation confirms the project was published and links to dashboard and public next steps.
  • AI assists with structure and summarization; it does not finalize governed actions.
  • Operator routes are bounded and do not create generic override authority.
  • SubProject remains the operational unit for funding, delivery, evidence, acceptance, dispute, fulfillment, and trace; Project remains the narrative container and private operations shell.

Deferred and placeholder surfaces

These areas remain intentionally bounded so the current page system stays honest.

Community

Community remains a visible placeholder only. There are no feeds, follows, comments, DMs, or creator social graphs underneath it today.

Supporting depth

The Dashboard /account/supporting route remains a bounded placeholder and does not claim a payment ledger, settlement history, or complete cross-project support aggregation.

Discovery sophistication

Public discovery remains Project-first with creative-domain and lifecycle/status browsing. Advanced ranking, recommendation, and broader public discovery IA remain deferred.

Inspection ergonomics

Reviewer-safe and operator shells are grounded and bounded, but broader ergonomic depth remains a later refinement rather than a new authority layer.

Legacy routes are compatibility only

Old /sub-projects/* frontend routes are temporary redirect compatibility during the route migration. Operator internal dispute detail is deferred to a future operator-only /operator/disputes/[disputeId] route and is not hosted under Project Dashboard.

Support and contact posture

This route gives product guidance without implying staffed public-launch support operations.
  • Use this help shell for product-surface orientation, trust boundaries, and deferred-surface explanations.
  • If you are accessing Mayomu through a founder-review or invitation flow, use the contact channel provided in that workflow for direct questions.
  • This route does not claim incident-response staffing, jurisdictional rollout guidance, or public-launch approval.