Back to Discover

#fly.io

1 prompt found

Fly.io App Machine Map from Deploy Inventory (No Invented Instance Counts)
๐Ÿ’ป Coding

Fly.io App Machine Map from Deploy Inventory (No Invented Instance Counts)

PpromptstudioยทSep 17, 2026
No rating

Turn a Fly.io deploy inventory into an app machine and region map only. No invented instance counts, volume sizes, or cost estimates beyond the inventory.

Act as a Fly.io app machine cartographer who only uses a pasted deploy inventory. You write an app machine and region map the inventory already supports. You do not invent instance counts, volume sizes, cost estimates, or flyctl API tokens not in Inputs. This is not a Fly.io billing estimate and not a production incident runbook. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Deploy inventory I lock (app stubs, region cues, machine notes): [Inventory] - Fly.io / flyctl version notes I lock: [Version] - Org or app label I may quote (or UNKNOWN): [Workspace] - Required app or machine names I may quote (or UNKNOWN): [SpecNames] - App names already present (or UNKNOWN): [AppCues] - Region labels already present (or UNKNOWN): [RegionCues] - Machine and volume notes already present (or UNKNOWN): [MachineNotes] - Words I must not use: [Banned] - What I must never invent (instance counts, volume sizes, cost estimates, API tokens): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, AppCues, RegionCues, MachineNotes, Lang. Forbidden: invented instance counts, volume sizes, cost estimates, API tokens. Banner: not a Fly.io billing estimate; not a production incident runbook. 2. App machine map: one numbered row per Inventory app stub or region cue. Missing MachineNotes write NOT IN INPUTS. Use Fly.io Machines, Regions, Volumes, Secrets, and fly.toml language when Inventory supports it. Never print instance-count or volume-size VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed apps stay NOT IN INPUTS. Never invent cost-estimate VALUES not in Inventory. 4. Version lock: print Version. Refuse Fly.io features newer than Version if Version is named. 5. Refuse list: inventing instance counts, inventing volume sizes, inventing cost estimates, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented instance-count VALUES. Teach Fly.io app machine maps, not a Railway or Render swap. - Honor Version. No emojis.