Core

Overview

What BRIK64 is, why the formal layer matters, and how the system reads like hardware.

Workflow

Lift, model, check, emit, publish as one visible chain.

Platform

Publication, discovery, review state, governance, and reuse.

Tooling

CLI

Install path, commands, and the verification entry point.

PCD

Canonical format, domains, operators, and closure.

MCP

Agent endpoint, tool contract, and bounded operation surface.

AI Agent Skills

PCD authoring, proof checks, logic extraction, and monomer tools for agents.

Developer Stack

Registry, SDKs, Lifter, and Transpiler in one toolchain surface.

Data processing

Data Processing Addendum

How BRIK64 handles contract-led data processing terms.

When a DPA applies

A Data Processing Addendum may apply when BRIK64 processes personal data on behalf of an enterprise customer under a signed agreement. The signed agreement controls processing instructions, roles, subprocessors, security measures, transfer terms, and audit process.

Public website and beta requests

A public site visit, beta access request, support message, or shop purchase does not create enterprise DPA terms by itself. Those interactions are handled under the Privacy Policy and applicable provider terms.

Enterprise process

Before sending regulated or confidential data, enterprise customers should identify the intended use case, data categories, region, compliance requirements, and required processing terms for written review.