The road guide

A responsible ecosystem,
built in stages.

ARCTA grows only when the previous stage is useful, understood and governable. Gameplay is live today. Personal progress is private. Community and regulated infrastructure advance only through separate evidence, consent, legal, security and technical gates.

Follow the stages Official current facts

Active now

Play and learn

The first stage is a real playable learning experience. Players explore the Community Base, complete missions and practice decisions through Knowledge, Trust, Humanity and Action. The goal is useful engagement, not financial speculation.

Purpose: Make serious learning approachable, memorable and action-oriented.
What exists: Web and Telegram gameplay, private progress, missions, Field Run and learning foundations.
Measures: Completion, comprehension, accessibility, performance, return play and quality feedback.
Gate forward: Stable cross-platform behavior, truthful onboarding, safe data handling and demonstrated learning value.

Excluded: purchase pressure, public investment claims, transferable rewards and guaranteed future benefits.

Protected foundation

Private progress

Progress should help the player, not profile the player. ARCTA uses privacy-aware records for missions, practices and recognition. Recovery and export capabilities should remain understandable, limited and reversible.

Purpose: Support continuity, reflection and mastery without creating a public financial identity.
Controls: Data minimization, anonymous or private defaults, clear recovery, export and deletion choices.
Measures: Recovery reliability, deletion integrity, user comprehension and absence of unnecessary personal data.
Gate forward: Reviewed privacy model, security validation, incident response and transparent consent for any new linkage.

Excluded: hidden identity matching, sale of player data, public scoring and automatic wallet linkage.

Evidence before scale

Community readiness

Community readiness is not declared by a product team alone. It is established through listening, representative testing, accessible participation, documented concerns and clear decisions about what should or should not proceed.

Purpose: Connect the ecosystem to real learning needs and responsible humanitarian practice.
Methods: Small pilots, structured feedback, safeguarding review, accessibility testing and partner due diligence.
Measures: Who participated, whose voice is missing, harms found, changes made and unresolved objections.
Gate forward: Documented demand, governance capacity, community consent where applicable and operational readiness.

Excluded: manufactured urgency, token-led recruitment, unverifiable impact claims and replacing local judgment with game scores.

Not active

Future regulated infrastructure

A future token, wallet or airdrop is a separate regulated and security-sensitive project. It cannot be activated by design work, community interest or technical possibility alone.

Required first: Jurisdiction-specific legal review, governance approval, threat modeling, economic design, custody decisions and independent security testing.
Public clarity: Eligibility, exclusions, risks, tax implications, supply, control and complaint routes must be understandable before participation.
Technical gate: Audited contracts and infrastructure, monitored release, incident response, backup and tested rollback.
Decision rule: If safe, lawful and useful operation cannot be demonstrated, this stage does not launch.

Current status: inactive. No gameplay activity guarantees eligibility or financial benefit.

How stage decisions are made

Every transition applies the same controlled standard and records what evidence supports the decision.

Knowledge gate

Is the need understood? Are claims sourced? Are risks, assumptions and unknowns visible?

Trust gate

Can people inspect the status, rules, data use, accountability and failure response?

Humanity gate

Does the change protect dignity, agency, accessibility, safeguarding and community voice?

Action gate

Are responsibility, resources, measures, stop conditions, backup and rollback ready?

Road guide acceptance record

Decision	Minimum evidence	Stop condition
Expand gameplay	Stable build, accessible use, meaningful feedback and privacy-safe operation.	Material safety, performance or comprehension failure.
Connect community programs	Defined audience, safeguarding, consent, partner capacity and outcome measures.	Unresolved harm, exclusion or misleading benefit claims.
Add identity or wallet linkage	Legal basis, data map, security model, explicit consent and deletion path.	Unnecessary collection or unmanageable identity risk.
Activate regulated infrastructure	All legal, governance, security, economic and operational approvals.	Any missing approval or untested critical control.