unix-compound

Turn a domain into single-purpose modules that talk via text streams. Lock success first. Build one module at a time. Stop when returns flatten. This is a process, not a framework.

When

• A messy domain needs a small set of one-thing-well pieces.
• You would otherwise fatten one script, prompt, or skill to cover it all.
• You need a stop rule, not another pass "to be thorough."

Not for: draining a ticket queue (ralph-loop), inventorying a shipped product (quality-loop), or grilling one feature (grill-execute-clear).

Process

goal → skeleton → sequence? → (build → check)* → next