Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the wiring to let a merged spec build itself to a finished PR without a human in the loop — opt-in per feature, fenced, and with an explicit escalation channel.
What's here
.github/workflows/autonomous-build.yml— fires only when aspec:PR is merged and carries theautonomous-buildlabel. Runs/buildheadlessly on Opus 4.8 to a green suite and opens abuild:PR. The label is the opt-in: unlabeled spec merges do nothing, so autonomy is never the default..github/workflows/deploy-autofix.yml— on a failed deploy, hands a fresh agentflyctl+ logs to diagnose and fix, opening afix: deploy …PR (not a push to main). Enable after the build loop is proven; it's the riskiest piece and gets the tightest leash.AUTONOMY.md— the contract: how it runs, the escalation rules, the fences, and the prerequisites.The design decisions, made literal
autonomous-buildlabel — small/confident work goes autonomous, novel/dangerous work stays in the loop.build-blocked:/deploy-blocked:issue and stops rather than spinning or faking green.Before this can run (one-time, owner-only)
ANTHROPIC_API_KEYto repo secrets (repo admin).FLY_API_TOKENis in repo secrets.autonomous-buildlabel.deploy-autofix.yml, setworkflows: ["…"]to your deploy workflow's name; uncomment the toolchain setup inautonomous-build.ymlfor your stack.Out of scope
Auto-merge of any PR (every PR stays a human gate), and direct Fastmail notification (GitHub issues are the default channel; wiring Fastmail to the two labels is a later enhancement).
These are framework templates with project-specific values marked for fill-in. Review, then merge to land the pattern.