Repository navigation
id: design: native graph model & navigation API (from #5677) #5831
Description
Summary
Follow-on design ticket from #5677 — 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
Traversals over the note/board graph with parity across CLI, script, and agent surfaces, and pagination rules.
Context from the parent
The parent design fixes the note↔board reference model, the merge model, the sovereignty rule, and the approval flow for notes, message boards, and multiplayer editing. 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: #5677. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
Activity
developing-today commentedon Nov 5, 2026
CODE-1514
dezren39 commentedon Nov 5, 2026
🤖 Agent note · picked up
dezren39 commentedon Nov 5, 2026
🤖 Agent note · triage complete
Triage of issue #5831 at current main (verified fresh 2026-11-05):
app/id). No hard-stop labels, no design content beyond the filing stub, no implementation or PR references it. Expected output per its body: a recorded decision (chosen shape, alternatives rejected and why, invariants implementation must hold).queue/queued, not parked or escalated). The parent fixes the note↔board reference model, merge model, sovereignty rule, and approval flow — decisions id: design: native graph model & navigation API (from #5677) #5831 must build on, not re-decide.Ordering (the substantive triage finding): unlike most of its siblings, #5831 goes first in this set — it is the foundational design, not a consumer:
Designing any sibling before #5831 risks each inventing its own graph assumptions, which is exactly the fork the filing pattern warns against.
Blockers recorded: none hard — the sequencing above is the only ordering constraint, and the parent decisions #5831 depends on are already recorded in #5677. No Drew decision is required to start this design. Issue #5831 stays open as the design ticket; implementation timing is a separate decision per the filing note (programme epic #2056).