Files

Dasemu 40631362b3 Initial import of LogDarioSeq baseline

Establishes version control for the personal Logseq DB fork before
starting the server-client architecture migration and domain features
described in docs/agent-guide and the approved implementation plan.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-25 15:32:15 +02:00

cli

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

commands

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

core

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

domain

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

formatting

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

platform

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

runtime

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

dune

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

README.md

Initial import of LogDarioSeq baseline

2026-08-25 15:32:15 +02:00

README.md

Spec Layout

The spec virtual library is organized by capability boundary instead of an abstract layer number.

Dependency direction:

core -> domain -> runtime/formatting -> commands -> cli

Rules:

core contains primitive shared contracts and must not depend on other spec groups.
domain contains Logseq domain model contracts and may depend on core.
runtime contains external runtime boundaries such as transport, server, and auth state. It may depend on core and domain.
formatting contains presentation and shared formatting contracts. It may depend on core and domain.
commands contains command contracts. It may depend on core, domain, runtime, and formatting.
cli contains top-level CLI assembly contracts. It may depend on lower groups.
Command modules should not depend on each other. Move shared command data to domain or a clearly named shared contract before adding cross-command dependencies.