Follow the work,
not the agent.

Agents come and go. Their work doesn't.

False Systems gives agent operations durable identity, bounded authority, independent observation, and evidence you can trust — from task to external effect.

See how it works ↓
An operation crosses authority and runtime boundaries, produces an external effect and leaves evidence.
01 / The operational gap

The result is outside the sandbox.

A pull request lives in GitHub. A deployment keeps running in your cluster. Neither disappears when the agent exits.

What does your sandbox know about the pull request it just produced?

Containing execution does not account for its effects.

02 / The operation

Follow the work,
not the agent.

The agent is disposable. The operation is not.

A process crashes. A session ends. A model changes. The operation keeps its identity, authority, lifetime, state, effects, observations, evidence and results.

03 / Control

Bound the access.
Track the consequences.

Access should be explicit, bounded and tied to the operation. The agent process and the operation’s authority have different lifetimes.

Control authority and lifetime →
04 / Continuity

Change agents.
Keep your progress.

Another authorized agent can continue with the operation’s state, artifacts and history. A handoff preserves what has already been completed.

Continue from saved state →
05 / Observation

See what actually happened
when you run agents.

Observe process execution, file activity and network connections independently of the agent’s account.

No layer gets to claim more than it can prove.

Understand observation →
06 / Verification

“Done” is a claim.
Check the evidence.

“Done. Tests pass.” is a claim. Compare it with independently recorded evidence, then apply your acceptance policy.

Know what was observed. Know what was not.

Decide what to accept →
07 / Attribution

Know what caused the change.

Connect actors, operations, credentials and observed effects into an operational chain you can defend.

Which automation caused this deployment? Which operation used the credential? What evidence supports that connection—and how confident is it?

Trace changes across systems →
08 / The architecture

One operation.
Independent responsibilities.

One system, with explicit responsibilities. No layer has to certify its own version of reality.

Acceptance

Taso

What evidence is sufficient?

Authority

Ote

What may this operation do?

Continuity

Solu

What survives agent replacement?

Observation

Selko

What was independently observed?

Attribution

Vartio

What caused the change?

One operation: Taso verifies acceptance, Ote controls authority, Solu preserves state, Selko observes independently and Vartio attributes effects.
Explore the architecture →
False Systems

Your systems.
Your authority.

Durable operations. Bounded authority. Independent observation.
Attribution and evidence for deciding what to trust.

Talk to us →Read our manifesto →