Files
2nd/10_Wiki/Topics/AI_and_ML/ADR-0001-project-chronicle-independent-module.md
T

94 lines
2.8 KiB
Markdown

---
id: wiki-2026-0508-adr-0001-project-chronicle-indep
title: ADR 0001 project chronicle independent module
category: 10_Wiki/Topics
status: needs_review
canonical_id: self
aliases: [P-REINFORCE-WIKI-714E4EE2]
duplicate_of: none
source_trust_level: A
confidence_score: 0.95
tags: [process-methodology]
raw_sources: []
last_reinforced: 2026-05-02
github_commit: pending
inferred_by: Claude Opus 4.7 (auto-normalize 2026-05-08)
---
# ADR-0001: Implement Project Chronicle Guard As An Independent Module
## Status
Accepted
## Context
The requested feature records project planning, questions, decisions, development logs, bugs, and retrospectives. Existing chat and agent systems already manage model interaction and agent skills.
## Decision
Implement Project Chronicle Guard as a separate module under `src/features/projectChronicle`.
## Reason
- It reduces the chance of regressions in chat and agent execution.
- It keeps the MVP focused on local Markdown generation.
- It can later receive events from chat or agents without owning those flows.
- It makes project-specific record storage easier to test and evolve.
## Alternatives
- Integrate into the existing Second Brain flow.
- Extend Agent Skill files to double as project records.
- Add a standalone Project Chronicle module.
## Selected Alternative
Add a standalone Project Chronicle module.
## Consequences
The first stage needs explicit sidebar actions to create and write records. Automatic extraction can be layered on later.
## 🔗 지식 연결 (Graph)
### Related Concepts (Auto-Linked)
* [[Events]]
* [[P-Reinforce]]
* [[Storage]]
* [[decisions]]
## 📌 한 줄 통찰 (The Karpathy Summary)
> *(TODO: 한 문장으로 핵심 통찰을 작성. "X는 Y 조건에서 Z 효과를 낸다" 구조 권장.)*
## 📖 구조화된 지식 (Synthesized Content)
**추출된 패턴:**
> *(TODO)*
**세부 내용:**
- *(TODO)*
## 🤖 LLM 활용 힌트 (How to Use This Knowledge)
**언제 이 지식을 쓰는가:**
- *(TODO)*
**언제 쓰면 안 되는가:**
- *(TODO)*
## 🧪 검증 상태 (Validation)
- **정보 상태:** needs_review
- **출처 신뢰도:** A
- **검토 이유:** *(P-Reinforce Phase 1 자동 정규화. 본문 검증 필요.)*
## 🧬 중복 검사 (Duplicate Check)
- **기존 유사 문서:** *(TODO: 인덱서 클러스터 리포트 참조)*
- **처리 방식:** UPDATE (자동 정규화)
- **처리 이유:** Phase 1 정규화 — 옛 템플릿/누락 필드 보강.
## ⚠️ 모순 및 업데이트 (Contradictions & Updates)
- **과거 데이터와의 충돌:** 없음
- **정책 변화:** 없음
## 🕓 변경 이력 (Changelog)
| 날짜 | 변경 내용 | 처리 방식 | 신뢰도 |
|------|-----------|-----------|--------|
| 2026-05-08 | P-Reinforce Phase 1 정규화 (frontmatter + 헤더 표준화) | UPDATE | A |