@recursiv/sdk 0.7.83 → 0.7.93

package/dist/privacy/facts.generated.d.ts

@@ -0,0 +1,79 @@
+export declare const PRIVACY_REGISTRY_VERSION: 0;
+export declare const PRIVACY_FACTS: readonly [{
+    readonly id: "agents.tool_mode.chat_only";
+    readonly status: "planned";
+    readonly enforcement: "server";
+    readonly capability: "web_tools";
+    readonly step: "S5";
+    readonly says: "An agent in chat_only tool mode is given no tools, so it opens no web page.";
+}, {
+    readonly id: "agents.turn_stamp";
+    readonly status: "enforced";
+    readonly enforcement: "server";
+    readonly capability: null;
+    readonly step: "S7";
+    readonly says: "Every reply a model writes in an agent chat through the platform's agent turn records, in metadata.ai, the model, its maker and the route, a model swapped in and whether for usage limits or after a failure, and the tools it called.";
+}, {
+    readonly id: "agents.personal_context_sections";
+    readonly status: "planned";
+    readonly enforcement: "server";
+    readonly capability: "activity";
+    readonly step: "S26";
+    readonly says: "A personal agent's turn carries no follows, upvotes, groups or views of the member unless the member turned that part of their activity on.";
+}, {
+    readonly id: "sealed.attest_before_send";
+    readonly status: "enforced";
+    readonly enforcement: "device";
+    readonly capability: "chat_tier";
+    readonly step: "S28";
+    readonly says: "The phone seals a Sealed request only to the key of a router it checked against a fresh challenge of its own: the router's report, signed by its AMD hardware, must answer that challenge with debug mode off and firmware at or above a floor, and its software must be a release Tinfoil signed and listed in a public log. If any check fails there is no key to seal to, so nothing is sealed or sent. How long a checked router is used before it is checked again is up to the app.";
+}, {
+    readonly id: "sealed.attest_second_signer";
+    readonly status: "planned";
+    readonly enforcement: "device";
+    readonly capability: "chat_tier";
+    readonly step: "S28";
+    readonly says: "The phone also requires Recursiv's own signature over the router's release, so a release Tinfoil signed alone is refused.";
+}, {
+    readonly id: "sealed.no_standard_fallback";
+    readonly status: "enforced";
+    readonly enforcement: "client";
+    readonly capability: "chat_tier";
+    readonly step: "S28";
+    readonly says: "The SDK sends a Sealed request only to the Sealed route, marked Sealed, and only once: a refusal, an error or an answer that is not sealed goes back to the app, and the SDK never sends the request again, to Sealed or to any other route.";
+}, {
+    readonly id: "sealed.gateway_opaque";
+    readonly status: "enforced";
+    readonly enforcement: "server";
+    readonly capability: "chat_tier";
+    readonly step: "S28";
+    readonly says: "The Sealed gateway passes each Sealed request and answer on as bytes it does not read: it never parses, stores or logs a request or answer body. It refuses a request that carries no EHBP encapsulated key, the mark of a sealed body, and a success answer that carries no well-formed EHBP response nonce, the mark of a sealed answer; it cannot tell from the bytes themselves whether a body is sealed.";
+}, {
+    readonly id: "sealed.dest_tinfoil_only";
+    readonly status: "enforced";
+    readonly enforcement: "server";
+    readonly capability: "chat_tier";
+    readonly step: "S28";
+    readonly says: "The Sealed gateway sends Sealed requests, and asks for attestation documents, only to the router origins its configuration lists, named exactly, and it lists only https origins of Tinfoil router hosts (inference.tinfoil.sh or router-N.tinfoil.sh). It refuses any other server a client names and follows no redirect.";
+}, {
+    readonly id: "sealed.no_server_history";
+    readonly status: "enforced";
+    readonly enforcement: "server";
+    readonly capability: "sealed_history";
+    readonly step: "S29";
+    readonly says: "The platform keeps no Sealed chat history: no Sealed route writes a conversation or message row, and the gateway stores no request or answer body.";
+}, {
+    readonly id: "sealed.backup_excluded";
+    readonly status: "planned";
+    readonly enforcement: "device";
+    readonly capability: "sealed_history";
+    readonly step: "S29";
+    readonly says: "Sealed chats saved on a phone are left out of the phone's backups.";
+}, {
+    readonly id: "sealed.no_push";
+    readonly status: "enforced";
+    readonly enforcement: "server";
+    readonly capability: "chat_tier";
+    readonly step: "S29";
+    readonly says: "No Sealed route sends a push notification or writes a notification: a Sealed answer goes back only on the request that asked for it.";
+}];

