Getting Started with FrootAI
Start with a useful outcome, not a product inventory.
Discover → choose → set up → complete → verify. Pick one path below and leave with evidence of a first win. You do not need to install every package or understand every FAI product first.
Shortest first win
Explore a real accelerator
No install required. Inspect a source, its evidence boundary, and Repo Intelligence before deciding what to build.
The product flow
Know which product owns the next step
FrootAI separates discovery, reusable solutions, conversion, and verification so a catalog entry is never mistaken for deployment evidence.
Discover
Solution Accelerator
Find and understand a repository or canonical Play.
Choose
Solution Plays
Start from a complete architecture and delivery contract.
Convert
FAI Orchard
Turn a selected repository into a governed candidate Play.
Verify
FAI Engine
Evaluate the exact artifact against explicit evidence.
Choose your first outcome
One path is enough to begin
Each path includes the action, evidence of completion, and a clear continuation. Change paths at any time; your link remains shareable.
Your first journey
- 01
Open Solution Accelerator
Search by outcome, cloud, stack, or publisher instead of starting from a product name.
- 02
Choose one source
Open a repository detail and confirm its publisher, license, evidence status, and canonical source link.
- 03
Inspect the bounded analysis
Review Repo Intelligence and the Agent Feed. Inferred relationships are labelled; catalog presence is not certification.
- 04
Choose the continuation
Open the source, ask Agent FAI, compare a related Play, or send the repository to Orchard for conversion.
Evidence of completion
- You can name the source repository and publisher
- You can distinguish discovered metadata from build or deployment evidence
- You have a canonical detail URL you can share
What happens next
- Compare a related Solution Play
- Convert the selected source in FAI Orchard
- Ask Agent FAI for a bounded architecture summary
Truth before confidence
Discovered, source verified, build verified, and deploy verified are different states. The UI should never collapse them into “production ready.”
Preview before mutation
Review repository content, workspace file plans, permissions, credentials, and cloud previews before any write or deployment.
Community over lock-in
Public catalogs, source links, contribution paths, and portable artifacts should remain understandable outside a single UI.
You are not blocked alone
Get help, learn, or improve the path
Ask Agent FAI for product guidance, use Learning Hub for concepts, or bring unclear setup and documentation back through the community contribution flow.