Skip to main content
BIR is the intermediate representation below PCD. It is the layer where a circuit description can be normalized for analysis, execution planning and target generation.

​
Where BIR Fits

PCD source -> parser -> normalized representation -> BIR -> generated artifact
PCD is the authoring surface. BIR is not the language an agent should invent by hand unless a task explicitly asks for low-level representation work.

​
What BIR Is For

  • Making generated structure easier to analyze.
  • Preserving a lower-level representation of the PCD.
  • Feeding compiler or runtime workflows.
  • Supporting artifact comparison when hashes and versions are available.

​
Agent Guidance

Agents should report BIR only when a command produced it or a source file explicitly contains it. Do not infer BIR content from a high-level explanation. When BIR appears in a report, include: 
PCD source:
Command:
BIR artifact:
Artifact hash:
Tool version:
Evidence status:

​
Evidence Status

BIR can support an engineering statement only under a stated inspected scope. A BIR file by itself does not describe the whole project, the runtime environment, or every generated target.