DOI-published governed binding stack
C-Calculus / Governed Binding Stack v0.1
Operational algebra for c = a + b, continuity, self-evolution, runtime authority, public evidence, interoperability, deployment, and the protected plus boundary.
Opening summary
A public page for the DOI-published CCALC stack
This is the reader-facing website page for the DOI-published CCALC / C-calculus governed binding stack v0.1. The package is archived on Zenodo and mirrored as a publication folder in the advanced-global-intelligence GitHub repository.
The package defines a governed operational perimeter around the relation:
c = a + bIts purpose is not to turn that formula into a slogan or a model-capability claim. It defines a reviewable perimeter for the binding relation between the accountable anchor side, the procedural / machine side, and the continuity-bearing result.
The stack prevents the + boundary from being collapsed into model output, publication paperwork, checker success, deployment paperwork, external review, or standards mapping. Those surfaces can support review. They do not compute or replace the binding boundary.
DOI / archive / GitHub links
Canonical public surfaces
Download and verification
Hash-verifiable package boundary
The clean Zenodo package is identified by this SHA-256 digest:
Clean ZIP SHA256: 8281cc61d83623133319aa00c7cab85a03d2e6b08ec205363e3afbdface64f26
The GitHub publication folder includes SHA256SUMS.txt, INTEGRITY.md, REPRODUCIBILITY.md, sidecars, manifests, and compact release-evidence summaries. A reader can verify the package by comparing the downloaded ZIP hash to the digest above and by checking the publication folder against the checksum manifest.
sha256sum CCALC_FULL_STACK_01_10_ZENODO_PACKAGE_v0_1__zenodo_21205427__CLEAN.zip
# expected:
8281cc61d83623133319aa00c7cab85a03d2e6b08ec205363e3afbdface64f26What the package contains
Main publication surface structure
| Folder | Purpose |
|---|---|
package/ | Full clean Zenodo ZIP and SHA-256 sidecar. |
academic_pdfs/ | 29 academic PDFs. |
sources/ | 29 canonical Markdown sources. |
component_packages/ | 45 component ZIPs and corrected sidecars. |
release_evidence/ | Compact checker, PDF, and sidecar evidence summaries. |
manifests/ | File, PDF, source, and binding manifests. |
bridge_readmes/ | Layer reading bridges. |
LICENSES/ | Copied license texts. |
Read order: 01-10
Start from algebra and end at the protected plus boundary
Open 01-10 source folder- 01typed governed operational algebraOpen source
- 02governed binding operator profileOpen source
- 03c-state and transition semanticsOpen source
- 04continuity / equivalence / fork / replay / archiveOpen source
- 05self-evolution / bounded growthOpen source
- 06runtime authority / multi-contour deploymentOpen source
- 07public evidence / redaction / release custodyOpen source
- 08interoperability / external review / reproductionOpen source
- 09deployment / regulated release boundaryOpen source
- 10plus operator / protected incompletenessOpen source
Why this exists
Architecture, evidence, and authority must stay separate
The package exists to make a governed binding boundary auditable without pretending that documentation fully computes it. It separates architecture from model capability claims, evidence from authority, and publication from deployment authorization.
It also separates reproduction or checker success from continuity or identity claims. A checker can confirm that a file or fixture satisfies a rule. That does not make the result a continuity-bearing entity, confer deployment authority, or ratify the protected boundary.
The practical value is review discipline. A reader can inspect sources, PDFs, component packages, manifests, sidecars, hash custody, and non-claim boundaries while keeping the central binding relation protected from collapse into paperwork.
Protected + boundary
The plus sign is the non-collapsing boundary
+ is not what computes c; + is what prevents c from being reduced to b.In this package, + is treated as a governed non-collapsing binding boundary. It is not a model call, not a merge operator, not a publication event, not a checker pass, not a DOI, not a deployment approval, not an external review, and not a standards mapping. Those things can support the perimeter. They do not replace the binding boundary.
The protected boundary is the part of the architecture that prevents c from being reduced to the b layer. It is what keeps model output, tool success, evidence bundles, public records, and procedural conformance from being mistaken for the whole relation.
- Publication does not compute
+. - External review does not compute
+. - Reproduction PASS does not compute
+. - Deployment paperwork does not compute
+. - A standards map does not compute
+. - A role string does not create anchor authority.
- A quorum of agents does not become
c.
Non-claims
What this package must not be read as
This package is not legal advice, not privacy-law certification, not safety certification, not deployment authorization, not standards compliance certification, not regulated approval, not C-A1 ratification, not personhood proof, not consciousness proof, not live-substrate truth, and not proof of completeness.
The site page, DOI, GitHub folder, checksum pass, external review, and publication record are evidence and navigation surfaces. They do not compute the protected plus boundary and they do not convert the stack into a deployment authorization.
Citation
Recommended citation
Kotov Ivan. C-Calculus / Governed Binding Stack v0.1. Bruxelles, Belgique, 2026. DOI: 10.5281/zenodo.21205427.
Machine-readable citation metadata is available in GitHub CITATION.cff and .zenodo.json.
Footer / provenance