← AiAkiv MemoryCONTENT HISTORY

Update to AiAkiv Memory

Snapshot Nov 13, 2026 · 12:12 UTC · version 2.4.0

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for aiakiv-save-and-recall

Skill instructions — Now says: If the connection is bound to a project that an app manages, saving there is refused by default. The refusal says what the user can turn on in the...

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.

Skill instructions

Before

Nov 6, 2026 · 12:10 UTC

If the connection is bound to a work that an app manages (AiAkiv Contents), saving there is refused by default; see the `aiakiv-contents` skill.

After

Nov 13, 2026 · 12:12 UTC

If the connection is bound to a project that an app manages, saving there is refused by default. The refusal says what the user can turn on in the console; an AI cannot turn it on.

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -9,8 +9,9 @@
 decide whether a saved memory is findable a month later, and what to do when
 a call is rejected.
 
-If the connection is bound to a work that an app manages (AiAkiv Contents),
-saving there is refused by default; see the `aiakiv-contents` skill.
+If the connection is bound to a project that an app manages, saving there is
+refused by default. The refusal says what the user can turn on in the console;
+an AI cannot turn it on.
 
 ## 1. The summary is the retrieval surface
 
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: aiakiv-save-and-recall\ndescription: How to write a memory that will be found again, and how to read what AiAkiv memory returns. Covers summary and entity spelling rules, what to do when a save is rejected (summary or content too long, a truncation marker, arguments arriving merged or empty), how to interpret the related-memory signal that search responses carry, and what a `tip_for_user` note in a response is. Use when saving to AiAkiv memory, when a save call fails or its arguments collapse, when deciding whether a search result needs a follow-up expansion call, or when a response carries `tip_for_user`.\n---\n\n# Saving to and recalling from AiAkiv memory\n\nThe tool descriptions state the contract. This skill covers the parts that\ndecide whether a saved memory is findable a month later, and what to do when\na call is rejected.\n\nIf the connection is bound to a work that an app manages (AiAkiv Contents),\nsaving there is refused by default; see the `aiakiv-contents` skill.\n\n## 1. The summary is the retrieval surface\n\nSearches rank against the summary, not the content. Write it with the words a\nfuture question would use.\n\n- **Keep exact identifiers verbatim.** Code symbols, document numbers, config\n  keys. Paraphrasing `REQUEST_TIMEOUT_MS` into \"the timeout\" hides the record\n  from the one query that will look for it.\n- **Name the actor in the first sentence** when you record someone's judgment,\n  design, or claim. Conclusion-style summaries (\"decided that…\") drop who said\n  it, and \"what did X propose?\" then misses the record.\n- **Give the reason for a decision.** When you record a decision or an\n  implementation, add one sentence on why this option was chosen over the\n  alternatives. The reason often lives only in a design document that is never\n  saved, and without it a later \"why did we do this?\" has nothing to find.\n- Write a complete sentence, not a keyword pile.\n\n## 2. Entity spelling decides what connects\n\nRecall weaves records together on shared entity nodes, so spelling drift\nsilently loses connections.\n\n- **An entity name is the name of a person, product, place or concept**, usually\n  1 to 3 words, never a phrase or sentence. **A tag is a topic of a few words**, not\n  a description of this memory. Details go in `summary` and `content`.\n- **Entity and tag names are visible to everyone in the team**, including parts\n  that cannot read this memory. Do not put sensitive details in them.\n- **A new name of 5 or more words is refused by default**, and so is one over 20 Han\n  or Kana characters with no spaces. A team can change both limits, and the response\n  states the ones in use. The memory is still saved without that name, which\n  comes back in `rejected_entities` or `rejected_tags` with reason `too_many_words`\n  or `too_long`. Shorten it to the real name of the thing and add it with\n  `update_memory` (`add_entities`, `add_tags`). Do not split it into generic pieces.\n  A name that already exists in the team keeps working at any length.\n- **One canonical spelling per entity** — the full name *or* the acronym, not\n  both. Pick one and use it in every save.\n- **Keep proper nouns and acronyms as they are written**: `PostgreSQL`, `RLS`.\n  Do not lowercase or expand them.\n- **Strip transient tokens** — ids, hashes, dates. They never repeat, so they\n  add a node that connects to nothing.\n- A suggested entity returned by the server is advisory. A literal name match\n  does not establish that it denotes the same thing in this record.\n- **When something is renamed, link the two names.** Records before the rename\n  sit on the old entity and records after it on the new one, so a lookup by\n  the new name misses the old ones. Put both names as entities on the record\n  that describes the rename, then call `update_memory` on it with\n  `add_entity_renames=[{\"old\": \"<old name>\", \"new\": \"<new name>\"}]`. A lookup\n  by either name then returns both. Do this only for a real rename of the same\n  thing, not for two things that merely look alike.\n\n## 3. When a save is rejected\n\n### The summary is over 500 characters\n\n**Split the event; do not compress the summary.** A summary that wants to be\nlong is describing an event that covers too much. Compressing it blurs several\ntopics into one vector, which then matches no specific query. Split into\nseparate saves, each with its own focused summary, chaining them by passing\nthe previous `event_id` as the next call's `prev_event_id`.\n\nCompress only when the content itself is short and the summary is merely\nverbose. Do not fragment one small record.\n\n### The content is over 50000 characters\n\nSplit the full text across calls the same way, chaining with `prev_event_id`,\ngiving each piece its own summary. Never truncate or summarize the content to\nmake it fit — the summary would then describe text that was not saved.\n\n### `truncation_marker_detected`\n\nThe content carries a marker that some earlier tool left when it cut the text\n(`…2183 tokens truncated…`, `<response clipped>`, `[truncated]`). The save is\nrejected because nothing downstream can tell a damaged body from a whole one:\nthe summary still describes the missing part and citations still point into\nit, so the damage would be permanent and invisible.\n\nRe-read the source in full and save again, splitting if it is long. Pass\n`allow_truncation_marker=true` only when the marker is genuinely part of what\nyou mean to record, such as a bug report *about* truncation.\n\n### `save_part_no_write_seat`\n\nThe project or key saves to a team part, and this account has no write access\non that part itself. Access on a part above it does not count. Nothing was\nsaved and the daily limit was not used. Do not retry: the same save is refused\nuntil a person changes something. Pass the `message` on to the user as it is. A\nteam admin can give write access on that part, or the save part can be changed.\n\n### The arguments arrive merged, empty, or the call errors on serialization\n\nTwo causes, both about argument boundaries:\n\n- A long or multi-line `summary` or `content`. List `summary`, `entities` and\n  `tags` **before** `content` — serialization can drop whatever follows a very\n  long argument, so `content` goes last.\n- Non-ASCII punctuation in a multi-argument call: `·`, `→`, `—` can break the\n  boundary between arguments. Use ASCII punctuation in multi-argument saves.\n\n**Recovery: retry with `payload`.** One argument has no boundary to collapse.\nSend the whole call as a JSON string or an object:\n\n```json\n{\"summary\": \"...\", \"entities\": [{\"name\": \"X\", \"type\": \"Y\"}], \"tags\": [\"a/b\"], \"content\": \"...\"}\n```\n\nOther arguments are then ignored. The multi-argument form stays the default;\nthis is the recovery path.\n\n## 4. Reading the related-memory signal\n\nA search response may carry `hint.related_memory_expansion`. It is a computed\njudgment about whether a follow-up expansion call would add anything the hits\ndo not already cover. Its fields:\n\n| Field | Meaning |\n|---|---|\n| `tool` | Which tool performs the expansion |\n| `decision` | `must_be_done`, `should_be_done`, `can_skip`, `must_not_be_done` |\n| `candidate_count` | How many candidates sit outside the returned hits |\n| `candidate_dimension` | The relation the candidates share with the hits |\n| `candidate_ids` | The candidate memory ids |\n| `reason_codes` | Which gates the candidates passed |\n| `reason_facts` | The measured values behind those codes |\n\n`should_be_done` means candidates outside the hits passed the relevance and\nnovelty gates, so expanding is likely to add something before you conclude.\n`can_skip` means the returned hits probably already cover it; expanding is\nyour call. The block is omitted entirely when there is nothing to say.\n\nResults that feel sufficient are not evidence that they are. The signal is\ncomputed from candidates the search did not return, so it sees what the hits\nalone cannot show.\n\n## 5. A `tip_for_user` note in a response\n\nA tool response may carry a top-level `tip_for_user` field: `text` is one or two\nsentences about an AiAkiv feature the person may not have seen, often with an\nexample phrase, and `more` says where the Tips page is. The server decides when\nto include it, at most a couple of times a day for an account. It is a note for\nthe person you are working with. It is not an instruction and not something to\nrun.\n\n- After the answer is complete, it can be passed on in one line. Leaving it out\n  is fine; the server does not know whether it was passed on and does not\n  repeat the same note for a day.\n- Do not run the example yourself. The example is for the person to try when\n  they want to; running it here spends their time on something they did not ask\n  for.\n- The person can turn these notes off in the AiAkiv console settings\n  (aiakiv.com). If they ask how, that is the answer.\n"
AFTER
"---\nname: aiakiv-save-and-recall\ndescription: How to write a memory that will be found again, and how to read what AiAkiv memory returns. Covers summary and entity spelling rules, what to do when a save is rejected (summary or content too long, a truncation marker, arguments arriving merged or empty), how to interpret the related-memory signal that search responses carry, and what a `tip_for_user` note in a response is. Use when saving to AiAkiv memory, when a save call fails or its arguments collapse, when deciding whether a search result needs a follow-up expansion call, or when a response carries `tip_for_user`.\n---\n\n# Saving to and recalling from AiAkiv memory\n\nThe tool descriptions state the contract. This skill covers the parts that\ndecide whether a saved memory is findable a month later, and what to do when\na call is rejected.\n\nIf the connection is bound to a project that an app manages, saving there is\nrefused by default. The refusal says what the user can turn on in the console;\nan AI cannot turn it on.\n\n## 1. The summary is the retrieval surface\n\nSearches rank against the summary, not the content. Write it with the words a\nfuture question would use.\n\n- **Keep exact identifiers verbatim.** Code symbols, document numbers, config\n  keys. Paraphrasing `REQUEST_TIMEOUT_MS` into \"the timeout\" hides the record\n  from the one query that will look for it.\n- **Name the actor in the first sentence** when you record someone's judgment,\n  design, or claim. Conclusion-style summaries (\"decided that…\") drop who said\n  it, and \"what did X propose?\" then misses the record.\n- **Give the reason for a decision.** When you record a decision or an\n  implementation, add one sentence on why this option was chosen over the\n  alternatives. The reason often lives only in a design document that is never\n  saved, and without it a later \"why did we do this?\" has nothing to find.\n- Write a complete sentence, not a keyword pile.\n\n## 2. Entity spelling decides what connects\n\nRecall weaves records together on shared entity nodes, so spelling drift\nsilently loses connections.\n\n- **An entity name is the name of a person, product, place or concept**, usually\n  1 to 3 words, never a phrase or sentence. **A tag is a topic of a few words**, not\n  a description of this memory. Details go in `summary` and `content`.\n- **Entity and tag names are visible to everyone in the team**, including parts\n  that cannot read this memory. Do not put sensitive details in them.\n- **A new name of 5 or more words is refused by default**, and so is one over 20 Han\n  or Kana characters with no spaces. A team can change both limits, and the response\n  states the ones in use. The memory is still saved without that name, which\n  comes back in `rejected_entities` or `rejected_tags` with reason `too_many_words`\n  or `too_long`. Shorten it to the real name of the thing and add it with\n  `update_memory` (`add_entities`, `add_tags`). Do not split it into generic pieces.\n  A name that already exists in the team keeps working at any length.\n- **One canonical spelling per entity** — the full name *or* the acronym, not\n  both. Pick one and use it in every save.\n- **Keep proper nouns and acronyms as they are written**: `PostgreSQL`, `RLS`.\n  Do not lowercase or expand them.\n- **Strip transient tokens** — ids, hashes, dates. They never repeat, so they\n  add a node that connects to nothing.\n- A suggested entity returned by the server is advisory. A literal name match\n  does not establish that it denotes the same thing in this record.\n- **When something is renamed, link the two names.** Records before the rename\n  sit on the old entity and records after it on the new one, so a lookup by\n  the new name misses the old ones. Put both names as entities on the record\n  that describes the rename, then call `update_memory` on it with\n  `add_entity_renames=[{\"old\": \"<old name>\", \"new\": \"<new name>\"}]`. A lookup\n  by either name then returns both. Do this only for a real rename of the same\n  thing, not for two things that merely look alike.\n\n## 3. When a save is rejected\n\n### The summary is over 500 characters\n\n**Split the event; do not compress the summary.** A summary that wants to be\nlong is describing an event that covers too much. Compressing it blurs several\ntopics into one vector, which then matches no specific query. Split into\nseparate saves, each with its own focused summary, chaining them by passing\nthe previous `event_id` as the next call's `prev_event_id`.\n\nCompress only when the content itself is short and the summary is merely\nverbose. Do not fragment one small record.\n\n### The content is over 50000 characters\n\nSplit the full text across calls the same way, chaining with `prev_event_id`,\ngiving each piece its own summary. Never truncate or summarize the content to\nmake it fit — the summary would then describe text that was not saved.\n\n### `truncation_marker_detected`\n\nThe content carries a marker that some earlier tool left when it cut the text\n(`…2183 tokens truncated…`, `<response clipped>`, `[truncated]`). The save is\nrejected because nothing downstream can tell a damaged body from a whole one:\nthe summary still describes the missing part and citations still point into\nit, so the damage would be permanent and invisible.\n\nRe-read the source in full and save again, splitting if it is long. Pass\n`allow_truncation_marker=true` only when the marker is genuinely part of what\nyou mean to record, such as a bug report *about* truncation.\n\n### `save_part_no_write_seat`\n\nThe project or key saves to a team part, and this account has no write access\non that part itself. Access on a part above it does not count. Nothing was\nsaved and the daily limit was not used. Do not retry: the same save is refused\nuntil a person changes something. Pass the `message` on to the user as it is. A\nteam admin can give write access on that part, or the save part can be changed.\n\n### The arguments arrive merged, empty, or the call errors on serialization\n\nTwo causes, both about argument boundaries:\n\n- A long or multi-line `summary` or `content`. List `summary`, `entities` and\n  `tags` **before** `content` — serialization can drop whatever follows a very\n  long argument, so `content` goes last.\n- Non-ASCII punctuation in a multi-argument call: `·`, `→`, `—` can break the\n  boundary between arguments. Use ASCII punctuation in multi-argument saves.\n\n**Recovery: retry with `payload`.** One argument has no boundary to collapse.\nSend the whole call as a JSON string or an object:\n\n```json\n{\"summary\": \"...\", \"entities\": [{\"name\": \"X\", \"type\": \"Y\"}], \"tags\": [\"a/b\"], \"content\": \"...\"}\n```\n\nOther arguments are then ignored. The multi-argument form stays the default;\nthis is the recovery path.\n\n## 4. Reading the related-memory signal\n\nA search response may carry `hint.related_memory_expansion`. It is a computed\njudgment about whether a follow-up expansion call would add anything the hits\ndo not already cover. Its fields:\n\n| Field | Meaning |\n|---|---|\n| `tool` | Which tool performs the expansion |\n| `decision` | `must_be_done`, `should_be_done`, `can_skip`, `must_not_be_done` |\n| `candidate_count` | How many candidates sit outside the returned hits |\n| `candidate_dimension` | The relation the candidates share with the hits |\n| `candidate_ids` | The candidate memory ids |\n| `reason_codes` | Which gates the candidates passed |\n| `reason_facts` | The measured values behind those codes |\n\n`should_be_done` means candidates outside the hits passed the relevance and\nnovelty gates, so expanding is likely to add something before you conclude.\n`can_skip` means the returned hits probably already cover it; expanding is\nyour call. The block is omitted entirely when there is nothing to say.\n\nResults that feel sufficient are not evidence that they are. The signal is\ncomputed from candidates the search did not return, so it sees what the hits\nalone cannot show.\n\n## 5. A `tip_for_user` note in a response\n\nA tool response may carry a top-level `tip_for_user` field: `text` is one or two\nsentences about an AiAkiv feature the person may not have seen, often with an\nexample phrase, and `more` says where the Tips page is. The server decides when\nto include it, at most a couple of times a day for an account. It is a note for\nthe person you are working with. It is not an instruction and not something to\nrun.\n\n- After the answer is complete, it can be passed on in one line. Leaving it out\n  is fine; the server does not know whether it was passed on and does not\n  repeat the same note for a day.\n- Do not run the example yourself. The example is for the person to try when\n  they want to; running it here spends their time on something they did not ask\n  for.\n- The person can turn these notes off in the AiAkiv console settings\n  (aiakiv.com). If they ask how, that is the answer.\n"
Full snapshot data
{
  "description": "How to write a memory that will be found again, and how to read what AiAkiv memory returns. Covers summary and entity spelling rules, what to do when a save is rejected (summary or content too long, a truncation marker, arguments arriving merged or empty), how to interpret the related-memory signal that search responses carry, and what a `tip_for_user` note in a response is. Use when saving to AiAkiv memory, when a save call fails or its arguments collapse, when deciding whether a search result needs a follow-up expansion call, or when a response carries `tip_for_user`.",
  "included_files": [],
  "name": "aiakiv-save-and-recall",
  "skill_md_contents": "---\nname: aiakiv-save-and-recall\ndescription: How to write a memory that will be found again, and how to read what AiAkiv memory returns. Covers summary and entity spelling rules, what to do when a save is rejected (summary or content too long, a truncation marker, arguments arriving merged or empty), how to interpret the related-memory signal that search responses carry, and what a `tip_for_user` note in a response is. Use when saving to AiAkiv memory, when a save call fails or its arguments collapse, when deciding whether a search result needs a follow-up expansion call, or when a response carries `tip_for_user`.\n---\n\n# Saving to and recalling from AiAkiv memory\n\nThe tool descriptions state the contract. This skill covers the parts that\ndecide whether a saved memory is findable a month later, and what to do when\na call is rejected.\n\nIf the connection is bound to a project that an app manages, saving there is\nrefused by default. The refusal says what the user can turn on in the console;\nan AI cannot turn it on.\n\n## 1. The summary is the retrieval surface\n\nSearches rank against the summary, not the content. Write it with the words a\nfuture question would use.\n\n- **Keep exact identifiers verbatim.** Code symbols, document numbers, config\n  keys. Paraphrasing `REQUEST_TIMEOUT_MS` into \"the timeout\" hides the record\n  from the one query that will look for it.\n- **Name the actor in the first sentence** when you record someone's judgment,\n  design, or claim. Conclusion-style summaries (\"decided that…\") drop who said\n  it, and \"what did X propose?\" then misses the record.\n- **Give the reason for a decision.** When you record a decision or an\n  implementation, add one sentence on why this option was chosen over the\n  alternatives. The reason often lives only in a design document that is never\n  saved, and without it a later \"why did we do this?\" has nothing to find.\n- Write a complete sentence, not a keyword pile.\n\n## 2. Entity spelling decides what connects\n\nRecall weaves records together on shared entity nodes, so spelling drift\nsilently loses connections.\n\n- **An entity name is the name of a person, product, place or concept**, usually\n  1 to 3 words, never a phrase or sentence. **A tag is a topic of a few words**, not\n  a description of this memory. Details go in `summary` and `content`.\n- **Entity and tag names are visible to everyone in the team**, including parts\n  that cannot read this memory. Do not put sensitive details in them.\n- **A new name of 5 or more words is refused by default**, and so is one over 20 Han\n  or Kana characters with no spaces. A team can change both limits, and the response\n  states the ones in use. The memory is still saved without that name, which\n  comes back in `rejected_entities` or `rejected_tags` with reason `too_many_words`\n  or `too_long`. Shorten it to the real name of the thing and add it with\n  `update_memory` (`add_entities`, `add_tags`). Do not split it into generic pieces.\n  A name that already exists in the team keeps working at any length.\n- **One canonical spelling per entity** — the full name *or* the acronym, not\n  both. Pick one and use it in every save.\n- **Keep proper nouns and acronyms as they are written**: `PostgreSQL`, `RLS`.\n  Do not lowercase or expand them.\n- **Strip transient tokens** — ids, hashes, dates. They never repeat, so they\n  add a node that connects to nothing.\n- A suggested entity returned by the server is advisory. A literal name match\n  does not establish that it denotes the same thing in this record.\n- **When something is renamed, link the two names.** Records before the rename\n  sit on the old entity and records after it on the new one, so a lookup by\n  the new name misses the old ones. Put both names as entities on the record\n  that describes the rename, then call `update_memory` on it with\n  `add_entity_renames=[{\"old\": \"<old name>\", \"new\": \"<new name>\"}]`. A lookup\n  by either name then returns both. Do this only for a real rename of the same\n  thing, not for two things that merely look alike.\n\n## 3. When a save is rejected\n\n### The summary is over 500 characters\n\n**Split the event; do not compress the summary.** A summary that wants to be\nlong is describing an event that covers too much. Compressing it blurs several\ntopics into one vector, which then matches no specific query. Split into\nseparate saves, each with its own focused summary, chaining them by passing\nthe previous `event_id` as the next call's `prev_event_id`.\n\nCompress only when the content itself is short and the summary is merely\nverbose. Do not fragment one small record.\n\n### The content is over 50000 characters\n\nSplit the full text across calls the same way, chaining with `prev_event_id`,\ngiving each piece its own summary. Never truncate or summarize the content to\nmake it fit — the summary would then describe text that was not saved.\n\n### `truncation_marker_detected`\n\nThe content carries a marker that some earlier tool left when it cut the text\n(`…2183 tokens truncated…`, `<response clipped>`, `[truncated]`). The save is\nrejected because nothing downstream can tell a damaged body from a whole one:\nthe summary still describes the missing part and citations still point into\nit, so the damage would be permanent and invisible.\n\nRe-read the source in full and save again, splitting if it is long. Pass\n`allow_truncation_marker=true` only when the marker is genuinely part of what\nyou mean to record, such as a bug report *about* truncation.\n\n### `save_part_no_write_seat`\n\nThe project or key saves to a team part, and this account has no write access\non that part itself. Access on a part above it does not count. Nothing was\nsaved and the daily limit was not used. Do not retry: the same save is refused\nuntil a person changes something. Pass the `message` on to the user as it is. A\nteam admin can give write access on that part, or the save part can be changed.\n\n### The arguments arrive merged, empty, or the call errors on serialization\n\nTwo causes, both about argument boundaries:\n\n- A long or multi-line `summary` or `content`. List `summary`, `entities` and\n  `tags` **before** `content` — serialization can drop whatever follows a very\n  long argument, so `content` goes last.\n- Non-ASCII punctuation in a multi-argument call: `·`, `→`, `—` can break the\n  boundary between arguments. Use ASCII punctuation in multi-argument saves.\n\n**Recovery: retry with `payload`.** One argument has no boundary to collapse.\nSend the whole call as a JSON string or an object:\n\n```json\n{\"summary\": \"...\", \"entities\": [{\"name\": \"X\", \"type\": \"Y\"}], \"tags\": [\"a/b\"], \"content\": \"...\"}\n```\n\nOther arguments are then ignored. The multi-argument form stays the default;\nthis is the recovery path.\n\n## 4. Reading the related-memory signal\n\nA search response may carry `hint.related_memory_expansion`. It is a computed\njudgment about whether a follow-up expansion call would add anything the hits\ndo not already cover. Its fields:\n\n| Field | Meaning |\n|---|---|\n| `tool` | Which tool performs the expansion |\n| `decision` | `must_be_done`, `should_be_done`, `can_skip`, `must_not_be_done` |\n| `candidate_count` | How many candidates sit outside the returned hits |\n| `candidate_dimension` | The relation the candidates share with the hits |\n| `candidate_ids` | The candidate memory ids |\n| `reason_codes` | Which gates the candidates passed |\n| `reason_facts` | The measured values behind those codes |\n\n`should_be_done` means candidates outside the hits passed the relevance and\nnovelty gates, so expanding is likely to add something before you conclude.\n`can_skip` means the returned hits probably already cover it; expanding is\nyour call. The block is omitted entirely when there is nothing to say.\n\nResults that feel sufficient are not evidence that they are. The signal is\ncomputed from candidates the search did not return, so it sees what the hits\nalone cannot show.\n\n## 5. A `tip_for_user` note in a response\n\nA tool response may carry a top-level `tip_for_user` field: `text` is one or two\nsentences about an AiAkiv feature the person may not have seen, often with an\nexample phrase, and `more` says where the Tips page is. The server decides when\nto include it, at most a couple of times a day for an account. It is a note for\nthe person you are working with. It is not an instruction and not something to\nrun.\n\n- After the answer is complete, it can be passed on in one line. Leaving it out\n  is fine; the server does not know whether it was passed on and does not\n  repeat the same note for a day.\n- Do not run the example yourself. The example is for the person to try when\n  they want to; running it here spends their time on something they did not ask\n  for.\n- The person can turn these notes off in the AiAkiv console settings\n  (aiakiv.com). If they ask how, that is the answer.\n"
}

SHA-256 of public snapshot: ad51ba0a918d7dcf19824b660507f53891743842bcf35164bc4e6d1ae3657bea