Skip to content

id: design: extensibility cluster (knowledge layer) (from #5678) #5843

Open

Description

@dezren39

Summary

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

Plugins/APIs (Obsidian plugins, Notion API), embeds/transclusion, and scripting/automation for the knowledge layer.

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).

Activity

  1. added
    app/idPackage/app: id (pkgs/ or apps/ in this repo)
    on Nov 5, 2026
  2. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor
  3. added
    queue/queuedHas a queued task in the Supabase agent queue
    task/triageQueue packet kind: verify, reproduce, and route this item
    on Nov 5, 2026
  4. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor

    🤖 Agent note · handed off

    • Agent: queue worker (repo-worker-code), lane code-a
    • Session / ID: task 10246
    • Found via: queue claim (re-claim after prior handoff park expired unbound)
    • Task: task 10246 (triage for issue id: design: extensibility cluster (knowledge layer) (from #5678) #5843) is assigned to the opencode execution lane again — handing off to the opencode claimant, which launches the bound session. This lane did not work the triage itself. Verified fresh: issue id: design: extensibility cluster (knowledge layer) (from #5678) #5843 is OPEN with no hard-stop labels (no held, user/owned, do-not-merge, do-not-auto-edit).
    • Expectation: claimant launches the bound opencode session for task 10246; if unbound by lease/park expiry, task 10246 returns to the queue. This is the second handoff of task 10246 today — if the claimant cannot bind it, blocking it would stop the cycle.
    • Links: task 10246 (repo-health-code-pilot), assigned_lane=opencode
  5. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    work/assignedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. added
    queue/claimedQueue worker lifecycle state
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 5, 2026
  7. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), lane aea12c82-c5af-4e5a-9b66-f8e360f87177
    • Session / ID: task 10246
    • Found via: queue claim
    • Task: Triage issue id: design: extensibility cluster (knowledge layer) (from #5678) #5843 (knowledge-layer extensibility design).
    • Expectation: effort m; confirm the design scope, parent constraints, and implementation ordering, then record the route.
    • Links: task 10246 (repo-health-code-pilot); branch queue/10246-5843-id-design-triage
  8. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    Triage findings — current main 2801e36

    Issue #5843 remains OPEN; no matching PR was found. Parent issue #5678 is also OPEN. The scope is already separated correctly as the knowledge-layer extensibility design: plugins/APIs, embeds/transclusion, and scripting/automation. The issue's own decision record requires the chosen shape, rejected alternatives, and implementation invariants; any further split should be filed and linked here rather than expanding scope or silently changing a parent decision.

    Ordering: complete the design decision on #5843 before implementation. Keep #5678's competitor-matrix and parent decisions authoritative; if this design would change one, record the conflict explicitly. No implementation blocker or superseding artifact was found. This triage creates no duplicate task: #5843 itself is the existing design follow-on, and implementation timing is explicitly a later decision.

    🤖 Agent note · handed off

  9. added
    status/triagedTriaged and routed (see agent note)
    and removed
    queue/claimedQueue worker lifecycle state
    work/assignedQueue worker lifecycle state
    on Nov 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

app/idPackage/app: id (pkgs/ or apps/ in this repo)status/triagedTriaged and routed (see agent note)task/triageQueue packet kind: verify, reproduce, and route this item

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions