Turn a requirement into a reviewable logic artifact.
Bound the behavior, compose supported operations, preserve local evidence, and carry accepted state into team review only when needed.
Requirement
Inputs, outputs, assumptions, fallback.
PCD
Monomers, branches, and EVA composition.
.brik
Local events, refs, decisions, and evidence state.
Review
Optional shared Platform handoff.
The blueprint is the review unit.
A bounded artifact makes planned, generated, or existing logic easier to inspect before it spreads through a larger system.
Requirement
State the selected behavior in terms a reviewer can reproduce: inputs, outputs, assumptions, and failure behavior.
Monomers
Use the supported atomic operation catalog instead of inventing hidden semantics.
PCD and EVA
Make branches, returns, sequence, and parallel composition explicit.
Evidence
Attach exact commands, outputs, hashes, decisions, and unresolved assumptions to the inspected scope.
Local first. Shared when the team needs it.
The workflow does not require a Platform login to begin. Collaboration is a separate handoff, not a prerequisite for local review.
Developer
Runs the CLI, inspects PCD candidates, and retains local .brik state.
AI agent
Uses skills and MCP context to work inside explicit authoring and reporting bounds.
Review team
Uses Platform topology, evidence lanes, ownership, and review state for collaboration.
Learn the model, then use the public tools.
Read the PCD language or start a local workflow with the CLI.