# Itinera > A workflow framework that keeps business rules separate from flow control. Separate process from logic. Make agentic code safer. Vision: Every process can be understood by reading it, by any person or agent, however fast the code around it changes. Mission: Itinera keeps business rules apart from flow control. Steps hold the rules and know nothing of the flow; each workflow states, in one place, its steps in order and the policies that decide what happens next; every journey reports what happened and who decided it. One specification gives that meaning to every language, and a shared conformance suite proves each release keeps it. Maintained by [Marlon Sousa](https://marlon-sousa.com/). Code on this site is pseudo-Rust, an illustration. Real, compiled code is in the book, and what Itinera does is defined only by the specification. ## The site - [Itinera](https://itinera-dev.org/index.md): Itinera is a workflow framework that keeps business rules separate from flow control, so every process can be understood by reading it, by people and by agents. - [Why Itinera](https://itinera-dev.org/why.md): How a payment system grows until nobody can say what a request does, why agents make it worse, and the same system with Itinera. - [Languages](https://itinera-dev.org/languages.md): Every language Itinera is implemented in, what each release claims, and how to install it. - [Specification](https://itinera-dev.org/specification.md): How the Itinera specification, the conformance suite and the implementations in each language fit together. - [Releases](https://itinera-dev.org/releases.md): How every Itinera release proves what it claims, with its conformance report. - [Roadmap](https://itinera-dev.org/roadmap.md): Itinera's tiers and milestones, in order, with what is available today. - [Contribute](https://itinera-dev.org/contribute.md): How to propose a feature for Itinera, how the process works, and how Itinera is built with AI. - [News](https://itinera-dev.org/news.md): Releases of Itinera, versions of its specification and new languages, as they happen. - [Brand](https://itinera-dev.org/brand.md): The Itinera logo, what it shows, its colours and how to use them. - [Accessibility](https://itinera-dev.org/accessibility.md): What was tested on the Itinera site and book, how, and how to report a problem. ## The book - [The Rust book](https://itinera-dev.org/book/rust/): Itinera taught in Rust, every example a complete program that compiles and runs. ## Specification and conformance - [Concepts](https://github.com/itinera-dev/spec/blob/main/spec/01-concepts.md): The vocabulary: steps, workflows, policies, hooks, lifecycles, executors, journeys. Read it first. - [The specification](https://github.com/itinera-dev/spec/blob/main/spec/README.md): What every implementation must do, in observable terms. - [VISION.md](https://github.com/itinera-dev/spec/blob/main/VISION.md): Why Itinera exists, its principles and what it is not. - [PROCESS.md](https://github.com/itinera-dev/spec/blob/main/PROCESS.md): How features are proposed, specified, implemented and released. - [The conformance suite](https://github.com/itinera-dev/conformance/tree/v0.1.0-rc.11): The cases every implementation runs, as data. ## Languages - [Rust](https://github.com/itinera-dev/itinera-rs): The Rust implementation. API reference: https://docs.rs/itinera, once published. - TypeScript: planned. - The JVM (Kotlin, with support for Java): planned. ## Optional - [News feed](https://itinera-dev.org/news/feed.xml): Releases and specification versions, as an Atom feed. - [Book index](https://itinera-dev.org/book/): Every edition of the book.