-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Collective Phase Control Fabric (CPCF) is an evidence-control toolkit for finite collective
workflows. It accepts typed records, validates their provenance and constraints, and projects
bounded results into an operational_organization_profile.
It is useful when a workflow must keep its evidence, authority, resource constraints, coordination state, and uncertainty explicit. CPCF does not autonomously operate other systems, and it does not certify a collective-superintelligence phase, consciousness, causal acceleration, statistical validity, thermodynamic feasibility, physical phase behavior, or runner isolation.
- Getting Started explains the offline commands that require no credentials.
- The CPCF Mental Model distinguishes records, projections, authority, and uncertainty.
- Evidence and Authority explains closed documents, signatures, trusted time, role separation, and source-of-record boundaries.
- Operational Profile and Scientific Scope explains what the thirteen-dimensional result means—and what it does not mean.
CPCF brings several kinds of evidence into one immutable analysis snapshot:
- provenance and lifecycle records;
- trust policy, signatures, and trusted time;
- typed transformations, resources, catalysts, and constraints;
- verification routes, independence/exposure information, and coordination state;
- declared perturbations, intervention alternatives, and trial bindings.
The platform can then report whether the declared inputs satisfy specific bounded requirements. Every requirement remains separate. A favorable score in one dimension does not compensate for a violation or unknown result in another.
The name uses concepts from organization theory and collective workflows, but the software does not turn those concepts into claims about a physical system. For example, an exact balance witness is a structural accounting result; it is not a claim about kinetics, equilibrium, entropy production, stability, or thermodynamic feasibility. Likewise, a registered trial binding is not a causal or statistical certification.
For the full boundaries, read Operational Profile and Scientific Scope and Research Basis and Limits.
External systems remain the source of record for their own missions, leases, certificates, claims,
and acceptance decisions. CPCF stores immutable bytes and its own projections; it does not silently
take over another system's authority. A queued response such as accepted is not proof that
evidence was admitted, an action succeeded, or an analysis is favorable.
For v0.6, adapter execution is outside the API and analysis worker. It occurs only through the separate external-runner protocol and receipt model. Earlier compatibility objects remain read-only and quarantined until newly created v0.6 evidence and quorum decisions satisfy the applicable rules.
See Execution and Legacy Compatibility and Remote Workspaces before taking any state-changing action.