AI operating system for mega on Autopilot
Inspired by Constellation Space — AI operating system for mega-scale satellite networks. . Loop until the workflow is current, exceptions are owned, and human sign-off is captured where required.
Inspired by Constellation Space
by Trooper
/loop 30m Start the "AI operating system for mega on Autopilot" loop. Inspired by Constellation Space (https://constellation.space). Goal: open work triaged, exceptions owned, and core research workflow current with audit trail Max iterations: 20 Between iterations run: Report open queue items, stale tasks, failed automations, and items awaiting human approval for Constellation Space Exit when: zero open items without owner or explicit escalation, all external actions approved or sent, and systems of record current Step 1 — Intake demand: Collect specs, quantities, lead times, and vendor constraints. Step 2 — Source and compare: Rank suppliers or components by spec, cost, and availability. Step 3 — Draft orders: Prepare POs or build configs with cited BOM lines. Step 4 — Human approval: Require sign-off before spend or manufacturing commits. Step 5 — Track fulfillment: Monitor delivery, QA, and exception handling to close. ## Before you start Connect plugins: - GitHub (required) — Read branches, PRs, reviews, checks, workflow runs, and source diffs. - Browser / Web access (required) — Open pages, inspect live state, collect evidence, and verify changes. - Google Analytics (required) — Read traffic, conversion, product, or campaign performance signals. - Notion (required) — Read and update approved briefs, docs, calendars, and reports. Attach skills: - Loop runner (required) — Self-pace iterations, run the check between passes, and stop only on the exit condition. - Code change + local verification (optional) — Edit code safely, run commands, and keep changes scoped. - CI debugging (optional) — Read failing checks, logs, and the smallest actionable root cause. - Approval workflows (optional) — Keep outbound actions in draft or approval states when risk is non-trivial. - Browser QA (optional) — Exercise product flows, capture visual evidence, and verify fixes in-browser. - Content operations (optional) — Turn signals into reviewable briefs while preserving source attribution. - Research monitoring (optional) — Compare sources over time and separate verified changes from noise. Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.
Paste the kickoff prompt into Cursor, Claude Code, or Codex. Deeplinks do not install hook files.
1. Intake demand
Collect specs, quantities, lead times, and vendor constraints.
2. Source and compare
Rank suppliers or components by spec, cost, and availability.
3. Draft orders
Prepare POs or build configs with cited BOM lines.
4. Human approval
Require sign-off before spend or manufacturing commits.
5. Track fulfillment
Monitor delivery, QA, and exception handling to close.
Guardrails
Rules the agent must follow so it cannot cheat the exit condition.
- Require human approval before customer-facing sends, payments, or legal submissions unless pre-approved templates apply
- Preserve full audit trail linking source data to every automated action
- Escalate compliance, safety, or regulatory-sensitive items immediately
More Research loops
Inbox Triage with Approval
On an interval, classify incoming mail, draft safe replies for routine threads, and escalate anything that needs a human decision.
Morning Operator Brief
Daily interval loop that reads your calendar, open tickets, and inbox priorities, then delivers a concise operator brief with ranked actions.
Customer Onboarding Watch
Interval loop that watches new signups, runs the onboarding checklist against each account, and nudges or escalates stuck users.
