GitHub transaction safety · 2026 · Solo — popularity-led research, Git object architecture, test-first implementation, editorial interaction design, security hardening, production verification

Decision Press

An evidence-to-action operator that reads a real merged GitHub pull request, sets a bounded ADR, and creates one draft pull request without gaining merge authority.

The problem

Consequential engineering decisions often survive only as fragments across a merged pull request: its description, changed files, review states, and merge identity. Decision Press reads that live public evidence, condenses explicit rationale into one conventional Markdown ADR, and lets an authorized maintainer open the record as a draft pull request. It does not infer objective truth, merge code, store credentials, or write until the operator reviews the exact artifact and attests to the bounded mutation. The product came from the secure 2026-08-11 Star Radar's daily #1 repository, PrimeIntellect-ai/prime-agent: 1,809 stars gained that day and 5,769 API-verified total stars. It translates demand for auditable agent execution into an adjacent human-controlled decision-publication workflow without cloning the source product, code, brand, or assets.

Architecture

Key decisions

01

Use Git object plumbing

The app creates a blob, derives a one-file tree from the current base, creates an explicitly parented commit, and advances a new ref without force. This exposes and tests consequential state transitions instead of hiding them behind a convenience endpoint.

02

Make publication compare-and-swap

The app snapshots pull, head, merge, and base identities while setting the ADR, then reloads them before mutation. Changed evidence fails closed rather than publishing stale state.

03

Spend the visual signature on the printing metaphor

The Operate surface uses a compositor-and-folio topology: live evidence is the type, the ADR is the sheet, and publication is the press run. Sky blueprint paper, Georgia display type, Consolas utility labels, yellow ink, and one paper-setting motion replace the dark technical instrument common to developer tools. Final anti-slop score: 0/10.

04

Keep authority narrower than convenience

Public evidence needs no token; private access and publication use a manually supplied fine-grained token held only in memory. The product creates a draft PR and never merges it.

Metrics

14
deterministic unit and transaction tests
5
production browser modes with zero overflow or runtime errors
0
high-severity dependency vulnerabilities
1809/day
observed star velocity of the upstream source