The Gremlin Model

A Gremlin is a named, bounded workflow: a defined input, a defined output, an agent roster, explicit handoff contracts, a completion condition, and at least one human gate. Gremlins never publish, deploy, or take irreversible action autonomously.

Three types

• Type A — single-agent. One agent, one bounded purpose, named because it is intentional and reusable.
• Type B — multi-agent pipeline. Specialists in sequence or parallel; the Gremlin defines the pipeline, handoffs, and completion.
• Type C — Gremlin Team. Chains complete Gremlins under a declared autonomy policy.

Maturity ladder

• draft — defined, not yet run end-to-end
• v0 — run once; contracts updated from real experience
• v1 — run 3+ times; contracts stable
• v2+ — substantive roster or contract change

The publication bar

A Gremlin appears in this catalog as published only after: 3+ real runs, a portability check (it makes sense outside its home setup), and human sign-off. Until then entries are honestly badged example or coming.