Autobahn extensions

Overview

My extensions to Autobahn, originally created by Eli Rousso / Rams. I built on its MIT-licensed markdown-backed board for my own agent-assisted workflow, adding bounded dispatch, review evidence, and contribution records. The original tool is at github.com/rams-design/autobahn; my extensions remain private. Images use the actual local UI with synthetic workspace and run records, with no workers or client systems connected.

The Challenge

A planned task, an agent run, a passed check, and a merged change are different events. I needed the interface to preserve those differences so a busy board could not imply that the work was finished or ready to ship.

Approach

1. Keep planning readable

The board retains Autobahn's markdown-first foundation. My backlog extensions add explicit next actions and distinguish active work, blocked work, and items waiting for review.

2. Bring evidence into the review

The review view brings the recorded stages, reports, check results, and final diff together. Missing or stale evidence remains visible, and a recorded acceptance is not presented as proof that a particular person approved it.

3. Record contributions carefully

The journal distinguishes open work, submitted reviews, reported completions, and merged changes. Its export retains categories and flags incomplete source coverage rather than turning every record into a shipped result.

Outcome

A private extension of an existing tool, used to make my workflow easier to inspect. Evidence interpretation and journal behavior have regression tests. Further pacing work remains in development. The screenshot run records are fictional demonstrations of the UI, not real model executions or shipped client work.

Proof points

Learnings

• →The planned state of a ticket should not stand in for execution evidence.
• →Check results, review decisions, and publication need separate meanings.
• →Contribution records are more useful when missing coverage is explicit.