How to Use This Wiki

This wiki uses relative-markdown links, a bibkey field, and typed folders.

Companion to CLAUDE.md. CLAUDE.md is the law (what the wiki is: page types,
frontmatter, templates, tag vocabulary). This file is the daily driver (how to read, write,
verify, and query
it). When they disagree, CLAUDE.md wins.

User note: This is still a living document. The wiki is brand new and evolving very quickly.

What this wiki is

A research knowledge base for a PhD thesis on a free-flying space manipulator. It compounds: you
add sources, the agent integrates them into interlinked pages, and you query the wiki, not the raw
PDFs. Page types live in typed folders — sources/ (one per paper, named by bibkey), topics/
(phenomena + techniques), results/ (named theorems / our own results), syntheses/ (evolving
overviews). Registries: notation.md (symbols), terminology.md
(terms). Proofs live in ../generated/math/; immutable source material in ../raw/.

Reading / querying (the loop)

  1. Start at index.md (static catalog) or, in Obsidian, _dashboard.md
    (live Dataview views).
  2. Find the relevant cluster; open the page; follow its related: field before searching wider.
  3. Answer from the synthesized wiki, citing bibkeys. Re-read ../raw/ only to verify a specific
    quote/equation.
  4. If a substantial answer is likely to be re-asked, file it as a synthesis page.
  5. If a query exposes a gap (a concept mentioned with no page), log it in log.md (PAGE NEEDED: …).

Writing (in Obsidian)

  • New page: Templater (⌘P → Templater: Create new note from template) → pick
    result / topic / synthesis from _templates. Date and title auto-fill.
  • Links: relative markdown only — [x](../topics/x.md). Never [[wikilinks]] (they break on
    GitHub); .obsidian/app.json locks this.
  • Symbols: render only from notation.md; if one is missing, add the row
    centrally — never coin notation per page.
  • Equations layer: wiki pages are derived from the private master
    my_writing/equations/current_sota.md — never paste it verbatim. A result page carries a
    proof-sketch and links the full proof in ../generated/math/.

Verifying (draft → verified)

Every agent-written page is review: draft. You (the human) browse drafts — the
_dashboard.md “drafts by type” view (or Dataview WHERE review = "draft") lists
them — correct them, and flip review: verified. Only a human sets verified; no page blocks any
other.

Flagging inconsistencies

When sources disagree, or a derivation was historically confused: add a one-liner to the page’s
inconsistencies: frontmatter list and an inline > [!warning] Inconsistency callout at the spot.
They auto-collect in _inconsistencies.md.

Maintaining

  • Ingest a paper: PDF → ../raw/pdf/<bibkey>.pdf, markdown → ../raw/md/<bibkey>/, add a
    ../raw/references.bib entry; then write sources/<bibkey>.md and propagate into every topic /
    result / synthesis it touches; append log.md. (Full steps: CLAUDE.md → Workflows → Ingest.)
  • Promote: settled items in INSIGHTS.md → evergreen pages at the weekly review;
    notation.md / terminology.md are promoted-to directly.
  • Lint (on request): broken relative links, invalid frontmatter, bibkey.bib mismatches,
    orphans, duplicates, thin pages. Present findings; do not auto-fix.

Where things live (map)

NeedGo to
Catalog of everythingindex.md (static) · _dashboard.md (Obsidian)
A paper’s notessources/<bibkey>.md
A concepttopics/<slug>.md
A theorem / our resultresults/<slug>.md (+ full proof in ../generated/math/)
An overview / debatesyntheses/<slug>.md
Symbols / termsnotation.md · terminology.md
Contradictions_inconsistencies.md
The schema (law)CLAUDE.md
Dataview setup detailsREADME.md
Immutable sources../raw/ (never edit)