Import a repo as a Solution Play
FAI Orchard turns any AI accelerator repo into a production-ready Solution Play — a signed bundle of policy-applied infrastructure, AVM-verified modules, and a verifiable provenance manifest. This guide walks the web import flow end-to-end and links to the CLI parity path.
ℹ️ TL;DR: open a play's detail page → Import as Solution Play → watch the 7-stage harvest stream → download the signed ZIP. Microsoft anchor repos are free; other repos need Pro.
§1 — Find a play
Browse the orchard catalog and open any play's detail page at `/orchard/<variety>/<slug>`. The detail card shows the marketplace badges (confidence band, AVM-composed, WAF score, cost band, carbon band, license class) plus two provenance disclosures:
- Why this exemplar? — the top-3 reference plays the scaffold step retrieved, with similarity scores.
- Why this module? — per resource, the top-3 AVM candidates and the reason the winner was selected.
§2 — Start the import
Click Import as Solution Play. You land on `/orchard/<variety>/<slug>/import`, which shows:
- A free vs paid notice. Microsoft anchor repos (first-party or `microsoft_official`) are free for everyone. Other repos require Pro so harvest costs stay sustainable.
- The primary Import button.
For paid repos, the button opens Stripe Checkout — a single import is €19, or go Pro (€9/mo) for unlimited imports. After payment, you're returned to the import page to start the run.
§3 — Watch the harvest stream
Starting an import enqueues a server-side harvest run and redirects you to `/orchard/<variety>/<slug>/import/<run_id>`. A live Server-Sent Events stream renders a 7-stage timeline:
- discover — resolve the repo + branch
- fetch — clone the source
- extract — analyze architecture + facts
- retrieve — find reference exemplars
- scaffold — generate the play skeleton
- compose-infra — select AVM modules + apply policy
- validate — run the 10-validator gate
The card shows the active stage, a live log tail (last 20 lines), and an ETA. The stream closes on completion or error.
§4 — Download your Solution Play
On success you get a signed download URL plus:
- the manifest URL
- a cosign verify command to check the bundle before deploying
- next-steps copy
Always verify before deploying:
```bash
cosign verify-blob
--bundle <play>.zip.sigstore
<play>.zip
```
A receipt email is sent for paid imports.
§5 — Customize before importing (optional, Pro)
Want org-specific defaults? Open Customize at `/orchard/<variety>/<slug>/customize` — a 7-step wizard:
- Regions — chip-multi-select from the cloud's region catalog.
- Models — per-cloud allow-list + explicit deny-list.
- Naming — prefix/suffix template with a live substitution preview.
- Tags — required governance tags (cost-center, owner, env, …).
- Network — private endpoints, VNet preset, DNS zone overrides.
- RBAC — managed identity, role-assignment policy, Key Vault.
- IaC — Bicep / Terraform / both, AVM-only vs gold, output format.
Finish the wizard to see a 3-way diff (vanilla vs FrootAI policy vs your policy) at `/orchard/<variety>/<slug>/customize/preview` before you import with your settings.
§6 — If something goes wrong
A failed run shows a clear error code + remediation, a support id, and two actions: Try again and Open a GitHub issue (pre-filled with the support id, run id, and error). Common codes:
| code | meaning |
|---|---|
| `harvest_failed` | a pipeline stage threw — check the failed stage |
| `run_expired` | the run record aged out (24h) — start a fresh import |
| `stream_timeout` | the progress stream exceeded its cap — re-open the run |
| `rate_limited` | too many imports this hour (10/h free, 60/h Pro) |
§7 — CLI parity
Everything above is also available from the `frootai orchard` command family — same harvest pipeline, same signed output:
```bash
discover → fetch → extract → retrieve → scaffold → compose-infra → commit
frootai orchard import <owner>/<repo>
customize policy defaults non-interactively
frootai orchard import <owner>/<repo> --customize ./policy.json
Microsoft anchors are free; other repos prompt for Pro auth
frootai orchard import Azure-Samples/azure-search-openai-demo ```
See the CLI getting-started for install (npm + winget / brew / apt) and auth, and the MCP server docs for the agent-native surface.
§8 — Get help
- GitHub: https://github.com/frootai/frootai
- Issues: https://github.com/frootai/frootai/issues
- Pricing: Enterprise & Pro