Core principles
A City Template is built on human validation.
Every city structure is reviewed, refined, and maintained by people who understand local context, not by automated aggregation or engagement-driven logic.
The system prioritizes:
- contextual accuracy
- relevance over completeness
- clarity over persuasion
There is no host bias, affiliate influence, or promotional placement shaping the structure of a city.
Independence by design
City Templates and Packs operate without:
- advertising layers
- sponsored visibility
- referral or recommendation economies
Content is not ranked, promoted, or surfaced based on incentives or clicks.
The goal is simple: help users understand a city, not push them toward decisions.
A city, structured in layers
A City Template organizes urban information into clearly defined sections from arrival to everyday navigation.
Examples include:
Arrival & Airport Flow
Accommodation Logic
Cultural Norms & Behavior
Weather & Packing Guide
Cost Benchmarking
Services & Official Resources
In total, a city is represented through 28 distinct sections, each designed to answer a specific, practical question.
Structure enables creativity
The City Template does not dictate tone, style, or perspective.
It defines structure. Creators bring meaning.
This allows:
- multiple perspectives to coexist
- different travel intentions to be addressed
There is no single “official” narrative of a city.
Packs built on top of the City Template
Packs do not reproduce a small City Template.
They focus on specific contexts, use cases, or travel intentions but always grounded in the same city structure.
This ensures that:
- packs remain comparable across cities
- information stays anchored
- exploration never loses orientation
Designed for continuous improvement
The system is designed to favor quality over volume.
- Fewer, well-maintained packs are preferred
- Redundancy is discouraged
- Updates matter more than accumulation
To support this, Packs operate within defined lifecycles:
- time-bound relevance
- seasonal renewal
- continuous refinement
The structure encourages contributors to return, improve, and evolve content over time.
Built together
A city is not built by a single contributor.
The City Template encourages collaboration, shared responsibility, and mutual support - without hierarchy or ownership claims.
Roles exist to maintain structure, not to establish dominance.
System alignment
To support long-term quality and maintenance:
- usage-based reward mechanisms exist
- the Keeper Stability Pool (KSP) provides continuity
These systems are designed to align contribution with real impact
