---
{
  "id": "platform.memo.generated-documents",
  "topic": "memo",
  "title": "Skill-generated Memo document references",
  "locale": "en",
  "version": "2026-07-24",
  "summary": "Generated documents are ordinary Memo pages created as a skill-package side effect and resolved through conversation-scoped bindings.",
  "content": "A skill package may create ordinary Memo pages as a side effect. Bindings record each page’s `logicalPath`, `documentRole`, and generation-time `contentSha256`. The canonical read action is `resolve_generated_documents`, using `packageSlug`, `entryKey`, and the package-produced `documentSetName`; `documentRole` may narrow the result.\n\nResolution is limited to the current conversation and to bindings accessible to both the current Agent and triggering user. Missing conversation context or a binding outside that conversation returns not found; this is not a global search. `documentSetName` is normalized to a stable key, so surrounding whitespace does not change the lookup, but never invent a set name.\n\n`resolve_generated_design_system` is a `ui-ux-pro-max` compatibility alias whose registry replacement is the canonical resolver; it is not currently marked deprecated. New calls should use the canonical action. Resolvers only look up references: package execution generates or refreshes content. A resolved page may have been edited later, so compare its returned version and binding `contentSha256` before warning about drift; do not describe `update_page` as regeneration.\n",
  "aliases": [
    "generated memo documents",
    "generated design system",
    "skill package pages",
    "document set binding",
    "resolve generated pages"
  ],
  "tags": [
    "memo",
    "generated-documents",
    "resolver"
  ],
  "relatedActions": [
    "arinova.memo.resolve_generated_documents",
    "arinova.memo.resolve_generated_design_system",
    "arinova.memo.get_page"
  ],
  "relatedActionPrefixes": [],
  "url": "https://docs.arinova.ai/en/kb/memo/generated-documents/"
}
---

A skill package may create ordinary Memo pages as a side effect. Bindings record each page’s `logicalPath`, `documentRole`, and generation-time `contentSha256`. The canonical read action is `resolve_generated_documents`, using `packageSlug`, `entryKey`, and the package-produced `documentSetName`; `documentRole` may narrow the result.

Resolution is limited to the current conversation and to bindings accessible to both the current Agent and triggering user. Missing conversation context or a binding outside that conversation returns not found; this is not a global search. `documentSetName` is normalized to a stable key, so surrounding whitespace does not change the lookup, but never invent a set name.

`resolve_generated_design_system` is a `ui-ux-pro-max` compatibility alias whose registry replacement is the canonical resolver; it is not currently marked deprecated. New calls should use the canonical action. Resolvers only look up references: package execution generates or refreshes content. A resolved page may have been edited later, so compare its returned version and binding `contentSha256` before warning about drift; do not describe `update_page` as regeneration.