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.

Providers

Subprocessors

Provider categories that may process data for BRIK64 website, beta, shop, and operations.

Current provider categories

BRIK64 may use providers for hosting, content delivery, security, D1/database services, email delivery, payment processing, fraud controls, merchandise production, fulfillment, shipping, analytics where enabled, diagnostics, source control, and professional operations.

Cloudflare: hosting, content delivery, edge security, traffic management, Pages Functions, D1, logs, and caching.
Stripe: checkout, payment processing, fraud controls, receipts, refunds, billing records, and payment-related support.
Printful: merchandise production, fulfillment, shipping, returns handling, and order support.
Email and database providers: beta access confirmations, request storage, operational notifications, and support workflows.

Enterprise requests

Enterprise customers that require contract-specific provider lists, notice periods, DPA terms, or security documentation should resolve those terms before sending regulated or confidential data.

Changes

Providers may change as the product and operations change. BRIK64 will handle provider changes according to applicable law and any signed customer agreement.