What Mirai Move delivers
One shared substrate — the Mobility Opportunity Case — delivered as Decision Intelligence, a Workspace, an API, Solution Design & Development, and Implementation support.
Prices are quoted per scope or still under review. Customers, revenue and contracts are shown only where a real record exists.
Decision Intelligence
scoped decision engagement
Regional Mobility Diagnostic
Betaworkspace or secure delivery- What it solves
- a region knows it has a mobility problem but not which need is real, which evidence supports it, and which solution classes are worth a pilot
- Who it is for
- municipality / public institution / transport operator
- Input needed
- region and scope question
- existing plans, surveys or constraints the organization already holds (optional)
- who decides and by when
- What Mirai Move does
- public-source discovery, evidence extraction, candidate qualification and Case formation run on schedule in Production; governed report drafting and secure token delivery exist; every Case is reviewed by a person before release
- What you receive
- a scoped Mobility Opportunity Case with evidence, freshness and contradictions visible
- solution-class options with Japan constraints (regulation, operation, cost) stated
- evidence gaps named as bounded research tasks
- recommended next step (validation, pilot design, supplier scouting) with its human gate
- Current maturity
- the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet— no real external organization has received a diagnostic yet; Case formation is currently held at the evidence frontier (QUALIFIED = 0), so a customer Case starts from the customer's question, not from a pre-qualified candidate
- Human gate
- a person reviews the Case and approves the deliverable before access is granted
- Not promised
- no buyer, procurement, pilot, certification or funding is promised or implied
- no guarantee that a qualified solution exists for the region
Enterprise Mobility Diagnostic
Betaworkspace or secure delivery- What it solves
- an enterprise needs a defensible, evidence-backed view of a Japanese mobility opportunity or constraint before committing budget
- Who it is for
- enterprise / facility operator / OEM
- Input needed
- the decision and its deadline
- scope (regions, scenarios, product classes)
- internal facts the enterprise can share (optional, private to its tenant)
- What Mirai Move does
- same substrate as the regional diagnostic; supplier/product intelligence is added from the qualified supplier records; enterprise-private inputs are held in the organization's tenant
- What you receive
- a Case with structured need, evidence, constraints and options
- product/supplier intelligence relevant to the scope
- open questions and validation plan
- a decision brief
- Current maturity
- the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet— offer pricing state is FOUNDER_REVIEW_REQUIRED (not publicly listed); supplier discovery for a new scope is an operator-run pipeline (ops/supplier-activation), not a wired runtime capability; no real enterprise engagement yet
- Human gate
- scope and the deliverable are approved by a person
- Not promised
- no buyer, procurement, pilot, certification or funding is promised or implied
- no market-size numbers without a cited source
Supplier Japan-fit Assessment
Betaworkspace or secure delivery- What it solves
- a supplier does not know which Japanese scenarios its product fits, which constraints it fails, and what evidence is missing before anyone in Japan could take it seriously
- Who it is for
- supplier / manufacturer (overseas or domestic)
- Input needed
- product submission through the supplier registration (organization, products, documents)
- target scenarios (optional)
- What Mirai Move does
- supplier registration, document intake, deterministic extraction, identity resolution and entity association run in Production (first real FINAL SUBMIT on 2026-09-06); Japan-fit evaluation exists for discovered suppliers and for Case constraints; document fields remain proposals until reviewed
- What you receive
- Japan-fit assessment per scenario with constraints stated (regulation, operation, localization)
- evidence gaps and unverifiable claims listed as such
- Solution Gap where the product does not fully fit, with the option to enter Design & Development
- governed follow-up path (no contact is made on the supplier's behalf without approval)
- Current maturity
- the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet— Japan-fit for a SUBMITTED supplier is not yet produced as a customer-facing deliverable automatically; structured product items are not exposed by the manual form; no real supplier has purchased an assessment
- Human gate
- contradictions and the assessment are reviewed by a person before release; any outreach on the supplier's behalf is a separate approved action
- Not promised
- no buyer, procurement, pilot, certification or funding is promised or implied
- no certification and no legal opinion — regulatory items are mapped, not certified
Supplier / Solution Scouting
Buildingworkspace or secure delivery- What it solves
- a need is clear but the candidates are not: which products or suppliers, from which markets, fit the constraints
- Who it is for
- municipality, operator, enterprise or implementation partner
- Input needed
- a Case or a need statement with constraints
- excluded suppliers / conflicts (optional)
- What Mirai Move does
- supplier discovery over approved public sources runs (90 discovered, 6 contact-verified on 2026-09-06); matching engine evaluates subjects against Case constraints; no scouting deliverable is assembled yet
- What you receive
- a scouting brief: candidates with evidence class per claim (supplier-provided / system-extracted / independently verified)
- match evaluation against the Case constraints
- conflict disclosure where Mirai Move has a supplier relationship
- Current maturity
- partly implemented; cannot deliver end to end— no offer row; no deliverable template; match engine has no match-eligible Case with hard constraints in Production
- Human gate
- candidates are approved by a person before any supplier is named to a customer
- Not promised
- no buyer, procurement, pilot, certification or funding is promised or implied
- no supplier is recommended without evidence class disclosed
- referral economics are a hypothesis and would be disclosed
Research / Evidence Brief
Betaworkspace or secure delivery- What it solves
- public evidence is scattered, stale and uncited; a research question needs a defensible evidence base with contradictions visible
- Who it is for
- university / research team / funding organization / general report user
- Input needed
- theme, region and question
- time window
- What Mirai Move does
- evidence store (4,074 rows), claims with provenance, insights pages and report factory exist
- What you receive
- evidence brief with citations, freshness and contradiction state
- candidate signals and Cases relevant to the question
- gaps as research tasks
- Current maturity
- the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet— no real external brief delivered
- Human gate
- the brief is reviewed by a person before release
- Not promised
- no primary data collection
- no peer review
Pilot / Validation Plan
Validation hypothesishuman-led, recorded in the workspace- What it solves
- a chosen option needs a validation design: what to measure, who must be involved, which constraints bind, what stops it
- Who it is for
- municipality / institution / enterprise
- Input needed
- a Case at decision stage
- stakeholders and constraints
- What Mirai Move does
- Case readiness/decision model and validation dossiers exist; the workshop is human-led
- What you receive
- validation plan with measures, gates and unknowns
- stakeholder map (public-source, no contact made)
- workshop summary when the workshop offer is used
- Current maturity
- a commercial hypothesis; delivery today would be manual— the plan is not generated by the runtime; it is manual work recorded in the Case
- Human gate
- a person leads the workshop and records the plan on the Case
- Not promised
- no buyer, procurement, pilot, certification or funding is promised or implied
- no pilot operation is run by Mirai Move
Mirai Move Workspace
private recurring organization workspace
Organization Workspace
Betaworkspace- What it solves
- one-off documents go stale the day they are delivered; organizations need a private, current view of the Cases, evidence, deliverables and changes that concern them
- Who it is for
- enterprise / OEM · municipality / institution · university / research · supplier · implementation partner · funding organization
- Input needed
- organization identity and members
- the Cases or questions in scope
- entitlement (what the organization may see and receive)
- What Mirai Move does
- tenant, membership, entitlement, linked-Case and deliverable objects exist (0188); access is by per-member hashed, expiring access links; every read is scoped by the tenant on the server; cross-tenant reads are refused and tested
- What you receive
- a private tenant with linked Cases (permissioned projections of shared objects — never a second copy of Case truth)
- evidence with classification and freshness
- deliverables and their review state
- activity / change record
- monitoring state for linked Cases
- Current maturity
- the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet— no real organization has a workspace; member invitation by email is not automated (access links are issued under human approval); monitoring is a read of Case freshness, not alerts
- Human gate
- a person approves the workspace, its linked Cases and every deliverable release
- Not promised
- no organization sees another organization's private data
- no automatic external action from a workspace
API / Embedded Capability
institutional read access to bounded capabilities
Mirai Move API
BetaAPI- What it solves
- an organization wants Mirai Move intelligence inside its own tools instead of a document
- Who it is for
- institution / enterprise / research organization integrating Mirai Move into its own systems
- Input needed
- organization credential (scoped, rate-bounded, auditable)
- bounded read requests
- What Mirai Move does
- v1 read contract with organization-scoped hashed credentials, scopes, per-credential rate boundary, audit rows and data-classification gating (0188); no internal control-plane operation and no external-action execution is reachable
- What you receive
- versioned read contract over Case summaries, classified evidence, supplier/product intelligence, match evaluations, Solution Gaps and monitoring state — each scoped to the organization's entitlement and to public/permissioned classification
- Current maturity
- the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet— no real organization holds a credential; write/subscription capabilities are not offered; match and Solution Gap reads return empty until a match-eligible Case exists
- Human gate
- credentials and entitlement scopes are issued, approved and revoked by a person
- Not promised
- no arbitrary external send
- no payment or contract action
- no internal control-plane operation
Solution Design & Development
workstream from Solution Gap to validated candidate
Solution Design & Development Workstream
Betaworkspace or secure delivery- What it solves
- the best available product does not fully fit the Japanese scenario, or no adequate solution exists; someone must turn the gap into requirements, options and a validated candidate
- Who it is for
- supplier whose product partly fits · municipality / enterprise whose need has no adequate solution
- Input needed
- a Case with recorded match evaluations (the gap forms only from evidence, never from opinion)
- supplier product facts where a supplier is involved
- What Mirai Move does
- Solution Gap → workstream → candidate → match re-entry runtime with trigger-enforced state machines is live (0185–0187) and proven synthetically; a workstream is born RESOURCE_REQUIRED with no assignee
- What you receive
- Requirements Brief (FACT / OBSERVED_REQUIREMENT / INFERRED_REQUIREMENT / CONSTRAINT / RECOMMENDATION / OPEN_QUESTION kept separate)
- gap analysis and adaptation / redesign / localization proposal (AI concepts are PROPOSALS)
- feasibility state (INFERENCE until a person or partner validates)
- validation plan and open questions
- resulting candidate solution that re-enters matching only after validation
- Current maturity
- the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet— human / partner engineering capability is RESOURCE_REQUIRED — Mirai Move does not have a design team and does not pretend to; no real gap exists yet (no match-eligible Case)
- Human gate
- approval before development; validation by a named person or partner before a candidate is called validated
- Not promised
- no engineering validation is claimed where only AI reasoning exists
- no team is fabricated
Implementation / Activation
governed coordination with human gates
Supplier Activation (Japan)
Buildinghuman-led, recorded in the workspace- What it solves
- a supplier identified from public information needs a governed path into Japanese scenarios: submission, Japan-fit, evidence gaps, redesign where needed, matches where supported
- Who it is for
- supplier / manufacturer
- Input needed
- public information identified by discovery
- the supplier's own submission
- What Mirai Move does
- discovery, verification, Japan-fit ranking and zh-CN outreach preparation run; the first batch (6 suppliers, digest c0d5ee72…) is prepared and AWAITING FOUNDER APPROVAL; EXTERNAL_ACTION_KILL engaged; real sends 0
- What you receive
- governed outreach (Chinese-language, Mirai Move identity, human-approved batch)
- registration → Japan-fit → evidence/constraint analysis → localization/redesign path → match where supported → governed follow-up
- Current maturity
- partly implemented; cannot deliver end to end— no batch has been approved or sent; no supplier has completed the path
- Human gate
- every batch is approved by a person; every send is bound to a digest
- Not promised
- no buyer, procurement, pilot, certification or funding is promised or implied
- referral economics are a hypothesis and would be disclosed as a conflict
Implementation / Market-entry Support
Validation hypothesishuman-led, recorded in the workspace- What it solves
- a decided direction needs coordination across parties, monitoring and governed communication
- Who it is for
- municipality / enterprise / supplier / implementation partner
- Input needed
- a Case with an approved direction
- the parties involved
- What Mirai Move does
- action packets, envelopes, follow-ups and outcome records exist; execution is approval-gated and currently killed
- What you receive
- implementation coordination records on the Case
- monitoring of Case changes
- governed multilingual communication drafts (approval-gated)
- Current maturity
- a commercial hypothesis; delivery today would be manual— human-led; no productized coordination runtime; no real engagement
- Human gate
- every external action is human-approved
- Not promised
- no buyer, procurement, pilot, certification or funding is promised or implied
- Mirai Move does not operate pilots
What maturity means here
Code or schema existing is not the same as a product being delivered.
- Live
- delivered to a real external organization through the runtime, repeatably
- Beta
- the runtime delivers end to end and is proven synthetically or internally; no real external delivery yet
- Building
- partly implemented; cannot deliver end to end
- Validation hypothesis
- a commercial hypothesis; delivery today would be manual
- Not available
- not offered
