# Development Log: Project Claim Policy Enforcement

## Purpose
Make the main answer obey Second Brain Trace evidence limits, especially when selected notes are General Knowledge or mixed with weak project evidence.

## User Feedback
Trace classification improved, but the main answer could still say phrases like "the architecture is flexible" or "the technical foundation is stable" without enough project evidence.

## Implementation Summary
- Added `projectClaimPolicy` to Second Brain Trace:
  - `allow`
  - `cautious`
  - `general-only`
- Added `projectClaimPolicyReason`.
- Changed policy derivation so broad project claims are allowed only when all selected notes can support project claims and grounding is high.
- Added strict guidance for `general-only`.
- Added caution guidance for mixed evidence.
- Added required wording for unsupported technical structure claims:
  - "현재 정보만으로는 기술 구조를 판단할 수 없습니다."
- Added tests for General Knowledge-only and mixed-evidence cases.

## Changed Files
- `src/features/secondBrainTrace.ts`
- `src/utils.ts`
- `src/features/projectChronicle/guardPrompt.ts`
- `tests/secondBrainTrace.test.ts`
- `tests/projectChronicleGuardPrompt.test.ts`

## Verification
- `./node_modules/.bin/tsc --noEmit`
- `npm run compile`
- `./node_modules/.bin/jest --runInBand`

## Result
Trace warnings now feed a clearer policy into the answer context, making it harder for the model to turn general architecture notes into unsupported project facts.
