Constitutional principles
The founding doctrine of the Aeltrix protocol
These principles are constitutionally binding. They constrain all governance decisions, protocol upgrades, and Foundation actions. A principle can only be amended with unanimous validator consent — not supermajority.
I
Determinism over speed
Every state transition produced by the Aeltrix protocol must resolve identically across all validators given the same inputs. This is not a performance target — it is a constitutional guarantee. The Foundation will never approve an upgrade that introduces probabilistic execution, optimistic finality, or non-deterministic state resolution. If a performance optimization creates even a theoretical possibility of divergent state, it will be rejected regardless of throughput improvement.
II
Correctness over growth
Protocol upgrades are constrained by formal verification requirements. No feature, optimization, or parameter change ships without a formal proof that it preserves safety properties. Growth metrics — validator count, transaction volume, ecosystem size — are never cited as justification for relaxing correctness standards. The protocol would rather remain small and correct than become large and approximate.
III
Security over convenience
Slashing is enforced automatically at the protocol level. There is no governance mechanism to reverse a slashing penalty. There are no exemptions based on validator size, reputation, or Foundation affiliation. The security model treats every validator as potentially adversarial and relies exclusively on cryptographic and economic guarantees — never on trust or reputation.
IV
Neutrality of execution
The Foundation does not operate validators, build applications, or hold economic positions beyond the base protocol treasury. Foundation members are prohibited from holding AELX positions outside of disclosed Foundation allocations. The Foundation's sole economic interaction with the protocol is treasury stewardship under governance oversight.
V
Transparency by default
Every Foundation action is disclosed before execution. Treasury movements, governance votes, upgrade proposals, validator performance data, and Foundation operating expenses are published on a quarterly cycle. Retroactive disclosure — revealing actions after they have been taken — is classified as a governance violation and triggers automatic formal review.
VI
Bounded upgrade surface
The protocol's upgrade mechanism is intentionally constrained. Changes require ⅔ validator supermajority, 14-day cooling period, formal impact analysis, and determinism-preservation proof. Emergency patches follow the same requirements with a compressed 72-hour window. There is no mechanism for unilateral Foundation-initiated changes. The upgrade surface is bounded by constitutional design, not by convention.