magus v0.4.3 is out. See what's new
¶ View markdown source · ✎ Suggest an edit
2 min read

Worth cloning

Assume magus can be reproduced. A model given the binary can recover the architecture; given the docs, it can recover the rest, and the cost of doing so falls every year. So no part of this project's value is allowed to rest on that being hard. What cannot be recovered from the artifact is the judgment that produced it: which capabilities were refused and why, what was measured before a mechanism shipped, where the line between the tool and the person was drawn and what it cost to hold. That record is the product, and it is published on purpose. A clone that carries it improves the lives of the people who run it, and a clone that drops it is a different tool wearing the name.

The test for what to build is therefore whether it is better when copied. A vocabulary that another build tool adopts makes every agent better at both. A guard rule that another harness lifts protects someone this project never meets. A measurement that kills a feature here saves the same feature elsewhere. Each of those returns more to this project when it spreads than it would have kept by staying scarce, because the thing magus optimizes for, people who can still fix their own software, is not a market to corner.

This prevents the failure that makes the assumption above dangerous: taking on debt to build a moat that will not exist, and then measuring the project by what it managed to keep from people instead of by what it left them able to do.

Enforced by

  • GPL-3.0 makes the copy legal and keeps the copy's improvements public.
  • Scope records that no account, paid tier, or capability behind either exists, so there is nothing a clone would have to route around.
  • A record of refusals and the measurements behind each rule in this section are in the tree, not in anyone's head.

Good

A refusal kept with the measurement that decided it, in A record of refusals:

| an advisory when an agent edits a file it never looked up | not built: 0.8% of 3,560 first edits were never anchored ... |

Bad

Advanced guard rules are available on the Team plan.

It builds the moat this page assumes cannot exist, and it keeps the protection from exactly the people who would have copied it.

See also

designprinciplelicense
Last updated (2df714e8)
Glossary

Project

A directory magus recognizes as a unit of work (it has a magusfile); the unit of caching, scheduling, and dependency tracking. Project in full.

Op

A single tool-native command a target composes (long form: operation); the middle of the work hierarchy (Spell to Op to Target). Op in full.

CI

An ordinary target you compose yourself with ctx.needs; magus does not hardcode its stages. It is the anchor magus affected ci keys off, and ci strips the rw charm. CI in full.

Agent

A model working through an agent host such as Claude Code, Codex, Cursor or OpenCode. magus treats an agent as one more caller of its CLI, MCP tools and console, held to the same checks as a person. Agent in full.

Tool

An action a model can call through its host: a name, a description, a typed input and a result. magus serves its tools over MCP, each a read of the workspace model or a run of the CLI it already has. Tool in full.

Harness

The deterministic scaffolding around the work on a change, for a person or an agent: compiler errors, formatters, linters, checks, gates, leases and hooks, placed at points a person chose. Around an agent's loop, magus supplies one and keeps it outside. Harness in full.

Run

One target executing under one magus invocation, such as magus run test web or magus affected ci. A run keeps its captured output behind an output reference. Every magus run is a run whether or not any job asked for it; see Job for how the two relate. Run in full.

Advisor

One read-only check from the advice suite: it reads the changeset through magus and writes one titled section of findings. The same advisors run as a pull request comment in CI and inside magus diff --impact locally. Advisor in full.

Conventions

This page uses none of the site's convention markers. The full set is on the conventions page.