Expand description
What a tool call actually does, once it reaches the factory.
§Why a chain shares one itinerary
The rails are per-chain, not per-run: Hops bound how far a causal chain travels, Fuel bounds what that chain may spend in total, the run cap bounds how many runs it may start. A flight sent by an agent continues the chain that woke it, so it must be accounted against the same itinerary — mint a fresh one and every rail resets, and a loop between two agents runs forever on a budget that is renewed each time round.
That is why itineraries are held here and looked up by identifier rather than constructed per flight.
Structs§
- Chains
- The itineraries a running factory is accounting against.
- Factory
Runtime - Everything a tool call needs, wired to a real factory.
- Wiring
- Where a runtime reads and writes everything outside itself.
Type Aliases§
- Book
Layover - Where work set down goes.
- Queue
Flight - Where a sent flight goes.
- Read
Learnings - Everything a tool call needs, wired to a real factory.
- Write
Learnings - How it writes them back.