[Codex] Add Analytics Finance Core templates

[sergstack]

Goal

Add minimal Finance / FP&A / Analytics core templates to the [Analytics] project without creating a duplicate finance workflow layer.

Context

[Analytics] already defines the Analytics Factory workflow:

question -> data contract -> stage -> mart -> calc -> findings -> memo -> judge/QA -> acceptance -> next run

AIOS_04_GOAL_PACKS_AND_COMMAND_SURFACE.md already includes finance_memo_factory, analytics_factory_loop, and audit_anomaly_review. dashboard_critic and reconciliation_builder are candidate packs and must stay candidate unless there is pilot evidence and explicit acceptance.

First step

Inspect the existing [Analytics] folder structure, Knowledge files, bundle files, upload lists, manifests, and repo conventions before creating or editing files. Do not assume destination folders exist.

Scope

Create or update minimal reusable templates/checklists for:

1. Analytics Context Pack
2. Variance Analysis Pack
3. Audit Anomaly Input/Output template
4. Finance Memo QA checklist

Template requirements

Each template must reinforce the existing Analytics Factory concepts:

• data contract
• grain
• period
• filters
• method
• QA
• limitations
• acceptance

LLM arithmetic remains forbidden. Memo narrative must be based only on verified Analytics facts.

Candidate file locations

Use only paths that exist or are supported by repo conventions, such as:

• ChatGPT/[Analytics]/Knowledge_Bundles/
• ChatGPT/[Analytics]/Knowledge/
• ChatGPT/[Analytics]/Templates/
• relevant upload or manifest files, only if required

Non-goals

• No new Finance / FP&A project layer.
• No core routing rewrite.
• No broad rewrite of PROJECT_INSTRUCTIONS.md.
• Do not promote candidate packs without pilot evidence and explicit acceptance.
• No production automation.
• No new retrieval/vector/search/web UI layer.
• No private examples in public repo files.
• No production-readiness claim.
• No auto-merge.

Acceptance criteria

• Minimal templates/checklists are added in the correct existing location.
• Templates reference data contract, grain, period, filters, method, QA, limitations, and acceptance.
• Candidate packs remain candidate unless evidence supports promotion.
• Upload/manifest references are updated only if repo conventions require it.
• Checks pass or blockers are documented.

Checks to run

python3 scripts/check_project_instructions_length.py
python3 scripts/check_repo_public_safety.py
python3 scripts/check_codex_goal_mode_defaults.py
python3 scripts/check_manifest_paths.py
python3 scripts/check_knowledge_bundles.py

Stop conditions

Stop and report blockers if there is no clear destination folder, if implementation requires a routing rewrite, if candidate packs would need promotion without evidence, or if checks cannot be run.

Rollback

If the PR is rejected or checks fail without a safe fix, revert only the added template files and related manifest/upload references.

Expected PR summary

• Added minimal Finance / FP&A analytics templates/checklists.
• No routing changes.
• No new project layer.
• Candidate packs not promoted.
• Checks run and results listed.
• Residual risks and rollback note included.
• No auto-merge.