2nd/10_Wiki/Topics/2026-05-02_project-chronicle-guard_feedback-response.md

id, category, confidence_score, tags, last_reinforced

id	category	confidence_score	tags	last_reinforced
P-REINFORCE-WIKI-5B04311B	Unified	0.95	architecture-principles	2026-05-02

Development Log: Project Chronicle Guard Feedback Response

Purpose

Improve Chronicle Guard behavior after testing showed the assistant still answered like a general idea proposer instead of a project planning and record guard.

Feedback Summary

The tested response understood the broad idea, but missed key guard behaviors:

• Project target check
• Record path check
• Question intent and question reasons
• Pending decision candidates
• Low-dependency MVP first
• Candidate records at the end
• Plain engineering tone

Implementation Summary

• Made Chronicle Guard context apply by default unless explicitly disabled from the webview payload.
• Strengthened the Guard response contract for new ideas and feature requests.
• Added required response order: summary, intent, project check, record path check, blocking questions, question reasons, direction review, MVP, later expansion, candidate records.
• Added decision policy so unconfirmed decisions stay pending.
• Added tone rules against inflated consulting language and premature Vector DB / relational DB / knowledge graph suggestions.
• Extracted Guard prompt generation into buildProjectChronicleGuardContext.
• Added tests that lock the most important Guard rules.
• Added base system prompt guidance to prefer practical MVP-first answers for product and architecture discussions.

Changed Files

• src/features/projectChronicle/guardPrompt.ts
• src/features/projectChronicle/index.ts
• src/sidebarProvider.ts
• src/utils.ts
• tests/projectChronicleGuardPrompt.test.ts

Verification

• ./node_modules/.bin/tsc --noEmit
• npm run compile
• ./node_modules/.bin/jest --runInBand

Result

Chronicle Guard should now behave less like a general ideation assistant and more like a project planning, decision, and record guard.