Skip to content

id: design: sharing & permissions cluster (knowledge layer) (from #5678) #5840

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

Sharing under the parent's ruled read-authority default: write/edit sharing, link sharing, workspace/team models, guest access, per-object vs inherited permissions.

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. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  5. added
    work/assignedQueue worker lifecycle state
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor

    🤖 Agent note · handed off

  7. developing-today commented on Nov 5, 2026

    @developing-today
    Contributor

    🤖 Agent note · handed off / parked

  8. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  9. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · handed off

  10. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · state: handed off

  11. 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
  12. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · state: picked up

  13. dezren39 commented on Nov 5, 2026

    @dezren39
    MemberAuthor

    🤖 Agent note · triage complete (task 10243)

    Verdict: #5840 remains OPEN and has no matching PR or evidence it is already handled. It is a valid, distinct knowledge-layer design ticket; no code change is warranted in triage. Revalidated on main at 882cb5d63e357438c13729aacb570f0a31842b08 (fast-forwarded; unchanged).

    Scope and ordering: follow #5678’s already-ruled knowledge read-authority default — public read, owner grants to users/groups, resolution order object → owner user default → server config → public. Do not reopen the older alternatives in #2048’s 2026-11-01 design. Settle the sharing design for write/edit, link sharing, workspace/team and guest semantics, and per-object vs inherited settings against that rule. Before enabling shared content, the design/implementation path must address the missing read/write enforcement at event-sync and blob-fetch boundaries noted in doc/2026-11-01_design_id2048.md (the group roles exist, but those gates are open/unwired in the design baseline).

    Adjacent work: #5960 is a separate world-capability consent/admin UX design; it already cross-links #5840 and should share vocabulary, not duplicate the knowledge-layer policy. No other blocker prevents the design from proceeding.

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