Skip to main content
A monomer is the smallest named operation in the BRIK64 vocabulary. Agents should use monomers to make logic explicit instead of hiding behavior in ad hoc helper code.

Selection Flow

  1. Identify the operation in plain language.
  2. Search the Monomer Catalog.
  3. Prefer core monomers when they express the operation.
  4. Use extended monomers only when the behavior crosses into external or specialized domains.
  5. Record any external dependency before composing the PCD.

String Example

PC string_size {
    fn string_size(a, b) {
        let joined = MC_40.CONCAT(a, b);
        let size = MC_43.LEN(joined);
        return size;
    }
}
This circuit uses:
MonomerPurpose
MC_40.CONCATJoin two strings.
MC_43.LENMeasure the joined string.

Arithmetic Example

PC byte_total {
    fn byte_total(a, b) {
        let total = MC_00.ADD8(a, b);
        return total;
    }
}
Review the relevant release and catalog before relying on detailed arithmetic behavior. Public docs list the vocabulary; precise semantics belong to the compiler-facing source and evidence for the release.

Agent Checklist

  • The monomer exists in the catalog.
  • The family matches the intended behavior.
  • The PCD keeps control flow explicit.
  • Extended behavior is recorded before composition.
  • The final explanation names each monomer used.