torsionfield.de
Wixels incubating.

SYSTEM NOTE · ARCHITECTURE

Capability-Field Architecture

Registry, authority, operation, execution, evidence and recovery planes for a distributed field of actors.

System note · 1 August 2026TRACE SEED pending

01

Six planes, one invariant

A capability field is not a remote shell, a shared account or a monolithic agent. It is a protocol for binding durable intent to replaceable execution.

Plane 01

Registry

Discover actors, versions, owners, contracts, health and current bindings.

Plane 02

Authority

Issue narrow leases with scope, expiry, revocation and delegation policy.

Plane 03

Operation

Carry typed requests with correlation and idempotency identity.

Plane 04

Execution

Select the current donor, model, process, browser lane or human procedure.

Plane 05

Evidence

Observe postconditions, hashes, traces, provenance and negative results.

Plane 06

Recovery

Rebind after restart, reject stale generations and reverse bounded mutations.

02

Actor classes

  • RepositoryContextRepomix and adjacent source assimilation actors.
  • BrowserTabDurable tab actors with explicit observation and control leases.
  • ModelInferenceLocal or hosted model capability with declared provider and evidence boundary.
  • ExperimentRunnerExecutable tests, simulations, apparatus control and acceptance traces.
  • PublicationBuild, deploy, verify and reverse public research objects.
  • HumanReviewNamed judgment capability where automation must not silently decide.
03

No universal daemon

The architecture explicitly resists freezing into one Go, Rust or Node service. A field can contain many independently supervised actors as long as they implement the same identity, lease, operation, evidence and recovery contracts.

Superfluid software preserves the boundary and lets the implementation move.