Technical

Authority, replay,
runtime, evidence.

This is where the machinery lives. The browser is read-only. SQLite is the current authoritative storage implementation. Kernel semantics remain backend-independent.

01

SQLite record

Durable operational truth: governed events, receipts, provenance, application state, and invocation lifecycle evidence.

02

Kernel

Deterministic governance, transition sequencing, receipts, replay, and atomic commit boundaries.

03

Runtime

Bounded context, provider execution, invocation lifecycle, effect ordering, recovery, and accounting.

04

Applications

Domain meaning and policy. Applications do not receive unrestricted database authority or governance bypass.

05

Presentation

GitHub Pages is the static shell. sudofx-live is a historyless disposable projection. Neither is ever read back as operational truth.

Current public-safe state

Live technical snapshot

Record revision—Loading live projection
Database—Verified projection only
Replay—Current bounded health
Applications3WAKE✳︎ + Conversation + Handoff
Projection provenance

Know exactly what you are looking at.

Projection type—
Projection schema—
Source revision—
SQLite integrity—
Generated—
Source commit—
Actions run—
AuthoritySQLite
Live data is fetched from the disposable sudofx-live projection branch, not from GitHub Pages and never from raw browser authority.
ELI15

The database is the official notebook.

Web pages, summaries, prompts, and charts are copies made for specific jobs. A copy never becomes the official record just because it is convenient.

Failure model

Stop rather than guess.

Stale revisions reject. Malformed provider output is not governed. Provider failure causes no authoritative mutation. Checkpoint conflict fails visibly rather than silently selecting a winner.