Skip to main content
BRIK64 agent work fails when the artifact becomes harder to inspect. Avoid these patterns.

​
Invented Vocabulary

Do not invent monomer names, file standards, command flags or evidence labels. Use the documented catalog and CLI reference.

​
Hidden Behavior

Do not hide important behavior in helper functions without explaining the circuit role. If the helper is necessary, explain its inputs, output and failure behavior.

​
Open Branches

Do not omit blocked cases or return different result kinds from different branches.

​
Unsupported Syntax

Do not write typed-argument syntax, arrow returns or symbolic EVA expressions as executable PCD unless the release documentation supports that syntax.

​
Unauthorized Agent Writes

Do not modify AGENTS.md through brik64 init. Use the public skill repository or host agent environment and require explicit review before writing:

​
Overstated Results

Do not use local checks as broad application claims. Pair results with command output, files changed and evidence status.

​
Internal Vocabulary In Product UI

Do not expose PCD, Polymer, monomer, DTL, ledger, certification or engine-tier language in ordinary user-facing frontend copy unless the page is explicitly an expert developer console. Translate internal BRIK64 terms into product-domain language: Raw PCD names, hashes, .brik paths and command output belong in expandable developer diagnostics, logs, reports or agent-readable evidence, not in primary application labels.