Method / trust / human governance

AI structures the work. Humans keep the final gate.

Mirai Move explains Japan mobility work as a public, evidence-gated system where AI helps structure the work and humans keep the high-risk decisions. Public intake, report previews, supplier materials, and research drafts all stay bounded before release.

PublicPreviewInternal DraftEvidence Needed

Method boundary

This page explains what Mirai Move collects, how AI helps, and where human review stays in charge. It does not certify suppliers, approve procurement, auto-publish reports, or promise delivery.

Operating loop

Operating loop

The public flow moves from intake to internal drafting with clear boundaries at every step. This page shows what is collected, what stays on hold, and where Founder review enters the loop.

Receive

Receive mobility issues, inquiry text, supplier materials, and public-source hints, then capture the first sentence.

Structure

Separate place, user, constraints, supplier conditions, and the evidence that still needs to be found.

Check sources

Compare public sources and submitted materials so claims, gaps, and follow-up questions stay distinct.

Route

Let AI sort the safe route candidate for inquiry, report, supplier, or internal review handling.

Hold gaps

Keep missing evidence visible as evidence gaps so the workflow does not jump straight to a final conclusion.

Send to Founder review

High-risk output, recommendation-like language, and any certification or delivery judgment stay on hold until a human reviews them.

PROBLEM TO SOLUTION

One connected journey from signals to implementation

Collect

Gather issue signals from regions, the field, and public sources

Structure

Organize issues, conditions, and stakeholders with AI assistance

Analyze

Surface questions while keeping sources traceable

Design

Shape reviewable options and reports

Implement & verify

Connect to pilots and adoption studies, then confirm outcomes

AI assists the analysis. Final judgments, publication, and proposals always pass human review.

Operating loop

Public review operating loop

AI can structure, summarize, compare, and draft.

InputInternal review requiredAI assists, not decides

Receive the first sentence and any supporting material, then keep it in preview mode.

Step details
  • Capture the first sentence
  • Suggest the likely route
  • Spot missing context
  • Decide if the case is approved
  • Approve a supplier
  • Release a report
  • Is the route guess sensible?
  • Did any sensitive data get added?
  • Does it stay in scope?
  • A short summary
  • A route suggestion
  • A safe preview state

Start with one sentence.

Receive

This checkpoint keeps only the information needed for public review.

No certification, procurement recommendation, deployment approval, or final delivery is created from this methodology page.

AI helps with structure, comparison, summary, and drafting, but it does not make the final call or open the public gate.

  • AI helps structure mobility problems and organize evidence.
  • AI does not automatically solve issues or publish public reports.
  • AI does not approve supplier recommendations, procurement, certification, deployment, payment, or client delivery.
  • AI output is used only after Founder review when the case is high risk.

Public claims must have a traceable source basis. If the evidence is weak, the claim stays a hypothesis or is removed from the public layer.

Public claims

Public explanations stay limited to claims with a traceable source path.

Unsupported claims

Claims without support are not stated as facts and remain under review.

Paid reports

Formal reports and paid deliverables require source lineage and review before they are released.

Report previews

Previews do not expose restricted conclusions or non-public assumptions.

Stakeholder paths

Paths by stakeholder

The same method serves different stakeholders, but the evidence depth and the type of review change by route. Every entry starts as preview-first and becomes sharper through evidence.

Individuals, families, communities

Start with daily mobility friction, household needs, or a local support issue.

Government, municipalities, enterprises, operators

Separate operating conditions, scope, and the public evidence that can be shared.

Suppliers and manufacturers

Separate product capability, service readiness, and Japan-fit questions without drifting into certification or recommendation language.

Report buyers and partners

Keep public previews, internal drafts, and source-backed deliverables separate.

Mirai Move collects only the mobility context that is relevant to the question at hand. Sensitive details are minimized, and community signals are anonymized or aggregated before public or report use.

Minimum necessary data

Collect only what is needed to explain the issue and keep the review grounded.

Private by default

Supplier-private and client-confidential material is not public by default.

Internal drafts

Report drafts and internal notes stay separated until they are ready for review.

Later gates

File upload, paid access, and live external actions remain governed by later approval gates.

Trust states

State labels used in public explanations

These are explanatory labels only; they are not workflow actions.

Public

Visible on the public site and safe to read openly.

Preview

A bounded state that is not the final output.

Internal Draft

Work in progress that stays inside the organization.

Evidence Needed

The source basis is not yet strong enough.

Founder Review

A human must see it before anything moves on.

Approved for Preview

Safe to show as a public preview.

Restricted

Still held back from external release.

This methodology page does not create certification, recommendation, procurement approval, deployment approval, or final delivery.