[Codex] Add candidate Communication Pack templates

[sergstack]

Goal

Add candidate Communication Pack templates for executive summary, communication QA, chart commentary, audit finding wording, and optional slide storyline. Do not create a new Presentation project or deck generator.

Context

Communication Pack should work after Analytics facts and QA. It should package verified findings into concise executive, finance, audit, or decision communication without inventing facts, causes, metrics, or recommendations.

Pre-check performed in chat: searched open issues for communication executive summary finance memo audit memo chart commentary presentation slide storyline audit finding; no direct duplicate was found. Codex should still inspect repo files and issue context before editing.

First step

Search existing open issues and repo files for:

• communication
• executive summary
• finance memo
• audit memo
• chart commentary
• presentation
• slide storyline
• audit finding

If overlapping work exists, report it and do not duplicate.

Scope

Add minimal candidate templates/checklists only, if repo conventions support the destination.

Candidate files, subject to repo convention check:

• EXECUTIVE_SUMMARY_TEMPLATE.md
• COMMUNICATION_QA_CHECKLIST.md
• CHART_COMMENTARY_STANDARD.md
• AUDIT_FINDING_WORDING_TEMPLATE.md
• SLIDE_STORYLINE_TEMPLATE.md

Candidate destination, subject to inspection:

• ChatGPT/[LLM]/Templates/
• ChatGPT/[Analytics]/Templates/
• ChatGPT/[AI OS]/Knowledge/
• or existing equivalent repo convention.

Requirements

• Templates remain candidate / ready for human review.
• No production promotion without pilot evidence and owner acceptance.
• Analytics facts first, LLM narrative second.
• Deterministic checks first.
• No LLM arithmetic.
• No LLM variance / driver / exposure / root-cause calculation.
• Root cause must be evidenced or marked requires management confirmation.
• Recommendations must trace to verified facts.
• Facts, interpretation, limitations, confidence, and next action must be visible.
• Stream Deck communication commands require Prompt QA before promotion.

Template coverage

Executive Summary should include:

• main message
• what changed
• why it matters
• evidence: source, period, scope/population, metric/amount
• risk / opportunity
• recommended action
• confidence
• limitations

Communication QA should check:

• main message exists
• source exists
• period exists
• scope/population exists
• metric/amount/fact exists where applicable
• facts separated from interpretation
• root cause evidenced or marked requires management confirmation
• recommendation traceable to verified facts
• recommendation actionable
• owner / next step visible
• limitations visible
• confidence visible
• no unsupported claims

Chart Commentary should use:

What it shows:
What changed:
Why it matters:
What to do next:

Audit Finding wording should use cautious structure:

Finding:
Criteria:
Evidence:
Risk:
Cause: [Known cause or requires management confirmation]
Recommendation:
Confidence:
Limitations:

Slide Storyline should remain optional and candidate-only. It must not become a deck generator.

Forbidden

• No new project folder.
• No Presentation project.
• No deck generator.
• No raw-data-to-deck workflow.
• No production reporting automation.
• No autonomous reporting.
• No autonomous retrieval.
• No vector DB.
• No embeddings.
• No semantic search.
• No web UI.
• No unsupported root cause.
• No recommendation not traceable to verified facts.
• No private/client/vendor/employee/bank/invoice/payment/tax ID/personal data.
• No secrets or credentials.
• No raw dumps.
• No runtime artifacts.
• No PROJECT_INSTRUCTIONS.md edits unless required and justified.
• No auto-merge.

Checks to run

python3 scripts/check_project_instructions_length.py
python3 scripts/check_repo_public_safety.py
python3 scripts/check_manifest_paths.py
python3 scripts/check_knowledge_bundles.py
python3 scripts/check_codex_goal_mode_defaults.py
git diff --check

Acceptance criteria

• Existing issue/repo overlap checked.
• Minimal reversible diff.
• Candidate templates added only if no duplicate scope exists.
• Templates preserve Analytics-first workflow.
• Communication QA includes source, period, scope/population, evidence, limitations, confidence, and recommendation traceability.
• Root cause rule included.
• No production promotion implied.
• No blocked promotion items introduced.
• No public repo safety risk introduced.
• Upload/manifest references updated only if repo conventions require it.
• If Knowledge bundles/upload lists change, note that live ChatGPT Project sync and smoke QA must be checked separately.
• Checks pass or blockers are documented.
• Rollback note included.
• No auto-merge.

Stop conditions

Stop and report blockers if:

• existing open issue or repo artifact already covers the same scope;
• no clear destination folder convention exists;
• work requires new project structure or core routing rewrite;
• work requires deck generator, raw-data-to-deck workflow, autonomous reporting, or production automation;
• work requires blocked promotion items;
• work requires LLM arithmetic or root-cause calculation;
• work requires unsupported recommendation or unsupported root cause;
• work requires private data, secrets, raw dumps, or runtime artifacts.

Rollback

If PR is rejected or checks fail without a safe fix, revert only added Communication Pack templates and any related manifest/upload references.

Expected PR summary

• Added candidate Communication Pack templates.
• Existing overlap checked.
• Analytics-first workflow preserved.
• No new Presentation project.
• No deck generator.
• No production reporting automation.
• No candidate promotion.
• Checks listed.
• Residual risks and rollback documented.
• No auto-merge.