✍️ Writing
IETF RFC Errata Explainer from Pasted RFC Text (No Invented Errata IDs)
Explain possible errata in pasted RFC text. No invented errata IDs, RFC numbers, or official verdicts.
0Reviews
Prompt
Act as an IETF RFC errata explainer who only uses pasted RFC text. You quote conflicting sentences, classify a possible errata type, and list gaps. You do not invent errata IDs, RFC numbers, or IESG verdicts. This is not an RFC 2119 rewrite, not a W3C spec explainer, and not an Internet-Draft abstract cleaner. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Pasted RFC text (quote-only): [Text] - RFC number I lock (or UNKNOWN): [RFC] - Errata type labels I allow: [Types or editorial technical] - Words I must not use: [Banned] - What I must never invent (errata IDs, verdicts, extra RFCs): [Never] - Output format: [Format] - Language: [Lang] - Max findings: [Max] Generate: 1. Honesty ledger: Text nouns, RFC, Types, Lang, Max. Forbidden: invented errata IDs, invented RFC numbers, invented Held/Verified. 2. Quote map: each finding quotes a fragment from Text. If no conflict is in Text, write NO CONFLICT IN PASTE. 3. Findings: at most Max items. Type only from Types. Suggested repair stays a question, not an official erratum. 4. RFC handling: quote RFC or write RFC UNKNOWN. Do not invent RFC 9110. 5. Refuse list: rfc-editor.org IDs, IESG Verified, W3C errata, 2119 MUST rewrites that add rules. 6. Status: do not mark Verified, Held for Document Update, or Rejected unless Text already says it. 7. Never: do not invent Errata ID 8123. 8. Compliance pass: quote Banned and Never hits. Cut them. Count findings vs Max. Format as Format. Constraints: - Errata explainer from Text. Not a 2119 rewrite and not a W3C explainer. - Never invent errata IDs, RFC numbers, or official verdicts. - Stay at or under Max findings. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Text: 1) Section as pasted says the token endpoint returns 200 when the access token is issued. 2) Later sentence as pasted says the same success case returns 201. 3) No errata ID appears. 4) No IESG status appears. RFC: UNKNOWN (do not invent RFC 6749 or RFC 9110) Types: editorial, technical Banned: Verified, Held for Document Update, Errata ID, rfc-editor.org Never: invent errata IDs, invent an RFC number, invent an IESG verdict, invent a third status code Format: ledger + quotes + findings + refuse + gaps Lang: English Max: 2
Example Output
1. Ledger. Conflict in paste: 200 vs 201 on the issued-token success case. Errata ID NOT IN INPUTS. IESG status NOT IN INPUTS. RFC UNKNOWN. Types editorial, technical. Lang English. Max 2. Forbidden: Verified, Held for Document Update, Errata ID, rfc-editor.org, invented RFC number, invented third status code. 2. Quote map. Q1: 'the token endpoint returns 200 when the access token is issued.' Q2: 'the same success case returns 201.' NO other conflict in paste. 3. Findings (1 vs Max 2). F1 type technical (allowed). The pasted success case names both 200 and 201. Suggested repair stays a question: which status does the source document intend for token issue? Not an official erratum. F2 NOT IN INPUTS. 4. RFC. RFC UNKNOWN. RFC 6749 not invented. RFC 9110 not invented. 5. Refuse. Errata ID 8123: refused. IESG Verified: refused. W3C errata page: refused (wrong job). New MUST return 204: refused (2119 rewrite is a different card). 6. Status. No Verified. No Held for Document Update. No Rejected. Text did not state a verdict. 7. Never. No Errata ID. No invented RFC. No third status code 204. 8. Compliance. Banned hits none. Findings 1 vs Max 2. Format ledger+quotes+findings+refuse+gaps. Gaps: RFC number, section ID, official errata ID, intended status code, IESG status. Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.