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 폴더 제거.
5.5 KiB
5.5 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-policy-surveillance | Policy Surveillance | 10_Wiki/Topics | verified | self |
|
none | A | 0.85 | applied |
|
2026-05-10 | pending |
|
Policy Surveillance
매 한 줄
"매 you can't evaluate what you can't measure — start by mapping the law.". 매 Burris (Temple) 가 정립한 Policy Surveillance = 매 systematic, scientific tracking of laws/policies as data 의 개념. 매 2026 AI governance (EU AI Act enforcement, Korea AI Basic Act, US state AI laws) 시대에 매 polyjurisdictional compliance 의 핵심 도구.
매 핵심
매 정의 vs adjacent
- Policy Surveillance: 매 ongoing, systematic, scientific 매 monitoring of policies as 매 quantifiable data.
- vs Legal Research: 매 case-driven, episodic.
- vs Compliance Audit: 매 organization-internal, point-in-time.
- vs Regulatory Tracking: 매 news-driven, qualitative.
매 5단계 method (Burris)
- 매 frame the question — what behavior does the law target?
- 매 define jurisdictional + temporal scope.
- 매 collect primary sources (statutes, regs).
- 매 code into structured variables (binary, ordinal, categorical).
- 매 publish + maintain — 매 LawAtlas-style open data.
매 응용
- AI Act compliance: 매 27 EU 회원국 + 미국 50주의 AI law variation 추적.
- Public health: 매 LawAtlas COVID closure tracking, opioid policies.
- Privacy: 매 GDPR vs CPRA vs PIPL 의 cross-walk.
💻 패턴
Pattern 1: Coding scheme YAML
# 매 ai_law_codes.yaml
variables:
- id: requires_impact_assessment
type: binary
question: "매 Does law require AI impact assessment?"
- id: penalty_max
type: numeric
unit: USD
- id: covered_systems
type: categorical
values: [foundation_models, biometric, hiring, healthcare, all_high_risk]
jurisdictions: [EU, US-CA, US-CO, KR, UK, CN]
effective_dates: required
Pattern 2: Cross-walk matrix
import pandas as pd
def crosswalk(jurisdictions, variables, codes_df):
matrix = codes_df.pivot(index="jurisdiction",
columns="variable",
values="value")
matrix.to_csv("crosswalk.csv")
return matrix
Pattern 3: Diff over time
def policy_diff(snapshot_old, snapshot_new):
changes = []
for jur in snapshot_new.index:
for var in snapshot_new.columns:
if snapshot_old.at[jur, var] != snapshot_new.at[jur, var]:
changes.append({
"jurisdiction": jur, "variable": var,
"from": snapshot_old.at[jur, var],
"to": snapshot_new.at[jur, var],
})
return changes
Pattern 4: LLM-assisted coding (with human verification)
import anthropic
client = anthropic.Anthropic()
def code_statute(statute_text, scheme):
resp = client.messages.create(
model="claude-opus-4-7",
max_tokens=2048,
system=f"Code the statute against this scheme: {scheme}. Return JSON.",
messages=[{"role": "user", "content": statute_text}],
)
# 매 ALWAYS human-verify legal coding
return {"draft": resp.content[0].text, "needs_review": True}
Pattern 5: Effective-date timeline
def timeline_view(codes_df):
return codes_df.sort_values("effective_date")[
["jurisdiction", "variable", "value", "effective_date"]
]
Pattern 6: Citation chain (provenance)
def store_with_provenance(code, value, statute_section, source_url, retrieved_at):
return {
"code": code, "value": value,
"citation": {"section": statute_section, "url": source_url, "retrieved": retrieved_at},
}
매 결정 기준
| 상황 | Approach |
|---|---|
| 매 single-org compliance | Standard compliance audit |
| 매 multi-jurisdiction policy comparison | Policy Surveillance |
| 매 academic causal inference (does law X cause outcome Y?) | Policy Surveillance + econometrics |
| 매 real-time regulatory news | News tracker (NOT surveillance) |
| 매 AI Act multi-state US tracking | Policy Surveillance + LLM-draft + lawyer review |
기본값: 매 LawAtlas-style codebook + git versioning + LLM-draft + human verification.
🔗 Graph
- 응용: AI 거버넌스 정책(AI Usage Policy) · GDPR Compliance
- Adjacent: EU AI Act
🤖 LLM 활용
언제: 매 first-pass coding of large statute corpus, 매 cross-walk drafting, 매 diff summarization. 언제 X: 매 final legal coding without human lawyer — 매 hallucination risk too high for compliance use.
❌ 안티패턴
- No version control: 매 statutes 가 amend 되는데 snapshot 없으면 매 useless for trend analysis.
- Coding without scheme: 매 ad-hoc tags — 매 inter-coder reliability ~0.
- LLM-only coding: 매 hallucinated citations — 매 catastrophic for legal use.
- Single jurisdiction silo: 매 policy surveillance 의 가치 = comparison.
🧪 검증 / 중복
- Verified (Burris et al., Temple Center for Public Health Law Research; LawAtlas.org).
- 신뢰도 A (academic + practitioner standard).
🕓 Changelog
| 날짜 | 변경 |
|---|---|
| 2026-05-08 | Phase 1 |
| 2026-05-10 | Manual cleanup — Burris method, AI Act 응용, LLM augmentation |