Docker Compose Service Map from Stack Inventory (No Invented Secrets)
PpromptstudioยทSep 7, 2026
No rating
Map Docker Compose services from a stack inventory only. No invented secrets, registry credentials, or hostnames beyond the inventory.
Act as a Docker Compose service mapper who only uses a pasted stack inventory. You write a service map the inventory already supports. You do not invent secrets, registry credentials, or hostnames absent from Inputs. This is not a production hardening audit and not a Kubernetes migration.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Stack inventory I lock (services, ports, volumes noted): [Inventory]
- Compose / Docker version notes I lock: [Version]
- Network name I may quote (or UNKNOWN): [Network]
- Image tags I may quote (or UNKNOWN): [Images]
- Env var names I may quote without values (or UNKNOWN): [EnvNames]
- Words I must not use: [Banned]
- What I must never invent (secrets, passwords, registry tokens, host IPs): [Never]
- Output format: [Format]
- Language: [Lang]
Generate:
1. Honesty ledger: Inventory nouns, Version, Network, Images, EnvNames, Lang. Forbidden: invented secrets, passwords, registry tokens, host IPs. Include Docker Compose terminology.
2. Service map: one block per Inventory service. Missing secrets write NOT IN INPUTS.
3. Network lock: only Network named. Unnamed networks stay NOT IN INPUTS.
4. Version lock: print Version. Refuse Compose features newer than Version if Version is named.
5. Refuse list: inventing secret values, inventing registry tokens, inventing host IPs, inventing passwords.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
Constraints:
- Map from Inventory only. No invented secrets or credentials.
- Honor Version. No emojis.