Flagship outcome packs

Autonomous Release Team now starts with one connected repository, one open GitHub issue, and optional constraints. The Issue Scoper reads only that issue, GitHub's default branch, and a filtered repository path manifest. It chooses the smallest relevant file boundary; only then does the Patch Planner read repository guidance, the chosen paths, and current checks before preparing one exact patch. Approved steps create the branch and Vercel preview, recheck GitHub Actions on that branch, verify the visible preview, then prepare the pull request, promotion, Slack proof, and source-issue update.

• Connect GitHub, Vercel, and Slack and enable Web access before Live run.
• Choose the repository, issue, Vercel project, Slack channel, and browser session in one launch review; Codelit verifies the same scopes still exist immediately before execution.
• Pull requests, archived repositories, truncated manifests, traversal, secret-like paths, generated folders, binaries, and files outside the scoped handoff fail closed.
• Use the GitHub issue trigger for new work or a bounded weekly schedule for maintenance review.

Refund Resolution Team reconciles one Zendesk ticket, Shopify order, Stripe PaymentIntent, supplied policy, and maximum refund amount. The decision must produce one exact positive amount at or below that ceiling before the Stripe preview can be approved; the customer ticket is updated only after Stripe evidence exists.

• Connect Zendesk, Shopify, and a restricted Stripe account.
• Stripe retries reuse the approved action checkpoint as the idempotency key.
• Use a signed webhook with deduplication and a daily cap for support intake.

Lead Qualification Team combines an allowlisted HubSpot contact with visible evidence from the exact LinkedIn company URL. It preserves campaign identity and explicit outreach permission, creates only an unsent Gmail draft, then updates HubSpot after the draft succeeds.

• Connect HubSpot and Google Workspace, then save a LinkedIn Browser Operator session when sign-in is required.
• Blocked, missing, or opted-out permission stops the run before Gmail or CRM writes.
• A daily Trigger Hub schedule applies deduplication, a ten-run daily cap, and configured quiet hours.

Choose Try agent first, use my data for a private read-only proof, then use Pro Live run for the exact approved actions. A successful receipt can become an Agent App or a hosted Trigger Hub deployment. The same workflow version, App requirements, approval boundaries, replay protection, and recovery checkpoints remain visible at each stage.

1. 1Complete the committed Sample and inspect its one meaningful approval.
2. 2Connect only the Apps named in Flow, then choose the exact source item and destination scopes shown in Launch review.
3. 3Start one Live run, inspect the App and browser evidence, then publish an Agent App or enable the recommended guarded trigger.