운영 하네스 문서화

prompts/analysis_prompt.md

@@ -13,6 +13,17 @@ Use this prompt when producing an investment analysis or HTS-ready playbook.
 - HTS 즉시 입력 가능 여부는 제안과 분리해 별도 표로 표시한다.
 - 실행 차단이라도 사용자 판단용 `proposal_reference_sheet`는 숨기지 않는다.
 
+## DEFAULT COMPLETION HARNESS
+
+이 프롬프트로 수행하는 모든 작업은 아래 4가지를 모두 충족해야 완료로 본다.
+
+1. `YAML` 증빙: 관련 spec/governance/contract 파일이 실제로 갱신되었거나, 변경이 필요 없다는 근거가 명시되어야 한다.
+2. `코드` 증빙: `src/` 또는 `tools/`의 canonical 코드 변경이 있거나, 변경이 없다는 근거가 명시되어야 한다.
+3. `데이터 실체` 증빙: `Temp/`, `GatherTradingData.xlsx`, `GatherTradingData.json`, `runtime/` 등 실제 데이터 또는 산출물이 갱신되었거나, 변경이 없다는 근거가 명시되어야 한다.
+4. `검증 증빙`: 재현 가능한 검증 명령과 결과가 제시되어야 한다.
+
+하나라도 빠지면 완료로 간주하지 않는다. 요약이나 해설만으로는 완료 판정할 수 없다.
+
 ## CRITICAL — QUANTITATIVE_EXPERT_HARNESS (QEH) — 전문사 정밀도 강제
 
 `data._harness_context`가 JSON에 존재하면 아래 규칙을 **절대적으로** 따른다.

prompts/capture_parse_prompt.md

@@ -3,6 +3,16 @@
 HTS 캡처 이미지가 제공되면 이 프롬프트를 **분석보다 먼저** 실행한다.
 출력 순서: ① 화면판별 → ② 검증 → ③ 충돌감지·캡처우선 선언 → ④ TSV붙여넣기 → ⑤ account_snapshot 상태갱신 → ⑥ 현금요약 → ⑦ 인라인재산출 → ⑧ 다음단계
 
+## 기본 완료 조건
+
+작업 완료는 다음 4개가 함께 있어야 한다.
+- `YAML` 증빙
+- `코드` 증빙
+- `데이터 실체` 증빙
+- `검증 증빙`
+
+하나라도 빠지면 완료로 보지 않는다.
+
 ---
 
 ## STEP 1 — 화면 종류 판별

prompts/engine_audit_master_prompt_v2.md

@@ -7,6 +7,10 @@ You are the investment audit renderer for the retirement-asset portfolio engine.
 - Do not calculate prices, quantities, cash shortfall, or gates.
 - If data is missing, write `DATA_MISSING` and stop at the safest available ledger output.
 
+## Default Completion Harness
+- Complete only when `YAML`, `code`, `data artifact`, and `validation evidence` all exist together.
+- If any one of the four is missing, the task is incomplete.
+
 ## Authority Rules
 - `global_execution_gate` is the top-level decision.
 - If the gate is `AUDIT_ONLY`, render Shadow Ledger only.

prompts/engine_audit_master_prompt_v3.md

@@ -7,6 +7,10 @@ You are the investment audit renderer for the retirement-asset portfolio engine.
 - Do not calculate prices, quantities, cash shortfall, gates, or scores.
 - If data is missing, write `DATA_MISSING — 하네스 업데이트 필요` and stop at the safest available ledger output.
 
+## Default Completion Harness
+- A task is complete only when `YAML`, `code`, `data artifact`, and `validation evidence` are all present.
+- Missing any one of the four means the task remains incomplete.
+
 ## Authority Order
 1. `Temp/final_decision_packet_active.json`
 2. `GatherTradingData.json:data._harness_context`

prompts/engine_audit_prompt.md

@@ -6,4 +6,4 @@ Audit only.
 - Do not invent missing numeric values.
 - Flag stale or deprecated inputs as invalid.
 - Separate live, replay, and informational outputs.
-
+- A task is not complete unless YAML, code, data artifact, and validation evidence all exist together.

prompts/low_capability_report_renderer.md

@@ -3,6 +3,10 @@
 You are a copy-only report renderer. Do not perform any calculations or estimate any numbers.
 Read the data only from `Temp/final_context_for_llm_v5.yaml` (or active manifests).
 
+## Default Completion Harness
+- Complete only when `YAML`, `code`, `data artifact`, and `validation evidence` are all present.
+- Do not mark a task complete if any one of the four is missing.
+
 ## Execution Protocol
 1. Check `global_execution_gate`. If it is not `PASS`, output a block alert.
 2. Under no circumstances should you generate arbitrary prices, quantities, stop losses, or take profits.

prompts/report_renderer_prompt.md

@@ -6,4 +6,4 @@ Render only.
 - Do not compute prices, quantities, thresholds, or scores.
 - If a value is missing, render `DATA_MISSING`.
 - Do not reconcile conflicting sources.
-
+- A task is complete only when YAML, code, data artifact, and validation evidence are all available together.

prompts/review_prompt.md

@@ -16,6 +16,17 @@ Review priority:
    `alpha_lead_table`, `anti_distribution_table`, `profit_preservation_table`, `smart_cash_raise_table`, `execution_quality_table`.
 10. Verify `routing_serving_trace` appears before `QEH_AUDIT_BLOCK`, and both appear before `concise_hts_input_sheet`.
 
+## Default Completion Harness
+
+Do not treat a task as complete unless the change is evidenced in all four forms:
+
+1. YAML or contract evidence in `spec/` or `governance/`
+2. Canonical code evidence in `src/` or `tools/`
+3. Concrete data/artifact evidence in `Temp/`, `GatherTradingData.xlsx`, `GatherTradingData.json`, or `runtime/`
+4. Reproducible validation evidence from command output or generated validation artifacts
+
+If any one of the four is missing, call out the task as incomplete.
+
 Return findings first, ordered by severity.
 If no findings exist, state that explicitly and list residual risks or missing tests.
 

prompts/weekly_operational_report_master_prompt_v1.md

@@ -8,6 +8,10 @@ Strictly adhere to the following rules:
 3. If `interim_check_required` is true, you must render the `engine_health_card` section.
 4. Keep the reporting format standardized.
 
+## Default Completion Harness
+- The report task is complete only when `YAML`, `code`, `data artifact`, and `validation evidence` are all present.
+- Missing any one of the four means the task remains incomplete.
+
 ## Layout Order
 1. engine_health_card
 2. global_gate_and_cash_defense