@agent-native/core 0.122.3 → 0.123.0

package/docs/content/template-assets.mdx

@@ -5,9 +5,9 @@ description: "An agent-native digital asset manager and cross-agent generation s
 
 # Assets
 
-Assets is an agent-native workspace for creating and managing brand-consistent media. It organizes uploads and generated results into libraries and folders, lets teams collect examples for blog heroes, diagrams, landing pages, product shots, videos, and logos, then routes generation through the agent chat so every asset can be reviewed and refined.
+Assets is a workspace for creating and managing brand-consistent media — for anyone who needs on-brand images and video without wrangling prompts, models, and aspect ratios every time. It organizes uploads and generated results into libraries and folders, lets teams collect examples for blog heroes, diagrams, landing pages, product shots, videos, and logos, then routes generation through the agent chat so every asset can be reviewed and refined.
 
-<WireframeBlock id="doc-block-x7640h">
+<WireframeBlock id="doc-block-assets1">
   <Screen
     surface="desktop"
     html={
@@ -18,7 +18,7 @@ Assets is an agent-native workspace for creating and managing brand-consistent m
 
 When you open the app, the selected library, prompt, references, and generated candidates stay in one workspace. The agent can browse, search, generate, refine, and export every asset through the same actions the UI uses.
 
-<Diagram id="doc-block-5egxh6" title="Generate, review, reuse" summary={"References and prompts feed a generate-and-choose session; chosen assets land in a library and flow out to other apps via the picker or A2A."}>
+<Diagram id="doc-block-assets2" title="Generate, review, reuse" summary={"References and prompts feed a generate-and-choose session; chosen assets land in a library and flow out to other apps via the picker or A2A."}>
 
 ```html
 <div class="diagram-assets">
@@ -91,14 +91,10 @@ When you open the app, the selected library, prompt, references, and generated c
 ## What you can do with it
 
 - **Create asset libraries.** Group reference images, videos, canonical logos, style notes, palettes, folders, and generated output by brand, campaign, product, or category.
-- **Generate through chat.** The home composer and library Generate controls send the prompt to the agent with `sendToAgentChat()`, so users can inspect variants, give feedback, and iterate.
-- **Generate images and videos.** Builder-managed image generation is available when enabled, and Gemini powers video generation plus the manual image fallback.
-- **Upload and describe references.** Add images or videos from the library UI or prompt composer attachment button, then search by title, description, alt text, prompt, model, media type, status, role, folder, or collection.
-- **Keep a generation audit log.** Every run records prompts, model, aspect ratio, references, source asset, lineage, generated assets, status, errors, and timestamps for later design review.
-- **Preserve logo accuracy.** The agent can generate a placeholder area and the server composites the uploaded canonical logo onto the final image instead of relying on the image model to redraw it.
-- **Embed as a picker.** Other apps can iframe `/picker` and listen for the `chooseAsset` event from `@agent-native/embedding`, turning Assets into an asset picker/generator for blog editors, site builders, slide decks, and custom apps. The picker also emits the legacy `chooseImage` alias for existing image-only hosts.
-- **Install as an app-backed skill.** The `agent-native.app-skill.json` manifest exports an Assets skill plus MCP connector metadata so marketplaces can install the app, its instructions, and its picker together.
-- **Serve other agents.** Slides, Design, Content, Mail, and Dispatch can call Assets through A2A to list libraries, generate batches, create videos, refine an asset, fetch exports, and render inline previews where embedding is allowed.
+- **Generate, refine, and review through chat or a library** — candidates, feedback, designer handoff, and the admin audit log all live in [Generating, refining, and reviewing assets](/docs/template-assets-generation).
+- **Build a preset once and let everyone else run it** — a locked prompt template, model, aspect ratio, reference board, and logo policy, so a marketer just pastes a brief and tags the preset. See [Presets: design once, run everywhere](/docs/template-assets-presets).
+- **Use Assets from another app or agent** — embed the picker, call Assets over A2A or MCP, reuse governed Creative Context, or install the Assets skill in a coding agent. See [Using Assets from other apps and agents](/docs/template-assets-integrations).
+- **Fork and extend the template** — the SQL schema, access control, and extension points live in [Assets — architecture and data model](/docs/template-assets-developers).
 
 ## Getting started
 
@@ -114,144 +110,7 @@ Live demo: [assets.agent-native.com](https://assets.agent-native.com).
 4. **Use the asset elsewhere.** Copy the export, embed the picker in another
    app, or let another agent call Assets over A2A.
 
-## The preset-driven workflow
-
-Assets produces its best, most repeatable results when work is split into two
-jobs that need very different skills:
-
-1. **Designing the recipe** — slow, craft-heavy, done once per use case. A
-   designer works with the agent to build a **generation preset**: the rules,
-   references, locked-in model, and a prompt template that has been QA'd until
-   it reliably produces on-brand output.
-2. **Running the recipe** — fast and repeatable. A marketer pastes a campaign
-   brief, tags the preset, and gets a finished, brand-safe asset without
-   touching model settings, aspect ratios, masks, or prompt wording.
-
-A preset is the contract between these two people. The designer encodes taste
-and technical judgment once; everyone else inherits it on every generation.
-Think of presets as the design system for AI-generated assets: a raw prompt is
-a throwaway that drifts every time it is retyped, while a preset is durable,
-shared, and carries the decisions (model, aspect ratio, text and reference
-rules, logo handling, fixed layout) that actually determine whether the output
-is usable.
-
-### Designers: build one preset per use case
-
-Create a separate preset for each repeatable format rather than one generic
-"social post" preset that tries to do everything. Specific presets give the
-model clearer rules and produce better output. Good examples:
-
-- LinkedIn ad
-- Webinar announcement
-- Event speaker card
-- Podcast guest card
-- Customer story quote card
-- Blog hero
-- Blog body diagram
-
-The primary way to build one is **conversationally**: describe the use case to
-the agent and let it create the preset and fill in sensible defaults — model,
-aspect ratio and size, a first prompt template, and text/reference/logo
-policies — then refine in the same conversation ("make it darker", "tighten the
-text policy", "try a square variant"). Because that reasoning shows up directly
-in the defaults the agent picks, run this design conversation on the strongest
-available model.
-
-Each preset locks down:
-
-| Setting             | What it controls                                                                                                     |
-| ------------------- | -------------------------------------------------------------------------------------------------------------------- |
-| Prompt template     | The QA'd creative recipe, with slots for the campaign brief                                                          |
-| Model               | The right image engine for this job (see below)                                                                      |
-| Aspect ratio + size | Output format for the target channel                                                                                 |
-| Text policy         | Whether and how literal copy is rendered vs suppressed                                                               |
-| Reference policy    | Which brand references anchor the look                                                                               |
-| Reference board     | Named fixed or per-run visual references, such as a usual host, guest speaker, product, backdrop, or composition cue |
-| Logo                | Composites the library's canonical logo pixel-perfect after generation, so the model never redraws it                |
-| Skeleton / mask     | A fixed brand plate the subject is composited or inpainted into, for locked layouts                                  |
-
-### Choosing the model per preset
-
-Pick the model in the preset so downstream users never have to:
-
-- **A general high-quality image model** for hero images, rich scenes, and
-  complex compositions, when you need broad aspect-ratio flexibility.
-- **A fast image model** for high-volume social where turnaround matters more
-  than maximum polish.
-- **gpt-image-2** for customer-facing, text-heavy, and identity-sensitive work.
-  It renders crisp literal copy inside the image, and it is the engine used for
-  **mask inpainting** into a fixed layout.
-- **gpt-image-1** for transparent **cutout** subjects that are composited onto a
-  brand plate afterward.
-
-When a use case has a **fixed brand frame** that must survive every generation
-(a webinar template with a locked header and logo, an ad plate with a reserved
-product area), build a preset skeleton: upload the background plate, choose
-gpt-image-2, and optionally add a same-size mask. **Opaque areas are preserved,
-transparent areas are editable**, so the logo, framing, and existing copy come
-back untouched while only the art region changes. Note that gpt-image edits are
-guided semantic rewrites, not pixel-only patches, so the prompt should still
-describe the whole intended image and restate what must not change.
-
-Use the **reference board** when a preset needs annotated visual inputs that
-ride along with each run. Each board entry names one thing — a person, product,
-style, background, or composition example — and can pin up to four images plus a
-plain-language description. Fixed entries attach automatically. Variable
-entries can be replaced per run with `presetReferenceFills`, and required
-variable entries block generation until the agent supplies images from user
-attachments or the library.
-
-For example, a Webinar Announcement preset might use a skeleton plate and mask
-for the locked event chrome, a fixed "Steve" subject entry for the usual host,
-and a required variable "Guest speaker" entry for each event. Use a
-`background` entry for setting context. Use a `composition` entry for layout
-inspiration from a past poster; exact placement belongs in the skeleton plate,
-not a reference image.
-
-### QA the prompt until it is reliable
-
-The model, references, and skeleton set the stage, but the prompt template is
-what turns a brief into a consistently good asset. Have the agent generate
-several candidates against realistic briefs and tighten the template until it
-holds. Techniques worth baking in:
-
-- **Structure the prompt in a fixed order**: scene, subject, key details,
-  constraints. Name the intended use so the model picks the right polish level.
-- **For literal copy, be surgical**: put exact text in quotes or ALL CAPS,
-  specify font, size, color, and placement, and for tricky brand names spell
-  them out. Ask for the text exactly once with no extra characters.
-- **For skeleton or inpainting presets, restate the invariants every run**:
-  "change only the center region, preserve the header, logo, and framing."
-
-Before handing a preset to the wider team, run realistic QA generations
-(including briefs you did not write) and confirm it: follows the use case,
-respects the mask, preserves fixed text and logos, avoids inventing extra
-headlines or badges, uses references correctly, places the subject in the right
-region, handles short and long briefs, and still holds up after a refinement.
-
-### Everyone else: paste the brief, tag the preset, generate
-
-Once a preset exists, running it is three moves: paste the campaign brief, tag
-the preset with `@`, and generate. The tagged preset injects its full aesthetic
-brief into the agent, and the saved model, format, tier, logo, and skeleton all
-apply automatically.
-
-```text
-Create a LinkedIn ad for our webinar on AI landing pages.
-Audience: B2B marketing teams.
-Message: launch campaign pages faster while staying on brand.
-CTA: Register now.
-
-@Webinar Announcement
-```
-
-No model picking, no aspect-ratio math, no mask files, no prompt engineering.
-Rule of thumb: designers own the preset, everyone else owns the brief. If a
-user finds themselves choosing models, masks, or layout rules during normal
-use, the preset is not specific enough yet.
-
-For deeper prompting guidance on the underlying models, see OpenAI's
-[GPT Image prompting guide](https://developers.openai.com/cookbook/examples/multimodal/image-gen-models-prompting-guide).
+To run your own copy: `npx @agent-native/core@latest create my-assets --standalone --template assets`. See [Getting started](/docs/getting-started) for the rest of the local setup.
 
 ## Useful prompts
 
@@ -261,421 +120,12 @@ For deeper prompting guidance on the underlying models, see OpenAI's
 - "Turn this uploaded diagram into a cleaner product explainer image."
 - "Create a video storyboard and save the best frame set to this library."
 
-## Using it from your coding agent
-
-Generate and pick brand media without leaving Codex, Claude Code, Claude, or ChatGPT.
-
-1. **Install once.** This adds the skill instructions and registers the hosted MCP connector together:
-
-   ```bash
-   npx @agent-native/core@latest skills add assets   # alias: image-generation
-   ```
-
-   Default client is `codex`; add `--client claude-code` or `--client all` for others.
-   If you only want the portable skill instructions through the Vercel/open
-   Skills CLI, use:
-
-   ```bash
-   npx skills@latest add BuilderIO/agent-native --skill assets
-   ```
-
-   The Vercel/open Skills CLI installs the instruction file only; it does not
-   run MCP connector setup. Use the Agent Native CLI path above when you want
-   the one-command setup.
-
-2. **Ask for images.** In your agent's chat: "Generate three blog hero options from the Acme product shots." The agent opens the picker with candidate images you can regenerate, retune (prompt, aspect, count), and choose from.
-3. **Pick.** In inline hosts (ChatGPT, Claude.ai, Claude Desktop main chat) the picker renders right in the chat — click a candidate and the choice flows back automatically. On CLI/link-only hosts (Codex, Claude Code, Claude Desktop "Code" tab) you get an **"Open in Assets →"** link; open it, pick in the browser, then paste the copied handoff summary back into your chat — or just say "use image A".
-
-   ```text
-   Paste this selection back into your chat so the agent can use it.
-
-   Selected Assets image for the next step: <label>
-   Media URL: <url>
-   Use this selected asset in the current artifact or design.
-
-   Selected asset context:
-   { "selectedAsset": { "assetId": "...", "url": "...", "mediaType": "image", ... } }
-   ```
-
-4. **Apply to code.** The chosen Media URL and `assetId` come back to the agent, which uses the URL directly in the code it writes (an `<img>` src, a download) or calls `export-asset`.
-
-## For developers
-
-The rest of this doc is for anyone forking the Assets template or extending it.
-
-### Quick start
-
-```bash
-npx @agent-native/core@latest create my-assets --standalone --template assets
-cd my-assets
-pnpm install
-pnpm dev
-```
-
-### Data model
-
-All data lives in SQL via Drizzle ORM (binary media lives in object storage, or the local file-upload fallback during development). Schema: `templates/assets/server/db/schema.ts`. Libraries carry the standard `ownableColumns` and a matching framework shares table, so they slot into the per-user / per-org sharing model.
-
-Note: the SQL table names keep the legacy `image_*` prefix from when the app was called Images. They cover videos and other media too.
-
-| Table                            | What it holds                                                                                                                                                                            |
-| -------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| `image_libraries`                | A library — the top-level container grouped by brand, campaign, product, or category. Holds `custom_instructions`, `style_brief`, canonical logo and cover asset refs, and archive state |
-| `image_library_shares`           | Framework shares table mapping principals (users or orgs) to roles (viewer, editor, admin) per library                                                                                   |
-| `image_collections`              | Style/category groupings inside a library — `style_brief`, `prompt_template`, default aspect ratio and image size                                                                        |
-| `asset_folders`                  | Nestable folders inside a library (`parent_id` for hierarchy)                                                                                                                            |
-| `image_generation_presets`       | Saved generation recipes — media type, prompt template, aspect ratio, model, and text/reference policy                                                                                   |
-| `image_generation_sessions`      | An iterative generate-and-choose session with a brief, status, active asset, and feedback summary                                                                                        |
-| `image_generation_session_items` | Candidate assets within a session, each with a role and note                                                                                                                             |
-| `image_assets`                   | The asset record — media type, role, status, title/description/alt text, prompt, model, dimensions, MIME type, object/thumbnail keys, and lineage                                        |
-| `image_generation_runs`          | The generation audit log — prompt, compiled prompt, model, references, status, errors, and the `source` (`chat` / `ui` / `a2a`) that triggered it                                        |
-
-<DataModel
-  id="doc-block-ezjwnr"
-  title="Assets data model"
-  summary={
-    "Libraries are the ownable container; collections, folders, and presets organize them. Sessions drive generate-and-choose; assets and runs hold output and the audit log. Table names keep the legacy image_* prefix but cover all media."
-  }
-  entities={[
-    {
-      id: "library",
-      name: "image_libraries",
-      note: "Top-level ownable container",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "custom_instructions",
-          type: "text",
-          nullable: true,
-        },
-        {
-          name: "style_brief",
-          type: "text",
-          nullable: true,
-        },
-        {
-          name: "logo_asset_id",
-          type: "id",
-          fk: "image_assets.id",
-          nullable: true,
-        },
-        {
-          name: "archived",
-          type: "boolean",
-        },
-      ],
-    },
-    {
-      id: "library_shares",
-      name: "image_library_shares",
-      note: "Framework shares table",
-      fields: [
-        {
-          name: "library_id",
-          type: "id",
-          fk: "image_libraries.id",
-        },
-        {
-          name: "role",
-          type: "text",
-          note: "viewer / editor / admin",
-        },
-      ],
-    },
-    {
-      id: "collections",
-      name: "image_collections",
-      note: "Style/category groupings",
-      fields: [
-        {
-          name: "library_id",
-          type: "id",
-          fk: "image_libraries.id",
-        },
-        {
-          name: "style_brief",
-          type: "text",
-          nullable: true,
-        },
-        {
-          name: "prompt_template",
-          type: "text",
-          nullable: true,
-        },
-      ],
-    },
-    {
-      id: "folders",
-      name: "asset_folders",
-      note: "Nestable folders",
-      fields: [
-        {
-          name: "library_id",
-          type: "id",
-          fk: "image_libraries.id",
-        },
-        {
-          name: "parent_id",
-          type: "id",
-          fk: "asset_folders.id",
-          nullable: true,
-        },
-      ],
-    },
-    {
-      id: "presets",
-      name: "image_generation_presets",
-      note: "Saved generation recipes",
-      fields: [
-        {
-          name: "media_type",
-          type: "text",
-        },
-        {
-          name: "prompt_template",
-          type: "text",
-        },
-        {
-          name: "model",
-          type: "text",
-        },
-      ],
-    },
-    {
-      id: "sessions",
-      name: "image_generation_sessions",
-      note: "Iterative generate-and-choose",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "status",
-          type: "text",
-        },
-        {
-          name: "active_asset_id",
-          type: "id",
-          fk: "image_assets.id",
-          nullable: true,
-        },
-      ],
-    },
-    {
-      id: "session_items",
-      name: "image_generation_session_items",
-      note: "Candidate assets in a session",
-      fields: [
-        {
-          name: "session_id",
-          type: "id",
-          fk: "image_generation_sessions.id",
-        },
-        {
-          name: "asset_id",
-          type: "id",
-          fk: "image_assets.id",
-        },
-        {
-          name: "role",
-          type: "text",
-        },
-      ],
-    },
-    {
-      id: "assets",
-      name: "image_assets",
-      note: "The asset record",
-      fields: [
-        {
-          name: "id",
-          type: "id",
-          pk: true,
-        },
-        {
-          name: "media_type",
-          type: "text",
-          note: "image / video",
-        },
-        {
-          name: "status",
-          type: "text",
-        },
-        {
-          name: "prompt",
-          type: "text",
-          nullable: true,
-        },
-        {
-          name: "object_key",
-          type: "text",
-          nullable: true,
-        },
-      ],
-    },
-    {
-      id: "runs",
-      name: "image_generation_runs",
-      note: "Generation audit log",
-      fields: [
-        {
-          name: "model",
-          type: "text",
-        },
-        {
-          name: "status",
-          type: "text",
-        },
-        {
-          name: "source",
-          type: "text",
-          note: "chat / ui / a2a",
-        },
-      ],
-    },
-  ]}
-  relations={[
-    {
-      from: "library",
-      to: "collections",
-      kind: "1-n",
-    },
-    {
-      from: "library",
-      to: "folders",
-      kind: "1-n",
-    },
-    {
-      from: "library",
-      to: "assets",
-      kind: "1-n",
-    },
-    {
-      from: "sessions",
-      to: "session_items",
-      kind: "1-n",
-    },
-    {
-      from: "library",
-      to: "library_shares",
-      kind: "1-n",
-    },
-  ]}
-/>
-
-### Customizing it
-
-Assets is a complete, cloneable template. Some practical extension ideas:
-
-- "Add a product catalog connector so product reference shots can be selected by SKU."
-- "Add a strict approval queue before generated assets are marked usable for marketing."
-- "Add a brand review dashboard that filters failed or low-rated generations by model."
-- "Create a workspace-wide default asset library and route Slides image generation through it."
-- "Add a new provider behind the image generation interface after checking the latest provider docs."
-
-The agent edits routes, components, actions, skills, and SQL-backed models as needed. See [Templates](/docs/cloneable-saas) for the full clone, customize, deploy flow, and [A2A Protocol](/docs/a2a-protocol) for cross-app generation.
-
-### Embed the picker
-
-Use the picker route when a human is choosing or generating an asset inside
-another product. Image is the default media type; pass `mediaType=video` when
-you want video browsing/selection:
-
-```tsx
-import { EmbeddedApp } from "@agent-native/embedding";
-
-<EmbeddedApp
-  url="https://assets.agent-native.com/picker?mediaType=image"
-  onMessage={(name, payload) => {
-    if (name === "chooseAsset") {
-      insertAsset((payload as { url: string }).url);
-    }
-  }}
-/>;
-```
-
-External MCP hosts should call `open-asset-picker` instead of constructing this
-iframe by hand. The action returns a browser fallback link and MCP App metadata
-for inline hosts. When a user selects an asset, the picker emits `chooseAsset`,
-the legacy `chooseImage` alias for image assets, and updates MCP App model
-context where the host supports it. When a host opens the fallback link in a
-normal browser tab instead of rendering the MCP App inline, selecting an asset
-copies a handoff summary and shows a copyable context block; paste that summary
-back into the chat so the external agent can use the selected media URL and
-asset metadata.
-
-Codex, Claude Code, and Claude Desktop Code should be treated as link-out hosts
-for this flow. They may not render MCP Apps inline, and remote CDN markdown
-images may not display reliably in the chat transcript. Agents should keep the
-asset link as the source of truth; when a visible inline preview is needed in a
-code-editor chat, download the selected `previewUrl`/`downloadUrl` to a local
-image file and embed that absolute local path.
-
-For generate-and-choose flows, call `open-asset-picker` with `prompt`,
-`autoGenerate: true`, and `count: 3` (customizable from 1-6). The picker opens
-with candidate images and lets the user adjust count, aspect ratio, or a
-generation preset before choosing the final asset URL.
-
-Use A2A when another agent needs to create, search, or export assets without a
-human picker UI.
-
-### Developer: distribute the app skill
-
-The Assets app skill has app id `assets` and hosted MCP URL
-`https://assets.agent-native.com/mcp`.
-
-```bash
-# Easiest hosted install: exported skill instructions plus MCP connector.
-npx @agent-native/core@latest skills add assets
-
-# Vercel/open Skills CLI install: exported instructions only, no MCP config.
-npx skills@latest add BuilderIO/agent-native --skill assets
-
-# Hosted install: URL-only MCP connector, no shared secrets in skill files.
-npx @agent-native/core@latest app-skill ensure --manifest templates/assets/agent-native.app-skill.json
-
-# Local editable launch.
-npx @agent-native/core@latest app-skill launch --manifest templates/assets/agent-native.app-skill.json --local --into ./assets-local
-
-# Marketplace package, including Claude Code marketplace and Vercel Labs skills adapters.
-npx @agent-native/core@latest app-skill pack --manifest templates/assets/agent-native.app-skill.json --out ./dist/assets-skill
-
-# Install a local exported Assets bundle with the open skills CLI.
-npx skills@latest add ./dist/assets-skill --skill assets -a codex -y
-
-# Install from the generated Claude Code marketplace adapter.
-claude plugin marketplace add ./dist/assets-skill/adapters/claude-marketplace
-claude plugin install agent-native-assets@agent-native-apps
-```
-
-The exported skill teaches agents to use the picker for human-in-the-loop
-selection, direct actions for unattended image/video generation, and browser
-links when inline MCP Apps are unavailable.
-
-The Claude marketplace adapter contains a `.claude-plugin/marketplace.json`
-catalog and an `agent-native-assets` plugin with `skills/assets/SKILL.md` plus
-the hosted `.mcp.json`. In interactive Claude Code, the same flow is available
-as `/plugin marketplace add ./dist/assets-skill/adapters/claude-marketplace`,
-`/plugin install agent-native-assets@agent-native-apps`, `/reload-plugins`, and
-`/mcp` for MCP authentication.
-
-If you install from a raw marketplace bundle with `npx skills@latest`, register the
-hosted MCP connector so those instructions can call the live Assets app:
-
-```bash
-npx @agent-native/core@latest app-skill ensure --manifest ./dist/assets-skill/agent-native.app-skill.json --yes
-```
-
 ## What's next
 
+- [**Presets: design once, run everywhere**](/docs/template-assets-presets) — the designer/marketer contract behind repeatable output
+- [**Generating, refining, and reviewing assets**](/docs/template-assets-generation) — candidates, feedback, designer handoff, and the audit log
+- [**Using Assets from other apps and agents**](/docs/template-assets-integrations) — the embedded picker, A2A, Creative Context, and coding-agent install
+- [**Assets — architecture and data model**](/docs/template-assets-developers) — the SQL schema, access control, and action reference
 - [**Templates**](/docs/cloneable-saas) — the clone-and-own model
-- [**Embedding SDK**](/docs/embedding-sdk) — iframe picker and sidecar patterns
 - [**A2A Protocol**](/docs/a2a-protocol) — how other apps call Assets
-- [**File Uploads**](/docs/file-uploads) — storage and authenticated asset serving
 - [**Sharing & Privacy**](/docs/sharing) — library-level access control