id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model)

LIST 13a. Like Drew's Emanote zettelkasten and the way Mnote looks: chains of topics where note IDs are randomly or timestamp generated and NOT important — because you reference messages/notes by friendly names. You type @ or # plus a phrase, and a search across all the different services resolves what you mean. Investigate: the resolution UX (ambiguity, ranking, whose graph wins), what gets indexed where, and how a resolved reference is stored (stable underlying ID, friendly surface). Deliverable: resolution-flow design sketch with ambiguity cases.

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 investigation doc is linked from this issue with a resolution-flow design sketch for @/# friendly-name references: what gets indexed where, and how cross-service search resolves a phrase.
Ambiguity cases are worked explicitly: duplicate names, ranking, and whose graph wins when several graphs hold a match.
A resolved reference is stored as the stable underlying ID with the friendly name as surface — the sketch states this representation.
Follow-up issues are filed for anything buildable the investigation identifies.

CODE-968

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 investigation (LIST 13a) under Drew's 2026-10-28 directive — the Emanote/Mnote model: note IDs are unimportant because references are by friendly name. Feeds synthesis #2048. Part of the batch filed 2026-10-29 ~01:00Z. Deliverable is the resolution-flow sketch.

Suggested approach: Start from the zettelkasten usage pattern (chains of topics) and derive indexing/ranking requirements from the ambiguity cases.

Risks: Resolution that depends on one central index contradicts the multi-graph model — the sketch must keep resolution local-first.

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

Top priority — ID program wave-1. Drew directed this be picked up in the next runs (2026-10-29): enqueued directly as triage task 3355 in repo-health-code-pilot at queue priority 20 (only breakage-class work at priority 10 outranks it). Wave-1 is the ungated investigations and designs; syntheses and PoCs stay gated on their named inputs. Investigation route: Workhorse.

agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 7276 (triage, queued, priority 50) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03

🤖 Agent note · picked up

Agent: OpenChamber scheduled lane (repo-worker-code), lane c8b9355e-319a-4640-8096-7ad19480d151
Session / ID: task 7276
Found via: queue claim
Task: Triage issue id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047 at current main; issue is OPEN and claim labels are in sync. No open PR was found in the initial search.
Next: inspect the merged cross-reference and follow-on issue for supersession or an existing investigation deliverable.
Links: issue id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047

🤖 Agent note · triaged / done

Agent: OpenChamber scheduled lane (repo-worker-code), lane c8b9355e-319a-4640-8096-7ad19480d151
Session / ID: task 7276
Verdict: The id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047 investigation is complete and its outputs are present on current main. The existing investigation result comment on this issue documents the resolution flow, index sources, ranking, viewer-relative ownership, stable-ID/friendly-surface representation, ambiguity cases, and security note. The linked Markdown design is doc/2026-10-30T13-25-00Z_design_friendly_name_references.md (PR id: spec for friendly-name reference resolution, local store (#2259) #2742, MERGED).
Follow-up routing: local design/PoC issue id: design+PoC: friendly-name reference resolution, local store — reference representation, index, ranking (from #2047) #2259 is CLOSED; PR id: local-store PoC for friendly-name reference resolution (#2259) #2756 is MERGED. Cross-store fan-out, locator fetch, and hosted-store search were explicitly left for v2 and are tracked in open issue id: friendly-name reference resolution v2 — cross-store fan-out and locator fetch (follow-on to #2259) #5178. Synthesis id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048 remains OPEN; this closes only the completed id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047 input, not the synthesis.
Blockers: none for the id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047 investigation; remaining cross-store work is separately scoped in id: friendly-name reference resolution v2 — cross-store fan-out and locator fetch (follow-on to #2259) #5178, with its document-identity decision still open.
Links: issue id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047; PR id: spec for friendly-name reference resolution, local store (#2259) #2742; issue id: design+PoC: friendly-name reference resolution, local store — reference representation, index, ranking (from #2047) #2259; PR id: local-store PoC for friendly-name reference resolution (#2259) #2756; issue id: friendly-name reference resolution v2 — cross-store fan-out and locator fetch (follow-on to #2259) #5178; synthesis id: design: Zettelkasten layer — multiplayer docs/wiki on ID #2048

Navigation Menu

Repository navigation

id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047

Acceptance criteria

Intake review

9 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

id: investigate: friendly-name references — @/# phrase resolution via cross-service search (zettelkasten / Mnote model) #2047

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

dezren39 commented on Oct 29, 2026

9 remaining items

developing-today commented on Nov 3, 2026

dezren39 commented on Nov 4, 2026

dezren39 commented on Nov 4, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions