Explanation
Each page here answers “why is it like this?”. Teaching a task is the job of the tutorial and the how-to guides, and listing options is the reference’s. Every page states a lean, gives the reason and names the cost. If the design record gives no reason, the page says that too.
field_struct
Section titled “field_struct”- Validity is computed on assignment: why every setter validates its own field, and what goes stale
- Coercion versus validation: two steps, two kinds of error, and three policies
actionable
Section titled “actionable”- Success, failure, skip: why a skip is its own outcome, and why halting is a throw
- The runner is a railway: the first outcome leaves the main track, and each track has its own hooks
- A result is a report, not a handle: you get plain data back, never the action
- Declared failures and result codes: why the codes are a contract
- ActiveModel-shaped, framework-free: copy the shape, keep Rails optional
- How the two gems fit together: input, output and result are all structs
- Metadata is the product: declarations are data, and adapters read them
- Typed, and documented once: every fact written once, every type generated from it
- Why these gems: where they came from
- The Gliders idea: work with the forces already in a system, not against them
- History: the earlier versions, and why this is a complete rewrite
FieldStruct, Actionable and their adapters are open source under the MIT license.