brik64 blueprint inspects a repository locally and writes a scoped evidence
bundle for review. In Beta18.2 it reports one of three modes so agents do not
overstate what happened:
pcd_certified: local PCD candidates and a local polymer were generated. This is a technical field name from the CLI report; it does not mean the code is certified.sdk_logic: logic was mapped for BRIK64 SDK-first adoption.inspection_draft: the command produced an inspection map only.
audit calls the blueprint workflow as one evidence layer and also records
doctor, ledger, policy lint, and PCD explain diagnostics.
The command writes:
What It Means
blueprint-report.jsonrecordsmode,blueprintSourceand count fields such ascertifiedPcdCount,polymerCountandsdkLogicModules. Names likecertifiedPcdCountare technical report fields; they do not mean the code is certified.operation-coverage.jsonlists operation families observed in source files.unsupported-logic.jsonlists logic that was not converted into scoped PCD candidates or SDK-first modules.pcd-inventory.csvis non-empty only when local PCD candidates were emitted.sdk-logic-modules.jsonlists modules that should be handled through BRIK64 SDKs instead of PCD in the current beta.- Mermaid output is a visual explanation, not a proof artifact.
- The report is local and does not upload private source.
Claim Boundary
brik64 blueprint is a scoped local workflow. The technical mode name
pcd_certified means local candidate evidence exists for generated
PCD/polymer artifacts; it is not a certification of the repository. sdk_logic
and inspection_draft are review modes only. None of these modes claim
whole-application proof, compliance certification, or that the code is
formally correct.
