You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Follow-on design ticket from #5678 — 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
Importing Evernote into the #2048 object model: source format and how to obtain it, mapping, degradation honesty, deduplication, and a test corpus.
Context from the parent
The parent is a design-to-make-designs: a competitor feature-matrix programme over the #2048 zettelkasten layer whose deliverable is one follow-on design per cluster and per importer, filed and linked on the parent. 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: #5678. Programme: epic #2056. Filed by WS-F (2026-11-04 ID design gap & expansion pass).
state: done (triaged; pickup and triage in one pass, lane code-h direct)
Triage 2026-11-05 (task 10249): well-scoped follow-on design ticket from #5678, verified open with no hard-stop labels and no decision record yet (only comment is the Kaneo link).
Routing: no blocker on Drew; the design's own checklist (source format/obtaining, mapping, degradation honesty, dedup, test corpus) is complete as a scope. Implementation timing is a separate later decision per the filing note.
Activity
developing-today commentedon Nov 5, 2026
CODE-1529
dezren39 commentedon Nov 5, 2026
agent-note:v1
Triage 2026-11-05 (task 10249): well-scoped follow-on design ticket from #5678, verified open with no hard-stop labels and no decision record yet (only comment is the Kaneo link).
Verified ordering context, fresh reads:
kind/designto match sibling tickets. Programme: epic epic: ID platform expansion — apps, comms, currency, hosting, boards (2026-10-28 directive, LIST 6–15) #2056.Routing: no blocker on Drew; the design's own checklist (source format/obtaining, mapping, degradation honesty, dedup, test corpus) is complete as a scope. Implementation timing is a separate later decision per the filing note.