Ask for a bounded enrichment.
<!-- [[TF: INLINE {"id":"critique","target":"#result","mode":"append","task":"..."} ]] -->The page becomes capability-aware.
It may declare work that a local Torsionfield client can perform through the user’s own ChatGPT or other subscription. The website receives neither the account credential nor proof that a named model executed the request.
Text and whitelisted variables.
No arbitrary provider-produced HTML, scripts or event handlers enter the document.
Donate a verified artifact.
<!-- [[TF: UPDATE OUTCOME {"id":"render","source":"#canvas","artifactType":"image/webp","policy":"quarantine"} ]] -->Contribution, not authority.
Verified bytes and bounded compute time produce provisional contribution credit. Credit buys no governance, reputation or scientific truth.
Execution boundary.
page comment → local ScriptCat / Torsionfield bridge → user confirms or has explicitly enabled bounded auto-run → participant-owned provider session → safe result schema → client-side application Canvas / SVG result → local SHA-256 → server recomputes SHA-256 → private R2 quarantine → D1 receipt and provisional credit → later independent evaluation → accept, reject, or retain as failed provenance
What this does not prove.
The protocol proves that particular bytes were received under a particular directive and contributor identifier. Without provider-signed transcripts or attested execution, it does not prove that ChatGPT, a specific model, or an untouched prompt produced them.