Audit Public Report Language

Make every shared sentence serve the audience. Remove the production trail from the public narrative while preserving facts, necessary qualifications, and decision-relevant context.

Load the file-format capability

Before inspecting or editing a report, load the relevant file Skill for PPTX, Slides, PDF, DOCX, HTML, Markdown, or the active design tool.

Use content-source-truth-auditor separately when a claim, count, date, publication status, attribution, or right needs factual verification. This Skill decides whether wording belongs in a public report and how to present it; it does not establish factual truth by itself.

Read public-language-audit-matrix.md for any multi-page or editable deliverable. Use it as the canonical source-to-classification-to-rewrite ledger, including notes, hidden content, metadata, and appendices exposed by the distribution format.

Lock the audience contract

Record:

• intended audience and presentation purpose;
• internal review, client review, leadership review, academic presentation, portfolio, or public distribution;
• shared format, including whether recipients receive an editable source file;
• visible slides or pages, appendix, speaker notes, comments, hidden slides, and internal audit files;
• facts and required legal, academic, financial, or methodological qualifications that must remain.

Treat speaker notes, hidden slides, comments, alt text, embedded filenames, and document properties as inspectable when an editable file will be shared. Do not assume hidden content is private.

Separate audience content from production reasoning

Classify every relevant text block:

Never delete a material qualification merely to make a slide cleaner. Rewrite it for the intended audience or move it to a location appropriate for that audience.

Detect non-public language

Flag these families:

Production and search trail

• “根据当前资料 / 根据截图 / 从文件中可识别 / 检索到 / 未找到”;
• “可核实 / 已核对 / 目前能够确认 / 完整列出如下”;
• filenames, folder paths, page-extraction notes, prompt wording, tool names, AI references, or generation steps;
• explanations of how content was collected, reconstructed, compared, or selected.

Internal count reconciliation

• why one count was included and another was excluded;
• denominator disputes, duplicate removal, temporary grouping logic, or manual tally notes;
• “X 个为背景数据，未计入项目” when the distinction serves the maker rather than the audience;
• reconciliation language that belongs in an audit table, methodology appendix, or source register.

Drafting and self-reference

• “本页用于展示 / 这里需要说明 / 后续可以补充 / 为避免误导”;
• TODOs, placeholders, open questions, review comments, and version-history notes;
• statements about the presentation, author, model, or production process instead of the subject.

Defensive caveats and evidence narration

• long explanations that defend why a claim can be shown;
• source quality commentary that the audience did not ask to evaluate;
• uncertainty phrased as production hesitation rather than a clear business status;
• internal approval routing, owner discussions, or unresolved evidence chains.

Sensitive or distribution-inappropriate content

• private names, internal links, permissions, customer details, unpublished decisions, or confidential status;
• speaker notes or hidden objects that reveal internal reasoning in a shared editable file.

Use phrase matching as a discovery aid. Judge the sentence by function and audience; do not delete every occurrence mechanically.

Rewrite for the audience

Apply these rules:

1. Lead with the business object, result, decision, change, or implication.
2. Remove claims about the maker's certainty such as “可核实” once the fact has passed verification.
3. Remove narration such as “完整列出如下”; let the title and structure introduce the list.
4. Keep only the denominator, time range, sample, or methodology the audience needs to interpret the number correctly.
5. Turn internal uncertainty into a concise status such as “待确认” only when that status affects the audience's decision.
6. Move detailed sources, inclusion rules, and evidence trails to an appendix or internal audit record when required.
7. Preserve the meaning, units, dates, names, qualifiers, and approved terminology of every retained fact.
8. Do not strengthen a claim during cleanup. Route unsupported certainty to Block or factual verification.

Examples:

Audit the complete file

1. Extract text from every slide, page, component, table, chart label, caption, footnote, and appendix.
2. Inspect notes, comments, hidden slides, hidden layers, alt text, links, document properties, and embedded filenames when the shared format exposes them.
3. Build a compact matrix with location, original text, classification, risk, proposed action, and replacement or destination.
4. Apply authorized revisions without changing verified meaning, layout hierarchy, or unrelated design.
5. Search again for exact rejected phrases and related process-language patterns.
6. Render or export the final public surfaces and inspect the audience reading flow.
7. Re-extract final text to catch content hidden by layout, cropping, or export behavior.

When the request is audit-only, stop after the matrix and recommended wording. When revision is authorized, edit the source file and preserve a recoverable original or version history.

Run the public-language gate

Pass only when:

• visible copy states audience-relevant facts, decisions, changes, or implications;
• no production reasoning, search narration, tool reference, count reconciliation, or internal drafting note remains on shared surfaces;
• necessary qualifications remain accurate and appropriately placed;
• public wording does not reveal private context or internal workflow;
• edits introduce no stronger or new unsupported claim;
• notes, hidden content, metadata, and appendices match the actual distribution boundary;
• final rendering and text extraction agree.

Return Pass, Rewrite, Move, Internal, or Block for every finding. Do not claim the file is ready for public distribution while any Block item remains.

Handoff

Return:

1. audience and distribution boundary;
2. files and surfaces inspected;
3. removed production-reasoning patterns;
4. rewritten audience-facing statements;
5. content moved to appendix, notes, or internal record;
6. blocked claims requiring verification or approval;
7. final public-language gate result.