package/dist/privacy/facts.generated.js

@@ -0,0 +1,93 @@
+// Generated by scripts/privacy-claims.mjs from docs/privacy-claims.json. Do not edit: CI refuses a hand edit.
+// Change the registry, then run: node scripts/privacy-claims.mjs --write
+export const PRIVACY_REGISTRY_VERSION = 0;
+export const PRIVACY_FACTS = [
+    {
+        id: "agents.tool_mode.chat_only",
+        status: "planned",
+        enforcement: "server",
+        capability: "web_tools",
+        step: "S5",
+        says: "An agent in chat_only tool mode is given no tools, so it opens no web page.",
+    },
+    {
+        id: "agents.turn_stamp",
+        status: "enforced",
+        enforcement: "server",
+        capability: null,
+        step: "S7",
+        says: "Every reply a model writes in an agent chat through the platform's agent turn records, in metadata.ai, the model, its maker and the route, a model swapped in and whether for usage limits or after a failure, and the tools it called.",
+    },
+    {
+        id: "agents.personal_context_sections",
+        status: "planned",
+        enforcement: "server",
+        capability: "activity",
+        step: "S26",
+        says: "A personal agent's turn carries no follows, upvotes, groups or views of the member unless the member turned that part of their activity on.",
+    },
+    {
+        id: "sealed.attest_before_send",
+        status: "enforced",
+        enforcement: "device",
+        capability: "chat_tier",
+        step: "S28",
+        says: "The phone seals a Sealed request only to the key of a router it checked against a fresh challenge of its own: the router's report, signed by its AMD hardware, must answer that challenge with debug mode off and firmware at or above a floor, and its software must be a release Tinfoil signed and listed in a public log. If any check fails there is no key to seal to, so nothing is sealed or sent. How long a checked router is used before it is checked again is up to the app.",
+    },
+    {
+        id: "sealed.attest_second_signer",
+        status: "planned",
+        enforcement: "device",
+        capability: "chat_tier",
+        step: "S28",
+        says: "The phone also requires Recursiv's own signature over the router's release, so a release Tinfoil signed alone is refused.",
+    },
+    {
+        id: "sealed.no_standard_fallback",
+        status: "enforced",
+        enforcement: "client",
+        capability: "chat_tier",
+        step: "S28",
+        says: "The SDK sends a Sealed request only to the Sealed route, marked Sealed, and only once: a refusal, an error or an answer that is not sealed goes back to the app, and the SDK never sends the request again, to Sealed or to any other route.",
+    },
+    {
+        id: "sealed.gateway_opaque",
+        status: "enforced",
+        enforcement: "server",
+        capability: "chat_tier",
+        step: "S28",
+        says: "The Sealed gateway passes each Sealed request and answer on as bytes it does not read: it never parses, stores or logs a request or answer body. It refuses a request that carries no EHBP encapsulated key, the mark of a sealed body, and a success answer that carries no well-formed EHBP response nonce, the mark of a sealed answer; it cannot tell from the bytes themselves whether a body is sealed.",
+    },
+    {
+        id: "sealed.dest_tinfoil_only",
+        status: "enforced",
+        enforcement: "server",
+        capability: "chat_tier",
+        step: "S28",
+        says: "The Sealed gateway sends Sealed requests, and asks for attestation documents, only to the router origins its configuration lists, named exactly, and it lists only https origins of Tinfoil router hosts (inference.tinfoil.sh or router-N.tinfoil.sh). It refuses any other server a client names and follows no redirect.",
+    },
+    {
+        id: "sealed.no_server_history",
+        status: "enforced",
+        enforcement: "server",
+        capability: "sealed_history",
+        step: "S29",
+        says: "The platform keeps no Sealed chat history: no Sealed route writes a conversation or message row, and the gateway stores no request or answer body.",
+    },
+    {
+        id: "sealed.backup_excluded",
+        status: "planned",
+        enforcement: "device",
+        capability: "sealed_history",
+        step: "S29",
+        says: "Sealed chats saved on a phone are left out of the phone's backups.",
+    },
+    {
+        id: "sealed.no_push",
+        status: "enforced",
+        enforcement: "server",
+        capability: "chat_tier",
+        step: "S29",
+        says: "No Sealed route sends a push notification or writes a notification: a Sealed answer goes back only on the request that asked for it.",
+    },
+];

