Documentation

Give agents current BRIK64 context on demand.

Expose command contracts, PCD rules, availability, and evidence vocabulary through a structured MCP surface.

Resource

brik64://pcd/rules

Agent request

Describe the bounded authoring contract.

Declare inputs and outputs

Use catalog monomers

Report evidence status

Fail closed on missing scope

Structured context instead of copied prompts.

An agent can discover the current contract for the selected task without treating internal terminology or old examples as authority.

Discover the current command name, install path, availability, and documented command families.

Read syntax, inputs, outputs, monomer selection, and fail-closed authoring guidance.

Use a consistent vocabulary for commands run, checked scope, assumptions, and missing evidence.

Keep public beta, closed beta, documentation, and preview status distinct.

MCP provides context; the repository, CLI output, and human review remain the sources for the actual work and decision.

The client lists the available BRIK64 resource or tool contract.

The agent asks for the bounded context relevant to its current task.

The agent follows the returned rules inside the repository workflow.

The agent returns commands, changes, assumptions, and evidence status.

MCP context is guidance and structured discovery. It is not an independent certification or approval service.

Use the MCP documentation for structured context and the Agent Skills page for repository-facing instructions.