Local systems for work that has to last

The chat ends. The work should still make sense.

Agent sessions produce decisions, changes, and corrections faster than anyone can file them. I build local-first tools that keep that trail legible and make it retrievable later.

Current work

Three applications, each with its own boundary.

Each application keeps its own technical boundary. Their shared job is continuity: keeping useful state after the session that produced it has gone.

/pastlightIn development

Pastlight

Find the earlier work behind today’s question.

Pastlight is approaching its M1 evidence gate. That result will define the first public boundary; there is no public build yet.

Current state →
/daybookTesting

Daybook

Reconstruct the working record from agent activity.

The application is being tested outside its own development environment. Its eventual commercial role remains open.

Current state →
/standingIn development

Standing

Turn repeated corrections into reviewed rules.

The correction mechanism is in daily use. The smallest useful release for another person has not been set yet.

Current state →

One lane, several forms

Shared purpose does not require a shared runtime.

Applications hold durable state. Methods carry intent through a change. Maintenance tools keep the agent environment understandable. Public evidence shows where each claim came from.

  1. 01 Applications

    Pastlight, Daybook, and Standing keep history, activity, and reviewed learning.

  2. 02 Method

    Agent Workbench carries an uncertain question to a reviewable commit.

  3. 03 Maintenance

    Context Governor keeps configuration legible and checks what the always-on context costs.

  4. 04 Evidence

    Trials hold bounded proofs. Sea Trials carries the longer account of what happened.

Public record

The short result and the long story live in different places.

A trial makes one result inspectable. The log records dated changes. Sea Trials gives the work enough room to help someone facing the same wall.

Trials

Bounded tests with an inspectable result.

No public trials are ready yet. The empty state stays honest until the first artifact earns a page.

Open trials →

Log

Dated changes without the essay around them.

Current product states and structural decisions, kept short enough to scan.

Open the log →

Publication

Sea Trials

Field notes, release stories, methods, and postmortems from the work. Product facts stay on this site; the full account lives on the publication.

Read Sea Trials