Logseq/Journal

• Logseq Journal

  • How a day reads in this garden: Person/codekiln's own writing up top, the recurring sections, and the end-of-day change log. An agent writes the change log and nothing else here — the blocks above it are Person/codekiln's, neither written nor removed by an agent. The conventions live here in one place; subpages carry section-specific detail. Parallels Logseq/Entity.

  • Change log — Filed and Updated

    • Each day ends with a record of what changed in the graph, as two top-level blocks:
      • Filed — pages that first appeared today.
      • Updated — pages that already existed and were edited today.
    • Filed and Updated are sibling top-level blocks — no parent wrapper and no intro line above them.
    • The line form is - # [[Filed]], with the bullet, which is the plurality across the graph and the only common form satisfying the bullet rule in .claude/rules/logseq-core.md. Where a journal's first line has lost its bullet, an editor save ate it rather than a person choosing.
    • A page appears under only one section per day. A page that was both created and edited today stays under Filed only.
      • mise run logseq:journal:lint reports journals that list a page under both sections; pass journal files to check only those.
    • Lines are link-only: - [[Some/Page]]. No Created … / Updated … boilerplate and no inline action text; add at most one short child sentence when it genuinely helps a reader.
    • This is a curated snapshot of the day's adventures — a Now/Page glimpse, not a full audit of every git change. Skip trivial stubs and noise.

    • Grouping

      • When a section runs past a handful of links, cluster them under plain-text labels — bare words or short phrases (tuis, entities, git tasks), not [[wikilinks]].
      • Choose labels with the human; they should jog memory and name the day's real clusters of discovery, not generic bins.
      • Labels are alphabetized, under Filed and under Updated alike. Items inside a label keep semantic order. The narrative above the change log is ordered however Person/codekiln wrote it and is left alone. This holds for 2026-08-25 Tue onward; a journal already written stays as it is.

  • Narrative and section titles

    • Above the change log, a day may carry topic-led blocks with editorial-style titles, and Person/codekiln writes those. Logseq/Journal/Editorial headings describes how they are titled, for their use rather than an agent's. Three agent-written narrative blocks were deleted by hand from the 2026-08-18 Tue journal, and an agent following that page reproduced the deletion again on 2026-08-24 Mon.
    • Logseq/Journal/Section/Friction describes a section Person/codekiln wrote once, on 2026-03-25 Wed, and no journal has carried since. Write it when they ask for it rather than expecting it in a day.

  • Worked example

    • journals/2026_06_27.md — a topic-led narrative block up top, then Filed and Updated as top-level blocks with grouped, link-only lists.