9148c358d0
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 폴더 제거.
4.3 KiB
4.3 KiB
id, title, category, status, canonical_id, aliases, duplicate_of, source_trust_level, confidence_score, verification_status, tags, raw_sources, last_reinforced, github_commit, tech_stack
| id | title | category | status | canonical_id | aliases | duplicate_of | source_trust_level | confidence_score | verification_status | tags | raw_sources | last_reinforced | github_commit | tech_stack | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| wiki-2026-0508-restorative-justice | Restorative Justice | 10_Wiki/Topics | verified | self |
|
none | A | 0.85 | applied |
|
2026-05-10 | pending |
|
Restorative Justice
매 한 줄
"매 처벌이 아닌 관계 회복으로 갈등을 해결". 매 1970s Howard Zehr 의 정립, 매 New Zealand 1989 Family Group Conference 법제화 가 milestone. 매 2026 software/community governance, AI safety incident response 에도 적용.
매 핵심
매 vs Punitive Justice
- Punitive: "What law was broken? Who did it? What punishment?"
- Restorative: "Who was harmed? What are their needs? Whose obligations are these?"
- Procedural: rule-following 강조. RJ 는 outcome (harm repair) 강조.
매 핵심 가치
- Accountability: 책임 의 active 인정 — passive 처벌 X.
- Healing: victim, offender, community 모두 의 회복.
- Voice: stakeholder 모두 의 발언권.
- Relationship: 관계 회복 우선.
매 응용
- School discipline (US, UK 의 도입).
- Criminal justice diversion programs.
- Workplace conflict (HR mediation).
- Online community moderation (Discord, GitHub).
- AI incident response (post-mortem culture).
💻 패턴
Conference structure
1. Pre-conference: 매 stakeholder 와 facilitator 의 prep.
2. Storytelling: 매 each party 의 narrative.
3. Impact: harm 의 articulation.
4. Need identification: what would help?
5. Agreement: concrete actions.
6. Follow-up: accountability check.
Software incident (post-mortem)
# Post-Mortem: Production Outage 2026-05-09
## Who was affected
- 12,000 users (3hr API down)
- On-call engineer (sleep disruption)
- CS team (200 tickets)
## What happened (no blame)
- Deploy at 03:00 UTC introduced N+1 query
- Monitoring alert delayed 15min
## Repair
- [ ] Refund/credit affected users
- [ ] On-call rotation adjustment
- [ ] CS team additional comp
## Prevention (system, not person)
- [ ] Pre-deploy load test gate
- [ ] Alert threshold tightening
Community moderation (RJ flow)
type Incident = {
reporter: UserId;
accused: UserId;
description: string;
};
async function restorativeFlow(i: Incident) {
await dm(i.reporter, "We hear you. What outcome would help?");
const need = await waitReply(i.reporter);
await dm(i.accused, `A community member shared they were hurt by [...]. Are you open to a conversation?`);
if (await consent(i.accused)) {
await scheduleFacilitatedChat(i.reporter, i.accused, need);
} else {
await escalateToFormal(i);
}
}
Circle process
- 매 participant 의 talking piece 보유시 발언.
- 매 facilitator 의 question prompt 의 sequence.
- 매 silence OK.
- 매 agreement 의 collective.
Apology framework (Lazare)
1. Acknowledgment: "I did X."
2. Explanation (not excuse): "Because Y."
3. Remorse: "I see harm caused."
4. Repair: "I will Z to make it right."
매 결정 기준
| 상황 | Approach |
|---|---|
| First-time, low-harm | RJ conference |
| Repeated, predatory | Punitive + protection |
| Power imbalance severe | RJ X (re-traumatization risk) |
| Anonymous online harm | Hybrid (account action + community education) |
| Workplace senior→junior | RJ + structural change |
기본값: harm-first framing + voluntary participation + structural prevention.
🔗 Graph
🤖 LLM 활용
언제: post-mortem template 작성, mediation script 초안, policy review. 언제 X: live mediation (human empathy 의 irreplaceable).
❌ 안티패턴
- Forced participation: 매 victim 의 secondary harm.
- Surface-only: structural cause 의 외면.
- No follow-up: agreement 후 accountability gap.
- Power blind: senior↔junior 의 same-level treatment.
🧪 검증 / 중복
- Verified (Howard Zehr "Changing Lenses", UN handbook 2020).
- 신뢰도 A.
🕓 Changelog
| 날짜 | 변경 |
|---|---|
| 2026-05-08 | Phase 1 |
| 2026-05-10 | Manual cleanup — RJ + software application |