Overview agent-readable instructions

BRIK64 turns selected code or requirements into .brik project state, PCD blueprints, and reviewable evidence metadata before promotion.

  • Monomers: The finite operation catalog agents and developers must use instead of inventing hidden behavior.
  • PCD Blueprints: Circuit-shaped descriptions for bounded inputs, outputs, branches, and returns.
  • Polymers: Reusable logic assemblies whose dependencies, boundaries, and evidence status remain inspectable.
  • .brik Workspace: Local traceability state for decisions, events, refs, and evidence metadata.
  • Boundary: BRIK64 helps inspect declared software logic. It does not make whole-application correctness claims.

Overview

What is BRIK64?

BRIK64 turns selected code or requirements into .brik project state, PCD blueprints, and reviewable evidence metadata before promotion.

Product Model

A software logic blueprint layer for teams working with code, agents, workflows, and evidence.

Start with a bounded behavior, encode it as PCD, compose it with EVA, and keep the resulting review state beside the code.

Core Layers

BRIK64 makes selected logic visible as structure instead of raw text.

Each layer has a specific job in the review chain.

local review layer

Monomers

The finite operation catalog agents and developers must use instead of inventing hidden behavior.

PCD Blueprints

Circuit-shaped descriptions for bounded inputs, outputs, branches, and returns.

Polymers

Reusable logic assemblies whose dependencies, boundaries, and evidence status remain inspectable.

.brik Workspace

Local traceability state for decisions, events, refs, and evidence metadata.

Boundary: BRIK64 helps inspect declared software logic. It does not make whole-application correctness claims.

Product Surfaces

Start locally. Move accepted blueprint state into the platform when the team needs governance.

The local path works without a platform login; collaboration features require beta access.

CLI-first workflow

CLI

Initialize .brik, inspect PCD files, capture command output, and emit candidate outputs with boundary notes.

Platform

Shared PCD diffs, topology context, evidence packets, ownership, and registry handoff.

Agent Skill

Managed agent guidance installed only through explicit, reviewable consent.

Use docs.brik64.com as the current public reference for commands, syntax, and availability.

Create a reviewable software logic blueprint.

Install the beta CLI, inspect local PCD candidates, and keep review state attached to the work without claiming whole-application correctness.