Company
BRIK-64 builds the formal layer for AI-era programming.
BRIK-64 combines a formal language, a canonical blueprint, a compiler path, platform workflows, and registry-oriented reuse around reviewable software. It clarifies what exists publicly today and where technical teams should go next.
Formal layer
PCD
The public story stays anchored to the bounded blueprint format.
Operator path
CLI → PCD → platform
The main route stays visible across the site.
Claim posture
Qualified
Public language stays tied to evidence present in the repo.
Company
What BRIK-64 is building and how the public stack fits together
Start with the language and compiler path, then follow the platform, registry, and documentation routes that carry the technical detail.
Formal language & compiler
PCD is the public format. The compiler path clips, checks, and emits from bounded specification rather than from test coverage.
Platform & registry workflows
Publication, discovery, review state, governance, and reuse. The registry makes bounded logic a shared resource.
Reviewable evidence posture
BRIK-64 does not certify organizations. It produces traceable verification artifacts for auditors, reviewers, and operators.
What BRIK-64 is today
A formal language, a compiler path, and reviewable workflows
The company thesis stays tied to product routes that exist on this site: PCD, the compiler chain, platform workflows, and reusable libraries.
Why it exists
BRIK-64 argues for bounded computation, explicit composition, and reviewable software before deployment or migration hides the logic.
What is public today
Foundations, PCD, platform, registry, CLI, SDK, and risk pages define the current public stack.
What stays out of scope
The company route does not invent customer, audit, or market-leadership claims that the repo cannot support.
System frame
Verified software
The public thesis stays tied to bounded verification rather than AI spectacle.
Delivery path
Compiler-led
Local workflows lead into platform and registry use rather than replacing them.
Truth boundary
Repo-backed
The site separates product evidence from broader market ambition.
Next routes
Technical references behind the company overview
Follow the stack into the technical references.
Move from the company overview into foundations, platform, and documentation without changing claim posture.