---
phase: 71-analytical-review-artifacts-and-runtime-surfaces
plan: 01
type: execute
wave: 1
depends_on:
  - 70-analytical-validation-mode-baseline
files_modified:
  - research/knowledge-hub/knowledge_hub/analytical_review_support.py
  - research/knowledge-hub/knowledge_hub/cli_review_handler.py
  - research/knowledge-hub/knowledge_hub/validation_review_service.py
  - research/knowledge-hub/knowledge_hub/aitp_service.py
  - research/knowledge-hub/knowledge_hub/aitp_cli.py
  - research/knowledge-hub/tests/test_aitp_service.py
  - research/knowledge-hub/tests/test_aitp_cli.py
  - research/knowledge-hub/tests/test_aitp_cli_e2e.py
autonomous: true
requirements:
  - REQ-ANV-03
must_haves:
  truths:
    - analytical validation must leave a durable artifact naming exact checks and outcomes
    - runtime read surfaces must expose analytical review artifacts through production code
    - service and CLI hotspot budgets must remain green after the phase lands
---

<objective>
Add durable analytical review artifacts and route them into the active runtime
review surfaces.
</objective>

<execution_context>
@D:/BaiduSyncdisk/Theoretical-Physics/.codex-home/get-shit-done/workflows/execute-plan.md
@D:/BaiduSyncdisk/Theoretical-Physics/.codex-home/get-shit-done/templates/summary.md
</execution_context>

<context>
@.planning/phases/71-analytical-review-artifacts-and-runtime-surfaces/71-CONTEXT.md
@.planning/REQUIREMENTS.md
@research/knowledge-hub/knowledge_hub/validation_review_service.py
@research/knowledge-hub/knowledge_hub/formal_theory_audit_support.py
</context>

<tasks>

<task type="auto">
  <name>Task 1: Add failing tests for analytical review durability and runtime surfaces</name>
  <files>research/knowledge-hub/tests/test_aitp_cli.py, research/knowledge-hub/tests/test_aitp_service.py, research/knowledge-hub/tests/test_aitp_cli_e2e.py</files>
  <read_first>research/knowledge-hub/tests/test_aitp_service.py, research/knowledge-hub/knowledge_hub/validation_review_service.py</read_first>
  <action>Add red tests that require a new analytical review artifact family, CLI entrypoint, and runtime bundle integration.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_aitp_cli.py research/knowledge-hub/tests/test_aitp_service.py -q</verify>
  <acceptance_criteria>
    - tests fail before implementation
    - failures prove that analytical review is missing as a production artifact family
  </acceptance_criteria>
  <done>A red contract exists for Phase `71`.</done>
</task>

<task type="auto">
  <name>Task 2: Implement analytical review support through production entrypoints</name>
  <files>research/knowledge-hub/knowledge_hub/analytical_review_support.py, research/knowledge-hub/knowledge_hub/cli_review_handler.py, research/knowledge-hub/knowledge_hub/validation_review_service.py, research/knowledge-hub/knowledge_hub/aitp_service.py, research/knowledge-hub/knowledge_hub/aitp_cli.py</files>
  <read_first>research/knowledge-hub/knowledge_hub/formal_theory_audit_support.py, research/knowledge-hub/knowledge_hub/aitp_service.py</read_first>
  <action>Add analytical review artifact materialization, thin service/CLI routing, and validation review bundle integration.</action>
  <verify>python -m pytest research/knowledge-hub/tests/test_aitp_cli.py research/knowledge-hub/tests/test_aitp_service.py research/knowledge-hub/tests/test_aitp_cli_e2e.py -q</verify>
  <acceptance_criteria>
    - `analytical-review` is accepted through the public CLI
    - `AITPService.audit_analytical_review(...)` writes a durable `analytical_review.json`
    - analytical validation mode promotes `analytical_review` into the primary runtime review bundle when present
  </acceptance_criteria>
  <done>Analytical review becomes a durable production artifact family.</done>
</task>

<task type="auto">
  <name>Task 3: Re-run review-surface regressions, budget checks, and the full suite</name>
  <files>research/knowledge-hub/tests/test_aitp_cli.py, research/knowledge-hub/tests/test_aitp_service.py, research/knowledge-hub/tests/test_aitp_cli_e2e.py, research/knowledge-hub/tests/test_runtime_profiles_and_projections.py, research/knowledge-hub/tests/test_maintainability_budgets.py</files>
  <read_first>.planning/REQUIREMENTS.md</read_first>
  <action>Re-run the review-artifact slice, maintainability watch budget, and the full knowledge-hub suite before advancing to research-judgment work.</action>
  <verify>python -m pytest research/knowledge-hub/tests -q</verify>
  <acceptance_criteria>
    - review-artifact slice exits 0
    - maintainability budgets stay green
    - no full-suite regression is introduced
  </acceptance_criteria>
  <done>Phase `71` lands on a stable verified baseline.</done>
</task>

</tasks>
