The operating covenant

A controlled
design standard.

ARCTA uses four connected tests for every experience, claim, service and technical decision. A feature is not ready because it looks complete. It is ready when it can demonstrate Knowledge, earn Trust, protect Humanity and support responsible Action.

Explore the four tests See the stage gates

Why control matters

A controlled standard protects meaning as the ecosystem grows. It helps players, learners, partners and communities distinguish verified capability from aspiration, and gives builders a repeatable way to decide what belongs in ARCTA.

Identity control

Approved marks, coin geometry, language and interaction patterns remain recognizable across web, game, Telegram, iOS and future Android releases.

Decision control

Each material change records its purpose, evidence, owner, tests, risks, release gate and rollback. Fast work is welcome, undocumented risk is not.

Claim control

Current functionality is separated from plans. Financial, regulatory and humanitarian claims require appropriate evidence and approval before publication.

Change control

Versions are checkpointed, tested and reversible. User feedback can change priorities without erasing evidence or silently weakening safeguards.

▤

Knowledge: understand before deciding

Knowledge means more than collecting information. It requires traceable sources, clear definitions, tested assumptions and honest uncertainty. In the game, it appears as learning foundations and evidence-aware choices. In services and training, it means methods that another practitioner can inspect and adapt.

Separate observation, interpretation and recommendation.
Use primary or authoritative sources where accuracy matters.
State what is known, unknown, changing or context-dependent.
Measure learning and outcomes with understandable indicators.
Retain evidence, decisions and version history without exposing private data.

Technical application: structured content, source metadata, deterministic rules where possible, testable acceptance criteria, accessible explanations and explicit fallback behavior.

∞

Trust: make behavior inspectable

Trust is earned through consistency, consent, transparency and accountability. ARCTA does not use visual excitement to hide limitations. Status language must tell people what is active today, what is private, what is experimental and what still needs permission.

Never present a planned token, wallet or airdrop as active.
Explain data boundaries before collecting information.
Provide support, reporting and correction routes.
Use backups, release gates and rollback for material changes.
Keep promises narrow enough to verify and broad claims out of production.

Technical application: privacy-safe defaults, visible focus states, release evidence, security checks, current-facts pages, failure messages and recoverable progress.

◎

Humanity: protect dignity and agency

Humanitarian service begins with people, not systems. ARCTA should encourage curiosity and action without exploiting urgency, vulnerability or personal identity. Participation must remain understandable, voluntary and proportionate.

Design for accessibility, low bandwidth and varied digital confidence.
Minimize personal data and avoid unnecessary identity linkage.
Use respectful, non-stigmatizing language and imagery.
Invite community feedback before claiming community readiness.
Make risk, consent and exit choices clear.

Technical application: semantic HTML, keyboard access, reduced-motion support, responsive layouts, readable type, touch-safe controls and privacy-preserving progress.

⌁

Action: turn insight into accountable progress

Action is deliberate movement toward a defined outcome. It connects learning to practice, assigns responsibility and measures whether a change helped. Activity without an outcome is not impact.

Define the problem, audience and desired change.
Choose the smallest safe intervention that can be tested.
Assign ownership, timing, resources and stop conditions.
Measure outputs, outcomes, unintended effects and learning.
Adapt, document and share what changed.

Technical application: short feedback loops, meaningful game goals, measurable completion, production validation, incident handling and documented next actions.

Technical and behavioral controls

Control	Required behavior	Evidence
Content integrity	Current facts and plans are clearly separated.	Source, review date, owner and status.
Visual identity	Approved assets and consistent hierarchy across platforms.	Asset manifest, responsive review and screenshots.
Accessibility	Keyboard, focus, contrast, touch and reduced motion work.	Automated checks plus human interaction review.
Performance	Critical content loads quickly and motion avoids layout shifts.	Build output, network review and device testing.
Privacy and safety	Collect only what is necessary and protect recovery paths.	Data map, threat review and deletion controls.
Release control	Material changes are tested, checkpointed and reversible.	Version, tests, backup, rollback and approval record.