⚠ DRAFT · UNPROMOTED · UNVERIFIED — not the published Atlas · facts/citations not gate-checked

Wiki Framework — how this works & how to reuse it

This Obsidian vault was generated, not hand-built. It is the reusable framework layer for Aesthetic Atlas and any other master's-degree course built on this engine (see ../../docs/METHODOLOGY.md).

Structure

Frontmatter contract (powers graph, filtering, Dataview)

Every theme note carries: type, id, domain, status counts (slides/books/articles/videos), subchapters, covered_subs, new_subs, maps_to, tags. Tags: #theme, #domain/, #status/....

Regenerate (authored chapters are preserved)

From the repo root:

PYTHONPATH=. .venv/bin/python scripts/atlas_gate.py wiki --built

It rebuilds the whole vault from docs/curriculum/curriculum.json. Edit the curriculum doc → re-run curriculum then wiki.

Preservation contract. The generator owns the frontmatter, the subchapter checklist, the source block and the ## Navigate footer — those are recomputed every run. Everything between the ## Chapter heading and the final ## Navigate is yours and is spliced back in verbatim; the run reports chapters_preserved. Two consequences: - Write the chapter under ## Chapter, never above it. Content placed outside that block (e.g. appended after ## Navigate) is generated territory and will be discarded. - If a theme note loses its ## Chapter heading the build stops with PreserveError rather than overwrite it. Restore the heading, then re-run.

Renaming a theme in the curriculum changes the note's filename, so the chapter does not follow it: the old file stays on disk and a fresh stub appears under the new name. Move the chapter across by hand, then delete the orphan.

Reuse for another course

  1. Point atlas/config/paths.toml + curriculum doc at the new course.
  2. Run catalogcoveragecurriculumwiki.
  3. No code changes — this generator is domain-agnostic.