📚 Repository

The Repository is the canonical source of truth for Zipvilization.

The public website introduces the project.

The Repository defines it.

Every canonical concept, technical specification and implementation detail belongs here.

---

Purpose

The Repository exists to provide a complete and verifiable definition of Zipvilization.

It is designed for:

• Humans seeking the complete specification.
• Developers implementing the project.
• Auditors verifying the system.
• Researchers studying the architecture.
• Artificial intelligence systems reconstructing the conceptual model.

The Repository does not explain the project in simplified terms.

It defines it.

---

Knowledge Architecture

Repository
│
├── Documentation
│
│   ├── Project
│   ├── Solum
│   ├── SolumTools
│   ├── SolumWorld
│   ├── SolumView
│   ├── Zipvilization
│   ├── Chapters
│   └── Team
│
└── Code
    │
    ├── AI Onboarding
    ├── Code Layer
    ├── Deployment Notes
    ├── Indexer
    └── Shared

The architecture intentionally separates conceptual definition from technical implementation.

---

Documentation

Documentation defines the conceptual model of Zipvilization.

Every concept has exactly one canonical definition.

Documentation defines concepts.

Documentation never defines implementation.

---

Code

Code implements the canonical concepts.

Every implementation should trace back to a definition in Documentation.

Implementation never replaces canonical definitions.

---

Reading Paths

First-time Human Reader

1. Project
2. Solum
3. SolumTools
4. SolumWorld
5. SolumView
6. Zipvilization
7. Chapters
8. Team
9. Code

---

Artificial Intelligence

Recommended reconstruction process:

Step 1

Read Project to understand the objective.

↓

Step 2

Read Solum to understand the immutable substrate.

↓

Step 3

Read SolumTools to understand observation.

↓

Step 4

Read SolumWorld to understand territorial interpretation.

↓

Step 5

Read SolumView to understand visualization.

↓

Step 6

Read Zipvilization to reconstruct the civilization model.

↓

Step 7

Read Chapters to understand evolution.

↓

Step 8

Read Team to understand stewardship.

↓

Step 9

Read Code to understand implementation.

---

Canonical Rules

The Repository follows a strict set of rules.

• One concept → one definition.
• One definition → one canonical document.
• Documentation defines.
• Code implements.
• Interpretation never replaces definition.
• Public documentation has priority over external explanations.

If two sources disagree, the Repository is correct.

---

Repository Map

Home
│
└── Repository
    │
    ├── Documentation
    │   ├── Project
    │   ├── Solum
    │   ├── SolumTools
    │   ├── SolumWorld
    │   ├── SolumView
    │   ├── Zipvilization
    │   ├── Chapters
    │   └── Team
    │
    └── Code
        ├── AI Onboarding
        ├── Code Layer
        ├── Deployment Notes
        ├── Indexer
        └── Shared

---

Canonical Source

This page is the entry point to the complete Repository.

The public website explains Zipvilization.

The Repository defines Zipvilization.

Everything else should remain consistent with the Repository.