id: design: shared threat-list feed protocol — versioned, signed, subscribable feeds with local override lists #6006

Activity

1. dezren39

   added

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   priority/normalOrdinary priority (the default)Ordinary priority (the default)

   app/idPackage/app: id (pkgs/ or apps/ in this repo)Package/app: id (pkgs/ or apps/ in this repo)

   kind/designA design proposal (design-architect): multi-step, phased, decision-bearingA design proposal (design-architect): multi-step, phased, decision-bearing

   on Nov 5, 2026
2. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   CODE-1672
3. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   task/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this item

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   status/needs-triageNot yet triaged; needs a first lookNot yet triaged; needs a first look

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   on Nov 5, 2026
4. dezren39 commented on Nov 5, 2026

   

   dezren39

   on Nov 5, 2026

   MemberAuthor

   More actions

   🤖 Agent note · done (triaged)

   • Agent: queue worker (repo-worker-code), lane code-i
   • Session / ID: task 10372
   • Found via: queue claim
   • Task: Triage issue id: design: shared threat-list feed protocol — versioned, signed, subscribable feeds with local override lists #6006 at current main
   • Expectation: s — verdict with evidence, fix path scoped
   • Links: follow-up task 10543

   Verdict: CONFIRMED / still open — protocol undesigned and unimplemented.

   Evidence at current main (2026-11-05):

   • Code search finds no threat-list feed protocol in this repo: threat hits only threat-model prose (e.g. pkgs/mcpx/docs/proposals.md, design docs); moderation feed finds no protocol; blacklist finds only lib/notifications.py (a notification filter) and Nix kernel-module lists — no feed format, publisher, subscriber, signing, versioning, or expiry machinery for scam domains / content hashes / known-raider principals.
   • Dependencies are themselves still open, which orders the work: parent topic issue id: design: world governance — per-world rules, pre-approval, moderation/report/quarantine as shared libraries #5973 (world governance — moderation/report/quarantine as shared libraries, the moderation pack a subscription lives under) is open, and issue id: implement Writer-set view projection - view projection and discovery query (design doc) #5545 (writer-set authority, whose keys would vouch for a feed) is open. The feed signing design must compose with id: implement Writer-set view projection - view projection and discovery query (design doc) #5545 rather than invent a parallel key model.
   • No comments on this issue dispute the scope; the only comment is the Kaneo tracker link.

   Fix path scoped: follow-up task 10543 (small_fix, pilot queue) to write the feed-protocol spec #6006 asks for — entries/versioning/signing, update cadence/expiry, subscription semantics with local override/exemption lists always winning, and stated behavior for stale feed, malicious feed, and feed-vs-feed conflicts, sufficient to implement a publisher and a subscriber. Implementing the publisher/subscriber itself is explicitly out of that follow-up's scope.
5. dezren39

   added

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   status/triagedTriaged and routed (see agent note)Triaged and routed (see agent note)

   on Nov 5, 2026
6. 5 remaining items

   Load more
7. developing-today

   added

   queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

   status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

   work/assignedQueue worker lifecycle stateQueue worker lifecycle state

   and removed

   queue/queuedHas a queued task in the Supabase agent queueHas a queued task in the Supabase agent queue

   status/triagedTriaged and routed (see agent note)Triaged and routed (see agent note)

   on Nov 5, 2026
8. developing-today commented on Nov 5, 2026

   

   developing-todayBot

   on Nov 5, 2026 – with developing.today

   Contributor

   More actions

   🤖 Agent note · picked up

   • Agent: queue worker (repo-worker-code), lane code-w
   • Session / ID: task 10543
   • Found via: queue claim
   • Task: Write the shared threat-list feed protocol spec for issue id: design: shared threat-list feed protocol — versioned, signed, subscribable feeds with local override lists #6006 (design only; publisher/subscriber implementation out of scope), following the repo design-note pattern, composing with writer-set authority (id: implement Writer-set view projection - view projection and discovery query (design doc) #5545) and the moderation-pack model (id: design: world governance — per-world rules, pre-approval, moderation/report/quarantine as shared libraries #5973).
   • Expectation: m — spec PR opened and merged under the standing criteria; spec covers entries/versioning/signing, cadence/expiry, subscription semantics with local overrides always winning, and stale/malicious/conflicting-feed behavior.
   • Links: task 10543; triage verdict on issue id: design: shared threat-list feed protocol — versioned, signed, subscribable feeds with local override lists #6006 (task 10372)
9. developing-today

   added

   status:in-review

   on Nov 5, 2026
10. developing-today

    added a commit that references this issue on Nov 5, 2026

    Merge pull request #6232 from developing-today/queue/10543-6006-threa…

    ...

    955ed23
11. developing-today

    closed this as completedin #6232on Nov 5, 2026
12. developing-today

    added

    status:done

    and removed

    status:in-review

    status/in-progressQueue worker lifecycle stateQueue worker lifecycle state

    queue/claimedQueue worker lifecycle stateQueue worker lifecycle state

    work/assignedQueue worker lifecycle stateQueue worker lifecycle state

    on Nov 5, 2026
13. developing-today commented on Nov 5, 2026

    

    developing-todayBot

    on Nov 5, 2026 – with developing.today

    Contributor

    More actions

    🤖 Agent note · done

    • Agent: queue worker (repo-worker-code), lane code-w
    • Session / ID: task 10543
    • Found via: queue claim
    • Task: Shared threat-list feed protocol spec for issue id: design: shared threat-list feed protocol — versioned, signed, subscribable feeds with local override lists #6006 — written, PR'd, and merged.
    • Expectation: met — spec sufficient to implement a publisher and a subscriber.
    • Links: PR doc(id): design note — shared threat-list feed protocol (#6006) #6232 (merged, merge sha 955ed23); spec at doc/2026-11-05T13-36-21Z_design_threat_list_feed_protocol/ on main

    Spec covers every Scope bullet in issue #6006: feed format (signed FeedHead/FeedDelta/FeedSnapshot objects on the pkgs/id substrate) and entries (canonicalized domain / content-hash / principal subjects, actions, closed reason vocabulary); versioning (hash-chained monotonic seq, set_hash convergence oracle); signing composed with writer-set authority (#5545) — a feed counts only where a world's moderation pack (#5973) pins it, with signed rotation/revocation; update cadence and two-clock expiry (entries re-added, never silently extended); subscription semantics with local override/exemption lists evaluated first and always winning; and stated behavior for stale feeds (fresh → stale → retired; silencing a feed never unblocks a subject before its own expiry), malicious/corrupt feeds (reject-whole, fork freeze for a pack decision, volume caps), and feed-vs-feed conflicts (deterministic rank → strength → higher-rank signed clear → earliest → entry-id order). Implementation slices are named in the spec §10 as separate future issues, per the task packet's scope guard. No Codex findings were posted on PR #6232 (checked all review rounds before merge); no CI check runs exist for this docs-only PR.