← AiAkiv MemoryCONTENT HISTORY

Update to AiAkiv Memory

Snapshot Oct 26, 2026 · 18:05 UTC · version 2.2.0

Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.

WHAT CHANGED

Instructions updated for aiakiv-links

Full description — Now says: means. Also covers public attaches (public memory attached to the user's team, listed under public_attaches with __public: ids).

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save AiAkiv Memory and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Full description

Before

Sep 30, 2026 · 23:09 UTC

means.

After

Oct 26, 2026 · 18:05 UTC

means. Also covers public attaches (public memory attached to the user's team, listed under public_attaches with __public: ids).

Skill instructions

Before

Sep 30, 2026 · 23:09 UTC

--- name: aiakiv-links description: >- Read a LINKED partner org's memory through the partner memory tools. Use when the user asks what a partner/linked org/team knows, wants to compare their memory with a partner's, mentions ...

After

Oct 26, 2026 · 18:05 UTC

--- name: aiakiv-links description: >- Read a LINKED partner org's memory through the partner memory tools. Use when the user asks what a partner/linked org/team knows, wants to compare their memory with a partner's, mentions a lin...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,80 +1,116 @@
----
-name: aiakiv-links
-description: >-
-  Read a LINKED partner org's memory through the partner memory tools. Use when
-  the user asks what a partner/linked org/team knows, wants to compare their
-  memory with a partner's, mentions a link or partner org, or when a probe
-  candidate carries side=remote. Covers choosing between search_partner_memory,
-  find_partner_memory_connections and query_partner_memory_graph, reading results, and what each error reason
-  means.
----
-
-# AiAkiv links (partner-org memory)
-
-A **link** is a read capability two orgs agreed to — not a project you switch
-into. You pass `link_id` per call; your own scope is untouched. Everything is
-read-only: you can never write into a partner org.
-
-**Always start with `list_partner_links`.** It is local (works even when the
-partner is down) and tells you which links are `usable` before you spend a
-remote call. If the tools are absent from the tool list, the server has links
-disabled — say so.
-
-**Call link tools one at a time.** Your org may have only one link call in
-flight at once. Two link tools issued in the same batch — the habit that serves
-you well everywhere else — means the second returns `error: busy` without
-running, even on a completely idle server. Await each call before starting the
-next; `list_partner_links` is local and does not count.
-
-## Which tool for which question
-
-| Question shape | Tool |
-|---|---|
-| "What does the partner know about X?" — search THEIR memory directly | `search_partner_memory(sentence, link_id)` — entry happens on their side; results are their events only |
-| "From what WE know, what connects to their side?" — walk from your context across shared ground | `find_partner_memory_connections` — entry in YOUR org, expansion crosses through **aliased entities** (entities the link declared "same thing on both sides") |
-| Explicit relations across both orgs (shared entities, vector distance, ranked bridges) | `query_partner_memory_graph(link_id, query, params)` — same language as `query_memory_graph`; see the `aiakiv-graph-query` skill |
-| Read one partner event's body | `get_partner_memory_content(link_id, event_id)` — paged; `event_id` comes from the other tools' results |
-
-## Reading results
-
-- Partner events carry `side: "remote"` (or a `link_id`). **Keep them
-  labelled as the partner's** when you reason or summarize — do not present
-  partner knowledge as the user's own, and do not re-save partner content
-  into the user's memory unless the user explicitly asks.
-- `find_partner_memory_connections` never claims something is *absent* on the partner side —
-  entry is home-only, so the partner is only reached through bridges. Absence
-  of remote candidates means "no bridge found", not "they don't know".
-- Aliased bridge entities carry `df_home` / `df_remote` (how common the
-  entity is on each side). Asymmetry is a signal: "1 here, 109 there" means a
-  passing mention for the user is a central topic for the partner — often the
-  most interesting finding in the response.
-- `found: false` from `get_partner_memory_content` means the link does not
-  surface that event — deliberately the same answer whether it is absent or
-  out of scope. Don't retry; don't speculate which.
-
-## When a call returns `status: "error"`
-
-The `reason` names what to do — an error here **never** means the user's own
-memory failed:
-
-- `no_links`, `link_not_found`, `link_not_active`, `link_expired`,
-  `org_not_party`, `principal_not_active` — this link cannot be read (or this
-  direction is closed). Show `list_partner_links` output; fixing it is an
-  owner/console action, not a retry.
-- `we_are_provider` — the user's org is the *providing* side; there is
-  nothing to read in this direction. Normal state, not a failure.
-- `contract_version_too_old` — both owners must re-consent;
-  `list_partner_links` → `reconsent` shows who is missing.
-- `budget_exceeded` — the remote row/time budget ran out mid-walk. Narrow the
-  ask (smaller `top_n`/`k`/`LIMIT`, tighter relation params) instead of
-  repeating it.
-- `busy` — a concurrency limit on **your** server (never the partner's). The
-  `detail` says which of two: the per-org limit, which is almost always
-  self-inflicted (two link calls issued together) — re-issue the refused one
-  once the other finishes, it cost nothing and did not run; or the server-wide
-  limit, shared with other tenants, where a short wait is the right response.
-  Either way it is not a partner problem.
-- `remote_failure`, `internal` — infrastructure failed; try later.
-
-Results can also be `partial` (budget hit mid-walk): what came back is valid,
-just incomplete — say so instead of treating it as the full picture.
+---
+name: aiakiv-links
+description: >-
+  Read a LINKED partner org's memory through the partner memory tools. Use when
+  the user asks what a partner/linked org/team knows, wants to compare their
+  memory with a partner's, mentions a link or partner org, or when a probe
+  candidate carries side=remote. Covers choosing between search_partner_memory,
+  find_partner_memory_connections and query_partner_memory_graph, reading results, and what each error reason
+  means. Also covers public attaches (public memory attached to the user's
+  team, listed under public_attaches with __public: ids).
+---
+
+# AiAkiv links (partner-org memory)
+
+A **link** is a read capability two orgs agreed to — not a project you switch
+into. You pass `link_id` per call; your own scope is untouched. Everything is
+read-only: you can never write into a partner org.
+
+**Always start with `list_partner_links`.** It is local (works even when the
+partner is down) and tells you which links are `usable` before you spend a
+remote call. If the tools are absent from the tool list, the server has links
+disabled — say so.
+
+Links run **one way**, and the list holds the ones whose reading direction
+points at the user's org — blocked ones included, with `usable` saying which
+answer right now. Links their org **provides** (their team issued the invite, so
+the link opens their memory to the partner) are left out entirely — nothing to
+read, nothing to fix; `provided_link_count` says how many exist, and they are
+managed in the console.
+
+**Call link tools one at a time.** Your org may have only one link call in
+flight at once. Two link tools issued in the same batch — the habit that serves
+you well everywhere else — means the second returns `error: busy` without
+running, even on a completely idle server. Await each call before starting the
+next; `list_partner_links` is local and does not count.
+
+## Public attaches (`public_attaches`)
+
+`list_partner_links` also returns `public_attaches`: public memory the user's
+team attached to itself in the console (team "Links" page, "Public attach"
+section). There is no contract and no partner on the other side. A public org
+is open to read anyway; the attach only adds name bridges (aliases) so walks
+and graph queries can cross into it. Each row has `kind: "public"`, a
+`link_id` of the form `__public:<org_id>`, `partner_name`, `usable`,
+`blocked_reason` and `alias_count`.
+
+- A `usable` public attach works in the same four tools with that `link_id`,
+  exactly like a link. Results carry `side: "remote"` the same way, and the
+  same rule applies: keep them labelled as the public org's, not the user's.
+- The section comes back to **every member**, even though the link contract
+  list is owner-only. `links: []` with `links_unavailable_reason:
+  "caller_not_owner"` and a `note` means the user is not the team owner, not
+  that nothing is readable: use the public attaches that are listed.
+- `blocked_reason: "attach_not_enabled"`, or a `__public:` id that is not
+  listed, means the attach is off or the org is no longer public. Turning it
+  on is a console action by the team owner; do not retry.
+- `alias_count: 0` means searches and bodies still work but walks and graph
+  queries stay home-only (no bridge). Say so instead of reporting absence.
+
+## Which tool for which question
+
+| Question shape | Tool |
+|---|---|
+| "What does the partner know about X?" — search THEIR memory directly | `search_partner_memory(sentence, link_id)` — entry happens on their side; results are their events only |
+| "From what WE know, what connects to their side?" — walk from your context across shared ground | `find_partner_memory_connections` — entry in YOUR org, expansion crosses through **aliased entities** (entities the link declared "same thing on both sides") |
+| Explicit relations across both orgs (shared entities, vector distance, ranked bridges) | `query_partner_memory_graph(link_id, query, params)` — same language as `query_memory_graph`; see the `aiakiv-graph-query` skill |
+| Read one partner event's body | `get_partner_memory_content(link_id, event_id)` — paged; `event_id` comes from the other tools' results |
+
+## Reading results
+
+- Partner events carry `side: "remote"` (or a `link_id`). **Keep them
+  labelled as the partner's** when you reason or summarize — do not present
+  partner knowledge as the user's own, and do not re-save partner content
+  into the user's memory unless the user explicitly asks.
+- `find_partner_memory_connections` never claims something is *absent* on the partner side —
+  entry is home-only, so the partner is only reached through bridges. Absence
+  of remote candidates means "no bridge found", not "they don't know".
+- Aliased bridge entities carry `df_home` / `df_remote` (how common the
+  entity is on each side). Asymmetry is a signal: "1 here, 109 there" means a
+  passing mention for the user is a central topic for the partner — often the
+  most interesting finding in the response.
+- `found: false` from `get_partner_memory_content` means the link does not
+  surface that event — deliberately the same answer whether it is absent or
+  out of scope. Don't retry; don't speculate which.
+
+## When a call returns `status: "error"`
+
+The `reason` names what to do — an error here **never** means the user's own
+memory failed:
+
+- `no_links`, `link_not_found`, `link_not_active`, `link_expired`,
+  `org_not_party`, `principal_not_active` — this link cannot be read (or this
+  direction is closed). Show `list_partner_links` output; fixing it is an
+  owner/console action, not a retry.
+  - One case has nothing to fix: a `link_id` that `list_partner_links` does not
+    list at all (the user may have copied it from the console's "links we
+    provide" group) is one their org **provides**, and its refusal is
+    `principal_not_active`. Say that it opens their memory outward rather than
+    sending them to fix a direction.
+- `attach_not_enabled` — a `__public:` id whose attach is off, or whose org is
+  no longer public (see "Public attaches" above). Owner/console action.
+- `contract_version_too_old` — both owners must re-consent;
+  `list_partner_links` → `reconsent` shows who is missing.
+- `budget_exceeded` — the remote row/time budget ran out mid-walk. Narrow the
+  ask (smaller `top_n`/`k`/`LIMIT`, tighter relation params) instead of
+  repeating it.
+- `busy` — a concurrency limit on **your** server (never the partner's). The
+  `detail` says which of two: the per-org limit, which is almost always
+  self-inflicted (two link calls issued together) — re-issue the refused one
+  once the other finishes, it cost nothing and did not run; or the server-wide
+  limit, shared with other tenants, where a short wait is the right response.
+  Either way it is not a partner problem.
+- `remote_failure`, `internal` — infrastructure failed; try later.
+
+Results can also be `partial` (budget hit mid-walk): what came back is valid,
+just incomplete — say so instead of treating it as the full picture.
Full technical diff · 2 changed fields

changed /description

BEFORE
"Read a LINKED partner org's memory through the partner memory tools. Use when the user asks what a partner/linked org/team knows, wants to compare their memory with a partner's, mentions a link or partner org, or when a probe candidate carries side=remote. Covers choosing between search_partner_memory, find_partner_memory_connections and query_partner_memory_graph, reading results, and what each error reason means."
AFTER
"Read a LINKED partner org's memory through the partner memory tools. Use when the user asks what a partner/linked org/team knows, wants to compare their memory with a partner's, mentions a link or partner org, or when a probe candidate carries side=remote. Covers choosing between search_partner_memory, find_partner_memory_connections and query_partner_memory_graph, reading results, and what each error reason means. Also covers public attaches (public memory attached to the user's team, listed under public_attaches with __public: ids)."

changed /skill_md_contents

BEFORE
"---\r\nname: aiakiv-links\r\ndescription: >-\r\n  Read a LINKED partner org's memory through the partner memory tools. Use when\r\n  the user asks what a partner/linked org/team knows, wants to compare their\r\n  memory with a partner's, mentions a link or partner org, or when a probe\r\n  candidate carries side=remote. Covers choosing between search_partner_memory,\r\n  find_partner_memory_connections and query_partner_memory_graph, reading results, and what each error reason\r\n  means.\r\n---\r\n\r\n# AiAkiv links (partner-org memory)\r\n\r\nA **link** is a read capability two orgs agreed to — not a project you switch\r\ninto. You pass `link_id` per call; your own scope is untouched. Everything is\r\nread-only: you can never write into a partner org.\r\n\r\n**Always start with `list_partner_links`.** It is local (works even when the\r\npartner is down) and tells you which links are `usable` before you spend a\r\nremote call. If the tools are absent from the tool list, the server has links\r\ndisabled — say so.\r\n\r\n**Call link tools one at a time.** Your org may have only one link call in\r\nflight at once. Two link tools issued in the same batch — the habit that serves\r\nyou well everywhere else — means the second returns `error: busy` without\r\nrunning, even on a completely idle server. Await each call before starting the\r\nnext; `list_partner_links` is local and does not count.\r\n\r\n## Which tool for which question\r\n\r\n| Question shape | Tool |\r\n|---|---|\r\n| \"What does the partner know about X?\" — search THEIR memory directly | `search_partner_memory(sentence, link_id)` — entry happens on their side; results are their events only |\r\n| \"From what WE know, what connects to their side?\" — walk from your context across shared ground | `find_partner_memory_connections` — entry in YOUR org, expansion crosses through **aliased entities** (entities the link declared \"same thing on both sides\") |\r\n| Explicit relations across both orgs (shared entities, vector distance, ranked bridges) | `query_partner_memory_graph(link_id, query, params)` — same language as `query_memory_graph`; see the `aiakiv-graph-query` skill |\r\n| Read one partner event's body | `get_partner_memory_content(link_id, event_id)` — paged; `event_id` comes from the other tools' results |\r\n\r\n## Reading results\r\n\r\n- Partner events carry `side: \"remote\"` (or a `link_id`). **Keep them\r\n  labelled as the partner's** when you reason or summarize — do not present\r\n  partner knowledge as the user's own, and do not re-save partner content\r\n  into the user's memory unless the user explicitly asks.\r\n- `find_partner_memory_connections` never claims something is *absent* on the partner side —\r\n  entry is home-only, so the partner is only reached through bridges. Absence\r\n  of remote candidates means \"no bridge found\", not \"they don't know\".\r\n- Aliased bridge entities carry `df_home` / `df_remote` (how common the\r\n  entity is on each side). Asymmetry is a signal: \"1 here, 109 there\" means a\r\n  passing mention for the user is a central topic for the partner — often the\r\n  most interesting finding in the response.\r\n- `found: false` from `get_partner_memory_content` means the link does not\r\n  surface that event — deliberately the same answer whether it is absent or\r\n  out of scope. Don't retry; don't speculate which.\r\n\r\n## When a call returns `status: \"error\"`\r\n\r\nThe `reason` names what to do — an error here **never** means the user's own\r\nmemory failed:\r\n\r\n- `no_links`, `link_not_found`, `link_not_active`, `link_expired`,\r\n  `org_not_party`, `principal_not_active` — this link cannot be read (or this\r\n  direction is closed). Show `list_partner_links` output; fixing it is an\r\n  owner/console action, not a retry.\r\n- `we_are_provider` — the user's org is the *providing* side; there is\r\n  nothing to read in this direction. Normal state, not a failure.\r\n- `contract_version_too_old` — both owners must re-consent;\r\n  `list_partner_links` → `reconsent` shows who is missing.\r\n- `budget_exceeded` — the remote row/time budget ran out mid-walk. Narrow the\r\n  ask (smaller `top_n`/`k`/`LIMIT`, tighter relation params) instead of\r\n  repeating it.\r\n- `busy` — a concurrency limit on **your** server (never the partner's). The\r\n  `detail` says which of two: the per-org limit, which is almost always\r\n  self-inflicted (two link calls issued together) — re-issue the refused one\r\n  once the other finishes, it cost nothing and did not run; or the server-wide\r\n  limit, shared with other tenants, where a short wait is the right response.\r\n  Either way it is not a partner problem.\r\n- `remote_failure`, `internal` — infrastructure failed; try later.\r\n\r\nResults can also be `partial` (budget hit mid-walk): what came back is valid,\r\njust incomplete — say so instead of treating it as the full picture.\r\n"
AFTER
"---\nname: aiakiv-links\ndescription: >-\n  Read a LINKED partner org's memory through the partner memory tools. Use when\n  the user asks what a partner/linked org/team knows, wants to compare their\n  memory with a partner's, mentions a link or partner org, or when a probe\n  candidate carries side=remote. Covers choosing between search_partner_memory,\n  find_partner_memory_connections and query_partner_memory_graph, reading results, and what each error reason\n  means. Also covers public attaches (public memory attached to the user's\n  team, listed under public_attaches with __public: ids).\n---\n\n# AiAkiv links (partner-org memory)\n\nA **link** is a read capability two orgs agreed to — not a project you switch\ninto. You pass `link_id` per call; your own scope is untouched. Everything is\nread-only: you can never write into a partner org.\n\n**Always start with `list_partner_links`.** It is local (works even when the\npartner is down) and tells you which links are `usable` before you spend a\nremote call. If the tools are absent from the tool list, the server has links\ndisabled — say so.\n\nLinks run **one way**, and the list holds the ones whose reading direction\npoints at the user's org — blocked ones included, with `usable` saying which\nanswer right now. Links their org **provides** (their team issued the invite, so\nthe link opens their memory to the partner) are left out entirely — nothing to\nread, nothing to fix; `provided_link_count` says how many exist, and they are\nmanaged in the console.\n\n**Call link tools one at a time.** Your org may have only one link call in\nflight at once. Two link tools issued in the same batch — the habit that serves\nyou well everywhere else — means the second returns `error: busy` without\nrunning, even on a completely idle server. Await each call before starting the\nnext; `list_partner_links` is local and does not count.\n\n## Public attaches (`public_attaches`)\n\n`list_partner_links` also returns `public_attaches`: public memory the user's\nteam attached to itself in the console (team \"Links\" page, \"Public attach\"\nsection). There is no contract and no partner on the other side. A public org\nis open to read anyway; the attach only adds name bridges (aliases) so walks\nand graph queries can cross into it. Each row has `kind: \"public\"`, a\n`link_id` of the form `__public:<org_id>`, `partner_name`, `usable`,\n`blocked_reason` and `alias_count`.\n\n- A `usable` public attach works in the same four tools with that `link_id`,\n  exactly like a link. Results carry `side: \"remote\"` the same way, and the\n  same rule applies: keep them labelled as the public org's, not the user's.\n- The section comes back to **every member**, even though the link contract\n  list is owner-only. `links: []` with `links_unavailable_reason:\n  \"caller_not_owner\"` and a `note` means the user is not the team owner, not\n  that nothing is readable: use the public attaches that are listed.\n- `blocked_reason: \"attach_not_enabled\"`, or a `__public:` id that is not\n  listed, means the attach is off or the org is no longer public. Turning it\n  on is a console action by the team owner; do not retry.\n- `alias_count: 0` means searches and bodies still work but walks and graph\n  queries stay home-only (no bridge). Say so instead of reporting absence.\n\n## Which tool for which question\n\n| Question shape | Tool |\n|---|---|\n| \"What does the partner know about X?\" — search THEIR memory directly | `search_partner_memory(sentence, link_id)` — entry happens on their side; results are their events only |\n| \"From what WE know, what connects to their side?\" — walk from your context across shared ground | `find_partner_memory_connections` — entry in YOUR org, expansion crosses through **aliased entities** (entities the link declared \"same thing on both sides\") |\n| Explicit relations across both orgs (shared entities, vector distance, ranked bridges) | `query_partner_memory_graph(link_id, query, params)` — same language as `query_memory_graph`; see the `aiakiv-graph-query` skill |\n| Read one partner event's body | `get_partner_memory_content(link_id, event_id)` — paged; `event_id` comes from the other tools' results |\n\n## Reading results\n\n- Partner events carry `side: \"remote\"` (or a `link_id`). **Keep them\n  labelled as the partner's** when you reason or summarize — do not present\n  partner knowledge as the user's own, and do not re-save partner content\n  into the user's memory unless the user explicitly asks.\n- `find_partner_memory_connections` never claims something is *absent* on the partner side —\n  entry is home-only, so the partner is only reached through bridges. Absence\n  of remote candidates means \"no bridge found\", not \"they don't know\".\n- Aliased bridge entities carry `df_home` / `df_remote` (how common the\n  entity is on each side). Asymmetry is a signal: \"1 here, 109 there\" means a\n  passing mention for the user is a central topic for the partner — often the\n  most interesting finding in the response.\n- `found: false` from `get_partner_memory_content` means the link does not\n  surface that event — deliberately the same answer whether it is absent or\n  out of scope. Don't retry; don't speculate which.\n\n## When a call returns `status: \"error\"`\n\nThe `reason` names what to do — an error here **never** means the user's own\nmemory failed:\n\n- `no_links`, `link_not_found`, `link_not_active`, `link_expired`,\n  `org_not_party`, `principal_not_active` — this link cannot be read (or this\n  direction is closed). Show `list_partner_links` output; fixing it is an\n  owner/console action, not a retry.\n  - One case has nothing to fix: a `link_id` that `list_partner_links` does not\n    list at all (the user may have copied it from the console's \"links we\n    provide\" group) is one their org **provides**, and its refusal is\n    `principal_not_active`. Say that it opens their memory outward rather than\n    sending them to fix a direction.\n- `attach_not_enabled` — a `__public:` id whose attach is off, or whose org is\n  no longer public (see \"Public attaches\" above). Owner/console action.\n- `contract_version_too_old` — both owners must re-consent;\n  `list_partner_links` → `reconsent` shows who is missing.\n- `budget_exceeded` — the remote row/time budget ran out mid-walk. Narrow the\n  ask (smaller `top_n`/`k`/`LIMIT`, tighter relation params) instead of\n  repeating it.\n- `busy` — a concurrency limit on **your** server (never the partner's). The\n  `detail` says which of two: the per-org limit, which is almost always\n  self-inflicted (two link calls issued together) — re-issue the refused one\n  once the other finishes, it cost nothing and did not run; or the server-wide\n  limit, shared with other tenants, where a short wait is the right response.\n  Either way it is not a partner problem.\n- `remote_failure`, `internal` — infrastructure failed; try later.\n\nResults can also be `partial` (budget hit mid-walk): what came back is valid,\njust incomplete — say so instead of treating it as the full picture.\n"
Full snapshot data
{
  "description": "Read a LINKED partner org's memory through the partner memory tools. Use when the user asks what a partner/linked org/team knows, wants to compare their memory with a partner's, mentions a link or partner org, or when a probe candidate carries side=remote. Covers choosing between search_partner_memory, find_partner_memory_connections and query_partner_memory_graph, reading results, and what each error reason means. Also covers public attaches (public memory attached to the user's team, listed under public_attaches with __public: ids).",
  "included_files": [],
  "name": "aiakiv-links",
  "skill_md_contents": "---\nname: aiakiv-links\ndescription: >-\n  Read a LINKED partner org's memory through the partner memory tools. Use when\n  the user asks what a partner/linked org/team knows, wants to compare their\n  memory with a partner's, mentions a link or partner org, or when a probe\n  candidate carries side=remote. Covers choosing between search_partner_memory,\n  find_partner_memory_connections and query_partner_memory_graph, reading results, and what each error reason\n  means. Also covers public attaches (public memory attached to the user's\n  team, listed under public_attaches with __public: ids).\n---\n\n# AiAkiv links (partner-org memory)\n\nA **link** is a read capability two orgs agreed to — not a project you switch\ninto. You pass `link_id` per call; your own scope is untouched. Everything is\nread-only: you can never write into a partner org.\n\n**Always start with `list_partner_links`.** It is local (works even when the\npartner is down) and tells you which links are `usable` before you spend a\nremote call. If the tools are absent from the tool list, the server has links\ndisabled — say so.\n\nLinks run **one way**, and the list holds the ones whose reading direction\npoints at the user's org — blocked ones included, with `usable` saying which\nanswer right now. Links their org **provides** (their team issued the invite, so\nthe link opens their memory to the partner) are left out entirely — nothing to\nread, nothing to fix; `provided_link_count` says how many exist, and they are\nmanaged in the console.\n\n**Call link tools one at a time.** Your org may have only one link call in\nflight at once. Two link tools issued in the same batch — the habit that serves\nyou well everywhere else — means the second returns `error: busy` without\nrunning, even on a completely idle server. Await each call before starting the\nnext; `list_partner_links` is local and does not count.\n\n## Public attaches (`public_attaches`)\n\n`list_partner_links` also returns `public_attaches`: public memory the user's\nteam attached to itself in the console (team \"Links\" page, \"Public attach\"\nsection). There is no contract and no partner on the other side. A public org\nis open to read anyway; the attach only adds name bridges (aliases) so walks\nand graph queries can cross into it. Each row has `kind: \"public\"`, a\n`link_id` of the form `__public:<org_id>`, `partner_name`, `usable`,\n`blocked_reason` and `alias_count`.\n\n- A `usable` public attach works in the same four tools with that `link_id`,\n  exactly like a link. Results carry `side: \"remote\"` the same way, and the\n  same rule applies: keep them labelled as the public org's, not the user's.\n- The section comes back to **every member**, even though the link contract\n  list is owner-only. `links: []` with `links_unavailable_reason:\n  \"caller_not_owner\"` and a `note` means the user is not the team owner, not\n  that nothing is readable: use the public attaches that are listed.\n- `blocked_reason: \"attach_not_enabled\"`, or a `__public:` id that is not\n  listed, means the attach is off or the org is no longer public. Turning it\n  on is a console action by the team owner; do not retry.\n- `alias_count: 0` means searches and bodies still work but walks and graph\n  queries stay home-only (no bridge). Say so instead of reporting absence.\n\n## Which tool for which question\n\n| Question shape | Tool |\n|---|---|\n| \"What does the partner know about X?\" — search THEIR memory directly | `search_partner_memory(sentence, link_id)` — entry happens on their side; results are their events only |\n| \"From what WE know, what connects to their side?\" — walk from your context across shared ground | `find_partner_memory_connections` — entry in YOUR org, expansion crosses through **aliased entities** (entities the link declared \"same thing on both sides\") |\n| Explicit relations across both orgs (shared entities, vector distance, ranked bridges) | `query_partner_memory_graph(link_id, query, params)` — same language as `query_memory_graph`; see the `aiakiv-graph-query` skill |\n| Read one partner event's body | `get_partner_memory_content(link_id, event_id)` — paged; `event_id` comes from the other tools' results |\n\n## Reading results\n\n- Partner events carry `side: \"remote\"` (or a `link_id`). **Keep them\n  labelled as the partner's** when you reason or summarize — do not present\n  partner knowledge as the user's own, and do not re-save partner content\n  into the user's memory unless the user explicitly asks.\n- `find_partner_memory_connections` never claims something is *absent* on the partner side —\n  entry is home-only, so the partner is only reached through bridges. Absence\n  of remote candidates means \"no bridge found\", not \"they don't know\".\n- Aliased bridge entities carry `df_home` / `df_remote` (how common the\n  entity is on each side). Asymmetry is a signal: \"1 here, 109 there\" means a\n  passing mention for the user is a central topic for the partner — often the\n  most interesting finding in the response.\n- `found: false` from `get_partner_memory_content` means the link does not\n  surface that event — deliberately the same answer whether it is absent or\n  out of scope. Don't retry; don't speculate which.\n\n## When a call returns `status: \"error\"`\n\nThe `reason` names what to do — an error here **never** means the user's own\nmemory failed:\n\n- `no_links`, `link_not_found`, `link_not_active`, `link_expired`,\n  `org_not_party`, `principal_not_active` — this link cannot be read (or this\n  direction is closed). Show `list_partner_links` output; fixing it is an\n  owner/console action, not a retry.\n  - One case has nothing to fix: a `link_id` that `list_partner_links` does not\n    list at all (the user may have copied it from the console's \"links we\n    provide\" group) is one their org **provides**, and its refusal is\n    `principal_not_active`. Say that it opens their memory outward rather than\n    sending them to fix a direction.\n- `attach_not_enabled` — a `__public:` id whose attach is off, or whose org is\n  no longer public (see \"Public attaches\" above). Owner/console action.\n- `contract_version_too_old` — both owners must re-consent;\n  `list_partner_links` → `reconsent` shows who is missing.\n- `budget_exceeded` — the remote row/time budget ran out mid-walk. Narrow the\n  ask (smaller `top_n`/`k`/`LIMIT`, tighter relation params) instead of\n  repeating it.\n- `busy` — a concurrency limit on **your** server (never the partner's). The\n  `detail` says which of two: the per-org limit, which is almost always\n  self-inflicted (two link calls issued together) — re-issue the refused one\n  once the other finishes, it cost nothing and did not run; or the server-wide\n  limit, shared with other tenants, where a short wait is the right response.\n  Either way it is not a partner problem.\n- `remote_failure`, `internal` — infrastructure failed; try later.\n\nResults can also be `partial` (budget hit mid-walk): what came back is valid,\njust incomplete — say so instead of treating it as the full picture.\n"
}

SHA-256 of public snapshot: 00ab5cbef6ff728708a6c34b6a584585a03fb0ed832599001e02d5d8cff094aa