@agent-native/core 0.24.2 → 0.24.4

package/docs/content/dispatch.md

@@ -9,7 +9,7 @@ Dispatch is the central app that sits in front of every other app in your worksp
 
 Without Dispatch, every app in a multi-app workspace ends up re-implementing the same plumbing: its own Slack bot, its own secret store, its own scheduled jobs, its own copy of the workspace's instructions. Rotating one API key turns into ten redeployments. Adding a new policy turns into ten copy-pastes. Dispatch centralizes all of that in one app so the others stay focused on their domain.
 
-> Dispatch is shipped as a first-party template. This page covers the **concept** — what it is, why you'd want it, and how it fits into a workspace. For the scaffolded app itself (routes, screens, agent guide), see the [Dispatch template](/templates/dispatch).
+> Dispatch is shipped as a first-party template. This page covers the **concept** — what it is, why you'd want it, and how it fits into a workspace. For the scaffolded app itself (routes, screens, agent guide), see the [Dispatch template](/docs/template-dispatch).
 
 ## When you want Dispatch {#when}
 
@@ -151,7 +151,7 @@ Then add credentials to the vault and (optionally) author global workspace resou
 
 ## See also {#see-also}
 
-- [Dispatch template](/templates/dispatch) — the actual scaffolded app, with its full action catalog and agent guide
+- [Dispatch template](/docs/template-dispatch) — the actual scaffolded app, with its full action catalog and agent guide
 - [Messaging](/docs/messaging) — connecting Slack, email, Telegram, WhatsApp
 - [A2A Protocol](/docs/a2a-protocol) — how cross-app delegation works under the hood
 - [Multi-App Workspace](/docs/multi-app-workspace) — the deployment shape Dispatch is built for

package/docs/content/faq.md

@@ -60,17 +60,17 @@ You can, but agent-native works best when built from the ground up. The architec
 
 The framework ships with production-ready templates you can use as daily drivers:
 
-- **[Calendar](/templates/calendar)** — Google Calendar + Calendly-style booking links
-- **[Content](/templates/content)** — Notion-style documents
-- **[Brain](/templates/brain)** — full-page company chat, cited memory, sources, and review queue
-- **[Assets](/templates/assets)** — brand asset libraries, uploads, and generated media
-- **[Slides](/templates/slides)** — presentation builder
-- **[Analytics](/templates/analytics)** — data platform (like Amplitude/Mixpanel)
-- **[Mail](/templates/mail)** — full-featured email client (like Superhuman)
-- **[Clips](/templates/clips)** — async screen + camera recording (replaces Loom)
-- **[Design](/templates/design)** — agent-native HTML prototyping studio
-- **[Forms](/templates/forms)** — form builder (like Typeform)
-- **[Dispatch](/templates/dispatch)** — workspace control plane: shared secrets, integrations, jobs
+- **[Calendar](/docs/template-calendar)** — Google Calendar + Calendly-style booking links
+- **[Content](/docs/template-content)** — Notion-style documents
+- **[Brain](/docs/template-brain)** — full-page company chat, cited memory, sources, and review queue
+- **[Assets](/docs/template-assets)** — brand asset libraries, uploads, and generated media
+- **[Slides](/docs/template-slides)** — presentation builder
+- **[Analytics](/docs/template-analytics)** — data platform (like Amplitude/Mixpanel)
+- **[Mail](/docs/template-mail)** — full-featured email client (like Superhuman)
+- **[Clips](/docs/template-clips)** — async screen + camera recording (replaces Loom)
+- **[Design](/docs/template-design)** — agent-native HTML prototyping studio
+- **[Forms](/docs/template-forms)** — form builder (like Typeform)
+- **[Dispatch](/docs/template-dispatch)** — workspace control plane: shared secrets, integrations, jobs
 
 Each template is a complete app with UI, agent actions, database schema, and AI instructions. See [Templates](/docs/cloneable-saas) for the full picture, or all [Templates](/templates).
 

package/docs/content/template-assets.md

@@ -9,6 +9,28 @@ Assets is an agent-native workspace for creating and managing brand-consistent m
 
 Use it when your team needs reusable visual direction and searchable source assets instead of one-off generic media prompts.
 
