Framework responsibilities

How Farmslot works describes the sequence. The division of responsibility lets different projects use that sequence without copying its implementation.

Component	Owns
Gateway	Run state, slot/resource admission, decisions and publication
Project pack	Project policy, fixtures, hooks and execution templates
Recipe provider	Project runtime and action bindings, domain authorization
Recipe engine	Graph execution, trace, capture lifecycle and claim derivation
Agent runtime	Task materialization, checklist events and terminal artifact checks
Command Center and Companion	Render shared gateway and review models; transport user actions
Worker	Code, recipe authoring and task outputs

Pool and slot configuration supplies machine paths, ports and device identity. Project providers implement their domain behavior and inherit the shared engine, CLI handlers and artifact validator. Clients render shared facts rather than recomputing gate eligibility or proof from file presence.

The recipe engine is the sole normal verdict authority. Workers execute eligible assertions; task ledgers transfer the selected schema-2 engine claims and ac only reads them. Retained schema-1 ledgers stay display only. See Recipe evidence loop for that boundary and Protocol boundaries for the package contracts.