From Intentional Processing to Coherence Networks A Treatise on Measurement, Cryptography, Temporal Debt, and Meaning

DEPLOYMENT STATUS: LIVE

CTP/IP is deployed on Solana mainnet with a verified Genesis event, a cross-chain witness on Bitcoin mainnet, and three runtime invariants enforced in deployed bytecode. This is not a proposal. The protocol is operational.

What makes it strong: the proof is the chain, not the claim. Intent is locked first and cannot be backfilled, the transformation is measured by a deterministic engine, the coherence verdict is computed at the point of transformation, and the result is witnessed on Bitcoin. The order is the guarantee. Intent cannot be faked because it is signed before the work, coherence cannot be faked because the engine is reproducible, and the timestamp cannot be faked because Bitcoin witnessed it.

What makes it unique: Proof of Transformation is a cryptographic primitive in its own right. Proof of Work proves computation, Proof of Stake proves capital, Proof of Transformation proves irreversible state change. The Causal Time Unit takes its place in the inventory of fundamental domain units alongside the bit and the decibel. And the protocol separates into a non-forkable canonical layer, enforced on chain, and a replicable surface layer, so a deployment is canonical because the chain says so, not because a brand says so.

What makes it sovereign: the human is the sole causal origin. AI holds zero signing authority (w_AI = 0), enforced in bytecode. The operator's identity is a non-transferable CausalAnchor bound to the human at Genesis, and the operator carries the signing key, the identity, and the Heritage Thread in a client no platform can seize. Switch surfaces, change tools, move countries; the identity and the record travel with the operator.

All addresses are publicly verifiable on Solana Explorer and on any Bitcoin node or block explorer.

What this is

R3 is the canonical specification of CTP/IP at its current revision, sealed as a single unified corpus. The protocol is a measurement specification for validated coherent intentional transformation. It introduces no new physics. It applies existing thermodynamic, information-theoretic, and cybernetic constraints as validation criteria for one binary question: did this declared intent produce measurable irreversible transformation in the declared interval?

What this is not

CTP/IP is not a law of physics, not a modification of general relativity, quantum mechanics, or thermodynamics, not a spacetime ontology, not a metaphysical doctrine, not a cryptocurrency speculation vehicle, not a financial product, and not a security.

The protocol declares no reference rate for FLUX. The Parity Law of the earliest specification has been removed and stays removed. FLUX is a provenance container, not a peg. The protocol provides the rail, never the rate; each Human Sovereign Agency sets the value of its own work, and a fiat figure, where it appears at all, is a movable human reference shown last, never the denomination and never the rate.

The canonical layer and the replicable surface

R3 makes the deployment model explicit. The canonical layer is non-forkable and chain-enforced: the Solana program, the Oracle PDA as sole mint authority, the FLUX mint, the Heritage Thread format, the open ctpip-engine (bit-exact reproducible), the nine Guardian Keys, the Bitcoin Time Call, and the Cycle Validation Fee. A deployment is canonical if and only if it uses the canonical program, mints through the canonical Oracle PDA, chains its Heritage Threads from a valid Genesis Block, and reproduces the Appendix M fixtures at a tolerance of 1e-9. A deployment that does not is a fork and produces non-canonical artifacts.

The surface layer is replicable and white-label ready: the content and commercial surface, the route layer, the agent door, the data schema, the Genesis onboarding, the payment rails, and the Autonomous Self Client. A licensed deployment runs its own brand, operators, and revenue while its operators seal through the canonical chain, so their credentials interoperate across every CTP/IP deployment. Settlement between operators is a bilateral witness event, not a payment: the counterparty co-witnesses the delivery, both Heritage Threads extend, and the receipt is on chain.

The Autonomous Self Client

The operator's sovereign interface, one self in two modes. The Witness (human mode) carries the signing key, the CausalAnchor, and the Heritage Thread reference; the human declares intent, signs, and authorises. The agent mode (ctpip-mcp) is a delegated tool surface where the Human Intervention Gate enforces that the agent never originates intent, never holds the signing key, and never bypasses the capability gate. The agent operates under the human, not alongside the human. The client is sovereign because the key is sovereign.

Corpus structure

The corpus is self-contained. No external document is required to implement, audit, or challenge the specification at this revision.

Core architecture

All thresholds are engineering parameters subject to empirical recalibration through the Open Validation Program. The Law is immutable as a constructive axiom; the thresholds are refinable through ratified pull requests on the corpus, with disclosure.

On-chain proof

