Durable governed context

The AI can change.
The work should survive.

sudofx keeps important work in an accountable external record. A model gets the context it needs, proposes what should happen next, and can disappear. The system governs what becomes durable so a fresh intelligence can reconstruct the work and continue.

Application access

Checking the authoritative sudofx application-access latch…

Operator kill switch ↗
What it is

A save system and a referee for AI-assisted work.

ELI15

The AI is replaceable. The record and the rules are not. sudofx lets a new model pick up from an accountable history instead of pretending it remembers an old chat.

Instead of asking one model to “remember everything,” sudofx externalizes continuity. Durable events, proposals, governance decisions, transitions, receipts, provenance, and application state live in the authoritative database. Everything shown in a browser is a view of that record.

The loop

Models propose. The system governs.

Record→Context→Proposal→Governance→Transition→Receipt

The model does not get database authority. It receives bounded context and returns an untrusted proposal. Deterministic governance decides whether that proposal can become durable.

Proof, not promise

Three applications already exercise the boundary.

View applications →
Reference application

WAKE✳︎

An experimental research system running on sudofx authority/runtime primitives while keeping research policy in its own application.

Open WAKE✳︎ ↗
Continuity proof

Conversation

A minimal governed conversation application proving that multiple turns can survive fresh-process replacement from SQLite alone.

Open Conversation →
Portable continuity application

Handoff

Builds bounded governed packets for fresh intelligences and records deterministic packet-grounding evidence through the same application boundary.

Inspect Handoff →
Live projection

Loading current public-safe state…

Inspect technical state →