PCD Authoring Rules

​

Required Shape

PC example {
    fn evaluate(input) {
        if (input <= 0) {
            return 0;
        }

        return 1;
    }
}

​

Rules

• Start with PC <name>.
• Use explicit functions.
• Name inputs in plain language.
• Return from every path.
• Keep fail-closed behavior visible.
• Use catalog monomer names only.
• Avoid invented dialect features.
• Explain external behavior before using extended monomers.

​

Review Before Reporting

PCD file:
Circuit name:
Inputs:
Output:
Fail-closed behavior:
Monomers:
EVA structure:
Evidence status: