Compose agents
visually.

Studio Drafts are private authoring state. They never load definitions from Pipeline-Repo, and connected Executor agents appear in a separate read-only catalogue. Clone an Executor definition when you want a new editable draft; the live installed definition is never edited in place.

Preview verifies capability-to-executor coverage and shows proposed reads and writes. Studio simulation produces an explainable draft-readiness result without live writes. A high score never makes an unsupported or outward action safe: Executor policy, validation, approval, certification and commissioning gates remain binding.

Exporting a signed agent package lets another workstation import a credential-safe copy pinned to the exact authored version. Studio does not silently mutate installed copies; every replacement is a new package reviewed and accepted by Executor.

1. Build: start a draft, clone a read-only Executor definition, or use Import as Draft. Importing a signed package as a draft does not install it in Executor.
2. Define the workflow graph in domain terms: inputs, stages, dependencies, outputs, validators, approval boundaries and required capabilities. Review node properties and edge order.
3. Check: inspect schema validity, missing bindings, unsupported capabilities and proposed reads/writes. Resolve every required contract gap.
4. Test: use the available simulation/draft tests and review their scope. A no-write simulation does not prove live provider success.
5. Resolve: correct missing inputs, capability coverage and validation findings. Preserve exact intended outputs and approval boundaries.
6. Save: retain the local draft as a new intended version. Changing an agent means its prior revision’s evidence cannot simply be relabeled.
7. Package: export a signed .forge-agent package with an authorized signing setup. Do not embed credentials, private history or runtime state.
8. Executor: explicitly send to a connected Executor when supported, or import the file there. Verify trust, compatibility, certification and commissioning before live use.

Studio’s developer signature attests to package bytes. Independent Fabric Intelligence certification is separate evidence for the exact workflow. Executor verifies any retained attestation and applies its own installation, compatibility, policy, credential and commissioning checks. A self-entered score, successful simulation or exported ZIP grants none of those gates.

Previously imported certified packages can be re-exported only through the verified retained-package path when eligible. Editing the draft does not preserve certification for the changed revision.

Test runs a no-write draft simulation. Certify directs you to connect, save and send the draft to Executor; it does not issue certification. Agent updates opens the connected Executor, where Import agent accepts a reviewed signed replacement package from the same trusted developer. Automatic capability refresh is unavailable: edit the draft, then Check and Test it. Delete local draft removes only the selected saved draft after confirmation and rejects stale revisions; its saved version history and installed Executor agents are retained.

Runtime replay, learning, evaluations and commissioning belong to Executor. A saved draft or successful simulation does not make an installed agent ready for production.

A trusted package with valid independent Fabric Intelligence certification and satisfied dependencies can become ready immediately for manual governed runs, without a second commissioning step. Automatic routing and production-effect authority remain disabled. Other valid imports stay disabled/decommissioned until their admission requirements are met. Unknown, invalid or revoked signatures are quarantined.