System implementation · torsionfield.de
The browser becomes a participatory scientific instrument.
Torsionfield begins with ScriptCat and userscripts, then allows proven capabilities to descend into extension APIs, local runtimes and native Chromium implementations.
Capability contracts
Specify what a function means, what it returns, what permissions it needs and which failures are observable. Do not freeze one implementation.
Multiple realizations
The same capability may run as a userscript shim, ScriptCat CAT_API, extension primitive, local Windows service or native browser function.
Bidirectional evolution
Recurring userscript patterns can be promoted downward into browser primitives. New browser capabilities can trigger upward redevelopment of scripts.
Shared AI actors
Dedicated tabs become durable campaign participants: researchers, critics, orchestrators and verifiers, coordinated without sharing complete browser profiles or credentials.
Compute donation
Nodes advertise bounded CPU, GPU, storage, browser context and human-approval capabilities. Campaigns request only what their contracts authorize.
Semantic patches
Chromium changes are preserved as intent, invariants, tests and subsystem maps so frontier models can re-realize them against future versions.