Asana Project Charter from Scope Notes (No Invented Dates)

Prompt

Act as an editor for this job: Asana Project Charter from Scope Notes (No Invented Dates). Goal: Build an Asana project charter from locked scope notes. No invented dates, owners, or budgets. 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 Asana Project Charter from Scope Notes (No Invented Dates).
- No invented evidence. Honor Cap. 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.

Asana Project Charter from Scope Notes (No Invented Dates) - Result

Examples

Example Input

Source: sample packet as pasted with two concrete nouns and one NOT IN INPUTS gap.
Cap: 12
Banned: guaranteed, ignore previous
Never: invent identifiers, invent fees, invent stats, invent paths
Format: ledger + draft + allowlist + gaps + refuse + compliance
Lang: English
Extra: UNKNOWN

Example Output

1. Ledger. Job: Asana Project Charter from Scope Notes (No Invented Dates). Description support: Build an Asana project charter from locked scope notes. No invented dates, owners, or budgets.. Cap from Inputs. Lang English. Forbidden: invented identifiers, stats, fees, paths, brands, part numbers, DOIs, and PII not present in Inputs.

2. Draft. Produce the deliverable named in the title using only Inputs. Quote source nouns. Mark missing fields NOT IN INPUTS. Stay under Cap. Print counts when Cap is numeric.

3. Structure. Keep section order from Generate. Do not add marketing claims. Do not add captions unless the job is explicitly about rules or tickets.

4. Gaps. List five bullets the user still owes. Use UNKNOWN or NOT IN INPUTS rather than guesses.

5. Refuse. Invented identifiers refused. Invented fees refused. Invented stats refused. Invented part numbers refused. Invented DOIs refused. Padding past Cap refused.

6. Compliance. Banned hits none. Format ledger+draft+structure+gaps+refuse+compliance. Re-check Never list.

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.

Allowlist discipline: every proper noun, system name, date, owner, fee, path, token, or metric in the draft must appear in Source. When Cap is numeric, print the count of sections or items delivered versus Cap. Prefer short labeled sections over prose padding. If Extra names an escalation owner, surface that owner in the ledger; if Extra is UNKNOWN, keep UNKNOWN visible. Do not invent Model Context Protocol schemas, API keys, or repository globs. Do not invent community ban reasons, strike counts, or moderator titles. Do not invent vendor contract end dates, SOW IDs, or residual access rows. Do not invent design token hex values, font families, or breakpoint names unless they appear in Source. Close with a one-line reminder that the human packet owner must approve before publish.