Agent Infrastructure — Interactive Demos

Synthetic demos of a personal multi-agent system by David Carlton Adams. All data is fictional; the architecture and interaction are real.

Trace is the shortest way in, about two minutes. Each page stands on its own.

Trace

one forwarded email followed through one day of the system: fourteen stops, nine on its path, each surface it touches and each gate it meets.

Where untrusted text stops, where a person's own call is required, what runs on a timer and only reports. Play the day, or tap a stop to see what that surface showed.

Flightpath

one-true-state project layer: cards, milestone bars, dependencies, collapse at every level.

One validating writer; every change logged with its reason. Staleness is computed from each project's own log rather than asserted, dues carry a type, and estimates are graded against actuals.

The Gazette

a daily personal newspaper: ranked classifieds, puzzle corner, graded course lesson.

Assembled overnight by an editor that runs with no tools. Everything from feeds and inbox is summarised, stripped of links and schema-checked before it can appear on the page. The linked Docket holds a forwarded job alert with a line planted for screening tools; it stays fenced off as data, and the machine summary points it out.

Gander

timeline + what-if sandbox over the same state layer: derived schedules, dependency cascades. Drag a bar and downstream dates follow; copy the scenario out as a proposal.

Schedules are derived from dependency order and, once calibrated, the estimate error factor, packed backward from deadlines. The critical path is drawn in gold beside a slack table, least slack first. Playing with the plan exports a proposal for the validating writer, shown as the Docket card it would file; the sandbox itself cannot write state.

Fictional data, real architecture. The projects, people, feeds and findings belong to an invented world; the lanes, gates, formats and timings are the production system's. All four pages share a 2026-10-02 snapshot; the README keeps the refresh log.

These pages are the public tier of a four-tier classification scheme. The scoped exports are built by adding allowed fields, never by redacting, so a field that was not cleared is simply absent.

Self-contained HTML, no external requests, nothing loaded from anywhere. Architecture notes in the README.