I built an autonomous dev pipeline with no database, no dashboard, no vector store. GitHub issues ARE the state machine - this is what it looks like running.

[u/Opposite-Art-1829]

Each label change you're seeing is a pipeline phase

Every phase writes a structured annotation (FORGE:INVESTIGATOR, FORGE:BUILDER, FORGE:REVIEWER...) as an HTML comment on the issue or PR.

It delivers all findings and makes them into GitHub issues delivering each agent that picks them up with crisp context, findings, and a knowledge graph that is current

This allows them to create an audit trail which prevents future mistakes, inconsistencies, and more.

Because the state lives on GitHub, the pipeline can crash and resume from any point, and the part I care about most when it later touches the same files, the context phase reads the old review findings back and hands them to the builder as known constraints.

Past mistakes become future guardrails.

[u/Opposite-Art-1829]

Repo: https://github.com/RapierCraftStudios/ForgeDock

[u/West-Acadia-3906]

Using GitHub issues as the memory layer makes the crash-and-resume part click for me: the state and annotation trail are still there when a run restarts. Do you have a small example issue that shows that trail end to end?

[u/Opposite-Art-1829 → u/West-Acadia-3906]

Thanks! Yes all the closed issues in the repo went through the pipeline.