---
audience: engineers
summary: "Three worked ScaiCore flows from end to end \u2014 invoice processor, customer\
  \ support agent, content pipeline."
title: Canonical examples
path: reference/language/examples
status: published
---

These examples demonstrate the v0.1 language using the resolved syntax rules.
All examples from earlier design iterations have been rewritten to follow:
- `=` for all assignments, `:` only for type annotations
- `goal` always internal to `@flexible` / `@guarded`
- Assignment capture only (`result = @block { ... }`)
- `@guarded` with explicit `guard` / `validate`
- `on_failure` error model in `@flexible`
- `enum[...]` for compile-time symbols, `"a" | "b"` for string unions
- `@conversation_policy` as language primitive
- `@budget`, `@debug` blocks where appropriate
- No `@adaptive` (deferred — use `if` + `@checkpoint` pattern, see §6.8), `@operator`, `@registry`, `goto`, or `any`

---

## In this section

- [Example: invoice processor](./examples/invoice-processor) — extract structured invoice data from a PDF, validate it, and route to a human reviewer.
- [Example: customer support agent](./examples/customer-support-agent) — entity-mode flow with memory, plugins, and an escalation path.
- [Example: content pipeline](./examples/content-pipeline) — multi-stage content generation and review using pipeline operators.