+![Assets library for brand media and generated output](https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F769092170a14474f998cbca47384f891?format=webp&width=1200)
+
+## Start Here
+
+1. **Create a library.** Add the brand, campaign, product, or content stream you
+   want to manage.
+2. **Upload references.** Add approved logos, product shots, style examples, or
+   existing videos so the agent has concrete material to work from.
+3. **Generate from chat or a library.** Ask for a hero image, diagram, product
+   shot, or video variant. Assets stores the prompt, references, model, status,
+   and lineage for review.
+4. **Use the asset elsewhere.** Copy the export, embed the picker in another
+   app, or let another agent call Assets over A2A.
+
+## Useful Prompts
+
+- "Generate three blog hero options using the Acme product screenshots as references."
+- "Create a square social image in the launch-campaign style."
+- "Find all approved assets for the onboarding redesign."
+- "Turn this uploaded diagram into a cleaner product explainer image."
+- "Create a video storyboard and save the best frame set to this library."
+
 ## 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.
@@ -77,7 +99,7 @@ context where the host supports it.
 Use A2A when another agent needs to create, search, or export assets without a
 human picker UI.
 
-### Distribute The App Skill
+### Developer: Distribute The App Skill
 
 The Assets app skill has app id `assets` and hosted MCP URL
 `https://assets.agent-native.com/_agent-native/mcp`.

package/docs/content/template-brain.md

@@ -19,17 +19,40 @@ The product surface stays simple on purpose: **Ask** is the primary chat
 experience, while **Sources**, **Review**, and **Knowledge** are admin/support
 surfaces for connecting data, approving proposals, and inspecting cited memory.
 
