Reference, experimental, and educational software associated with the published drafts. Maturity labels are deliberately conservative.
| Project | Draft scope | Status | Source |
|---|---|---|---|
| TCT for WordPress | TCT -03 | Experimental prerelease · 3.0.0-alpha.6 | GitHub |
| TCT Cloudflare Worker | TCT -03 | Canary · Alpha.3 generic coded lane; Alpha.2 WordPress and apex lanes | GitHub |
| TCT deployment validator | TCT -03 | Experimental · v0.1.0-alpha.1 | GitHub |
| Collaborative-state demos | TCT -03, AST -02, Semantic -01, Merge -00 | Educational · v0.1.0-alpha.1 | GitHub |
Current deployment surfaces
WordPress origin
This site exposes TCT machine surfaces from a WordPress origin through the Alpha.2 identity adapter. It is a test deployment, not a production-suitability claim.
Generic coded origin
The Alpha.3 canary preserves origin-generated identity and gzip representations across Cloudflare at generic-tct.llmpages.org.
Standalone verification
The validator and implementation-owned checks inspect bounded public surfaces without becoming part of either origin.
TCT Alpha.3 coded-representation result
The standalone experiment used the same substantive 1,450-word article for its human-facing C-URL and machine-facing M-URL. For a gzip-capable client, the median C-URL body was 4,678 bytes and the deterministic M-URL body was 4,176 bytes, a 10.731% reduction for this fixture.
The stronger result is representation correctness: identity and gzip use distinct body-derived strong ETags and Content-Digest values, while experimental Unencoded-Digest identifies their common unencoded representation. The direct-origin suite passed 37/37 checks and the Cloudflare edge/origin suite passed 63/63 checks.
Read the experiment summary Open the live M-URL Inspect the retained canary
Interpretation
- Experimental interfaces and packaging may change.
- A passing test establishes only behavior covered by that exact test, version, environment, and configuration.
- The byte result does not establish fewer requests, lower origin processing cost, production capacity, independent adoption, or compatibility with arbitrary origins and intermediaries.
- Historical repositories and generations may remain public for provenance; they are not silently promoted to current implementations.
- Test-only controls and fixture credentials are not production security mechanisms.