FleetForge Quickstart
Welcome to FleetForge. This quickstart mirrors the 5-minute tour: launch the local Trust Mesh, run the Hello Fleet acceptance flow, then verify the signed receipts. Expect to spend about ten minutes end-to-end.
How to read these docs: (1) Run the live demo to see receipts fire. (2) Open the Hello Fleet tutorial and follow it once. (3) Verify all four artifacts—capability token, guardrail verdict, manifest, replay. (4) Add an adapter when you need parity with AutoGen, CrewAI, or a custom flow.
1. Launch the Trust Mesh locally
Use the baked-in just demo target to run the runtime, adapters, ClickHouse, and Grafana together:
git clone https://github.com/fleetforgedev/fleetforge.git
cd fleetforge
just demo
Keep the terminal open—you’ll watch planner + worker checkpoints stream by. Toggle guardrails with environment variables (e.g., FLEETFORGE_POLICY_DEFAULT='{"deny_external_calls":true}' just demo) to match the tour’s “Add guardrails” step.
2. Walk through Hello Fleet
Hello Fleet is the canonical acceptance path that your demo, CLI, and /demo storyline all reference. Follow it once to confirm end-to-end receipts and replay parity:
- Hello Fleet tutorial →
- Applies the same commands showcased on the
/productpage. - Includes replay + policy toggles so you can rehearse the “deny, retry, unblock” narrative.
This walkthrough is the receipt chain in order: Wasm guardrails at every hop (Policy Plane), deterministic spans (Replay doc), CLI receipts you can hand to Risk (fleetforge-ctl), and the AI Bill of Materials you export from the same run_id (AIBOM reference).
Other adapters
LangGraph agent_team stays canonical so /, /demo, and CLI all reference the same receipts. When you intentionally showcase AutoGen, CrewAI, Semantic Kernel, or a custom adapter, follow the instructions in the Adapter Matrix, then rerun this LangGraph slice so the storyline never drifts.
3. Inspect receipts and branch out
Every run writes a manifest + C2PA (and optional SCITT) receipt. Verify them locally:
fleetforge-ctl verify build/receipts/<run_id>.c2pa.json \
--manifest build/receipts/<run_id>.json
Next steps:
- Browse the Concepts section for the Trust Mesh pillars (Delivery, Policy, Replay).
- Dive into the Reference CLI docs and AI Bill of Materials to wire receipts into your own release gates.
- Integrate your framework via the Adapter Matrix after the Hello Fleet run lands cleanly.
Once this quickstart feels comfortable, head back to /product when you need a crisp refresher or share it with teammates who only have five minutes.