Riddim Software Factory
AI Tinkerers

May 20 submission narrative

EPAC factory story: a public bug report becomes a shipped iOS fix.

The demo thesis is simple: GitHub Issue → symphonyd dispatch → developer-agent PR → reviewer-agent gate → evidence bundle → auto-merge → TestFlight candidate → App Store release.

Open factory floor Inspect EPAC receipts

Narrative spine

A lonely app bug becomes a public, auditable production change.

  1. 01

    Prompt becomes an issue.

    The public artifact is GitHub Issue #499: the Parliament calendar jumped to January 2001 when the active tab was tapped again. The issue records the reproduction, impact, resolution, and EPAC-1940 migration note.

  2. 02

    Symphony dispatches developer agents.

    symphonyd turns scoped work into an isolated implementation branch. The demoable public output is reviewable code from riddim-developer-bot, not a private chat transcript.

  3. 03

    Developer-agent PRs carry the work.

    PR #494 scoped the fix: disable the calendar scroll-to-top path, add a visible Today action, declutter Parliament and Members toolbars, and add targeted regression coverage.

  4. 04

    Reviewer-agent and CI gate the merge.

    The reviewer bot asked for evidence before merge. The final PR carries the review trail plus committed artifacts under docs/review-artifacts/EPAC-1940.

  5. 05

    Auto-merge produces release candidates.

    After merge, the fix moved through the release machinery. The public proof trail includes a post-merge TestFlight build workflow and a later App Store submission workflow.

  6. 06

    The public app closes the loop.

    The final receipt is outside the factory: epac is public on the App Store. The demo stays honest about the boundary: autonomous work can prepare and prove the change, while App Store release remains a deliberate gate.

Live demo

Five-minute live-demo runbook.

  1. 00:00

    Open this page and read the thesis sentence in the first viewport.

  2. 00:45

    Click Open factory floor. Show the active factory floor, queue depth, and receipts filling in as work orders move.

  3. 01:45

    Open the EPAC receipts ledger, then the featured EPAC-1940 receipt. Point out the public receipt model before diving into GitHub.

  4. 02:45

    Open Issue #499, then PR #494. Show the issue-linked agent work and reviewer-gated merge evidence.

  5. 04:00

    Open the evidence artifacts, the App Store submission workflow, and the public App Store listing.

Current state

The proof is public enough for a cursory review.

A reviewer can start at the receipt, then jump to the GitHub issue, PR, evidence screenshots, workflows, and App Store listing without needing Linear access.

Older receipts still show the EPAC-1919/1930 corrective loop, but the canonical submission example is EPAC-1940 / GitHub Issue #499 because it reaches a visible App Store outcome.