Templates & Marketplace

The Templates & Marketplace surface is how Builders share their work and Cloners discover and reuse it without filing engineering tickets. It also hosts the pre-built reference templates the platform team curates.

This section covers:

• Sharing an agent — the Builder flow: dependency resolution, listing details, publishing internally.
• Cloning an agent — the Cloner flow: discover, try, clone, complete setup.
• Admin controls — who can share, who can clone, per-project toggles.
• Pre-built reference templates — the UNO Rulebook Knowledge Base, the Web Research Tool, and the UNO Rulebook & Web Research Agent — concrete examples showing how the pieces of SimplAI fit together.
• Pre-built productised agents — the Document Intelligence Agents (PDFs → structured data + executive-ready insights) and the Org Flows Agent (auto-built, source-backed org chart with N-1 / N-2 hierarchy).

Where the Marketplace lives

• The Marketplace sidebar tab — the unified browse surface. Today it shows the Internal Marketplace (your tenant). A future SimplAI Marketplace tab is on the roadmap.
• The Deployment → Marketplace sub-tab inside an Application — where Builders initiate sharing, track listing status, and publish or unpublish.

What ships today (M1 — internal-only)

• Internal sharing — within the same tenant. Builders share, other tenant members discover and clone.
• Sandboxed trial sessions — Cloners try a shared agent before cloning. Trial credits charge the Cloner, never the Builder.
• Guided cloning — destination project selector, pre-clone summary of dependencies, automatic setup dialog if credentials are required.
• Builder analytics — total clones, clone time series, tenant breakdown by org (no PII), trial session counts, listing impressions.
• Admin controls — who can share / who can clone (Admin Only, All Members, Specific Roles), per-project toggles.
• Knowledge Base sharing — actual KB data is not shared. The Builder can either add a dummy KB stub or use "Create Dummy KB with AI" which generates a representative KB from a prompt.
• Audit log — every share, update, unpublish, clone, trial event.

What's not yet shipped (planned for future milestones): cross-tenant sharing, the public SimplAI Marketplace, monetisation flows, cross-tenant KB sharing with owner approval.

Sharing principles

• Cloned agents are first-class. They land in the Cloner's chosen project, tagged "Cloned from: <Source>", and are treated like any other Application.
• Cloners can edit but cannot re-share. A clone is a derivative; only the original Builder can publish it as a Marketplace listing.
• Billing is isolated. All trial and post-clone execution is charged to the Cloner. The Builder is never charged for downstream usage.
• Credentials are stripped at publish time. The Cloner provides their own credentials via the setup dialog after cloning.

How a clone happens (high-level)

1. Cloner browses the Marketplace and finds a listing.
2. Cloner clicks Try — a sandboxed trial session opens with trial credits drawn from the Cloner's account.
3. Cloner clicks Clone when they're happy with the trial. Pre-clone summary shows what's needed (credentials, KB resolutions, optional components).
4. Clone executes — the Builder's published version is snapshotted as an immutable "Cloned from v<X>" baseline. The clone lands in the Cloner's chosen project.
5. If credentials are Required by cloner, the setup dialog opens automatically. The agent shows an orange "Setup Incomplete" badge until the Cloner fills them in.

After this, the cloned agent runs like any other agent the Cloner has built.