Ferrite samples are receipts for a product pattern. Each pack includes the domain sketch, deploy shape, workflow, schema or search material, observability, and a runbook that explains what to verify.
Sample catalogue
| Sample | Use it to learn |
|---|---|
| Commerce fulfillment | Checkout admission, inventory reservation, payment wait, fulfillment |
| Support copilot | Ticket intake, knowledge retrieval, SLA escalation |
| Content studio | Editorial review, search, and multichannel publishing |
| IoT incident response | Telemetry intake, classification, runbook dispatch |
| SaaS billing | Usage metering, invoicing, tenant audit |
| Compliance vault | Evidence intake, approval, retention, audit search |
| Collaborative editor | Human and agent planning over convergent text |
| Ferrite Cal | Guarded slot holds, booking, staff operations |
| Workflow orchestration | Private multi-step incident runbooks |
| Secure release rollout | Admission, approval, progressive release, recovery |
Validate the sample layer you use
bash samples/validate-samples.sh
cargo test -p ferrite-sample-apps --test native_samples_gate -- --nocapture
cargo test -p ferrite-workflows --test sample_definitions_gate
cargo test -p ferrite-search --test sample_search_specs_gateThe deployable ferrite-sample-apps runtime serves all packs behind
/samples/. Search, SQL, workflow, and observability files have their own owner
and validation. A well-formed schema does not prove it ran through the SQL app;
a structural check does not prove a public deployment.
Borrow a sample
- Read the pack README and runbook.
- Identify which files are executable and which are reference material.
- Copy the domain pattern into a real app manifest with the exact resources it needs.
- Run local state, retry, and failure tests.
- Deploy a preview and read back the durable effects.
Use Apps when you need a complete browser, identity, and agent-native implementation.