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

# Core And Extended Monomers

> How to choose between BRIK64 core and extended monomer vocabulary.

BRIK64 monomer vocabulary is organized as core operations and extended operations.

| Category | Meaning |
| - | - |
| Core | Preferred default for ordinary arithmetic, logic, memory, control, I/O, string, crypto and system-shaped operations. |
| Extended | Specialized or external-domain vocabulary used only when a core operation cannot express the bounded requirement. |

## Core Monomers

Core monomers should be the first choice for ordinary authoring. Prefer them whenever the requirement can stay inside bounded local logic without specialized external contracts.

## Extended Monomers

Extended monomers are useful when behavior crosses into specialized domains such as float math, network, graphics, audio, filesystem extensions, concurrency or interop.

## Selection Guidance

When extended monomers appear in a PCD, document why a core monomer was insufficient.

```text theme={null}
Extended monomer reason:
External boundary:
Evidence status:
```

Do not treat either category as proof that the resulting code is correct. Monomer selection is authoring guidance under a declared scope.


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