| Internet-Draft | CTP/IP Seal Verification | November 2026 |
| Lisboa | Expires 19 May 2027 | [Page] |
This document describes how any party verifies a Proof of Transformation seal issued under the Causal Time Protocol (CTP/IP), and the wire protocol used to invoke a LUX Runtime and to request seal verification over a network. A seal attests that a transformation declared in advance by a Human Agency, through a signed Intention Signature (IntentSig), was validated by the LUX Runtime, and that the resulting certificate was committed to a Merkle batch anchored on the Solana and Bitcoin public ledgers.¶
The document specifies the certificate fields, the five layer verification procedure, the artifact identity check, the message types and envelope of the wire protocol, and the IANA registrations the protocol requests. It does not specify the measurement method by which a LUX Runtime computes the Coherence Index; that method is outside the scope of this document.¶
One seal attests intent, human origin, decision authority, authorship, substance, causal time and anchoring, for a Human Agency and for any agent acting under it. The protocol has been in development since 2020 and is deployed. Its canonical specification is published as Corpus Delta 1 under DOI 10.5281/zenodo.21950371.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 19 May 2027.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document.¶
This document may not be modified, and derivative works of it may not be created, and it may not be published except as an Internet-Draft.¶
The Internet protocol suite carries data and confirms that it arrived intact. It does not record whether the data reflects a transformation that a person intended before it happened, nor whether that transformation was checked against the intention. As automated agents act on behalf of people, the absence of that record leaves no verifiable link between a human decision and the outcome an agent delivers.¶
The Causal Time Protocol (CTP/IP) addresses this gap with a seal. A Human Agency declares an intention and signs it before work begins. Observables are captured while the work runs. The LUX Runtime evaluates the outcome against the declared intention and, when the evaluation passes, issues a Proof of Transformation certificate. The certificate is committed to a Merkle batch whose root is anchored on two independent public ledgers. Anyone can later verify the seal without trusting the issuer.¶
The cycle has four stages: Point of Intention, Point of Response, Zero Boundary and Proof of Transformation. This document is concerned with what the last stage produces and how a third party checks it.¶
CTP/IP is one standard for Human Agency and for every agent that acts under it. A single Proof of Transformation carries, in one sealed record, the proof of the declared intent, the proof that a human originated the action, the proof that the human held decision authority before it began, the proof of authorship, the proof of substance, the proof of causal time and the proof of anchoring (Section 6). None of these is a separate protocol; each is one attestation of the same seal. Each validated seal also emits FLUX, the Proof of Lived Transformation (Section 6.1).¶
The standard is universal by structure: any domain whose observables can be mapped to the protocol's inputs is measurable by it. Its calibrated, operational domain today is software engineering. Other domains are at research stage. The origin and dated record of the protocol, from 2020, are given in Appendix A.¶
In scope:¶
Out of scope:¶
Verification requires no licence. Issuing seals requires a licensed LUX Runtime.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The LUX Runtime invocation contract is:¶
LUX_Runtime.validate(IntentSig, Telemetry_Stream,
Pre_State, Post_State) returns Result
Result {
Verdict: VALID | INVALID,
Gamma: float,
CTU_Generated: float,
Artifact_Class: SEED | BLOOM | ROOT | REJECTED
}
¶
A LUX Runtime MUST apply the Guardian Gates in the following order. Cheaper checks run first. Failure at any gate halts evaluation and is recorded as a deficit entry.¶
| Order | Gate | Passes when |
|---|---|---|
| 1 | Intent | An IntentSig signed by a Human Agency is present. An IntentSig originated by an automated system alone is rejected. |
| 2 | Evidence | An evidence hash is present and non empty. |
| 3 | Anchor | The CausalAnchor is present and linked, and the prev_hash chain is intact. |
| 4 | Coherence | The effective Gamma is at or above Gamma_min, which is 0.70 in the Canonical Seal Profile. |
| 5 | Deficit | The cycle is not in an impossible state and drift budgets are within tolerance. |
The coherence thresholds are stipulated design parameters chosen by the author of the protocol. They are not derived from physical theory. The protocol defines two profiles.¶
Both profiles remain subject to Section 13.¶
Every certificate carries one tier, set by its Gamma.¶
| Tier | Gamma range |
|---|---|
| SEED | 0.70 up to but not including 0.8187 |
| BLOOM | 0.8187 up to but not including 0.95 |
| ROOT | 0.95 to 1.00 |
A cycle with Gamma below 0.70 is INVALID in this profile. It generates no ctu and no certificate.¶
The term Proof of Transformation is used in three qualified senses. Proof of Transformation (Stage) is the final stage of the cycle. Proof of Transformation (Consensus) is the attestation by the network that a transformation is valid. Proof of Transformation (Certificate) is the cryptographic artifact issued on success. Unqualified, the term in this document means the Certificate.¶
A record is a Proof of Transformation only if all of the following hold:¶
A record that lacks any one of these is not a Proof of Transformation, whatever name it is given. A system that attests only one property of a cycle, such as human origin, decision authority, authorship or anchoring, implements one attestation of a Proof of Transformation and is not itself a Proof of Transformation.¶
The Causal Time Unit (ctu) is the unit of validated causal time. It is written in lower case as "ctu", and its unit symbol is "ct", on the pattern of the bit and the decibel. The ctu measures whether a transformation was validated against its declared intention. UTC orders events by clock time; the ctu weights them by validated transformation. The two are complementary coordinates.¶
ctu is generated, not measured. It is emitted only by a cycle that validates in the Canonical Seal Profile, under the law:¶
T = k * E * V * A if Gamma >= Gamma_min k = phi = 1.618033988749895 Gamma_min = 0.70 (Canonical Seal Profile)¶
where T is the validated transformation, instantiated as ctu, and E, V and A are the Energy, Vector and Attention observables on the unit interval. The mapping of raw signals to E, V and A is the responsibility of a domain adapter and is outside the scope of this document.¶
The ctu is non fungible, non transferable, non tokenisable and non collateralisable. It is bound to the Human Agency who produced it through the Proof Counter, which is bound to the Human Agency's CausalAnchor. An implementation MUST NOT provide any means to transfer, sell, collateralise or otherwise convey a ctu between Human Agencies. An implementation that does is not CTP/IP. An agent cannot earn a ctu.¶
A conforming implementation MUST NOT be used for any of the following:¶
A Proof of Transformation is a single record with several attestations. A verifier checks all of them through the procedure in Section 7.¶
Agency is covered by the same seal. When an agent carries out the work, the seal records the Human Agency who declared and signed the intention, and the agent's part is recorded as execution, never as authorship or authority.¶
When a seal validates in the Canonical Seal Profile, FLUX is emitted alongside it. FLUX is more than a token: it is the receipt of a transformation that a Human Agency declared, lived and had validated. Every FLUX unit is a provenance stamped container recording which Human Agency sealed which cycle and at what Gamma.¶
FLUX is minted only under the LUX Runtime Oracle PDA, a program derived address with no private key, so no human key can mint or freeze it. Emission is bound to validated cycles and set by the seal's tier. FLUX is transferable; the ctu it accompanies is not, and stays bound to the Human Agency who earned it.¶
A seal is anchored across five persistence layers.¶
| Layer | Cadence | Role |
|---|---|---|
| 1. Operational Store | Continuous | Sealed certificates enter. |
| 2. Merkle Batches | Per batch | Certificates aggregate into Merkle trees. |
| 3. Solana VaultAnchor | Daily, at 00:00 UTC | The daily Merkle root is committed. |
| 4. Bitcoin | One foundational Time Call per Human Agency; monthly batch anchors | Roots are inscribed with the prefix "CTPIP:SEAL:". |
| 5. Polaris Oracle Data Vault | Real time, in parallel | Independent witness of the record. |
A verifier MUST perform the steps in order. A seal that fails a step is non conforming at that layer.¶
A seal that passes all five steps is verified. Its evidence is then anchored on two independent ledgers, the Solana chain and the Bitcoin proof of work chain.¶
Verification proves that a specific Gamma value, computed by the LUX Runtime over a specific evidence hash, was committed at a specific moment and cannot be altered without breaking SHA-256, Ed25519 or the consensus of Solana and Bitcoin. Once committed, no seal can be modified, deleted or revoked without producing a root that fails verification.¶
Verification does not prove that the submitted observables faithfully represented the Human Agency's state at the time of the cycle. The mapping from raw signals to observables is the responsibility of a domain adapter, which carries its own falsifiability conditions. A verifier MUST NOT present a verified seal as proof of more than the commitment.¶
Artifacts of the protocol are identified by their behaviour on chain, not by names, logos, tickers or metadata. Any party verifying that an artifact belongs to the protocol MUST:¶
An artifact whose mint authority does not resolve to these addresses is not a sealed artifact of the protocol, whatever its metadata states.¶
Published identifiers:¶
The wire protocol transports the LUX Runtime invocation contract of Section 3.1 and seal verification requests over a network. A LUX Runtime that accepts network originated cycles MUST implement it. A client that submits cycles to a LUX Runtime outside its own address space MUST implement it.¶
| Code | Name | Direction | Purpose |
|---|---|---|---|
| 0x01 | INTENT_DECLARE | Client to LUX Runtime | The Human Agency declares cycle intent. Carries the IntentSig and the observation window. |
| 0x02 | INTENT_ACK | LUX Runtime to Client | Acknowledges intent registration and opens the cycle channel. |
| 0x03 | MEASURE_SUBMIT | Client to LUX Runtime | Submits the observables for the cycle. |
| 0x04 | VALIDATE_REQUEST | Client to LUX Runtime | Requests the Gamma verdict on the submitted observables. |
| 0x05 | SEAL_RESPONSE | LUX Runtime to Client | Returns the ZK-TSL certificate, or a rejection. |
| 0x06 | DEBT_NOTICE | LUX Runtime to Client | Notifies cumulative deficit accrual or regime escalation. |
| 0x07 | VERIFY_REQUEST | Verifier to LUX Runtime | Requests confirmation of a recorded seal. |
| 0x08 | VERIFY_RESPONSE | LUX Runtime to Verifier | Returns the seal verification result. |
Every message is carried in the following envelope.¶
+--------+------------+------------+-------------+-----------+ | Type | Length | Sequence | Payload | Signature | | 1 byte | 2 bytes | 4 bytes | Length | 64 bytes | | | big endian | big endian | bytes | (Ed25519) | +--------+------------+------------+-------------+-----------+¶
The maximum payload is 65,535 bytes. Larger observable submissions use chunked delivery of MEASURE_SUBMIT, which is outside the scope of this document.¶
Each message is signed with the sending party's signing key. The IntentSig is signed with the Human Agency's CausalAnchor key. Messages from a LUX Runtime (INTENT_ACK, SEAL_RESPONSE, DEBT_NOTICE and VERIFY_RESPONSE) are signed with the LUX Runtime's published signing key. The LUX Runtime Oracle PDA and the program ID identify the runtime's on chain state, not the signer, because a program derived address holds no private key.¶
Implementations MUST support Ed25519. A later revision may add or substitute post quantum signature algorithms [FIPS204] [FIPS205] with explicit version negotiation.¶
This section records the status of known implementations at the time of writing, following [RFC7942]. It is to be removed before publication as an RFC.¶
The wire protocol does not provide confidentiality for observables. Where a Human Agency requires observables to remain private, the source adapter MUST compute locally before transmission.¶
The protocol validates transformations, not people. The Coherence Index measures how well an action achieved its stated purpose. It does not measure human worth, standing or productivity. Any use that ranks, scores, disciplines or coerces people is outside the protocol and invalidates its premise.¶
CTP/IP, Causal Time Protocol, Intentional Processing, Sealed Energy, LUX Runtime, Polaris Oracle, FLUX, ctu, TKDF-256, Heritage Thread, Time Call and Symbiotic Operator Network are marks of the estate, used in commerce and asserted as such. Use of a mark to designate a deployment, product or service as CTP/IP, or as conforming to it, requires a licence. Nominative reference in research, criticism, comparison or teaching does not.¶
Use of the protocol is free for research, for group discussion and for personal use, including verification of seals, reading, auditing and replication of the specification. Commercial use requires a licence, and so does any use of the protocol with tokenization. Embedding the architecture or any component in a commercial product or service requires a commercial licence from Time Foundation. Operating an instance whose outputs are recorded as CTP/IP seals, or that emits FLUX, additionally requires a LUX Runtime licence. A commercial deployment that avoids the marks, renames the components, or declines to claim CTP/IP status still requires the commercial licence if it embeds the architecture.¶
No licence arises by implication, by reference or by conduct.¶
This document requests provisional registration of the URI scheme "ctp" in the "Uniform Resource Identifier (URI) Schemes" registry, following [RFC7595].¶
This document requests the following entry in the "Service Name and Transport Protocol Port Number Registry", following [RFC6335].¶
Implementations in private networks may use other ports. Port 7369 is the default for operation on the public Internet.¶
This document requests registration of the media type "application/ctp+json", following [RFC6838].¶
The following records are public and dated, and can be checked by any party.¶
CTPIP:DSZG: 8b7f008c3d49a73a046bcb70fb964585f879d29bf5988ede1eb7d2faff7fefe0:S¶
The deployment record can be checked in minutes with public endpoints only, using the eleven checks given at the front of [CORPUS].¶
This document is the sole work of its author.¶