Riddim Software Factory

Demo artifact

Fixing a Live iOS App With an Auditable Software Factory.

A bug report for epac moved through a traceable chain: transcript, public issue, autonomous PR, evidence artifacts, TestFlight workflow, and public App Store release.

  1. PromptTranscript creates EPAC-1940
  2. IssueGitHub Issue #499
  3. PRPR #494
  4. EvidenceReview artifacts
  5. WorkflowTestFlight run
  6. App StoreReleased app

epac shipment line

A receipt fills as the work order moves.

Request, scope, dispatch, build, evidence, review, release candidate, shipped.

  1. Req
  2. Scope
  3. Dispatch
  4. Build
  5. Evidence
  6. Review
  7. RC
  8. Shipped

Featured dynamic receipt

Fix Parliament calendar retap scroll and add visible Today action

Shipped

A public GitHub issue records the bug: re-tapping the active Parliament tab sent the sitting...

  1. Prompt/source Bug report: Parliament calendar jumps to January 2001
  2. Public issue GitHub Issue #499 records the public work order
  3. Dispatch/dev agent symphonyd dispatched Riddim Developer Bot
  4. PR PR #494 merged commit 6ee535f5
  5. Reviewer agent Reviewer-bot requested evidence before approval
  6. Evidence Committed before/after screenshots, recordings, and evidence README
  7. TestFlight candidate Post-merge TestFlight workflow included the fix
  8. App Store release epac 1.10 is public on the App Store
What you can inspect 63 populated receipt fields across the seeded line.

epac factory floor

Work orders move. Receipts fill in.

Every work order starts with a sparse receipt. As intake, scope, dispatch, development, evidence, review, and release departments touch it, the receipt gains public artifacts.

Factory state

15 work orders
63 fields populated

Assembly line · Request → Scope → Dispatch → Build → Evidence → Review → Release candidate → Shipped

On the line

Queue depth across the departments

8 active departments · 42 fields pending

Intake desk

Request

2

Scope desk

Scope

2

Dispatch desk

Dispatch

1

Developer bay

Build

2

Evidence department

Evidence

2

Review desk

Review

2

Release desk

Release Candidate

2

Output bay

Shipped

2

Moving work packet

Current gate: Human release gate

  1. 01 Dispatch Symphony claims the ticket and opens the branch.
  2. 02 Developer agent Developer-bot implements the scoped change.
  3. 03 Reviewer agent Reviewer-bot checks the branch.
  4. 04 Merge The accepted PR merges.
  5. 05 TestFlight The release candidate waits for a signed build.
  6. 06 Human validation A person verifies the build on device.
  7. 07 Corrective ticket Any validation fallout loops back into scope.
  8. 08 Release gate The packet waits for final release approval.

Current work order

epac

Human handoff for Retire Aurora by moving to S3 and CloudFront

Current: Release Candidate

The Aurora retirement project needs a human-owned release gate for demos, sign-offs, App Store Connect handling, and real-environment verification after autonomous implementation finishes.

Human release gate

Featured dynamic receipt

epac-1940

Fix Parliament calendar retap scroll and add visible Today action has the full public chain populated, from source issue to App Store release.

/receipts/epac/epac-1940/ Transcript creates EPAC-1940

Receipt filling

63 / 105 fields

Populated fields are public artifacts already attached to a receipt. Pending fields are the next proof items a department must produce.

Waiting signals

Next things entering the factory

  • Work orders entering intake 2 signals are waiting to be scoped
  • Evidence queue 2 receipts are waiting on screenshots, manifests, or release proof
  • Release gate 2 work orders are in TestFlight or human validation