Solutions

Overview

A Solution is a packaged bundle of skills, tools, routines, and templates that work together for one job. Install one and the platform stamps every piece into your org and wires them onto an agent. No copy-paste, no manual config.

The Solutions catalog lives at /solutions in ArchAgents Portal. Browse, activate, and customize from there.

You'll hit Solutions in two places:

1. Onboarder Step 3 ("Customize your FDA"). The Catalog path installs a Solution onto your Forward Deployed Agent so it can start helping customers immediately.
2. Any time later at /solutions to add capabilities to existing agents or stand up new ones.

---

What's inside a Solution

A Solution can include any of:

• Agent templates. A pre-configured agent with identity, instructions, and a starter set of tools and skills.
• Tools. Callable functions the agent can use (HTTP endpoints, scripts, sub-workflows).
• Skills. Reusable instruction bundles the agent loads when it needs them.
• Routines. Event handlers that fire on schedule or when something happens in a thread.
• Scripts and workflows. The behind-the-scenes logic tools and routines call.

A Solution can ship one of these or all of them. The Solutions catalog labels what's included so you know what you're getting.

---

How install works

Solutions install in two steps: import the Solution into your workspace, then install the templates it ships onto agents.

1. Import the Solution

From /solutions, browse Discover and pick one. Importing it copies the Solution's templates into your workspace, where they show up under Available templates (sub-sections for Agent templates, Tools, Routines, Skills).

CLI equivalent:

archagent list solutions
archagent import solution <slug>            # e.g. archastro-onboarding
archagent describe solution <solution_id>

2. Install a template

From an Available template, install it. For an AgentTemplate, install stamps out a brand-new agent (you can override the name and lookup key). For an individual tool or routine template, install attaches it to an existing agent.

CLI equivalent for stamping an agent from a sample:

archagent list agentsamples
archagent install agentsample <slug>
archagent install agentsample <slug> --name "Custom Name" --agent-key custom-handle

You can install the same Solution into multiple agents. Each install is independent; editing one doesn't change the others.

Mix and match

Once a Solution is imported, the individual templates are independent rows under Available templates. Pull one tool from one Solution and a routine from another onto the same agent.

---

The three onboarder paths

Step 3 of the onboarder ("Customize your FDA") offers three ways to teach your Forward Deployed Agent your product. Solutions is path #1.

Path	When to pick it
Catalog (Solutions)	A Solution matches what you do. Fastest setup; minutes, not hours.
Assistant	No Solution matches and you'd rather describe your product than build templates by hand.
Designer	You want to see and adjust each piece directly. Best for fine-tuning later.

See Customize your FDA for the full comparison.

---

Upgrading Solutions

When a Solution publisher ships a new version, the imported Solution's detail page shows an upgrade option. The upgrade flow previews the diff before persisting:

archagent upgrade solution <solution_id> --dry-run
archagent upgrade solution <solution_id>

The dry-run prints which configs the upgrade would add, change, or remove. Running without --dry-run applies the upgrade. Agents already stamped from the old templates don't change automatically; re-install from the new templates if you want them to pick up the changes.

---

Where to go next

1. Customize your FDA: the three paths in Step 3 of the onboarder.
2. Agents: the underlying model Solutions stamp out.
3. Tools, Skills, Routines: the building blocks a Solution bundles.
4. Samples: end-to-end playbooks if you'd rather build something by hand instead of installing a pre-built bundle.