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

precedent-search

An advisory: it explains, and blocks nothing, on a hunt for one distinctive name, which refs answers with verified sites.

What it catches

A hunt for one distinctive name, which refs answers with verified sites.

Why

A precedent hunt is a search for one distinctive name, and it is the search the graph answers best: refs lists verified sites, so you land on working code instead of assembling it from grep hits. Measured over 1,499 sessions: 42% of new files were preceded by one of these, 71% in subagent sessions, where only 12.9% reached for a magus verb at all.

Seeing it

A verdict names its rule in brackets, which is how you got here:

advise [precedent-search]: ...

magus describe rule precedent-search prints the same entry at a terminal, and magus describe rules lists every rule this workspace enforces.

See also

  • All rules - what this workspace enforces, deny first
  • The guard - how a verdict is reached and wired
guardrulesprecedent-searchadvise
Last updated (d966bfce)
Glossary

Workspace

The magus root directory that owns a set of projects and shared config; the unit magus operates over. See workspace.

Session

An agent host's conversation, by the id the host delivers to its hooks. magus never mints one: a record with no session is unattributed, and the OS user it carries says whose account ran it.

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.

Conventions

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