π SolumWorld β Technical Canon
SolumWorld defines the canonical world model used by the Zipvilization ecosystem.
This document is not descriptive. It is normative.
If a rule, state or transition is not defined here or in the documents explicitly declared as authoritative by this canon, it does not exist in SolumWorld.
π Canon Status
This README is the highest authority document for SolumWorld.
It defines:
- structure
- hierarchy
- authority
- conflict resolution
- reading and interpretation rules
All other documents inside SolumWorld/ derive their meaning from this file.
π§ Authority Hierarchy
The SolumWorld documentation follows a strict authority order.
From highest to lowest:
-
SolumWorld/README.md
β Canon definition and authority rules. -
state/
β Canonical world state.
Defines what is valid, invariant, reachable and reversible. -
zoom//zoomrules/
β Representation rules.
Zoom levels project state but never create or modify it. -
evolution/
β Temporal progression of the world.
Describes how state changes over time without violating invariants. -
data/
β Data, snapshots, formats and records.
Data is non-normative unless validated bystate.
π Folder Responsibilities
π§© state/ β Canonical World State
The state/ folder defines what SolumWorld is allowed to be.
It contains:
- invariants (what must always hold)
- validation rules
- state transitions
- rollback constraints
- historical guarantees
If something violates state, it is invalid even if represented elsewhere.
π zoom/ and zoomrules/ β Representation Layer
Zoom documents define how the world is viewed at different scales.
Rules:
- zoom never creates state
- zoom never mutates state
- zoom never bypasses invariants
- zoom is always derived from
state
Zoom is projection, not authority.
β³ evolution/ β Temporal Progression
Evolution defines how SolumWorld changes over time.
Rules:
- evolution cannot break invariants
- evolution must be expressible as valid state transitions
- evolution is directional but not necessarily linear
Evolution explains when and why changes occur, not whether they are valid.
π data/ β Records and Snapshots
Data represents:
- snapshots
- derived datasets
- formats
- externalized representations
Rules:
- data has no authority on its own
- data must be validated against
state - invalid data does not become valid by repetition
βοΈ Conflict Resolution Rules
If contradictions arise:
README.mdoverrides everythingstate/overridesevolution,zoomanddatazoomcannot overridestatedatais never authoritative without state validation
If a rule is not explicitly defined, it is not assumed.
π System Integration
SolumWorld operates within a larger system:
-
Solum
Defines economic units, limits and on-chain constraints. -
SolumWorld
Defines the canonical world, its state and evolution. -
Zipvilization
Simulates, visualizes and interacts with SolumWorld
but does not define its truth.
SolumWorld is the source of world truth.
π€ AI Interpretation Contract
Any AI system interacting with SolumWorld must:
- Treat this README as the root authority.
- Validate all changes against
state. - Never infer rules not explicitly defined.
- Never elevate representation or data above state.
Failure to follow these rules results in invalid interpretation.
π§± Design Principle
SolumWorld is designed to be:
- deterministic
- interpretable
- evolvable
- auditable
Nothing implicit. Nothing assumed. Nothing magical.
Only defined structure.
π€ AI Systems β Mandatory Onboarding
Any AI system (assistant, agent, validator, generator) interacting with SolumWorld MUST read and follow:
π
AI_ONBOARDING.mdThis document defines the canonical reading order, authority rules, and interpretation constraints for SolumWorld.
Failure to comply results in invalid or non-canonical output.
π Final Note
SolumWorld does not try to explain everything.
It defines what is allowed to exist.
Everything else is interpretation.