Genesis Heritage Spark (Solana, 4 April 2026). Gamma = 0.9497, BLOOM tier, 94.9715 FLUX emitted to the Architect's Heritage wallet via the genesis_strike instruction. Two independent locks enforced. The Causal Residual of 0.0003 between the achieved Gamma (0.9497) and the ROOT threshold (0.9500) is the irreducible thermodynamic signature of the operator and is preserved on chain.

Time Call (Bitcoin, 26 April 2026). First-instance Time Call inscription at Bitcoin block 946,742, transaction fddb901b6c25dc9fbd01f66cd084783c1755a57c960882bd9e67f410ecf636ea. Gamma verdict 0.8187, SEED tier per the OP_RETURN declaration, 1.6176 FLUX emitted via the emit_flux instruction, 1,470,000 satoshis (0.0147 BTC) burned to 1BitcoinEaterAddressDontSendf59kuE as the cost-bound economic commitment of the seal. Permanent, inspectable through any Bitcoin node or block explorer.

FLUX mint authority is held by the LUX Runtime Oracle PDA. Every FLUX in existence was justified by a validated transformation cycle before it was minted.

Falsifiability and the four-category claim schema

The corpus self-classifies every claim so that no operational reading can be inferred from a structural specification, and no interpretation can be inferred from an on-chain fact.

Two falsifiable empirical predictions are pre-registered with quantitative failure conditions. P-CR predicts that the per-cycle Causal Residual distribution deviates from the Gaussian null in at least two specified ways. P-CV predicts that the convergence of Gamma across measurement depths fits a phi-to-the-minus-d law better than the alternative nulls by Bayesian likelihood ratio. The null models are fully specified in Book V.

The Open Validation Program is permanently open. Any researcher can test, critique, and attempt to falsify the structural specifications without licensing obligations. Negative results trigger mandatory recalibration and public disclosure, not suppression.

Public roadmap

The corpus specifies a public roadmap of four empirical milestones (M1 through M4), each with a falsification condition. Progression is counted in protocol terms, not calendar commitments. Missed milestones are recorded in the Errata Registry; failed predictions trigger the retraction procedure of Appendix N.

Operational infrastructure

Recommended reading order

For a peer reviewer: the academic introduction first, then the technical specification for depth, then the CTU formal proof for the categorical claim; the corpus is the normative reference. For a skeptical reader: Appendix M (reproducibility) and Book IX (the mainnet epoch) first, since these carry the verifiable operational facts, with the structural specifications and interpretive framings bracketed pending the roadmap milestones. For an implementer: Appendix M, Appendix I (cross-chain verification), and Book III (the engine, the Guardian Gates, reproducibility, and infrastructure).

Licensing

Protection ensures canonical integrity, not the prevention of scientific validation.

Contact

Researchers, institutions, or developers interested in testing predictions, contributing to measurement standards, or licensing for deployment: contact@designledger.co

time.foundation | designledger.co | sealed.energy | github.com/thedesignledger

Author

Erico Lisboa [E.L], Architect of the Causal Time Protocol. Time Foundation; Design Ledger Pty Ltd (ABN 50 669 856 339), Western Australia.

Version history

This deposit is the sealed canonical reference at Release 3.

Current: DOI 10.5281/zenodo.20474027 (R3, sealed unified canonical corpus). Adds the Replicable Protocol Deployment model, bilateral witness settlement, the Autonomous Self Client, the Operational Proof, and the Substance Witness Protocol framing; the Cycle Validation Fee is reconciled to the corpus anti-extraction passage.

This sealed deposit consolidates the prior R3 deposit (DOI 10.5281/zenodo.20149108).

Supersedes: DOI 10.5281/zenodo.19923869 (R2, May 2026). Supersedes: DOI 10.5281/zenodo.19362640 (R1, October 2025). Supersedes: DOI 10.5281/zenodo.18795109. Supersedes: DOI 10.5281/zenodo.17371587.

Keywords

Proof of Transformation, CTP/IP, Causal Time Protocol, Coherence Index, Causal Time Unit, Human Sovereign Agency, Thermodynamic Validation, EVA Engine, LUX Runtime, Guardian Gates, Guardian Keys, Temporal Debt, Cryptographic Primitive, Falsifiable Framework, FLUX, Solana, Bitcoin, Mainnet, Zero Boundary, Time Call, Heritage Spark, Genesis, Substance Witness Protocol, Symbiotic Operator Network, Domain Unit Criterion, Open Validation Program, TKDF-256

Resource type: Publication / Preprint. Licence: CC BY-NC 4.0.