Skip to archive results
// FIELD TRANSMISSIONS

System Logs

An archive of decisions, failures, changes, and shipped work. The record stays useful by keeping the sequence—and the limits—visible.

5entries on record

Latest entry

Recovery Starts With State Continuity

Long-running agent recovery depends on preserving execution state, pending decisions, artifacts, and side-effect history rather than simply retrying the last request.

A retry is easy to reason about when the request is the whole unit of work. It fails, you try again, and — provided the operation is safe to repeat — nothing particularly complicated has happened.

Recent transmissions

A portable floodlight casts a narrow beam across a smooth finished wall.

The Diagnostic Build Was Not the Release

A May 2026 Liminal Tarot paywall failure showed why a build instrumented to expose a runtime defect was not yet the artifact that should cross the release boundary.

diagnosticsrelease-engineering
Close-up of a generic retro game console with one cartridge loaded and several others nearby.

The Gateway Moved the Dependency Upstream

A multi-model gateway can reduce coupling to individual models while concentrating routing, billing, observability, and policy in the abstraction layer itself.

ai-gatewayslock-in
Close-up of two contrasting rock formations meeting along a prominent diagonal fault line across a rugged cliff face.

The Boundary Was the Architecture

A reconstructed decision note on why Dream Atlas separated its public archive, noindex workspace, and mutable demo into distinct authority lanes.

boundary-designarchitecture
A hand holding a smartphone beside a reflective glass surface, where multiple fading reflections of the phone recede into the distance.

The Source Was Correct. The Installed App Wasn't.

A reconstructed Liminal Tarot release incident about stale native assets, candidate identity, and why a green source tree cannot prove what reached a device.

release-integritynative-packagingincident-reconstruction