Torsionfield Runtime · Specification v3.2

Make the browser a programmable runtime.

Torsionfield begins with a ScriptCat-derived extension and a local Torsion Node. It turns webpages, authenticated AI sessions, userscripts, local tools, and optional peers into callable capabilities with explicit authority, observed effects, recovery, and rollback.

SPECIFICATION v3.2SCRIPTCAT-FIRSTLOCAL-FIRSTEDGE PLANE STAGED
DIRECT IMPLEMENTATION PATH
01 select    webpage element + goal
02 generate  through an authenticated AI page
03 install   into the real ScriptCat registry
04 run       against the target page
05 observe   the requested postcondition
06 repair    from real failure evidence
07 retain    working version or roll back

NO CENTRAL MODEL CREDENTIALS
NO FAKE DOWNLOAD-ONLY INSTALL
NO SUCCESS WITHOUT OBSERVATION

Nothing is silently prohibited. Nothing is silently trusted. Nothing is silently verified. Nothing is silently accepted.

The first complete product

One reversible browser-to-script loop.

The first release is not a browser fork, a distributed governance platform, or a promise of autonomous correctness. It is a working local browser runtime that can generate, install, execute, inspect, repair, and roll back a real userscript.

Choose a page, element, and desired behavior.
Use the user’s existing authenticated model session.
Write the complete script into ScriptCat’s canonical registry.
Run it and observe whether the behavior occurred.
Return exact evidence, patch, rerun, or restore.
Four cooperating planes

The implementation has clear physical boundaries.

01
Chat Runtime

Provider adapters control composers, submission, streaming output, attachments, and completion state on authenticated AI pages.

02
ScriptCat Runtime

Router, Mother Script, target selection, userscript registry, mutation, protected agent tabs, and operation identity.

03
Torsion Node

Authenticated local files, processes, tools, artifacts, durable journal, identity, and optional peer transport.

04
Participant Edge

An optional participant-owned cloud cell for persistent endpoints, encrypted buffering, release state, and local-node handoff.

Do not collapse these decisions

Permission, trust, assurance, and acceptance are independent.

Permission

May this exact operation execute under the selected authority profile?

Participant trust

How reliable is this participant for this task, role, consequence, device, and context?

Assurance

Which properties of identity, execution, observation, isolation, recovery, and attestation are actually supported?

Acceptance

Who is willing to rely on this exact result, for what purpose, despite what uncertainty?

Runtime invariants

Effects must be observable and recoverable.

  • Durable identities are separate from ephemeral browser tab IDs.
  • Non-idempotent effects are observed before retry.
  • Provider adapters are interaction contracts, not one selector.
  • Participant model credentials remain local.
  • Explicit unrestricted owner profiles remain expressible.
  • Cloudflare and peer networking remain optional.
OPERATION STATE
created
→ accepted
→ routing
→ running
→ awaiting_result
→ succeeded | failed
→ unknown_outcome

UNKNOWN_OUTCOME:
the effect may have occurred,
so observe before retry.
Capabilities

Useful before the network exists.

Generate and install userscripts

Full metadata, grants, match patterns, versions, enabled state, provenance, run evidence, and rollback.

Provider-independent chat execution

ChatGPT, Gemini, Perplexity, GitHub Copilot, Grok, AI Studio, and other pages through explicit adapters.

Protected agent tabs

Durable agent identity, restoration, ownership, anti-discard policy, and explicit release.

Local execution

Files, processes, MCP tools, artifacts, and long-running work through the Torsion Node.

Participant-owned edge cells

Cloudflare is the first reference binding, not the semantic identity of the capability.

ForkSense

Study current code, rejected proposals, forks, maintenance, and executable evidence before external integration.

Current implementation boundary

Architecture and evidence remain separate.

The public specification defines the intended runtime. Dated implementation evidence records what has actually passed. The Windows semantic harness has verified tests; the complete ScriptCat extension, Torsion Node, Debian runner, and participant edge pilot remain implementation work rather than implied completion.

Honest status

Specification: v3.2.

Product site: live.

Repository: public.

Complete integrated runtime: not yet delivered.

Participant Edge: approved for a bounded pilot, not general availability.

Alpha participation

Register a person, not their credentials.

The alpha form records interest. Provider cookies, model credentials, local files, and private keys remain local. Registration is not required for browser-only use.

  • Explore or help build the ScriptCat-first runtime.
  • Operate a Torsion Node or test a participant-owned edge cell later.
  • Publish only capabilities and endpoints you explicitly select.