> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brik64.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# Composition

> How BRIK64 composes monomers, PCD Blueprints, Polymers and system topology.

BRIK64 composition is the process of building larger logic from smaller inspected pieces.

The public model is:

```text theme={null}
Monomer -> PCD Blueprint -> Polymer -> Application/System topology
```

## Layers

| Layer | Responsibility |
| - | - |
| Monomer | Atomic operation vocabulary. |
| PCD Blueprint | Bounded circuit description. |
| EVA structure | The way operations and branches compose. |
| Polymer | A composed unit built from PCD candidates and dependencies. |
| Application/System topology | The larger graph of Polymers, artifacts and integration boundaries. |

## Failure Propagation

Composition is only as strong as its dependencies:

```text theme={null}
invalid PCD -> blocks Polymer refresh
stale dependency -> marks Polymer stale
missing artifact -> limits evidence status
unreviewed generated output -> remains local candidate
```

## Agent Workflow

1. Build or inspect a PCD first.
2. Identify monomers and external boundaries.
3. Describe EVA structure.
4. Run local checks.
5. Create or refresh a Polymer.
6. Report the evidence status of the composed result.

Composition helps expose structure. It should not be used as a shortcut around review, command output or artifact evidence.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.