+![Brain company chat with cited memory sources](https://cdn.builder.io/api/v1/image/assets%2FYJIGb4i01jvw0SRdL5Bt%2F9c9fe3b5b9494e33803cd3f494cba356?format=webp&width=1200)
+
 Use Brain when your team wants agents to answer questions like "why did we make
 this product decision?", "how does this in-development feature work?", or "what
 changed in this process?" with links back to the source conversation, meeting,
 or issue.
 
-Brain is intentionally on an open-source, Glean-shaped path, but it is not a
-complete Glean replacement today. V1 is company chat plus cited memory over
-reviewed knowledge. V1.5 adds Brain-wide search across knowledge,
-captures, and sources, plus reusable workspace connections for source
-credentials. V2 points toward federated app/source search, permission-aware
-result filtering, ranking, and an expertise graph as a future platform layer.
+Brain's shipped shape is company chat plus cited, reviewed memory over approved
+sources. The current template also includes Brain-wide search across knowledge,
+captures, and source records, plus reusable workspace connections for source
+credentials. Broader federated workspace search and expertise ranking are
+platform direction, not something you need to set up on day one.
+
+## Start Here
+
+1. **Try the demo.** Open Ask and choose **Start demo**. Brain seeds a small
+   product-decision corpus, runs the trust checks, and asks a cited question so
+   you can see answers, citations, review, and not-found behavior before adding
+   real company data.
+2. **Add one source.** Start with a single Slack channel, Granola Team-space
+   feed, GitHub repository, Clips export, or generic transcript webhook. Keep
+   the scope small until citations and review quality look right.
+3. **Review before publishing.** Use Review to inspect evidence, edit wording,
+   and approve only durable company memory.
+4. **Ask from the source.** Use Ask for questions that should be grounded in
+   approved knowledge, not raw chat logs.
+
+## Useful Prompts
+
+- "What did we decide about annual pricing, and where was that discussed?"
+- "Find the most recent onboarding-process change and cite the source."
+- "Summarize what this GitHub discussion means for the launch plan."
+- "Review the pending memory proposals and flag anything too vague to publish."
+- "Which sources are stale or failing sync?"
 
 ## What It Includes
 
@@ -402,7 +425,7 @@ workspaces and reveals Review, Knowledge, and **Run eval** follow-ups once the
 demo is ready.
 
 `run-retrieval-eval` checks an offline real-channel-style retrieval set. It
-uses existing workspace Brain data when #dev-fusion stale Fusion branch answers
+uses existing workspace Brain data when the expected branch-safety answers
 already have citation-backed support; otherwise, with `seedIfMissing` enabled,
 it seeds a small Slack-style fallback corpus and re-runs the same checks. The
 result covers Slack-style citations, branch-safety terms, and an unsupported
@@ -442,6 +465,6 @@ The template follows the agent-native four-area contract:
 - **Application state:** route, filters, and selected IDs mirror into `application_state` for agent context.
 
 See [Dispatch](/docs/dispatch) for the workspace control plane, the
-[Dispatch template](/templates/dispatch) for the scaffolded app,
+[Dispatch template](/docs/template-dispatch) for the scaffolded app,
 [Workspace](/docs/workspace) for shared resources, and
 [A2A Protocol](/docs/a2a-protocol) for cross-app delegation.

package/docs/content/template-clips.md

@@ -30,6 +30,25 @@ Think along the lines of Loom + Granola + Wisprflow rolled into one app — but
 - **Smart library views.** Group by project, filter by speaker, auto-tag based on content.
 - **Edit the transcript through chat.** "Fix the mis-transcribed word at 1:42." "Pull three quotes for a blog post." The agent edits the transcript and the UI updates live.
 
+## Start Here
+
+1. **Open Library.** Browse screen recordings, meeting recordings, dictations,
+   folders, and spaces from one place.
+2. **Record or import.** Capture a screen recording, start from a calendar
+   meeting, or use push-to-talk dictation.
+3. **Let the agent clean it up.** Generate a title, summary, chapters, action
+   items, or cleaned-up transcript text.
+4. **Search and reuse.** Ask for the clip, quote, action item, or decision you
+   need, then share the result with the right visibility.
+
+## Useful Prompts
+
+- "Summarize this clip for a product update."
+- "Find the meeting where we discussed the rollout plan."
+- "Pull three customer quotes from this transcript."
+- "Create action items from the last sales call."
+- "Clean up this dictation and turn it into a Linear ticket."
+
 ## Why it's interesting
 
 Three things make Clips a good showcase of what agent-native enables:

package/docs/content/template-design.md

@@ -9,6 +9,27 @@ Design is an agent-native HTML prototyping studio. Instead of a layered drawing
 
 Use it when you want a polished landing page concept, product UI direction, brand exploration, or interactive prototype that can leave the tool as real HTML.
 
+![Design studio showing generated HTML prototypes and tweak controls](https://cdn.builder.io/api/v1/image/assets%2F348da13fcd8b414c87de9066196f7266%2F961bedb713a94463b834c1f2f4643bcf?format=webp&width=1200)
+
+## Start Here
+
+1. **Describe the artifact.** Ask for the screen, flow, landing page, or visual
+   direction you want. Include audience, tone, and any product constraints.
+2. **Compare directions.** Generate a few variants, pick the strongest one, and
+   keep refining instead of starting over.
+3. **Tune the details.** Use tweak controls for common visual changes, or ask
+   the agent for layout, copy, responsive, and interaction changes.
+4. **Export when it is useful.** Download HTML, ZIP, or PDF once the prototype
+   is ready to hand to another tool or teammate.
+
+## Useful Prompts
+
+- "Create three landing-page directions for a technical analytics product."
+- "Make this dashboard denser and easier to scan for an operations team."
+- "Apply our saved design system and simplify the mobile layout."
+- "Export this prototype as a ZIP once the final variant is selected."
+- "Turn this HTML into a stronger pricing page without changing the brand colors."
+
 ## What You Can Do With It
 
 - **Generate complete prototypes.** Describe the screen or page you need and the agent creates a working HTML document with Tailwind styling and Alpine interactions.

package/docs/content/template-forms.md

@@ -28,6 +28,25 @@ When you open the app, you see your forms, the current editor, and a live previe
 - **Route submissions.** Send submission payloads to webhooks, Slack, Discord, or Google Sheets using the built-in integrations.
 - **Publish public forms.** Share a public form URL and show a thank-you message after submission.
 
+## Start Here
+
+1. **Create a form from a prompt.** Ask for the form you want, including the
+   audience and what should happen after submission.
+2. **Refine in the editor.** Adjust labels, validation, choices, and order in
+   the visual builder when direct editing is faster.
+3. **Publish and share.** Use the public form URL for respondents, then watch
+   results arrive in the Responses view.
+4. **Connect destinations.** Route new submissions to Slack, Discord, Google
+   Sheets, webhooks, or your own extension point.
+
+## Useful Prompts
+
+- "Create a beta signup form with role, team size, and priority use case."
+- "Add a required NPS question and a free-text follow-up."
+- "Post every new response to the product Slack channel."
+- "Summarize this week's submissions and group them by customer segment."
+- "Make this form shorter without losing the fields we need for routing."
+
 ## Why it's interesting
 
 The useful part of an agent-native form builder is that setup and iteration happen in the same place. You can ask the agent to add fields, adjust copy, connect Slack notifications, or inspect the submission data, while the UI remains the direct editor for the same SQL records.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agent-native/core",
-  "version": "0.24.2",
+  "version": "0.24.4",
   "type": "module",
   "description": "Framework for agent-native application development — where AI agents and UI share state via files",
   "license": "MIT",