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

# What Is BRIK64?

> A practical model of BRIK64, Digital Circuitality, PCD, monomers, EVA and local evidence.

BRIK64 is a way to make software logic easier to inspect. It turns bounded requirements into circuit-shaped blueprints so developers and AI agents can review what the logic does before it spreads across systems.

The core model is:

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

Each layer has a specific job:

| Layer         | Role                                                                        |
| ------------- | --------------------------------------------------------------------------- |
| Monomer       | Atomic operation vocabulary.                                                |
| PCD Blueprint | Circuit description for bounded logic.                                      |
| EVA           | Composition model for sequential, conditional and parallel structure.       |
| Polymer       | Composed logic built from one or more PCDs.                                 |
| `.brik`       | Local traceability workspace for decisions, events and evidence references. |
| CLI           | Local command surface for the current public beta PCD workflow.             |
| Skill         | Managed agent instructions installed only with explicit consent.            |

## Digital Circuitality

Digital Circuitality is the engineering discipline behind BRIK64. It treats software as something that should be shaped like circuitry: bounded inputs, finite operations, explicit composition, deterministic behavior where the scope declares it, and evidence that can be inspected later.

For users, this means BRIK64 is not just another code-generation layer. It is a way to make an AI agent or developer explain the logic it is creating:

1. What are the inputs and outputs?
2. Which atomic operations are needed?
3. How are operations composed?
4. What artifacts prove what happened?
5. Which parts are available today and which require future platform support?

## Local-First Product Model

The local CLI path is the default because it keeps source and iteration close to the developer. Agents can use BRIK64 without requiring login for the local flow. Managed `AGENTS.md` instructions should only be written through an explicit, reviewable user-approved action.