Current
Records and principles
Whitepaper, governance guide, product scope, Founder boundaries, and a public development record.
Starport Legends
Opening the record.
Loading verified public content
Governance principles
Starport does not use a decorative vote screen to simulate community power. The sequence is delivery, public evidence, stable operation, structured participation, and only then binding execution.
Four layers
Publish scope, decisions, changes, development context, and the reason each material choice exists.
Define who may propose, what evidence is required, how discussion works, and which matters remain protected.
Introduce verifiable eligibility and voting only after the community and product have real operating history.
Connect approved decisions to budgets or systems only with legal authority, security controls, and accountable operators.
Authority map
Current
Whitepaper, governance guide, product scope, Founder boundaries, and a public development record.
After stable operation
Community discussion and proposals around defined, supportable decisions with published evidence.
Only after readiness
Identity-gated voting, executable budgets, or treasury controls after legal, technical, security, and operating review.
Guardrails
Governance cannot compensate for the absence of a coherent game or operating practice.
Material proposals need context, costs, alternatives, risks, and an auditable decision trail.
A single financial position should not silently become unlimited control over game design or treasury decisions.
Narrative coherence, safety, legal duties, and production reality require explicit boundaries around community authority.
Early workflows should be limited, observable, and capable of being corrected before irreversible execution.
The standard
Legitimacy comes from a process people can understand: who may decide, what evidence they saw, which duty limits the choice, how the outcome is recorded, and who remains accountable for execution.
Open the governance record