package/dist/privacy/index.d.ts

@@ -0,0 +1,48 @@
+/**
+ * `@recursiv/sdk/privacy`: the platform privacy facts, generated from the claims registry (docs/privacy-claims.json
+ * in recursivlabs/recursiv). Each fact says one thing the platform does with member data and whether this SDK release
+ * marks it enforced, which it does only once every test that proves it is real and runs in CI.
+ *
+ * An app shows a privacy sentence only when the facts it rests on are live: enforced here AND listed by the API it
+ * talks to (`sdk.privacy.capabilities()`), so neither a newer SDK nor a newer API can make a claim on its own. A fact
+ * held on the phone (`enforcement: 'device'`) needs a third check, the app's own: neither this SDK nor the API can see
+ * which native module the phone runs, so the app names the device facts its installed module carries (`deviceFacts`).
+ *
+ * The types live here, not in the SDK's shared types, so this entry point stands alone.
+ */
+import { PRIVACY_FACTS, PRIVACY_REGISTRY_VERSION } from './facts.generated.js';
+export { PRIVACY_FACTS, PRIVACY_REGISTRY_VERSION };
+export type PrivacyFact = (typeof PRIVACY_FACTS)[number];
+export type PrivacyFactId = PrivacyFact['id'];
+/** `planned`: the platform does not yet prove it. `enforced`: every test that proves it is real and runs in CI. */
+export type PrivacyFactStatus = 'planned' | 'enforced';
+/** Where a fact holds: on the server, on the phone (the native module), in the SDK, or in both server and client. */
+export type PrivacyFactEnforcement = 'server' | 'device' | 'client' | 'server_and_client';
+/** GET /privacy/capabilities: the facts the deployed API's build marks enforced, and the commit it runs. */
+export interface PrivacyCapabilities {
+    /** The commit the API was built from, or `unknown`. */
+    api_commit: string;
+    /** Fact ids, sorted. An id this SDK release does not know is never live here. */
+    facts: string[];
+}
+/** The fact with this id, or undefined for an id this SDK release does not know. */
+export declare function privacyFact(id: string): PrivacyFact | undefined;
+/** Whether this SDK release marks the fact enforced. An unknown id is not. */
+export declare function isFactEnforced(id: string): boolean;
+export interface LiveFactOptions {
+    /**
+     * The device facts (`enforcement: 'device'`) the app's installed native module carries, as the app knows from the
+     * module revision it ships (for Sealed, @recursiv/e2ee-react-native). A device fact is live only when it is named
+     * here too. Left out, no device fact is live. A fact says what the module does, not what the app does with it: for
+     * `sealed.attest_before_send` the app chooses how long a checked router is reused, so copy that says the router is
+     * checked before every send needs the app to check before every send.
+     */
+    deviceFacts?: Iterable<string>;
+}
+/**
+ * Enforced in this SDK release AND listed by the deployed API, and for a device fact also named in `deviceFacts`.
+ * Missing capabilities mean nothing is live.
+ */
+export declare function isFactLive(id: string, capabilities: PrivacyCapabilities | null | undefined, options?: LiveFactOptions): boolean;
+/** Every fact that is live for this API (and, for device facts, this app's native module), in registry order. */
+export declare function liveFacts(capabilities: PrivacyCapabilities | null | undefined, options?: LiveFactOptions): PrivacyFactId[];

