Documentation

Describe the logic before reviewing the code.

PCD turns a bounded requirement into an inspectable circuit of inputs, decisions, operations, outputs, and fallback behavior.

approval_boundary.pcd

input amount: Money
input role: Role

branch role == guest
  return amount >= 1000

fallback deny

role

compare

approve

deny

A small language for a bounded decision.

PCD keeps the review unit and its domain boundaries narrow enough to understand and explicit enough to reproduce.

Name what enters the selected circuit and what it must return.

Select supported atomic operations instead of hiding behavior inside ad hoc code.

Keep sequence, branches, and parallel paths visible as structure.

Declare the fallback when an input or assumption falls outside the reviewed scope.

The same bounded description can support local authoring, topology inspection, and a team review handoff.

Write the decision, inputs, outputs, and assumptions.

Choose monomers and make branch structure explicit.

Use the CLI to read the PCD and retain command evidence.

Carry the selected blueprint into Platform when collaboration is required.

PCD makes declared logic inspectable. It does not by itself certify the generated implementation or the whole application.

Start with a bounded requirement, then use the public language docs and CLI to create a reviewable blueprint.