CLAUDE

05 Aug 2026 -
Open in Logseq
    • CLAUDE.md This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

    • What this repo is This is not a software project. It is Mike's personal Logseq knowledge base, codenamed "AMMDI" — a plain-text, git-backed outliner wiki of journal entries and topic pages. There is no build, lint, or test tooling; there is nothing to compile or run. Work here consists of reading and editing Markdown outline files. Deploy path (for context, not something to run from here): this repo → goddinpotty (a static site generator, separate repo) → ../hyperphor-git/ammdi → published to a server.

    • Structure

    • journals/ — one file per day, named YYYY_MM_DD.md (e.g. 2026_08_05.md). Freeform daily notes, dream logs, reading notes, work log entries (often under a # WorkDay heading).
    • pages/ — one file per topic/entity, named after the page title (e.g. 'Pataphysics.md, [Article Title](url).md). This is the bulk of the content — thousands of notes on books, people, concepts, projects, and clipped web articles.
    • assets/ — images and other files referenced from journal/page content.
    • whiteboards/ — Logseq whiteboard files (.edn).
    • draws/ — Excalidraw drawings.
    • logseq/ — Logseq's own config and metadata (config.edn, custom.css, pages-metadata.edn, etc.), plus bak/ and .recycle/ backup dirs generated by the app. Don't treat files under logseq/bak/ or logseq/.recycle/ as live content.
    • bin/autogit.sh — an unused helper (superseded by Logseq's own auto-commit); not part of any active workflow.
    • .obsidian/ — leftover config from an abandoned experiment trying Obsidian as an alternative viewer (see Obsidian.md for notes on why that didn't stick). Logseq is the tool actually in use.
    • File format conventions Files are Markdown outlines (bullet-per-block), matching how Logseq itself writes them:

    • Every top-level bullet is a block; nesting (tabs) represents outline hierarchy.
    • Blocks often carry Logseq metadata directly under the bullet text: `id::`, `created-at::`, `updated-at::` (and similar `key: value` property lines). Preserve these when editing existing blocks rather than stripping them.
    • [[Page Name]] is a wiki-link to another page in pages/; #tag is an inline tag. Page files may start with a ---\ntitle: ...\n--- front-matter block when the page title contains characters that don't match the filename directly.
    • Clipped web articles are typically named after the article title/URL and begin with a source link.
    • Journal entries use # WorkDay and similar inline headings to demarcate sections within a day.
    • A convention exists for tagging AI/Claude-authored blocks so they're visually distinguishable from Mike's own writing (see pages/Claude.md) — if asked to add content into journals/pages, mark it accordingly rather than blending in silently.
    • Working in this repo

    • When editing or adding notes, match the existing outline style (bullet blocks, nesting, property lines) rather than converting to prose or restructuring pages.
    • Don't "clean up" id::/created-at::/updated-at:: metadata — it's load-bearing for Logseq's block references and backlinks.
    • Avoid modifying anything under logseq/bak/, logseq/.recycle/, or .obsidian/ — these are tool-generated or abandoned, not authored content.
    • This repo is excluded from gitweekall reporting (see .noreport).