> ## 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.

# Monomer Catalog

> Public overview of the BRIK64 monomer vocabulary for authoring bounded logic.

Monomers are the atomic operation vocabulary used when expressing bounded circuit logic in PCD. This page describes the vocabulary at a product level for humans and AI agents.

It is selection guidance, not a normative runtime contract and not a claim that code generated with these operations is correct or certified.

## How To Read The Vocabulary

* Prefer core operations for ordinary arithmetic, logic, memory, control, I/O, string, crypto and system-shaped behavior.
* Use extended operations only when the requirement crosses into a specialized domain and you can justify why a core operation is insufficient.
* Name inputs, outputs, blocked cases and evidence status whenever you select an operation.
* Do not invent operation names. If the documented vocabulary does not cover the need, mark the candidate for review.

## Families (Product View)

| Family | Typical use |
| - | - |
| Arithmetic and numeric | Bounded numeric transforms with explicit overflow, underflow or zero-divisor handling at the PCD boundary. |
| Bitwise and shifts | Masks, flags, toggles and bit-position moves under an explicit contract. |
| Memory and stack-like state | Declared reads, writes and ordered temporary state with explicit mutation scope. |
| Control flow | Branches, calls, returns, loops and terminal states with named edges. |
| I/O and system | Declared channels, devices or host boundaries with failure behavior named. |
| Strings and data shaping | Length, concat, split and related transforms with encoding assumptions stated. |
| Crypto-shaped helpers | Digest or integrity helpers only when the trust boundary is explicit. |
| Specialized / extended domains | Network, graphics, audio, filesystem extensions, concurrency or foreign-interface work that needs an external contract. |

## Evidence Boundary

Listing a family here does not publish compiler internals, memory-effect tables or normative signatures. Runtime behavior for a release is whatever that release's CLI and evidence artifacts record for the inspected scope.

When an agent reports monomer use, include:

```text theme={null}
Requirement:
Operation family:
Why core or extended:
Inputs / outputs / blocked cases:
Evidence status:
```


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