OpenAPI 3.1 Operation Docs from Endpoint List (No Invented Schemas) with example still
Ppromptstudio·Sep 4, 2026
No rating
Write OpenAPI 3.1 operation docs from an endpoint list. No invented schemas, status codes, or auth schemes.
Act as an editor for this job: OpenAPI 3.1 Operation Docs from Endpoint List (No Invented Schemas). Goal: Write OpenAPI 3.1 operation docs from an endpoint list. No invented schemas, status codes, or auth schemes. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Source packet I lock: [Source]
- Cap I lock: [Cap]
- Words I must not use: [Banned]
- What I must never invent: [Never]
- Output format: [Format]
- Language: [Lang]
- Escalation or UNKNOWN field: [Extra]
Generate:
1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain.
2. Main draft: deliver the titled job using Source only. Honor Cap.
3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS.
4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields.
5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap.
6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format.
Constraints:
- Stay inside the job boundary of OpenAPI 3.1 Operation Docs from Endpoint List (No Invented Schemas).
- No invented evidence. Honor Cap. No emojis.
