buzz-unbriefed
A deny rule by default: it refuses the first Buzz a session authors, by file write or magus buzz -e, before reading the Buzz skill, and names what to run instead.
What it catches
The first Buzz a session authors, by file write or magus buzz -e, before reading the Buzz skill.
Why
Buzz is in no model's training data, so what gets written is Go or TypeScript with the serial numbers filed off, and enough of it parses to reach review. Typical errors of an agent with this repository open throughout: fs\glob indexed as strings when it returns [Path]; .append on a list declared without mut; the ternary form, which upstream-strict parsing rejects outside --embedded; archive\extract, which does not exist; a missing import "fs"; and .sub sliced by character on BYTE-indexed strings. Reading first supplies every one of them. It grades the session, not the file: one Skill(magus-buzz-lang) and every later Buzz write passes. Reads are never gated, since reading is how the language gets learned, so magus buzz <file> and magus buzz -t <file> run something that already exists and go untouched.
Default and override
By default this rule takes the decision deny. A workspace sets it by name, in its root
magusfile, to deny, advise or off:
magus\guard.builtins({"buzz-unbriefed": "advise"})
A loosening takes effect once it is committed; a tightening applies at once.
Seeing it
A verdict names its rule in brackets, which is how you got here:
deny [buzz-unbriefed]: ...
A workspace that sets this rule to advise sees advise [buzz-unbriefed]: ... instead.
magus describe rule buzz-unbriefed 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
- Setting a built-in rule - how a workspace changes this default