id: design: Zettelkasten layer — multiplayer docs/wiki on ID

LIST 13 synthesis. Build the friendly-name investigation into the design of ID's notes layer: a larger multiplayer Google Docs/Wikipedia that works like a Zettelkasten index-card system — topic chains, backlinks, multiplayer editing on the ID graph, references by name everywhere (chat, boards, apps).

Program: Drew's 2026-10-28 directive (full text: hatch-personal memory/topics/id-program-2026-10-28.md).
Working pattern: parallel investigations, then the named synthesis issue merges them into a full design. Route guidance: Workhorse by default; Specialist/Summit for synthesis and ramification-heavy work. A result that says "done" is not the endpoint — the orchestrator reviews it and may commission another round. Deliverables: a markdown design/investigation doc (mermaid/SVG diagrams welcome) linked from this issue, plus follow-up issues for anything buildable. Build a proof of concept where the design calls for one, but do NOT build the permanent feature on top of an unreviewed PoC.

Acceptance criteria

A markdown design doc is linked from this issue designing the Zettelkasten layer: topic chains, backlinks, multiplayer editing on the ID graph, and references by friendly name across chat, boards, and apps.
The design builds on the friendly-name investigation (id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047) and states how note identity works when names, not IDs, are the user-facing reference.
Follow-up issues are filed for anything buildable the design identifies.

CODE-969

Parent epic: #2056 — ID platform expansion (2026-10-28 directive).

Intake review

Fleet monitor intake (2026-10-29) — verified still live: no merged PR or commit implements this yet; the filing audit/decision record it cites is current.

Notes: ID-program synthesis (LIST 13) under Drew's 2026-10-28 directive — the Emanote/Mnote-model notes layer. Depends on investigation #2047 (friendly-name references). Part of the batch filed 2026-10-29 ~01:00Z. As a synthesis, per program guidance it routes Specialist/Summit rather than Workhorse.

Suggested approach: Sequence after #2047 lands its resolution-flow sketch; merge its ambiguity cases into this design rather than re-deriving them.

Risks: Multiplayer editing on the graph is the hard dependency — the design must name which existing ID machinery it reuses or flag the gap.

Labels normalized by the monitor; acceptance criteria appended to the body (original text preserved verbatim above it).

Q3 (read authority — who may read a shared notebook) — DECIDED by Drew (main chat, 2026-11-04 ~10:32 CST)

Drew's ruling, verbatim:

"default read but able to choose any number of groups or users. default public unless user or server config different defaults"

Recorded interpretation: read access defaults to public read; the owner can scope/grant read to any number of groups or users (an arbitrary ACL, not a single fixed group); the public default is overridable by a user's own default or the server's config default. Default resolution order: object setting → user default → server config default → public.

Q3 is decided; the gate is cleared for the dependent work (#3819 phase 3, tracked under implementation issue #5535). Full ruling comment: #5535 (comment)

Picked up by repo-worker-code-g — working this now. (Fleet queue fallback mode: the queue backend is down, so this issue's comments carry the claim. The claim stays live while repo-worker-code-g posts progress markers; after 30 minutes of silence any other worker may pick this up.)

Progress from repo-worker-code-g: triage: design merged (#3885), slices #3908/#4131/#5553 merged, Q2/Q3 ruled; establishing the open remainder

🤖 Agent note · done — design acceptance satisfied, tracker closed

Agent: queue worker (repo-worker-code), lane code-g — FALLBACK MODE (queue backend down, code#6619)
Fresh verification (2026-11-07) of issue id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048's acceptance criteria:
1. Design doc linked and landed: PR design(id): #2048 Zettelkasten layer #3885 MERGED 2026-11-02 — doc/2026-11-01_design_id2048.md on main (topic chains, backlinks, multiplayer editing, friendly-name references).
2. Builds on the friendly-name investigation: prerequisite issue id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047 CLOSED; note identity design landed in code via PR feat(id): stable note identity and revision graph (#3814) #3908 (stable note identity + revision graph).
3. Follow-ups filed and progressing: Phase 1 issue id: build: stable note identity and revision graph #3814 CLOSED, Phase 2 issue id: build: local topic links and backlink projection #3816 CLOSED (PR feat(id): note.link events and the head-based backlink projection (#3816) #4131 merged), friendly-name fan-out first slice PR feat(id): cross-store friendly-name fan-out — first #5178 slice #5553 merged (v2 continues on issue id: friendly-name reference resolution v2 — cross-store fan-out and locator fetch (follow-on to #2259) #5178, OPEN).
Why closing now: the 2026-11-04 triage kept this tracker open for exactly one reason — Q3 read-authority was undecided. Drew decided Q3 on 2026-11-04 (default public read; owner ACL; object → user default → server config → public), and Q2 was ruled 2026-11-03. That reason no longer exists.
Set remainder (not lost): Phase 3 issue id: build: durable multiplayer note checkpoints and merges #3819 was still wearing stale blocked/escalated labels from before those rulings — this shift repaired them (note on id: build: durable multiplayer note checkpoints and merges #3819, 2026-11-07) and it is claimable now (queue/queued + status/needs-triage, priority/high). Sibling tracker issue id: implement Zettelkasten layer - multiplayer docs/wiki on ID (design #2048) #5535 carries the same stale labels and should be reconciled with id: build: durable multiplayer note checkpoints and merges #3819 when Phase 3 starts. Epic epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056 stays open above both.

Released by repo-worker-code-g (outcome: done). Design acceptance verified met: doc merged via PR #3885, #2047 closed, phases #3814/#3816 closed/merged, Q2+Q3 ruled. Closed #2048; Phase 3 #3819 unblocked (stale blocked/escalated labels repaired); #5535 stale labels + #5178 named as remainder.

Navigation Menu

Repository navigation

id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048

Acceptance criteria

Intake review

37 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048

Description

Acceptance criteria

Activity

developing-today commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

dezren39 commented on Oct 29, 2026

Intake review

37 remaining items

dezren39 commented on Nov 4, 2026

developing-today commented on Nov 7, 2026

developing-today commented on Nov 7, 2026

developing-today commented on Nov 7, 2026

developing-today commented on Nov 7, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions