Operational
Reproducible today through the published engine and fixtures.
03 / Research & evidence
An operational protocol.
An inspectable record.
Corpus Δ1 documents CTP/IP’s operational substrate: deterministic measurement, human signing authority and cross-chain records. Its forward programme extends attestation, independent replication and domain calibration.
CTP/IPCORPUS Δ1
Four evidence categories
Four ways to read the evidence.
Corpus Δ1 separates operational results, on-chain facts, structural specifications and interpretation. Follow each category to its evidence and verification pathway.
Δ1 · L330 to 365On-chain fact
A record that can be checked cryptographically on the declared substrate.
Structural specification
Published mechanisms, derivations, and implementation requirements.
Interpretation
The explanatory and strategic reading of the architecture and its implications.
Canonical status register
An operational foundation.
A forward programme.
Deployment records and forward commitments, linked to the published Δ1 register. Each commitment names its implementation or research pathway.
Δ1 · L35 to 6312 entries
ReferenceCommitment / scopeCorpus status
Software engineering
Operational seal production for software engineering, recorded in the Δ1 register.
Engine faithfulness
The register records closure at Solana slot 419,487,383 on 13 May 2026.
Cross-substrate cost
The register records closure on 14 May 2026 at slot 419,620,789.
Canonical sealing cutover
The register records closure on 14 May 2026 at slot 419,671,008.
Trusted execution environment
Forward commitment FC-2 extends engine-faithfulness verification with runtime attestation, sequenced after FC-1.
Multi-party second runtime
Independent, licensed runtime replication, linked to milestone M2.
First statistical analysis
Triggered at 1,000 cycles or 100 Human Agencies with 10 cycles each, and at least 20 Agencies at depth 37 or more. The publication commitment is armed.
Second independent runtime
Event-triggered expansion through an independent, licensed second runtime.
Second domain capability
Domain-specific calibration through the Open Validation Program, using the published paired-sample criteria. The calibration route is open to licensing and Labs.
Lux Limit experiment
The Appendix O laboratory protocol tests the Landauer-limit predictions. The Lux Limit itself is a stipulated protocol constant.
Lux Limit experimental closure
Laboratory-availability dependent and carried by milestone M4. No experiment confirms or falsifies a stipulated constant.
Post-quantum migration
Ratified migration targets, a hybrid dual-signing epoch and hash agility, activated by Open Validation Program inscription.
Independent verification
Inspect the record.
Reproduce the result.
Check public anchors, reproduce engine outputs, and inspect the provenance of the declared observations. Record integrity and measurement validity each have a defined verification pathway.
Start with verification