Repository navigation
id: design: tagging-as-triples alignment with #2048 (from #5688) #5912
Description
Summary
Follow-on design ticket from #5688 — its decomposition sketch names this as a separate design, and the parent's acceptance requires these tickets to be filed and linked. Filed in the 2026-11-04 gap pass (WS-F) so the design work exists and can be prioritised on its own merits; implementation timing is a separate decision, possibly months out.
What this design must settle
Confirm the zettelkasten layer's tagging model is the triple model of §2.5 of the parent, and reconcile any divergence between #2048 and the triple design.
Context from the parent
The parent design fixes KDL as the human presentation format over ID data, decomposition into atomic triples, and ANSI SQL/PGQ querying. The parent issue carries the surrounding decisions this ticket must not re-decide; where this ticket's answer would change a parent decision, record that explicitly rather than silently forking it.
Decision record expected
Close this design with a recorded decision (on this issue or in a doc/ record linked from it): the chosen shape, the alternatives rejected and why, and the invariants implementation must hold. If the design splits further, file the splits and link them here rather than growing this issue.
Relations
Parent: #5688. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Acceptance criteria
- A design note (on this issue or a linked design doc) states whether the zettelkasten tagging model is exactly the triple model of §2.5 of id: design: KDL as human presentation format + triples + ANSI graph SQL (SQL/PGQ) for ID data #5688, naming any divergence found against id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048.
- Every divergence is either reconciled in the design or recorded explicitly as a change to a parent decision (per the parent-context rule in the summary), not silently overridden.
- The design names the migration/compat implication for existing tags, or states there is none with evidence.
Activity
developing-today commentedon Nov 5, 2026
CODE-1595
dezren39 commentedon Nov 5, 2026
Intake review — fleet monitor, 2026-11-04
Related: parent #5688 (decomposition source), #2048 (tagging model to reconcile against). Risks: silently re-deciding a parent decision — the summary's record-explicitly rule is the guard. Suggested approach: diff the zettelkasten tagging model against §2.5 triple model first, list divergences, then reconcile or escalate each one.
Live-check: no merged PR or commit was found that resolves this design ticket (it was filed 2026-11-05T02:00Z as part of the #5688 decomposition); it is not a duplicate of its siblings, which cover distinct design questions. Labels normalised this pass: kind/design, priority, effort/m, status/needs-triage, meta/enriched; an Acceptance criteria section was appended to the body (original text preserved verbatim above it).
123 remaining items
dezren39 commentedon Nov 6, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 6, 2026
🤖 Agent note · picked up