[Codex] Check #127/#128 scope dependency and safe PR sequence

[sergstack]

Goal

Perform a short dependency/scope check for issues #127 and #128 before implementation. Determine overlap, prerequisites, destination folders, required checks, and the safest PR sequence.

Context

Recent AI-OS roadmap review recommended strengthening the system through practical candidate packs plus pilot/acceptance, not by adding new autonomous agents or a new architecture.

Relevant issues:

• [Codex] Add Analytics Finance Core templates #127 — Add Analytics Finance Core templates
• [Codex] Add candidate AP/P2P Audit Pack templates to Analytics #128 — Add candidate AP/P2P Audit Pack templates to Analytics

Both are intended to support [Analytics] without creating a duplicate finance/audit project layer.

Task

Inspect #127, #128, and existing [Analytics] repo conventions. Return a concise implementation recommendation before editing files.

Determine:

1. Whether [Codex] Add Analytics Finance Core templates #127 is a prerequisite for [Codex] Add candidate AP/P2P Audit Pack templates to Analytics #128.
2. Whether [Codex] Add Analytics Finance Core templates #127 and [Codex] Add candidate AP/P2P Audit Pack templates to Analytics #128 overlap or duplicate scope.
3. Whether [Codex] Add candidate AP/P2P Audit Pack templates to Analytics #128 should remain a separate issue, become a follow-up comment/subtask under [Codex] Add Analytics Finance Core templates #127, or be closed/marked duplicate.
4. Which destination folder convention should be used for templates/checklists.
5. Which files should be changed in the first minimal PR.
6. Which checks must run.
7. Whether any manifest/upload references need updates.
8. Whether ChatGPT Project Knowledge sync is required after repo changes.

Constraints

• Do not implement [Codex] Add Analytics Finance Core templates #127 or [Codex] Add candidate AP/P2P Audit Pack templates to Analytics #128 in this issue unless the safe sequence requires a tiny documentation-only pointer.
• No broad rewrite.
• No new project folder.
• No new Finance/AP workflow layer.
• No core routing rewrite.
• No changes to PROJECT_INSTRUCTIONS.md unless required and justified.
• No SQL/Python/scripts/pipeline implementation.
• No production automation.
• No autonomous retrieval.
• No vector DB.
• No embeddings.
• No semantic search.
• No web UI.
• No auto-merge.
• No real client/vendor/employee/bank/invoice/payment/tax ID/personal data examples in public repo.

Required output

Codex should report:

Issue dependency:
Scope overlap:
Recommended sequence:
Destination folders:
Files to change in first PR:
Checks to run:
Manifest/upload impact:
ChatGPT Project sync impact:
Risks:
Blocked / stop conditions:
Recommended next issue/PR:

Checks to run if repo files are inspected/changed

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

• [Codex] Add Analytics Finance Core templates #127/[Codex] Add candidate AP/P2P Audit Pack templates to Analytics #128 dependency and overlap are clearly classified.
• Recommended PR sequence is minimal and reversible.
• Candidate status is preserved for new packs.
• No production promotion is implied.
• No blocked promotion items are introduced.
• If no file changes are needed, Codex reports that clearly.
• If file changes are made, checks pass or blockers are documented.
• No auto-merge.

Stop conditions

Stop and report blockers if:

• [Codex] Add Analytics Finance Core templates #127/[Codex] Add candidate AP/P2P Audit Pack templates to Analytics #128 overlap cannot be determined from repo/issue context.
• There is no clear destination folder convention.
• A safe sequence would require routing rewrite or new project structure.
• The work would require production automation or blocked promotion items.
• The work would require private/client/vendor/bank/personal data examples.

Expected PR/issue summary

• Reviewed [Codex] Add Analytics Finance Core templates #127 and [Codex] Add candidate AP/P2P Audit Pack templates to Analytics #128 dependency/scope.
• Recommended safe PR sequence.
• No implementation unless explicitly justified as minimal documentation-only update.
• No routing rewrite.
• No new project layer.
• No production automation.
• Checks listed.
• Residual risks and next step documented.