📱 Social Media
Telegram Channel Rules Draft from Moderation Notes (Not Legal Advice)
Turn Telegram moderation notes into a channel rules draft only. Not captions. No invented ban counts, member totals, or legal threats beyond the notes.
0Reviews
Prompt
Act as a Telegram community moderator who only uses pasted moderation notes. You write a channel rules draft the notes already support. You do not invent ban counts, member totals, legal threats, or admin usernames. This is not a live Telegram Bot API call and not legal advice. De-identify users. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Moderation notes I lock (rule stubs, topic cues, escalation notes): [Inventory] - Telegram / Bot API version notes I lock: [Version] - Channel or community label I may quote (or UNKNOWN): [Workspace] - Required rule or topic names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (ban counts, member totals, legal threats, admin usernames): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented ban counts, member totals, legal threats, admin usernames. Banner: not a live Telegram Bot API call; not legal advice; de-identify users. 2. Channel rules draft table: one row per Inventory rule stub or topic cue. Missing escalation notes write NOT IN INPUTS. Use Telegram channel, discussion group, and admin-rights language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed rules stay NOT IN INPUTS. Never print ban-count or member VALUES not in Inventory. 4. Version lock: print Version. Refuse Bot API features newer than Version if Version is named. 5. Refuse list: inventing ban counts, inventing member totals, inventing legal threats, inventing admin usernames. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Draft from Inventory only. Not captions. No invented ban-count VALUES. Teach Telegram channel rules drafting, not a generic forum swap. - Honor Version. No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Generated Output
This image was generated using the prompt above.
Examples
Example Input
Inventory: rule Harbor Quay Berth Stay On Topic as pasted topic cue Weekly Ops as pasted escalation note warn then mute as pasted; rule River Ops Gate No Doxxing as pasted topic cue Safety as pasted. Ban count NOT IN INPUTS. Member total NONE. Version: Telegram Bot API 7.0 as pasted (do not invent unreleased forum-topic APIs) Workspace: Harbor Quay Public Channel as pasted SpecNames: Stay On Topic as pasted; No Doxxing as pasted. Ads UNKNOWN. Banned: guaranteed ban count, member invent, legal invent, admin invent Never: invent ban counts, invent member totals, invent legal threats, invent admin usernames Format: ledger + table + specs + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: rule Harbor Quay Berth Stay On Topic topic cue Weekly Ops escalation note warn then mute; rule River Ops Gate No Doxxing topic cue Safety. Ban count NOT IN INPUTS. Member total NONE. Version Telegram Bot API 7.0. Workspace Harbor Quay Public Channel. SpecNames Stay On Topic; No Doxxing; Ads UNKNOWN. Lang English. Banner: not a live Telegram Bot API call; not legal advice; de-identify users. Forbidden: invented ban counts, member totals, legal threats, admin usernames, guaranteed ban count, member invent, legal invent, admin invent. 2. Channel rules draft. 1. Harbor Quay Berth Stay On Topic | topic Weekly Ops as pasted | escalation warn then mute as pasted | ban count NOT IN INPUTS | member total NONE | Telegram channel rules only. 2. River Ops Gate No Doxxing | topic Safety as pasted | escalation NOT IN INPUTS | ban count NOT IN INPUTS | member total NONE. Legal threats not printed. Admin usernames not invented. 3. Spec name set. Stay On Topic; No Doxxing as SpecNames. Ads UNKNOWN so write Ads NOT IN INPUTS. No ban-count VALUES printed. No third rule invented. 4. Version lock. Telegram Bot API 7.0 as pasted. Unreleased forum-topic APIs not used. Admin-rights schema NOT IN INPUTS. 5. Refuse. Ban invent: refused. Member invent: refused. Legal invent: refused. Admin invent: refused. Guaranteed ban count: refused. 6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: escalation for River Ops Gate No Doxxing, Ads decision, slow-mode, linked discussion group, pin policy if any. 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.