Domain types for Layover.
This crate holds the parts of the design that can be reasoned about and tested without spawning anything. It reads configuration and prompt files from disk; it does not run processes, serve HTTP or call an LLM.
- [
agent] — who an agent is: name, description, purpose, access - [
route] — edges in the route map - [
pipeline] — named entry points, their triggers and their flags - [
prompt] — composing an agent's instructions from files, conditional on flags - [
config] — parsing a factory definition fromlayover.toml - [
graph] — the route map as a directed graph - [
mod@validate] — load-time checks that fail before a human stops watching - [
flight] — the message envelope - [cost] — the ledger, rate cards and the factory-wide Fuel Reserve
- [itinerary] — Hops, Fuel and the deterministic run cap
- [
barrier] — rendezvous joins, including reset and reachability-based abandonment
See docs/architecture.md and docs/routing.md in the repository for the design these
types implement.