.pcd source is the human-readable
circuit description.
This page is the public documentation for the PCD file shape used with the
current CLI workflow: the PCD File Standard v1.0 envelope, programming baseline
notes, and schema fields shown below.
For distributable or synchronized artifacts, BRIK64 can use a JSON envelope around exact source bytes.
certification_refs is a legacy technical identifier in the
published schema. It holds evidence references and does not imply external
certification or that the code is correct.
Hash Boundary
The semantic hash is calculated from exactpcd_source bytes. Metadata and evidence references are operational context, not part of the semantic source.
Metadata Boundary
Metadata can describe authorship, source authority and local workflow context. It must not contain secrets, tokens, raw private source snapshots or absolute local paths.Editing An Enveloped PCD
When editing an enveloped PCD:- Update
pcd_sourceintentionally. - Recompute or request recomputation of
semantic_pcd_sha256. - Preserve metadata only when it remains true.
- Record the command that produced the new artifact.

