loopsmith-core 0.1.1

Config model and validation for loopsmith.

A loop config is the A–H model from the template:

• A information — static context handed to every node
• B pre_execution — the "do it manually first" work list
• C goals — named objectives in natural language
• D validations — how a goal is checked, per goal or overall
• E success — what counts as success, per goal or overall
• F stop_gates — the four layered exits
• G schedules — time or event triggers
• H constraints — limits applied per node or globally

Validation exists to make the corpus rule enforceable: a goal without a machine-checkable validation is the single most common way loops fail, so the config is rejected rather than run.