Files
2nd/10_Wiki/Topic_Business/Project_Logs/2026-05-02_project-chronicle-guard_feedback-response.md
T
Antigravity Agent 9148c358d0 docs(10_Wiki): 위키 전체 재구성 — Topic_* 폴더를 4개 카테고리로 통합 + 대규모 중복 제거
Topic_Agent/Topic_Blog/Topics/Topics_Biz/Topics_Meeting/Topics_Rag의 마크다운 지식 문서를
Topic_General/Topic_Programming/Topic_Graphic/Topic_Business 4개 카테고리로 재분류.

- 중복 제거: frontmatter의 status:duplicate/merged + duplicate_of/redirect_to 필드로
  자기 자신을 중복으로 선언한 리다이렉트 stub 1032개 제거, 완전 동일 내용 파일 472개 제거,
  동일 파일명·다른 내용 충돌 시 더 큰(완전한) 버전만 유지(162개 제거) — 총 1639개 중복 제거.
- 분류: 폴더 단위로 명확한 항목(AI_and_ML/Coding/Architecture 등 → Programming,
  Comfyui/Visual_Effects → Graphic, Topics_Biz/Topics_Meeting/사업 등 → Business,
  Poetic_Blog_Writing/창의성/Game_Design 등 → General)은 폴더 우선순위로,
  나머지 혼재 폴더(Topic_Agent/Topic_Blog/Topics 루트/Thinking & Reasoning/Other/UI_UX_Assets)는
  title/tags 키워드 스코어링으로 파일 단위 분류(불명확한 경우 General로 폴백).
  원본 폴더명은 "From_*" 서브폴더로 보존해 추적 가능성 유지.
- 최종 배치: Programming 2784 / General 1608 / Graphic 285 / Business 249 = 4926개 문서.
- 에이전트 운영 상태(.astra/.agent/.obsidian/sessions/memory/_company/docs/lessons/_shared/src)는
  지식 콘텐츠가 아니므로 재분류 대상에서 제외하고 원위치 유지.
- Topics/Topic_email(상위 보호 폴더 Topic_email과 파일명 100% 중복) 삭제 — 보호 폴더 자체는 미변경.
- 완전히 비게 된 Topic_Agent/Topic_Blog/Topics_Biz/Topics_Rag 폴더 제거.
2026-07-05 00:33:48 +09:00

2.1 KiB

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.

🔗 Knowledge Connections