feat: org_setup에 팀(channel) 레이어 등록 지원 추가#236
Open
thrcle wants to merge 2 commits into
Open
Conversation
- SemanticFederationTool(/term_custom): 채널(팀)/전사/개인 3계층 용어 등록·조회·삭제 - OrgSetupTool(/org_setup): DB 스캔 + LLM으로 팀별 용어 자동 추출 → 전사(guild) 레이어 저장 - Discord UI: /term_custom 호출 시 범위 selectbox → 용어 입력 modal (2단계 UX) - 채널이 팀 경계 역할 → 팀 멤버십 관리 불필요, 충돌 설계상 없음 - lookup: 개인 > 채널(팀) > 전사(guild) (narrow→wide, git branch 방식) - kv_list_prefix() 추가 + LIKE 와일드카드 이스케이프 보안 수정 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
- /org_setup에 team 파라미터 추가 — team 지정 시 LLM 추출 용어를 channel 레이어에 저장 - org만 지정 시 기존과 동일하게 guild 레이어에 저장 - clear도 레이어 단위로 정확히 삭제되도록 수정 - 데이터셋/로그 파일 .gitignore에 추가 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/org_setup커맨드에team파라미터 추가 — 전사(guild) 외 채널(팀) 단위로 비즈니스 용어 등록 가능team지정 시 channel layer, 미지정 시 guild layer에 KV 저장term_custom의 narrow→wide lookup(member > channel > guild)과 동일한 scope chain 사용Depends on
#235 (feat/semantic-federation) — 해당 PR과 함께 순서대로 머지 요청
Test plan
/org_setup term:활성고객 definition:... team:마케팅→ channel layer 저장 확인/org_setup term:활성고객 definition:...(team 없음) → guild layer 저장 확인/term_custom list로 lookup 우선순위 확인