Minion docs

New here? Start with What is Minion?

Principles

The rules Minion is built by, and how they apply to the packages you write.

The short rules Minion is built by, and what each one means for the packages you write.

The common path is the one the product takes. Options, fields and branches that exist only for other paths get deleted.

Show one example that matches the current code. When a procedure has several steps, make it a script or a package.

Fail where the code can still name the mistake and refuse the bad write, not later behind a quiet fallback.

When a new way replaces an old one, the work isn't done until the old way is gone.

Fix what makes something slow instead of hiding it with longer timeouts, retries or a degraded mode.

Minion exposes generic primitives. Vendors and frameworks are configuration or ordinary dependencies, not platform branches.

Agents load guidance on demand. Keep the entry point tiny and put detail one step away.

If every test were deleted, production would still keep the code. Test seams that fail that check don't belong.

Keep each fact in one record. Anything derived from it is a cache, and the write path refreshes that cache.

One test covers one workflow: the setup, the actions, and assertions checked against something the code doesn't share.

Ship cheap, reversible changes quickly. Spend the review on changes that are expensive or impossible to undo.