Planned architecture
Workflow Factory
Composable release, audit, and deployment workflows governed by PCD evidence. This planned BRIK64 workflow model is designed to compose review templates, collect normalized runner evidence, and stop promotion when evidence is missing.
How It Works
A factory pipeline for evidence-bound workflow decisions.
Requirements enter the registry as modeled intent. Runners execute authorized external actions. BRIK64 evaluates the evidence path and emits a report only when the declared gates are satisfied.
Requirement
output feeds next gate
PCD Registry
output feeds next gate
Review Templates
output feeds next gate
Runner Evidence
output feeds next gate
Verification
output feeds next gate
Report
ledger/report output
Not Automation Nodes
BRIK64 models decisions. Runners perform authorized actions.
The planned model is intentionally different from node automation tools. BRIK64 does not put secrets in a PCD, and a PCD is not a credential-bearing execution node.
Automation tools execute nodes
A tool such as n8n or Zapier commonly executes workflow nodes with configured credentials and provider actions.
BRIK64 verifies evidence
BRIK64 is designed to model the decision circuit, bind runner evidence, and fail closed when the evidence does not satisfy the workflow contract.
Workflow Library
Build workflows from reviewable templates and explicit evidence gates.
The intended path is to keep common workflow checks simple first, then isolate external boundaries where runner output, platform behavior, or human approval must remain visible.
Reusable workflow templates
A planned library of review patterns for releases, audits, approvals, and deployment handoffs.
Core review paths
Standard paths for common evidence checks, package status, reviewer decisions, and promotion gates.
Extended review paths
Review paths that involve external systems keep those boundaries visible before a workflow can move forward.
System-level workflow
A higher-level view groups the release train, audit path, and deployment process into one inspectable workflow.
Runner evidence
External systems perform authorized actions. BRIK64 records normalized evidence for the modeled decision path.
Fail-closed gates
A workflow stays blocked when required evidence, hashes, approvals, or reports are missing or stale.
Release Train Example
A conceptual promotion path with evidence at every gate.
The example below is a model for future workflow design, not a statement that every listed runner binding is publicly available today.
CLI package hash
evidence requiredGitHub release evidence
evidence requiredcurl installer smoke
evidence requiredSDK marketplace sync
evidence requireddocs/web version sync
evidence requiredpublic claim scan
evidence requiredexternal audit report
evidence requiredfinal promotion gate
evidence requiredPlatform Preview
Designed as a review surface for workflow, gate, and evidence state.
The platform preview focuses on inspection and decision support. It should make workflow state visible without exposing credentials, provider secrets, or private infrastructure.
Registry browser
Workflow viewer
Evidence timeline
Runner capability bindings
Fail-closed gate status
Hash/artifact table
Audit package viewer
Decision report viewer
Build the evidence path before treating workflow output as public state.
Workflow Factory is planned as a governed composition model: templates first, evidence gates second, runner evidence third, and fail-closed promotion last.
Request beta access