Skip to main content

Studio Quickstart: Your First Journey in 10 Minutes

FAOS Studio is where you design agent Journeys on a visual canvas β€” drag nodes, wire them together, and see governance and validation right on the graph, not asserted in a slide. This guide mirrors the in-product Studio tour step for step, so whether you read this first or click through the tour, you'll learn the same first Journey with the same vocabulary.

No code required

Studio Journeys are built by dragging and configuring nodes β€” agents, conditions, compliance checks, case-management steps, and more. You do not need to write code to build one.

What you'll do​

  1. Open Studio and load a real banking KYC example
  2. Tour the five working surfaces: palette, canvas, properties, validation, and test
  3. Save your Journey
  4. Publish it through the governance gate
  5. Run it and read the Monitor view
  6. See what to do next

Step 1 β€” Open Studio and load the example​

Open Studio from the Build-lane navigation (/studio). A brand-new Journey starts on an empty canvas β€” there's nothing to point at yet, so load the example instead: click Load the KYC example on the welcome screen. This seeds a real 10-node banking KYC Journey (two agent steps, a condition, a human-approval step, a PII Scanner, and a Compliance Gate) so every surface below has something real to show you.

Step 2 β€” The five surfaces​

Node palette​

Node palette β€” 26 node types across 7 categories

26 node types across 7 categories β€” agents, conditions, compliance, case management, and more. Search, then drag any node onto the canvas to build your flow.

The canvas​

The canvas β€” the Journey graph with edges and Moat badges

This is your Journey graph. Edges show how the run flows β€” the edge legend decodes each connection type, and the Moat badges on agent nodes show their vetted capabilities.

Properties panel​

Properties panel β€” real agent configuration

Select the first agent node ("Document Verification") and the right panel shows its real configuration β€” model, skills, and catalogs. Select any node to edit its configuration.

Validation​

Validation β€” governance made provable on the canvas

Validation runs right on the canvas, and the PII Scanner and Compliance Gate nodes make governance provable β€” not asserted in a slide.

Test & Evaluate​

Test and Evaluate β€” the compliance trail before going live

Evaluate the Journey and preview its compliance trail before going live. The evidence lives on the canvas β€” the answer to the EU-AI-Act-era buyer question "how do you know it's safe?"

Step 3 β€” Save​

Save with Cmd/Ctrl + S. The lifecycle chip goes to draft, and saving unlocks Publish and the Playground for this Journey.

Step 4 β€” Publish, then Run​

Runs are deny-by-default until a release definition exists β€” so Publish first to pass the governance gate (identity β†’ eval β†’ policy β†’ approval β†’ evidence), then Run. Execution of the business steps you drew arrives in a later release; today's Run evaluates the governance gate itself, and the Monitor view is honest about what actually executed β€” it never implies more happened than did.

Step 5 β€” Read the Monitor view​

After a Run, the Monitor view shows you exactly which gate stages evaluated and their verdicts. If a stage fails, the reason is shown verbatim β€” never a generic "something went wrong."

What's next​

  • Look up any node β€” the Studio Node Reference covers all 26 node types across every category, with the same honesty about what the runtime executes today.
  • Explore templates β€” the Studio template library has journeys across multiple verticals; several ship with a guided walkthrough of their own ("Open with walkthrough" on the template card).
  • Hand off from Architect β€” if you started by describing your Journey in conversation with the Architect experience, use "Customize in Studio" to bring it onto the canvas without losing your context.
  • Export β€” Journeys built in Studio export to portable workflow formats for teams that want to run them outside FAOS.
  • Replay the tour anytime β€” restart the in-product tour from the Studio empty-state screen or the keyboard-shortcuts panel.
Honesty by design

This guide states plainly what Studio does today. Where a step's full promise (like the business-step execution behind Run) isn't shipped yet, this page and the in-product tour say so β€” governance-first products don't get to fudge their own onboarding.