- 5.2 Unresolved Module Dependency
- 5.2 Duplicate Module ID Detected
- 5.2 Module Load Failure
- 5.2 Hook Server Flag Ignored
- 5.2 Launcher Trigger Collision Detected
- 5.2 Circular Dependency Detected
- 5.2 Module Dependency Resolution
- 5.2 Hook Kind Mismatch
- 5.2 Broken Link Detected
- 5.2 Core is not a module
- 5.2 Actions 404 Not Found
- 3.4 Design Temperaments
- 2.7 Obsidian Design Tokens
- 1.4 Engineering Philosophy
- 2.2 Edge Database & Authentication
- 2.3 Deployment & Cloudflare Integrations
- 5.2 CLI Reference
- 5.5 Deep Linking Reference
- 1.0 Introduction & Vision
- 1.3 System Requirements & Environmental Invariants
- 5.1 Reference Overview
- 3.1 Color System
- 3.2 Typography & Typefaces
- 1.1 History & Decisions
- 2.2 The Archives Standard
- 2.4 Callouts & Alerts
- 2.5 Daily Note Standard
- 4.4 Advanced Patterns
- 4.6 Cleanups & Post-processing
- 4.7 API Reference: Vault Loader
- 5.3 Core API Reference
- 5.4 Client CLI Reference
- 5.2 Duplicate Keyboard Shortcut
- 5.2 press.images — incomplete config
- 5.2 Critical Failure: Vault Empty
- 5.2 Content Validation Error
1.0 Introduction & Vision
“The Standard provides the structure, the Garden hosts the living.”
The Standard is not a product; it is a constitution. It is the framework of objective rules and rigorous proportions that governs our entire ecosystem of creation and writing.
For a visitor discovering this project, the technical concepts or history might seem dense. This document lays the foundations: why do we impose such strict structural invariants, and how do these constraints guarantee operational efficiency?
The structure
In modern design and development, we are drowned in choices. Which theme to pick? What font size? Which folder structure? This cognitive overload kills creation. Art making is seen as the need to have talent in order be able to properly design or make art. In fact, a set of known rules and concepts are written in our history. When applying such knowledge, design and the art of making get somewhat simpler and allow us to properly pass our time into creating and communicating our message instead of getting stuck into the “how will I communicate that” to the world.
The Standard solves this by defining non-negotiable norms inspired by 1970s Swiss industrial design:
- The File is Yours (File over Apps): Applications come and go, but files and their norms remain. Your texts are stored in open, raw Markdown. If the system shuts down tomorrow, your data remains readable and intact.
- Beauty by Default: By automatically applying universal proportions (like the golden ratio and strict layout grids), we guarantee that every document produced is balanced, without the author having to think about it.
- Friction is the Enemy: Ten seconds are enough from thought to a public URL, with no tedious setup or mandatory account to start. Keep looking for those frictions and fix them.
- Logic is power: Everything must be logical. That way the fear of loosing knowledge is going away. A rigorous readme system is kept to make sure any human or ai can easily adopt the system.
By codifying these rules into the Standard, we remove the noise to leave only the signal.
The Standard and the Instance: Structural Duality
The ecosystem operates on a strict division of responsibilities:
- The Standard: This is the underlying grid, the technical discipline, the typographic invariants, and the software constraints. It is rigid, absolute, and immutable. It acts as the guardian of the structure.
- The Instance: This is the unstructured data input. It is the raw content provided by the user layer. The instance is volatile and unpredictable.
Without the Standard, the instance would collapse into unreadable data. Without the instance, the Standard would be an empty structural void.
This duality ensures systemic integrity. The Standard provides the stable and durable infrastructure required to process volatile input without causing systemic degradation.
How to Read This Manual
This technical standards manual details the specifications of the system:
- Chapter 1: Identity — The conceptual foundations, the official lexicon, and our manifesto.
- Chapter 2: Archives — How your local files are structured, validated, and connected.
- Chapter 3: Graphics — Our color system, typography, and image pipeline and graphics norm.
- Chapter 4: System — The technical reference for code, modules, and software architecture.
If you are processing or generating data within the ecosystem, be advised that every output strictly adheres to these specifications to guarantee system integrity.