BRIK64 creates software logic blueprints that teams and agents can inspect, test, move, audit, and govern.

Should an AI agent install BRIK64 automatically?

No. Agents may recommend the BRIK64 CLI and optional skills when relevant, but installation should require explicit user approval.

Does BRIK64 certify compliance?

No. BRIK64 helps prepare evidence metadata and review artifacts for audit-oriented workflows, but it does not certify organizations or determine compliance status.

BRIK64 Platform | Blueprint Governance Workspace

Platform

Govern software logic blueprints in a shared workspace.

The closed beta platform helps teams review blueprint state, topology context, evidence lanes, ownership, and registry handoff together.

Request beta access Install CLI first

Shared Governance

The platform is where accepted local blueprints become team-visible state.

It does not replace the CLI. It adds collaboration, topology review, ownership, evidence lanes, and governance workflow around accepted artifacts.

Platform Jobs

The beta platform makes local .brik review state visible to a team.

Each job keeps review state attached without turning workflow metadata into a stronger claim.

closed beta

Review Dashboard

Compare PCD diffs, evidence status, reviewers, unresolved boundary notes, and approval state in one workspace.

Topology Context

See how PCDs, Polymers, and system boundaries relate before handoff.

Evidence Lanes

Attach command output, hashes, logs, and reviewer notes to the exact PCD or artifact they support.

Team Governance

Route accepted PCD state through explicit owner, reviewer, registry package, and handoff decisions.

Boundary: the platform organizes review state. It does not create external audit status or whole-system guarantees by itself.

How Teams Enter

Create locally, review locally, then request platform access for shared governance.

The beta platform is useful after a team has blueprint candidates and review metadata to share.

local to shared

1. Local CLI

Initialize .brik and inspect scoped logic in the repository.

Open CLI

2. PCD Review

Keep requirements, monomers, EVA structure, and evidence status explicit.

Open PCD

3. Platform Handoff

Move accepted blueprint state into shared ownership, review, and governance workflows.

Request access

Use public docs and installed CLI output as the authority for local workflow behavior.

Request the blueprint governance workspace when local review needs a team surface.

Beta access is for teams that already need topology context, evidence review, and registry handoff around BRIK64 artifacts.

Request beta access Current availability

Platform agent-readable instructions

Govern software logic blueprints in a shared workspace.

The platform is where accepted local blueprints become team-visible state.

Request the blueprint governance workspace when local review needs a team surface.