Generation Overview

​

Required Flow

1. Restate the requirement in bounded language.
2. Name inputs, outputs and blocked cases.
3. Select monomers from the catalog.
4. Write PCD with explicit branches and returns.
5. Explain EVA composition in source structure or topology metadata.
6. Create a Polymer only after the PCD candidate exists.
7. Preserve .brik traceability.
8. Run local CLI checks.
9. Report evidence status and remaining assumptions.

​

Example Agent Trace

Requirement: approve orders under a configured limit.
Inputs: amount, limit.
Output: 1 approve, 0 block.
Blocked cases: non-positive amount, non-positive limit, amount > limit.
Monomers: comparison/control in PCD; no extended monomers needed.
Composition: conditional gate followed by explicit return.
Evidence: local CLI output after generation and checks.

​

What Agents Must Avoid

• Do not modify AGENTS.md through brik64 init.
• Do not write outside the managed BRIK64 section unless the user asks.
• Do not invent monomer names.
• Do not treat local evidence as a broad application claim.
• Do not describe future hosted features as active local behavior.
• Do not expose PCD, Polymer, monomer, DTL, ledger, certification or internal engine vocabulary in ordinary end-user frontend copy. Use domain language such as bounded logic, domain rule, validation contract, local trace or review state.

​

Handoff Format

Requirement:
Inputs:
Output:
Fail-closed behavior:
Monomers used:
EVA structure:
Files changed:
CLI checks run:
Evidence status:
Open assumptions: