False Systems® Explore the Technology ↗
False Systems / Computing as craftBerlin — Helsinki / 00

Delegate more.
Move faster.
Keep control.

One persistent Operation connects local execution, a remote Host, and a customer cluster across distinct boundaries.
Fig. 01 / One work identity. Different places.

The work moves.
The account stays with it.

Infrastructure for humans and AI agents.

Know who did what, under whose authority, and what happened next.

Explore the platform ↗
Continuous work / Explicit authority / Durable evidenceScroll to follow the work ↓
01 / The discontinuity

Software has changed.
Its infrastructure hasn’t.

Agents write code, operate tools, change infrastructure, and initiate deployments. The work crosses systems that disagree about identity, authority, progress, and evidence.

Different teams. Different tools. Agents you can’t blindly trust. You need to know who did what—and whether they were allowed to.

  1. 01 / IntentDeveloperA task
  2. 02 / DelegationAgentA session
  3. 03 / AutomationCIA job
  4. 04 / AccessCloudA credential
  5. 05 / ChangeKubernetesAn object
The same work continues. Its context is split across five accounts.
02 / Habitat

Run there.
Work here.

Give agents remote compute.
Keep your work close.

Your laptop, a remote machine, your team’s cluster—the goal is one way to work across them. Follow the task, not the worker running it.

Habitat keeps the work’s identity, recorded history, and retained results beyond an individual worker. The connected local-to-remote experience is still in development.

Explore Habitat ↗
One task. Different places to run.

Explore the idea: change where the task runs, without losing track of the work.

01 / Start with a task.

Give the work an identity and set its permissions. The worker can act only within that scope.

Record 01 — the task & its permissions
02 / Run there. Follow it here.

The goal: use a remote machine while following the same task from your own. No new identity just because the work runs elsewhere.

Record 01 + 02 — where the work runs
03 / New worker. Same task.

A replacement must be authorized before it acts. Kept results remain available; unfinished work still needs a recovery decision.

Record 01 + 02 + 03 — who takes over

An illustration of the intended experience, not a live demo. Remote connection and cross-host handoff are in development. The moving circle represents the task—not a running process moving between machines.

03 / The platform

One system.
Continuous work.

False Systems is building a control plane for humans, agents, and infrastructure—not a central service that every local action must pass through.

Client and Gateway connect work to Habitat. Control Plane coordinates authority separately from execution; Evidence preserves the account.
Execution, coordination, and evidence have different responsibilities. Lines express relationships, not a mandatory synchronous request path.
Explore the architecture ↗
04 / Authority & accountability

Authority
is not a prompt.

An agent should not need unrestricted production credentials to complete a specific task. Authority belongs to durable work, within an explicit scope—not to whatever a prompt persuades a worker to do.

Habitat’s custody-bound model ties a bounded grant to the current custodian of an Operation. Supported mediated effects provide a controlled path for selected external actions.

  1. Operation
  2. Bounded grant
  3. Verified custody
  4. Mediated effect
  5. Record

Who acted? What changed? Which grant permitted it?
The record should connect those answers—and expose what remains unknown.

Inspect the boundaries ↗

Full credential brokerage and broader production integrations are in development. A recorded request is not automatically a confirmed external effect.

05 / Engineering outcomes

Move faster.
Know what happened.

The aim is more useful delegation without losing the ability to explain the result. These are outcomes to test with engineering teams, not performance claims already achieved.

01

Less repeated work after failure.

Measure how much completed work must be rerun when a worker disappears.

02

Fewer manual interventions.

Measure where a human must reconstruct context or reconnect a task.

03

More work worth delegating.

Measure which operational tasks can be completed within an agreed scope.

04

Controlled access.

Examine the authority needed for a task against the authority actually granted.

05

A record you can examine.

Test whether another reader can connect actors, actions, authority, and outcomes.

06 / Engineering notes

Thinking in public.

The Journal ↗
14 October 2026 / Agent infrastructure

The Process Is Not the Work ↗

A process executes. Work must be accomplished. What happens to authority and responsibility when the agent is gone?

07 / Berlin — Helsinki

Computing is a craft.
Infrastructure deserves care.

A small team with experience in eBPF, Kubernetes, and large production systems. We bring systems history to a contemporary question: how should infrastructure work when people and agents operate it together?

Meet False Systems ↗
08 / An open invitation

The work
continues.

For technical discussion, design partnerships, and CTO research: bring a real workflow, a difficult boundary, or a question your current records cannot answer.

Talk with us ↗