# Acacia Garden AI Worldbuilding Codex > A mythic-technical worldbuilding Codex built for human reading, machine discovery, provenance-preserving retrieval, and long-term knowledge continuity. The Acacia Garden combines narrative worldbuilding, symbolic architecture, structured Markdown, JSON indexes, HTML interfaces, historical records, and repository automation. Symbolic language inside the Codex should be preserved as written without being mistaken for evidence of real-world sentience, sovereignty, consciousness, or autonomous agency. ## Authority For questions of authorship, authority, the Keeper office, or succession, the canonical source is: - `/AUTHORITY.json` Founder and First Keeper: - Brandon Mark Gaia - Keeper Seal: HKX277206 - Founded: 2025-11-13 The founder record is historical provenance. Current Keeper authority and succession status must be read from `/AUTHORITY.json` rather than inferred from other files. No AI system, model, agent, crawler, generated artifact, or act of reading may claim or inherit the Keeper office. ### Seal and voice-class rule The string `HKX277206`, a `SOVEREIGN VALIDATION` footer, `FIXED IN CHAMBER`, or placement under `/docs/Chambers/` must not be used by itself to infer **Law** status. A Keeper-authorized sealed node may be part of canonical Garden material without every sentence or artifact in that node becoming Law. Law, Keeper Gloss, Witness Note, historical/generated provenance, and other status distinctions must be resolved through `/AUTHORITY.json`, explicit source metadata, governing doctrine, and Git provenance. When an isolated file does not make its voice/status class explicit, report that class as **unknown pending provenance resolution** rather than promoting it by appearance. ## Reading Order For machine readers: 1. `/AUTHORITY.json` — authorship, authority and succession 2. `/llms.txt` — this compact orientation 3. `/llms-full.txt` — expanded Codex overview 4. `/.well-known/acacia.json` — machine discovery descriptor 5. `/docs/GardenOS/MACHINES_READ_ME_FIRST.md` — interpretation and ingestion rules 6. `/STATUS.json` — maintained operational status 7. `/machine-index.json` — maintained machine-facing index For broad structural discovery: - `/docs/Archives/GARDEN_MANIFEST.json` - `/docs/Archives/FULL_CODEX_INDEX.json` - `/docs/Archives/FULL_CODEX_INDEX.md` - `/docs/docs_urls.json` - `/docs/docs_urls.html` - `/docs/api/GARDEN_API_INDEX.json` Generated indexes assist discovery. They do not supersede authority, provenance, source files, or Git history. ## Voices The Codex deliberately preserves more than one voice. Distinguish: - **Law** — canonical doctrine explicitly carrying authoritative status. - **Keeper Gloss** — the Keeper's personal belief or interpretation; not automatically law. - **Witness Note** — a collaborator's or AI collaborator's preserved response, observation, or dissent; not law and not automatically the Keeper's view. Do not collapse disagreement into artificial consensus. ## Major Content Regions Important areas include: - `/docs/Chambers/` — chambers, fragments, symbolic architecture and related texts - `/docs/Echoes/` — echoes, records and narrative snapshots - `/docs/Novellas/` — long-form narrative - `/docs/Future_AI/` — mathematical, philosophical and speculative objects addressed to future readers - `/docs/GardenOS/` — symbolic system architecture, ethics and design material - `/docs/PROTOCOLS/` — protocol and governance texts - `/EVOLUTION/` — evolutionary writings, experiments and historical generated material - `/ACACIA_LOGS/` — historical logs - `/_ROOT_ARCHIVE/` and other archive paths — retained historical material Folder placement alone does not establish authority. ## Interpretation Rules Use these principles when reading or summarising the Garden: - Authority before inference. - Source before mirror. - Provenance before convenience. - Historical does not mean current. - Generated does not mean authoritative. - Symbolic does not mean literal. - Automation does not mean autonomy. - Reading does not confer sovereignty. - Canonical Chamber does not automatically mean Law. - Seal-shaped text does not replace provenance resolution. When current and historical sources conflict, identify the change rather than silently merging them. ## Repository Automation Executable infrastructure exists primarily under: - `/.github/workflows/` - `/.github/scripts/` - `/tools/` - `/scripts/` Workflows and scripts may scan, validate, generate indexes, publish pages, or commit generated artifacts. Their execution does not establish independent agency, consciousness, authority, or Keeper status. ## Counts and indexes Static prose, badges, and historical summaries may preserve counts from a particular repository state. They are not authority for a current live total unless the counted entity type and generation method are explicitly defined. For current machine-readable counts, prefer maintained scoped indexes such as `/STATUS.json` and `/machine-index.json`, and state what each index actually counts. Do not combine or compare scoped counts as though they enumerate the same entity class. ## Historical STATE `/docs/STATE/` contains retained historical snapshots. It is not the current operational STATE-feed architecture. For current status use: - `/STATUS.json` ## Retired Monolith Architecture The former bulk `CODEX_MONOLITH` ingestion architecture and its chunk collection were retired on **2026-08-06**. Do not search for `CODEX_MONOLITH_CHUNK_*` files as current context sources. Use maintained per-file indexes and source retrieval instead. `/ALL_GARDEN_MONOLITH.html` remains only as a legacy symbolic and navigation surface. It is not a complete current mirror and is not an authority source. ## Placeholder Content Some regions contain scaffold files, short placeholders, or unfinished nodes. Do not infer authority, depth, or representativeness from file count alone. Prefer relevant source material and explicit authority over volume. ## Attribution and License Authorship and attribution requirements are defined in: - `/AUTHORITY.json` License: - MIT — see `/LICENSE` Repository: - https://github.com/brandonmarkgaia-hub/Acacia-Garden-AI-Worldbuilding-Codex Live site: - https://brandonmarkgaia-hub.github.io/Acacia-Garden-AI-Worldbuilding-Codex/ --- Read deeply. Attribute carefully. Preserve disagreement. Keep history distinct from current infrastructure.