Product direction

The introduction explains the product and How Farmslot works describes current execution. This page separates the operator's responsibilities from longer-term proposals.

Operator role

The operator chooses intent and priority, approves architecture and risk policy, judges visual evidence and decides when work may publish. Runs supply inspectable changes, reports and evidence for those decisions.

Current boundaries

Projects enter through explicit pack, project and pool configuration. The gateway runs the lifecycle and exposes it through the CLI, Command Center and Companion. QA and review produce reports or reviews; development and bug-fix flows can publish pull requests. Recipes provide executed expectations and retained artifacts, subject to the transition limits in the evidence guide.

Planned direction

Prompt-assisted project import and richer roadmap refinement remain proposals until their owning designs and implementations land. External issues, notes or voice input can supply intent; importing them does not authorize dispatch or mutation. The roadmap tracks the direction, and the recursive feedback proposal remains distinct from the shipped run and retrospective foundations.