Projects
Four projects preserve different parts of one durable work trajectory.
Start from the failure each project prevents, the capability it currently provides, and the evidence that supports its maturity. Ownership details remain on the project page.
01Agent system
Tested architectural coreProblemA capable model can finish one run while the user's larger task, accepted decisions, and unfinished work disappear with the session.
What it doesPreserves goals, tasks, accepted decisions, assignments, and completion evidence above replaceable model runs and local processes.
Open question · testingCan Host complete a general repository Goal without absorbing Runtime mechanics?
See the next test ↗02Agent system
Production-tested local runtimeProblemShell commands and transient processes do not preserve enough identity or evidence for a later agent to know what actually happened.
What it doesTurns admitted local operations into durable jobs, observable process state, bounded output, artifacts, cancellation, and restart recovery.
Open question · testingWhich real structured operation can complete the minimal Effect contract across a second backend?
See the next test ↗03World interaction
Experimental boundaryProblemAn external action can lose its response while paths, identities, and provider conditions change, making a blind retry unsafe.
What it doesCorrelates target, path, identity, authority, provider execution, receipts, observations, uncertainty, reconciliation, and rebinding around one external interaction.
Open question · testingCan one Host Task combine path evidence and provider execution, reconcile a lost response, and continue without duplicate work?
See the next test ↗RFoundations
Active research foundationProblemAgent systems can accumulate shared abstractions faster than real workloads justify them.
What it doesCompares proposed contracts against mature baselines and keeps only the responsibilities that survive replacement, interruption, and a deletion test.
Open question · testingWhich contracts survive a second independent workload without being tailored to one repository?
See the next test ↗Host owns the meaning and accepted progress of durable work. Runtime owns local execution facts. World owns conditioned external interaction. Computing tests which shared contracts remain necessary across those boundaries.
Source, tests, releases, receipts, and each repository's current documents remain the technical authority. This site provides orientation, evidence paths, and dated judgment.