package/dist/privacy/index.js

@@ -0,0 +1,42 @@
+/**
+ * `@recursiv/sdk/privacy`: the platform privacy facts, generated from the claims registry (docs/privacy-claims.json
+ * in recursivlabs/recursiv). Each fact says one thing the platform does with member data and whether this SDK release
+ * marks it enforced, which it does only once every test that proves it is real and runs in CI.
+ *
+ * An app shows a privacy sentence only when the facts it rests on are live: enforced here AND listed by the API it
+ * talks to (`sdk.privacy.capabilities()`), so neither a newer SDK nor a newer API can make a claim on its own. A fact
+ * held on the phone (`enforcement: 'device'`) needs a third check, the app's own: neither this SDK nor the API can see
+ * which native module the phone runs, so the app names the device facts its installed module carries (`deviceFacts`).
+ *
+ * The types live here, not in the SDK's shared types, so this entry point stands alone.
+ */
+import { PRIVACY_FACTS, PRIVACY_REGISTRY_VERSION } from './facts.generated.js';
+export { PRIVACY_FACTS, PRIVACY_REGISTRY_VERSION };
+const BY_ID = new Map(PRIVACY_FACTS.map((fact) => [fact.id, fact]));
+/** The fact with this id, or undefined for an id this SDK release does not know. */
+export function privacyFact(id) {
+    return BY_ID.get(id);
+}
+/** Whether this SDK release marks the fact enforced. An unknown id is not. */
+export function isFactEnforced(id) {
+    return BY_ID.get(id)?.status === 'enforced';
+}
+/**
+ * Enforced in this SDK release AND listed by the deployed API, and for a device fact also named in `deviceFacts`.
+ * Missing capabilities mean nothing is live.
+ */
+export function isFactLive(id, capabilities, options = {}) {
+    const fact = BY_ID.get(id);
+    if (!fact || fact.status !== 'enforced')
+        return false;
+    if (!Array.isArray(capabilities?.facts) || !capabilities.facts.includes(id))
+        return false;
+    if (fact.enforcement === 'device')
+        return new Set(options.deviceFacts ?? []).has(id);
+    return true;
+}
+/** Every fact that is live for this API (and, for device facts, this app's native module), in registry order. */
+export function liveFacts(capabilities, options = {}) {
+    const deviceFacts = [...(options.deviceFacts ?? [])];
+    return PRIVACY_FACTS.filter((fact) => isFactLive(fact.id, capabilities, { deviceFacts })).map((fact) => fact.id);
+}

package/dist/resources/discovery-merge.d.ts

@@ -54,6 +54,20 @@ export declare function discoveryRowTitle(row: unknown): string | null;
 export declare function discoveryLeadable(item: DiscoveryPostItem): boolean;
 /** A post with a picture or a video of its own that the reader sees unblurred. */
 export declare function discoveryShowsMedia(item: DiscoveryPostItem): boolean;
+/**
+ * What makes an item the same post as another on one screen: its key, and for an open-network post its network and id
+ * as the network spells it (a Nostr event id in any case) and each picture or clip file it carries (by address, and by
+ * content hash for a file named by one). Two notes that carry one clip are one post to a reader: a bot posting it
+ * again, a mirror account, the source index's copy beside the provider's. A Minds post is its key alone.
+ */
+export declare function discoveryItemIdentities(item: DiscoveryItem): string[];
+/**
+ * The rows with each post shown once: a post item whose identity (discoveryItemIdentities) is in `shown`, or was on an
+ * earlier item of the rows, leaves its module, which keeps its spec in step; a module of posts left with none is dropped.
+ * A story keeps its headline when its posts go, and rows that are not modules pass as they are. `shown` gains the
+ * identities of every post kept.
+ */
+export declare function withoutRepeatedDiscoveryItems<T>(rows: readonly T[], shown?: Set<string>): T[];
 /** A player found this video file (or HLS playlist) will not play: no Discover module promotes it, and it gets no video boost. */
 export declare function reportDiscoveryVideoUnavailable(url: string): void;
 /** Forget every report (a test seam, or a new viewer). */
