Reduce Analytics Project Instructions below safe length threshold

[sergstack]

Summary

Audit found [Analytics] Project Instructions are near the character limit, reportedly around 7936 characters. This creates high risk that the next meaningful edit will fail length checks or force rushed edits.

Goal

Reduce ChatGPT/[Analytics]/PROJECT_INSTRUCTIONS.md below a safer threshold while preserving current Analytics behavior.

Target: keep the instruction below about 7200 characters if feasible, without weakening output modes, stop conditions, deterministic calculation rules, QA requirements, or evidence discipline.

Context

Audit notes:

• [Analytics] is the most production-oriented project instruction.
• Output modes are useful and should be preserved: quick / standard / full / autoloop.
• Stop conditions are concrete and should remain clear.
• Some checklist / registry material may overlap and could be moved or referenced from Knowledge instead of repeated in Project Instructions.
• Terms such as INOUT, Definition Card, and risk_basis may depend on Knowledge context; verify they are defined in uploaded bundles or keep enough explanation in the instruction.

Scope

Allowed files:

• ChatGPT/[Analytics]/PROJECT_INSTRUCTIONS.md
• ChatGPT/[Analytics]/Knowledge_Bundles/*.md only if moving or referencing material requires bundle sync
• relevant Analytics Knowledge files only if a concise section must be moved from instructions into Knowledge
• upload lists / manifests only if bundle references change

Avoid editing other project folders.

Required work

1. Measure current Analytics instruction length.
2. Identify duplicated or overly detailed sections that can be compressed.
3. Preserve the core Analytics behavior:
   • deterministic calculations before narrative;
   • no LLM arithmetic;
   • data contract / grain / period / currency clarity;
   • QA status and confidence;
   • stop conditions;
   • output modes;
   • autoloop remains supervised only.
4. If moving detail from instructions to Knowledge, ensure the Knowledge bundle remains consistent.
5. Keep terms that are required for safe execution either defined in instructions or clearly referenced in bundled Knowledge.
6. Keep the final instruction readable and operational, not just shorter.

Do not change

• Do not weaken Analytics stop conditions.
• Do not remove deterministic calculation requirements.
• Do not allow LLM arithmetic.
• Do not change project routing boundaries.
• Do not introduce production automation.
• Do not add new autonomous agent behavior.
• Do not broaden scope into Analytics methodology redesign.

Checks to run

Run standard repository checks:

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

Run targeted search:

rg -n "quick|standard|full|autoloop|stop|INOUT|Definition Card|risk_basis|deterministic|LLM arithmetic|QA|confidence|grain|period|currency" "ChatGPT/[Analytics]"

Acceptance criteria

• Analytics Project Instructions are below the safe target if feasible, ideally under about 7200 characters.
• Output modes remain clear.
• Stop conditions remain clear and not weaker.
• Deterministic calculation requirements remain clear.
• No LLM arithmetic remains explicit.
• Required terms are either defined or clearly supported by bundled Knowledge.
• Knowledge bundles and source files remain consistent if touched.
• Standard checks pass, or blockers are reported honestly.
• PR opened for human review if files change.
• No auto-merge.

Suggested branch

codex/reduce-analytics-instruction-length

Expected PR summary

• Reduced Analytics Project Instructions below safer length threshold.
• Preserved output modes, stop conditions, deterministic calculation rules, and QA requirements.
• Synced Knowledge bundles if any content moved or referenced.
• Ran standard repo checks.

Human review

Required before merge.

[sergstack]

Re-verified against current repo state while processing the issue queue.

Evidence:

• wc -m ChatGPT/[Analytics]/PROJECT_INSTRUCTIONS.md => 7188, which is below the requested safe target of about 7200 chars.
• python3 scripts/check_project_instructions_length.py passes for all six Project Instructions.
• python3 scripts/check_knowledge_bundles.py passes.
• python3 scripts/check_codex_goal_mode_defaults.py passes.
• Targeted search confirms the Analytics instruction/bundled corpus still covers quick / standard / full / autoloop, stop conditions, deterministic calculation, QA, confidence, grain, period, currency, risk_basis, INOUT, and Definition Card.

Conclusion: this issue appears already fixed by prior repo changes. I did not open an empty PR. Recommended action: close #88 as already resolved, unless Sergey wants a stricter new target below 7188 chars.

[sergstack]

Closing as already resolved by current repo state. Prior evidence shows Analytics Project Instructions are below the safe target, relevant checks pass, and the required Analytics behavior remains covered.