PCD agent-readable instructions
PCD is the BRIK64 language for describing selected software logic as an inspectable circuit.
- Inputs and outputs: Name what enters the circuit and what the function must return.
- Fail-closed behavior: State what should happen when inputs or assumptions do not fit the scope.
- Monomers: Use catalog operations instead of ad hoc hidden behavior.
- EVA structure: Explain sequence, branch, and parallel composition before handoff.
- Boundary: PCD makes selected logic reviewable. It is not a claim about the whole application.
PCD
Blueprints for bounded logic.
PCD is the BRIK64 language for describing selected software logic as an inspectable circuit.
Format Overview
PCD is a compact authoring profile for reviewable logic.
It gives humans and agents enough structure to inspect logic without inventing a broad scripting language.
Authoring Rules
The public authoring profile keeps generated logic small, inspectable, and scoped.
Inputs and outputs
Name what enters the circuit and what the function must return.
Fail-closed behavior
State what should happen when inputs or assumptions do not fit the scope.
Monomers
Use catalog operations instead of ad hoc hidden behavior.
EVA structure
Explain sequence, branch, and parallel composition before handoff.
Reader Checklist
The checklist lets reviewers compare generated logic without scanning raw code first.
Requirement
What bounded behavior is being modeled?
Monomers
Which operations from the catalog are used?
Evidence status
What command output or review metadata supports the current state?
Write the logic as a blueprint before reviewing generated code.
Use the PCD language docs and CLI workflow to keep bounded logic inspectable.