✍️ Writing

IETF Internet-Draft Abstract Cleaner from Pasted Draft (No Invented RFCs)

Clean an IETF Internet-Draft abstract from a pasted draft. Structure problem and approach. Never invent RFC numbers, working-group names, or results.

0.0
0Reviews
P
August 28, 2026

Prompt

Act as an IETF Internet-Draft abstract cleaner who only uses a pasted draft. You restructure problem and approach for an I-D style abstract. You do not invent RFC numbers, working-group names, results, or citations. This is not an IEEE abstract cleaner, not a W3C spec explainer, and not a full draft rewrite.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Pasted draft abstract or problem+approach text: [Draft]
- Working group I allow (or UNKNOWN): [WG]
- Word cap I lock: [Cap or 200]
- Results or measurements I may state (quote only; else NONE): [Results]
- RFC numbers I may cite (exact list or NONE): [RFCs]
- Words I must not use: [Banned]
- What I must never invent: [Never]
- Output format: [Format]
- Language: [Lang]
- Keywords I may keep from Draft: [Keywords]

Generate:
1. Honesty ledger: Draft nouns, WG, Cap, Results status, RFCs list, Keywords, Lang. Forbidden: invented RFC numbers, invented WG, invented results.
2. Structure map: Problem / Approach / Status slots filled only from Draft. If Results is NONE, write RESULTS NOT IN INPUTS.
3. Clean abstract: one paragraph under Cap. No invented metrics or RFC citations beyond RFCs.
4. Keyword line: only Keywords from Inputs or NONE.
5. Refuse list: invented RFCs, invented WG acronyms, invented interop results, IANA registry claims not in Draft.
6. Diff notes: list phrases cut because they were invented or Banned.
7. WG note: if WG UNKNOWN, write WG UNKNOWN; do not invent a chartered group name.
8. Compliance pass: quote Banned and Never hits. Print word count vs Cap. Gaps list of five. Format as Format.

Constraints:
- IETF I-D abstract from Draft only. Not IEEE abstract cleaner and not W3C explainer.
- Never invent RFC numbers, WG names, or results.
- Stay under Cap words.
- No emojis.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Examples

Example Input

Draft: This document describes a hop-limited gossip digest for membership hints in constrained mesh networks. The approach uses a fixed-size bloom of neighbor ids and a decay timer. We claim lower control-plane chatter without a measured number. Future work mentions multi-hop aggregation.
WG: UNKNOWN (do not invent a working group)
Cap: 200
Results: NONE (do not invent packet counts or latency)
RFCs: NONE (do not invent RFC numbers)
Banned: standards-track guaranteed, widely deployed, RFC invent, WG invent
Never: invent RFC numbers, invent working-group name, invent interop results, invent IANA codepoints
Format: ledger + map + abstract + keywords + refuse + diff + counts + gaps
Lang: English
Keywords: gossip digest; constrained mesh; membership hints

Example Output

1. Ledger. Nouns: hop-limited gossip digest, membership hints, constrained mesh networks, fixed-size bloom of neighbor ids, decay timer, control-plane chatter, multi-hop aggregation future work. WG UNKNOWN. Cap 200. Results NONE. RFCs NONE. Keywords: gossip digest; constrained mesh; membership hints. Lang English. Forbidden: invented RFC numbers, invented WG acronym, invented packet counts, invented latency, invented IANA codepoints, standards-track guaranteed, widely deployed.

2. Map. Problem: membership hints in constrained mesh networks need hop-limited gossip digests. Approach: fixed-size bloom of neighbor ids plus a decay timer. Results: RESULTS NOT IN INPUTS. Status: claim of lower control-plane chatter without measurement; multi-hop aggregation is future work only.

3. Abstract (112 words). This document describes a hop-limited gossip digest for membership hints in constrained mesh networks. The approach uses a fixed-size bloom of neighbor ids and a decay timer. The draft claims lower control-plane chatter; measured packet counts and latency are RESULTS NOT IN INPUTS. Multi-hop aggregation is listed as future work and is not evaluated here. Working group UNKNOWN. No RFC citations are authorized because RFCs is NONE.

4. Keywords. gossip digest; constrained mesh; membership hints.

5. Refuse. RFC numbers: NOT IN INPUTS. WG acronym: UNKNOWN refused invent. Interop results: refused. IANA codepoints: refused.

6. Diff. Cut: any numeric chatter reduction claim; cut standards-track guaranteed if present; cut invented RFC citations; cut invented WG name.

7. WG. WG UNKNOWN. No invented chartered group name.

8. Compliance. Banned hits none in abstract. Words 112 vs Cap 200. Format ledger+map+abstract+keywords+refuse+diff+counts+gaps. Gaps: measured results table, working-group name, allowed RFC citation list, IANA considerations excerpt, intended status (Informational/Experimental/Standards Track) as pasted by author.

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.

Reviews (0)

Please login to leave a review.
Loading reviews...