Skip to main content
PCD means Program Circuit Description. Raw .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.
The field name 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 exact pcd_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:
  1. Update pcd_source intentionally.
  2. Recompute or request recomputation of semantic_pcd_sha256.
  3. Preserve metadata only when it remains true.
  4. Record the command that produced the new artifact.

Public Boundary

The PCD standard defines file shape, metadata, canonical hash boundaries and authoring rules for the published file format. It is not itself a compiler release, external certification, runtime artifact or evidence pack.