symfonic.cli.example_journeys

example_journeys

The twelve curated journeys — one canonical example per capability domain.

T4.3.3 / REQ-S4.3: canonical stateless, tools, memory, knowledge, multimodal, sub-agent, human approval, safety, observability, MCP/plugin, CLI and FastAPI examples using public imports only.

Declaration order is ladder order — the sequence an adopter should meet them in — and :func:symfonic.cli.examples.journeys re-derives that order from :data:~symfonic.cli.example_spec.JOURNEY_DOMAINS so the ladder has exactly one definition.

Every rung is copy-out standalone: no journey imports a sibling, because symfonic examples add <name> copies exactly one directory and a journey that reached outside its own folder would be broken the moment it was taken. The four rungs that need a multi-round model each carry their own byte- identical offline_provider.py for the same reason.