About Farrow
The simplified product model, implementation boundaries, native evidence, current limits, and release gates.
- Design explains why Farrow has one Inventory, one deployment, and one fixed-IP network.
- Status separates implemented behavior, native validation, and remaining release gates.
- Engineering defines source, generated-output, package, image-pipeline, and evidence boundaries.
Farrow’s simplified one-deployment architecture, networking, state, safety boundaries, and review conclusion.
What the current simplified tree has passed natively, what remains unverified, and what blocks 1.0.
Source layout, build and test gates, image normalization, release outputs, and evidence policy.