@@ -151,7 +165,9 @@ export declare function weaveDiscoveryArrival<T extends {
  * that are not posts (a story, a rail, a row of the client's own) take the places they would have had woven in one by
  * one, and the posts fill the other places by engagement under the network mix (DiscoveryEngagementMerge). The first
  * post at the top of the feed, or below the line where it turned (`floor`), leads what comes under it (takeLead): never
- * a post with no picture or clip that nobody engaged with while the batch holds one with either.
+ * a post with no picture or clip that nobody engaged with while the batch holds one with either. A post the rows already
+ * show, or that arrives twice (the same open-network post, or another note with the same clip: discoveryItemIdentities),
+ * is shown once, where it was first.
  */
 export declare function mergeDiscoveryArrival<T extends {
     id: string;

package/dist/resources/discovery-merge.js

@@ -130,6 +130,79 @@ export function discoveryLeadable(item) {
 export function discoveryShowsMedia(item) {
     return discoveryLeadable(item) && hasMedia(item.post.media);
 }
+// ── One post, shown once ────────────────────────────────────────────────
+/** A file named by its SHA-256 (Blossom, nostr.build): the same bytes wherever they are served from. */
+const CONTENT_HASH = /\/([0-9a-f]{64})(?:\.[a-z0-9]{1,8})?$/i;
+/**
+ * What makes an item the same post as another on one screen: its key, and for an open-network post its network and id
+ * as the network spells it (a Nostr event id in any case) and each picture or clip file it carries (by address, and by
+ * content hash for a file named by one). Two notes that carry one clip are one post to a reader: a bot posting it
+ * again, a mirror account, the source index's copy beside the provider's. A Minds post is its key alone.
+ */
+export function discoveryItemIdentities(item) {
+    if (item.kind !== 'social')
+        return [item.key];
+    const post = item.post;
+    const identities = [item.key];
+    if (typeof post.protocol === 'string' && typeof post.nativeId === 'string' && post.nativeId) {
+        identities.push(`post:${post.protocol}:${post.protocol === 'nostr' ? post.nativeId.toLowerCase() : post.nativeId}`);
+    }
+    for (const entry of Array.isArray(post.media) ? post.media : []) {
+        const url = entry?.url;
+        if (typeof url !== 'string' || !/^https?:\/\//i.test(url))
+            continue;
+        const address = url.split('#')[0];
+        identities.push(`media:${address}`);
+        const hash = CONTENT_HASH.exec(address.split('?')[0])?.[1];
+        if (hash)
+            identities.push(`blob:${hash.toLowerCase()}`);
+    }
+    return identities;
+}
+/**
+ * The rows with each post shown once: a post item whose identity (discoveryItemIdentities) is in `shown`, or was on an
+ * earlier item of the rows, leaves its module, which keeps its spec in step; a module of posts left with none is dropped.
+ * A story keeps its headline when its posts go, and rows that are not modules pass as they are. `shown` gains the
+ * identities of every post kept.
+ */
+export function withoutRepeatedDiscoveryItems(rows, shown = new Set()) {
+    const out = [];
+    for (const row of rows) {
+        if (!isModule(row)) {
+            out.push(row);
+            continue;
+        }
+        const items = row.items.filter(item => {
+            if (!isPostItem(item))
+                return true;
+            const identities = discoveryItemIdentities(item);
+            if (identities.some(identity => shown.has(identity)))
+                return false;
+            for (const identity of identities)
+                shown.add(identity);
+            return true;
+        });
+        if (items.length === row.items.length) {
+            out.push(row);
+            continue;
+        }
+        if (!items.some(item => isPostItem(item) || item.kind === 'cluster'))
+            continue;
+        out.push(withItems(row, items));
+    }
+    return out;
+}
+/** The identities of every post the rows show (discoveryItemIdentities). */
+function shownIdentities(rows) {
+    const shown = new Set();
+    for (const row of rows)
+        if (isModule(row))
+            for (const item of row.items)
+                if (isPostItem(item))
+                    for (const identity of discoveryItemIdentities(item))
+                        shown.add(identity);
+    return shown;
+}
 // ── Videos that can play ────────────────────────────────────────────────
 /** Video files (or playlists) a player found will not play this session: never promoted again. */
 const UNAVAILABLE_VIDEOS = new Set();
@@ -332,9 +405,12 @@ export function poolDiscoveryGalleries(modules, now, keep) {
     for (const galleries of themes.values()) {
         const seen = new Set();
         const cards = galleries.flatMap((gallery, from) => gallery.items.filter(isPostItem).flatMap((item, index) => {
-            if (seen.has(item.key))
+            // One card per post: a picture two galleries (or two notes) carry is pooled once (discoveryItemIdentities).
+            const identities = discoveryItemIdentities(item);
+            if (identities.some(identity => seen.has(identity)))
                 return [];
-            seen.add(item.key);
+            for (const identity of identities)
+                seen.add(identity);
             return [{ item, gallery, network: discoveryPostNetwork(item), rank: rankDiscoveryItem(item, reference, now), order: index * galleries.length + from }];
         })).sort((a, b) => a.rank.tier - b.rank.tier || b.rank.score - a.rank.score || a.order - b.order);
         const counts = new Map();
@@ -492,12 +568,16 @@ export function weaveDiscoveryArrival(rows, arriving, reached, floor = 0) {
  * that are not posts (a story, a rail, a row of the client's own) take the places they would have had woven in one by
  * one, and the posts fill the other places by engagement under the network mix (DiscoveryEngagementMerge). The first
  * post at the top of the feed, or below the line where it turned (`floor`), leads what comes under it (takeLead): never
- * a post with no picture or clip that nobody engaged with while the batch holds one with either.
+ * a post with no picture or clip that nobody engaged with while the batch holds one with either. A post the rows already
+ * show, or that arrives twice (the same open-network post, or another note with the same clip: discoveryItemIdentities),
+ * is shown once, where it was first.
  */
 export function mergeDiscoveryArrival(rows, arriving, reached, floor = 0, now = Date.now()) {
     const at = arrivalPlace(rows, reached, floor);
     const head = rows.slice(0, at);
-    const below = at >= rows.length ? [...arriving] : weave(arriving, rows.slice(at));
+    // A post already in the rows, or twice in what arrives, is shown once: where it was first (withoutRepeatedDiscoveryItems).
+    const fresh = withoutRepeatedDiscoveryItems(arriving, shownIdentities(rows));
+    const below = at >= rows.length ? fresh : weave(fresh, rows.slice(at));
     const posts = below.filter(isDiscoveryPostModule);
     if (!posts.length)
         return [...head, ...below];

package/dist/resources/discovery-progressive.d.ts

@@ -77,9 +77,10 @@ export declare const FIRST_SCREEN_MS = 2500;
  */
 export declare const VISITOR_FIRST_SCREEN_MS = 800;
 /**
- * A module without the items in `seen` (item keys). Posts already shown by another source's module are not shown again:
- * the sessions dedupe within themselves, but across them a story's member posts can also arrive in that network's own
- * page. A module that loses items keeps its spec in step. A suggestion already shown leaves its rail, and a rail left
+ * A module without the items in `seen` (item keys, or any identity of a post: discoveryItemIdentities). Posts already
+ * shown by another source's module are not shown again: the sessions dedupe within themselves, but across them a story's
+ * member posts can also arrive in that network's own page, and one clip in two notes. A module that loses items keeps
+ * its spec in step. A suggestion already shown leaves its rail, and a rail left
  * with fewer than two is dropped; a story already shown is dropped whole, and keeps its headline and outlets when only
  * its posts were shown; a post module with none left is dropped (null).
  */

package/dist/resources/discovery-progressive.js

@@ -1,5 +1,6 @@
 import { readFalloverSteps } from './discovery-fallover.js';
 import { composeFirstScreen } from './discovery-first-screen.js';
+import { discoveryItemIdentities } from './discovery-merge.js';
 /** How long a round keeps waiting for its slower sources once one of them has answered. */
 export const DISCOVERY_STRAGGLER_MS = 3000;
 /**
@@ -22,9 +23,10 @@ const isSuggestion = (item) => item.kind === 'group' || item.kind === 'person' |
 /** A suggestion rail with fewer is not drawn: the session builds none with fewer either. */
 const SUGGESTIONS_MIN = 2;
 /**
- * A module without the items in `seen` (item keys). Posts already shown by another source's module are not shown again:
- * the sessions dedupe within themselves, but across them a story's member posts can also arrive in that network's own
- * page. A module that loses items keeps its spec in step. A suggestion already shown leaves its rail, and a rail left
+ * A module without the items in `seen` (item keys, or any identity of a post: discoveryItemIdentities). Posts already
+ * shown by another source's module are not shown again: the sessions dedupe within themselves, but across them a story's
+ * member posts can also arrive in that network's own page, and one clip in two notes. A module that loses items keeps
+ * its spec in step. A suggestion already shown leaves its rail, and a rail left
  * with fewer than two is dropped; a story already shown is dropped whole, and keeps its headline and outlets when only
  * its posts were shown; a post module with none left is dropped (null).
  */
@@ -32,7 +34,7 @@ export function withoutSeenItems(module, seen) {
     const lead = module.items[0];
     if (lead?.kind === 'cluster' && seen.has(lead.key))
         return null;
-    const items = module.items.filter(item => item.kind === 'cluster' || !seen.has(item.key));
+    const items = module.items.filter(item => item.kind === 'cluster' || !discoveryItemIdentities(item).some(identity => seen.has(identity)));
     if (items.length === module.items.length)
         return module;
     if (module.items.some(isSuggestion)) {
@@ -46,14 +48,15 @@ export function withoutSeenItems(module, seen) {
                 module: { ...element, props: { ...element.props, itemKeys: items.map(item => item.key) } } } } };
 }
 /**
- * Claims the posts a module shows, and only those. A story claims the members it carries, never its whole member list:
- * the Minds session reads a story's network members only through its member reader, which may fail, time out or be
- * missing. A member the story does not carry still shows in its network's own page.
+ * Claims the posts a module shows, and only those, by every identity (discoveryItemIdentities). A story claims the members
+ * it carries, never its whole member list: the Minds session reads a story's network members only through its member
+ * reader, which may fail, time out or be missing. A member the story does not carry still shows in its network's own page.
  */
 function remember(module, seen) {
     for (const item of module.items)
         if (isPost(item))
-            seen.add(item.key);
+            for (const identity of discoveryItemIdentities(item))
+                seen.add(identity);
 }
 /** The other networks a feed over every source reads, in the session's own order. */
 export function discoveryRemoteSources(networks, source) {

package/dist/resources/discovery.d.ts

@@ -506,7 +506,15 @@ export interface DiscoveryModule {
     id: string;
     presentation: DiscoveryLayout['presentation'] | DiscoveryRecommendationKind | DiscoveryRadarPresentation;
     source: DiscoveryLayout['source'];
-    /** Subject of the featured window (a browse-category id or `mixed`), for specific module copy. */
+    /**
+     * Subject of the module (a browse-category id), for specific module copy ("Videos in Science"). A post module carries
+     * one only when its featured window was themed so AND most of its own posts were judged into that category (0.7.84):
+     * a window's theme is one judgment of up to six posts taken together, and the module features some of them (one clip,
+     * a conversation) or gathers pictures from the whole page, so an open-network clip with no judgment of its own was
+     * titled after its neighbours ("Videos in Technology" over a Nostr clip of birds). Today a post is judged into a
+     * category when a category feed served it (the read's category filter), so modules on a feed with no category carry
+     * none. A radar story carries its cluster's theme. Absent: title the module by its kind alone.
+     */
     theme?: string;
     items: DiscoveryItem[];
     spec: {