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.

Security

Security posture for BRIK64 public web, beta access, shop, and reporting channels.

Security practices

BRIK64 uses controlled beta access, server-side validation for forms and commerce flows, reputable infrastructure providers, payment processors for card handling, and operational logging for abuse and incident investigation.

No public certification claim

This page does not claim SOC 2, ISO 27001, GDPR certification, HIPAA compliance, PCI certification, FedRAMP, or similar external compliance status unless a separate public certificate or signed report expressly says so.

Sensitive data

Do not submit secrets, private keys, production credentials, regulated data, or confidential customer data through public forms or beta workflows unless BRIK64 approves that use in writing.