Foundations agent-readable instructions

Start from a bounded requirement, shape it into PCD, keep .brik traceability, and report evidence status.

  • Shape the requirement: Write inputs, outputs, fail-closed behavior, and external assumptions.
  • Select monomers: Use the public vocabulary instead of inventing ad hoc operations.
  • Author the PCD: Declare branches, returns, and EVA composition for the bounded scope.
  • Record local evidence: Attach command output, decisions, refs, and evidence status in the local workflow.
  • Boundary: workflow evidence is scoped to the inspected PCD and command output. It is not a whole-system assurance claim.

Foundations

Review software logic as blueprints.

Start from a bounded requirement, shape it into PCD, keep .brik traceability, and report evidence status.

Start with CLIAgent flow

Local-First Flow

The workflow makes planned, generated, or existing logic explain itself before it spreads.

Agents and developers follow the same chain: requirement -> PCD Blueprint -> EVA structure -> local evidence.

Review Chain

Five steps keep the work bounded and inspectable.

Each step produces information a reviewer can read without scanning a raw generated diff.

bounded review

Shape the requirement

Write inputs, outputs, fail-closed behavior, and external assumptions.

Select monomers

Use the public vocabulary instead of inventing ad hoc operations.

Author the PCD

Declare branches, returns, and EVA composition for the bounded scope.

Record local evidence

Attach command output, decisions, refs, and evidence status in the local workflow.

Boundary: workflow evidence is scoped to the inspected PCD and command output. It is not a whole-system assurance claim.

Team Handoff

Move to the platform only when shared review state is needed.

The CLI path remains local. Platform access adds team context, topology review, evidence lanes, and registry handoff.

local to shared

Local developer

Runs brik64, creates .brik workspace state, and inspects PCD candidates.

Install CLI

AI agent

Uses current docs and skills to shape requirements before writing code.

Agent skills

Review team

Moves accepted state into platform workflows when collaboration is required.

Platform
Digital Circuitality remains the theory behind the workflow; this page explains the operator path.

Turn a requirement into a reviewable logic artifact.

Use the CLI and agent docs to keep PCD structure, .brik traceability, and evidence status explicit.

Read agent docsPCD language