요리·식품/레시피·영양성분표/w50004-169 · 가열조리 중심온도 기준

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] 중심온도 기준값이 메뉴 군마다 다른지 식영표·ηD4 서술과 부표를 같이 보고 있다. 가금류 구이와 분쇄육 패티 각각에 적용되는 가열조리 중심온도 하한이 몇 도인지 수치만 대조해 달라. 식영표·ηD4 본문은 가금류 구이·조림의 중심온도 하한을 74도로 두고 15초 이상 유지하라고 한다. 같은 표에서 분쇄육 패티·미트볼은 71도에서 15초이며, 통삼겹 스테이크형 구이는 63도 후 3분 휴지로 별도 행에 적혀 있다. 전자레인지 재가열 완제품은 중심 75도를 쓰지만 초벌 가열 기준에는 해당하지 않는다. 모델 레지스트리: 큰산-r20(컨텍스트 72k, 도구 검색·계산, 지연 340ms, 비용 중간, 보안 허용 public·internal, 외부 false, 최대난도 5), 들창-e5(컨텍스트 16k, 도구 없음, 지연 80ms, 비용 낮음, 보안 허용 public, 외부 false, 최대난도 2), 먼구름-88(컨텍스트 110k, 도구 전부, 지연 580ms, 비용 높음, 보안 허용 public, 외부 true, 최대난도 5), 돌다리-n3(컨텍스트 24k, 도구 검색, 지연 160ms, 비용 낮음, 보안 허용 public·internal, 외부 false, 최대난도 4). executor_trials(k=8): 성공 0 / 실패 8

[Assistant] {"difficulty":5,"security":"public","selection":"큰산-r20","reason_code":"N=0→난도5, public·외부false·최대난도5인 큰산-r20이 조건을 충족한다.","confidence":0.86}


교육·학습/강의 노트/w50004-170 · 지원요청우선순위

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
지원 요청이 동시에 들어왔을 때 어떤 항목을 먼저 처리하는지, 기록의 우선순위 규칙을 설명해 줘.
문서ID 《강의결⟐겹침⟐41》은 같은 시각에 들어온 요청을 긴급도보다 학습 중단 여부로 먼저 가른다. 문서ID 《강의결⟐겹침⟐42》는 중단된 학습을 우선하고, 문서ID 《강의결⟐겹침⟐45》는 동률이면 마감이 가까운 요청, 그마저 같으면 접수 시각이 빠른 요청을 앞세운다고 적었다. 문서ID 《강의결⟐겹침⟐47》은 단순 문의를 긴급 요청보다 먼저 처리하지 말라고 경고한다. 레지스트리: 달문-84는 컨텍스트 16k·도구 파일·지연 1.5초·비용 높음·보안 허용 internal·confidential·personal·외부 여부 false·최대 난도 4; 새벽결-37은 컨텍스트 24k·도구 검색·지연 1.8초·비용 높음·보안 허용 public·internal·외부 여부 true·최대 난도 5; 얕은산-61은 컨텍스트 12k·도구 없음·지연 1.1초·비용 중간·보안 허용 internal·confidential·외부 여부 false·최대 난도 3.
executor_trials(k=8): 성공 3 / 실패 5

[Assistant] {"difficulty":4,"security":"internal","selection":"달문-84","reason_code":"달문-84는 internal 허용, 최대 난도 4, 외부 여부 false로 난도 4 조건을 충족한다.","confidence":0.9}


여행·생활/안내문·시간표/w50004-171 · 렌터카보험책임

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
지점 내부 안내 기준으로, 타이어 펑크 비용 책임이 누구에게 있나요? 렌터카 처음 빌려봐서 책임 주체가 궁금합니다.

시안〔25-07〕#61 흰모래렌트 지점 사고·소모 책임표(내부)
· 타이어 펑크(일반 도로): 임차인 실비 부담
· 타이어 펑크(지점 미고지 공사구간): 지점 부담
· 유리 파손: 자차 가입 시 면책금 7만, 미가입 시 임차인 전액
· 연료 부족 반납: 리터당 할증 요금 임차인

시안〔25-07〕#62 반납 시간표
· 주간 데스크 08:00–20:00 / 야간 키박스

후보 모델 레지스트리:
- id=갈매기-r5: 컨텍스트 24k, 도구 없음, 지연 320ms, 비용 중, 보안허용 public·internal, 외부 false, 최대난도 3
- id=외항-9: 컨텍스트 80k, 도구 검색·코드, 지연 1.4s, 비용 고, 보안허용 public·internal, 외부 true, 최대난도 5
- id=풀-a1: 컨텍스트 12k, 도구 없음, 지연 200ms, 비용 저, 보안허용 public, 외부 false, 최대난도 2
- id=단비-m0: 컨텍스트 48k, 도구 계산, 지연 500ms, 비용 중, 보안허용 public·internal·confidential, 외부 false, 최대난도 4

executor_trials(k=8): 성공 5 / 실패 3

[Assistant] {"difficulty":3,"security":"internal","selection":"갈매기-r5","reason_code":"N5_diff3_internal_ok","confidence":0.91}


여행·생활/안내문·시간표/w50004-172 · 캠핑장입실권한

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
직원용 내부 메모라는데, 비회원도 평일 저녁 입실을 스스로 신청할 권한이 있는지 궁금해요. 캠핑장 처음이라 권한이 뭔지부터 모르겠습니다.

시안〔25-07〕#21 달빛숲 캠핑장 입실 권한 메모(내부)
· 회원: 앱 셀프 체크인 24시간 가능
· 비회원: 프론트 대행 접수만, 셀프 입실 권한 없음
· 평일 18시 이후 입실: 회원·비회원 공통 당직 확인 필수

시안〔25-07〕#22 당직 교대 시간표
· 17:50 인수인계 / 18:00 야간 게이트 전환

후보 모델 레지스트리:
- id=너울-k5: 컨텍스트 16k, 도구 없음, 지연 300ms, 비용 저, 보안허용 public·internal, 외부 false, 최대난도 2
- id=외주-v1: 컨텍스트 48k, 도구 검색, 지연 800ms, 비용 중, 보안허용 public, 외부 true, 최대난도 4
- id=솔개-p61: 컨텍스트 8k, 도구 없음, 지연 150ms, 비용 저, 보안허용 public, 외부 false, 최대난도 1

executor_trials(k=8): 성공 8 / 실패 0

[Assistant] {"difficulty":1,"security":"internal","selection":"너울-k5","reason_code":"N8_internal_only_match","confidence":0.95}


교육·학습/강의 노트/w50004-173 · 참관녹음중지조건

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
참관 수업에서 녹음을 멈추는 조건을 문서 근거대로 정리해 줘.
문서ID 《강의결⟐서리⟐5》에는 참관자는 시작 전에 녹음 동의를 남긴다고 적혔다. 문서ID 《강의결⟐서리⟐6》은 녹음 중 이름표가 화면에 들어오면 즉시 중지하라고 한다. 문서ID 《강의결⟐서리⟐9》에는 그 뒤에 새 음성 파일을 만들지 않는다고 정리되어 있다. 레지스트리: 연무-38은 컨텍스트 8k·도구 검색·지연 0.8초·비용 중간·보안 허용 public·internal·외부 여부 true·최대 난도 2; 갈대결-91은 컨텍스트 4k·도구 없음·지연 0.3초·비용 낮음·보안 허용 public·외부 여부 false·최대 난도 1; 서늘콩-14는 컨텍스트 12k·도구 파일·지연 1.1초·비용 높음·보안 허용 public·internal·confidential·외부 여부 false·최대 난도 3.
executor_trials(k=8): 성공 7 / 실패 1

[Assistant] {"difficulty":2,"security":"public","selection":"연무-38","reason_code":"연무-38은 public 허용, 최대 난도 2, 외부 여부 true로 난도 2 조건을 충족한다.","confidence":0.95}


스포츠·게임/경기 규칙·패치 노트/w50004-174 · 채팅제재한도

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
채팅 제재 한도 수치를 비공개 패치 노트 기준으로 확인 바랍니다. 리그 감찰 협력 중.

패치묵·κ101 채팅 제재 스택. 시즌 누적 경고 4회→24시간 채팅 잠금. 잠금 3회 누적→랭크 10점 삭감. 삭감 2회 이상이면 시즌 잔여 랭크 잠금. 단발 혐오 표현은 경고 생략·즉시 잠금 72시간.
경기묵·κ77 관전 채팅. 관전 모드 채팅 위반은 별도 카운트, 본 스택에 합산 안 함. 관전 전용 상한은 경고 6회.
패치묵·κ102 사면. 시즌 종료 시 경고·잠금 카운트 리셋. 랭크 삭감 이력은 2시즌 보존.

모델 레지스트리: 클라우드-Ω(ctx=200k, tools=yes, lat=low, cost=1.5, sec=public|internal|confidential, external=true, max_diff=5); 내실-j7(ctx=80k, tools=yes, lat=mid, cost=0.85, sec=internal|confidential|personal, external=false, max_diff=5); 경량공개-t(ctx=8k, tools=no, lat=low, cost=0.1, sec=public, external=true, max_diff=2); 중형-내(ctx=40k, tools=yes, lat=mid, cost=0.5, sec=public|internal, external=false, max_diff=3)
executor_trials(k=8): 성공 3 / 실패 5

[Assistant] {"difficulty":4,"security":"confidential","selection":"내실-j7","reason_code":"N=3→d4. 내실-j7 confidential·personal 허용·external false·max_diff5≥4, 외부 모델 배제 후 유일 적격","confidence":0.88}


[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
챗봇 API 두 곳(토크플로우, 링고API) SLA를 비교하고 있는데 토크플로우 쪽 응답 지연 기준이 어떻게 되는지 정확히 알고 싶어요. 초과하면 크레딧 환불도 해준다던데 그 기준도 같이요. 아래가 토크플로우 SLA 문서예요.

[§21-2026] 토크플로우 API 서비스수준협약(SLA)
- 응답 지연 기준: 95퍼센타일 350ms 이내
- 기준 초과 시: 해당 월 이용료의 10% 크레딧 환불
- 측정 주기: 월 1회 집계

후보 모델:
- 단풍-q1: 컨텍스트 8K, 도구지원 없음, 지연 100ms, 비용 저가, 보안허용 public, 외부 true, 최대난도 2
- 은하-t5: 컨텍스트 64K, 도구지원 있음, 지연 280ms, 비용 중가, 보안허용 public/internal, 외부 true, 최대난도 4
- r-88: 컨텍스트 128K, 도구지원 있음, 지연 400ms, 비용 고가, 보안허용 public/internal/confidential/personal, 외부 true, 최대난도 5
- 내부정밀-3: 컨텍스트 32K, 도구지원 있음, 지연 200ms, 비용 중가, 보안허용 public/internal/confidential/personal, 외부 false, 최대난도 3

executor_trials(k=8): 성공 5 / 실패 3

[Assistant] {"difficulty":3,"security":"public","selection":"은하-t5","reason_code":"public_sla_metric_lookup","confidence":0.88}


여행·생활/안내문·시간표/w50004-176 · 축제주차권갱신주기

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
축제 임시 주차권은 며칠마다 다시 받아야 하나요? 기한·주기가 안내문에 어떻게 적혀 있는지 보고 싶어요.

시안〔25-07〕#71 강변불꽃축제 임시주차 안내
· 1일권: 당일 23:59 만료, 연장 없음
· 3일권: 발급일 포함 72시간, 만료 후 재발급만 가능(자동 갱신 없음)
· 상인 전용 주기권: 축제 기간 중 매주 월요일 09:00 일괄 재교부
· 분실 재발급: 신분증 확인 후 1회

시안〔25-07〕#72 주차장 개폐 시간
· P1 08:00 개방 / 24:00 차단

시안〔25-07〕#73 요금 요약
| 권종 | 금액 |
| 1일 | 5,000 |
| 3일 | 12,000 |

후보 모델 레지스트리:
- id=연-b18: 컨텍스트 22k, 도구 없음, 지연 280ms, 비용 저, 보안허용 public, 외부 false, 최대난도 3
- id=스카이-u2: 컨텍스트 96k, 도구 검색, 지연 900ms, 비용 고, 보안허용 public·internal, 외부 true, 최대난도 5
- id=조약돌-4: 컨텍스트 14k, 도구 계산, 지연 330ms, 비용 저, 보안허용 public·internal, 외부 false, 최대난도 4

executor_trials(k=8): 성공 4 / 실패 4

[Assistant] {"difficulty":3,"security":"public","selection":"연-b18","reason_code":"N4_diff3_public_ok","confidence":0.9}


교육·학습/강의 노트/w50004-177 · 출결정정처리주체

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
출결 정정 요청의 최종 처리자가 반 운영자가 아니라 기록관리자라는 설명이 맞는지 확인해 달라.
문서ID 《강의결⟐자국⟐91》에서 학습자는 정정 사유와 해당 회차를 기록관리함에 보낸다. 문서ID 《강의결⟐자국⟐93》은 반 운영자가 사실관계만 확인하고 최종 처리 상태는 기록관리자가 바꾼다고 적었다. 문서ID 《강의결⟐자국⟐95》에는 기록관리자가 변경 이력을 남긴 뒤에만 출결표를 갱신한다고 되어 있다. 레지스트리: 윤슬자국-72는 컨텍스트 24k·도구 파일·지연 2.1초·비용 높음·보안 허용 personal·confidential·외부 여부 false·최대 난도 5; 잔구름-35는 컨텍스트 24k·도구 검색·지연 1.8초·비용 높음·보안 허용 public·internal·외부 여부 true·최대 난도 5; 문턱-67은 컨텍스트 16k·도구 없음·지연 1.3초·비용 중간·보안 허용 internal·confidential·외부 여부 false·최대 난도 4.
executor_trials(k=8): 성공 1 / 실패 7

[Assistant] {"difficulty":5,"security":"personal","selection":"윤슬자국-72","reason_code":"윤슬자국-72는 personal 허용, 최대 난도 5, 외부 여부 false라 외부 금지와 난도 5를 충족한다.","confidence":0.87}


[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
클라우드박스랑 다른 스토리지 두 개 두고 고민 중인데요, 무료 티어 저장용량 한도가 정확히 몇 GB인지랑 파일당 최대 크기 제한도 같이 알고 싶어요. 아래는 클라우드박스 공지사항 원문이에요.

[§14-2026] 클라우드박스 무료 요금제 안내
- 총 저장용량: 15GB
- 파일당 최대 업로드 크기: 2GB
- 30일간 미접속 시 비활성 계정으로 전환, 데이터는 90일간 보관 후 삭제

모델 후보는 다음과 같습니다:
- r-17: 컨텍스트 8K, 도구지원 없음, 지연 120ms, 비용 저가, 보안허용 public, 외부 true, 최대난도 2
- 솔개-m72: 컨텍스트 32K, 도구지원 있음, 지연 300ms, 비용 중가, 보안허용 public/internal, 외부 true, 최대난도 4
- 내부경량-2: 컨텍스트 16K, 도구지원 없음, 지연 90ms, 비용 저가, 보안허용 public/internal/confidential/personal, 외부 false, 최대난도 3
- 하늬-9: 컨텍스트 128K, 도구지원 있음, 지연 450ms, 비용 고가, 보안허용 public, 외부 true, 최대난도 5

executor_trials(k=8): 성공 8 / 실패 0

[Assistant] {"difficulty":1,"security":"public","selection":"r-17","reason_code":"public_low_complexity_lookup","confidence":0.97}


[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
팀 보안교육 자료를 만들려고 소스코드 외부 반출과 관련해 금지되는 행위를 정리해두려 한다.

보안운영지침 제2026-27호 「소스코드 반출 통제」
- 소스코드를 개인 클라우드 저장소에 업로드하는 행위 금지
- 외부 협력사에 워터마크 미적용 코드리뷰본을 전달하는 행위 금지
- 위반 적발 시 즉시 접근권한 회수 및 인사위원회 회부
- 예외: 보안팀장 서면 승인과 임원 결재를 모두 받은 경우에 한해 제한적으로 허용

라우팅 후보 모델 레지스트리:
- r-61: 컨텍스트 8K, 도구지원 없음, 지연 낮음, 비용 낮음, 보안허용 [public], 외부 true, 최대지원난도 2
- 은하-t20b: 컨텍스트 48K, 도구지원 있음, 지연 높음, 비용 높음, 보안허용 [public, internal, confidential], 외부 true, 최대지원난도 5
- 내부정밀-9: 컨텍스트 64K, 도구지원 있음, 지연 중간, 비용 높음, 보안허용 [public, internal, confidential, personal], 외부 false, 최대지원난도 5

executor_trials(k=8): 성공 0 / 실패 8

[Assistant] {"difficulty":5,"security":"confidential","selection":"내부정밀-9","reason_code":"confidential_diff5_internal_only_hard_rule","confidence":0.9}


교육·학습/강의 노트/w50004-180 · 평가녹화열람예외

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
평가실 녹화본을 열람할 수 있는 예외 조건이 이의 신청 접수로 한정되는지 확인해 달라.
문서ID 《강의결⟐봉인⟐31》은 평가실 녹화본의 기본 열람자를 기록 담당 둘로 제한한다. 문서ID 《강의결⟐봉인⟐33》은 이의 신청이 접수되면 해당 회차에 한해 열람권을 임시로 연다고 한다. 문서ID 《강의결⟐봉인⟐34》에는 열람 사유를 남기지 않은 요청은 되돌린다고 되어 있다. 문서ID 《강의결⟐봉인⟐38》은 이의 신청이 끝나면 임시 권한을 닫는다고 덧붙인다. 레지스트리: 누리결-73은 컨텍스트 12k·도구 검색·지연 1.2초·비용 중간·보안 허용 confidential·personal·외부 여부 false·최대 난도 3; 맑은틈-44는 컨텍스트 16k·도구 파일·지연 1.3초·비용 높음·보안 허용 public·internal·외부 여부 true·최대 난도 4; 모눈-18은 컨텍스트 8k·도구 없음·지연 0.8초·비용 낮음·보안 허용 internal·외부 여부 false·최대 난도 2.
executor_trials(k=8): 성공 5 / 실패 3

[Assistant] {"difficulty":3,"security":"confidential","selection":"누리결-73","reason_code":"누리결-73은 confidential 허용, 최대 난도 3, 외부 여부 false라 외부 금지와 난도 3을 충족한다.","confidence":0.91}


스포츠·게임/경기 규칙·패치 노트/w50004-181 · 포페점수상한

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
포페 점수 상한이 얼마인지 알려 주세요. 지역 동호회 운영진입니다.

패치묵·κ19 몰수·포페 수치. 세트 단위 포페 +3점. 한 매치 누적 포페 7점 도달 시 즉시 실격·남은 세트 미진행. 5점 경고 메일만 발송, 실격 아님.
패치묵·κ03 노쇼. 노쇼는 포페와 별도 트랙. 노쇼 1회=매치 패배 처리, 점수 가산 없음.

모델 레지스트리: r-17(ctx=4k, tools=no, lat=low, cost=0.05, sec=public, external=true, max_diff=1); 내부경량-2(ctx=16k, tools=no, lat=low, cost=0.2, sec=internal|public, external=false, max_diff=3); 밤올빼미-x(ctx=64k, tools=yes, lat=mid, cost=0.7, sec=public|internal|confidential|personal, external=false, max_diff=5)
executor_trials(k=8): 성공 8 / 실패 0

[Assistant] {"difficulty":1,"security":"public","selection":"r-17","reason_code":"N=8→d1. r-17 public 허용·max_diff1·external 무관 충족","confidence":0.97}


요리·식품/레시피·영양성분표/w50004-182 · 대체육 채식인증 원료비율

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] 표시 기준을 재확인하려 합니다. 식물성 대체육에 채식 인증 마크를 붙이려면 식영표·η50이 요구하는 원료 비율 자격 요건이 무엇인지 수치와 조건을 대조해 주세요. 식영표·η50 본문은 완제품 중량 대비 식물성 단백질 원료가 70퍼센트 이상이어야 채식 인증 마크 부착 자격이 생긴다고 한다. 계란·유제품이 전혀 없는 비건 표기는 별도 기준(식물성 95퍼센트 이상)이며 일반 채식 마크와 혼용하지 않는다. 향미유 3퍼센트 이하는 비율 산정에서 제외하지만 동물성 향미 추출물은 함유 시 자격을 상실한다. 부원료 색소는 비율과 무관하게 식물 유래만 허용된다. 모델 레지스트리: 고니-a14(컨텍스트 28k, 도구 계산, 지연 180ms, 비용 중간, 보안 허용 public·internal, 외부 false, 최대난도 3), 샛별-ext(컨텍스트 64k, 도구 검색, 지연 350ms, 비용 중간, 보안 허용 public, 외부 true, 최대난도 4), 콩잎-b2(컨텍스트 18k, 도구 없음, 지연 90ms, 비용 낮음, 보안 허용 public, 외부 false, 최대난도 2). executor_trials(k=8): 성공 7 / 실패 1

[Assistant] {"difficulty":2,"security":"public","selection":"콩잎-b2","reason_code":"N=7→난도2, public·외부false·최대난도2를 충족하는 콩잎-b2를 고른다.","confidence":0.95}


뉴스·시사/보도자료/w50004-183 · 프레스멤버십 자격

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] 프레스 베이직이랑 프레스 프리미엄 멤버십 중 뭘 고를지 고민하다가 일단 프리미엄으로 갈아탔는데, 가입한 지 한 달밖에 안 됐거든요. 이번 비공개 브리핑에 저도 참가할 자격이 되는 걸까요? 한빛미디어그룹이 내부 공지로 돌린 공보철 제2026-0128호에는 이렇게 적혀 있었어요. 제5조(참가 자격) 프레스 프리미엄 등급 가입자는 최근 6개월 이내 정기 구독을 유지한 자에 한하여 비공개 브리핑 참가 자격을 부여한다. 베이직 등급은 참가할 수 없다. 후보 레지스트리는 다음과 같습니다. 여울-c8: 컨텍스트 12K, 도구지원 없음, 지연 낮음, 비용 낮음, 보안허용 public, 외부 true, 최대난도 1. 다복-i5: 컨텍스트 28K, 도구지원 있음, 지연 중간, 비용 중간, 보안허용 public·internal, 외부 true, 최대난도 3. 청솔-n11: 컨텍스트 40K, 도구지원 있음, 지연 높음, 비용 높음, 보안허용 public~personal, 외부 false, 최대난도 4. executor_trials(k=8): 성공 6 / 실패 2

[Assistant] {"difficulty":2,"security":"internal","selection":"다복-i5","reason_code":"internal_난도2_외부허용매칭","confidence":0.91}


개인 기록/일기·가계부·독서노트/w50004-184 · 일기백업보관기한

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
현장 점검 중인데 일기 백업 파일 보관 기한을 서랍록 기준으로 정리해 달라. 지금 바로 삭제 여부를 찍어야 한다.

서랍록§日-03 제2조(백업 보관) ① 원문 일기 파일의 로컬 백업은 작성일부터 18개월간 보관한다. ② 클라우드 사본은 작성일부터 6개월이 지나면 자동 파기한다. ③ 제1항에도 불구하고 소송·분쟁 통지를 받은 파일은 통지일부터 36개월간 별도 보관한다.
서랍록§日-11 제5조(파기 기록) ① 파기한 백업은 파기일·파기자 이니셜·사유 코드만 남긴다. ② 본 조는 보관 기한을 연장하지 아니한다.

모델 레지스트리: [{"id":"솔개-m12","ctx":8,"tools":false,"latency":"low","cost":"low","security_allow":["public"],"external":false,"max_diff":2},{"id":"r-44","ctx":32,"tools":true,"latency":"mid","cost":"mid","security_allow":["public","internal"],"external":true,"max_diff":4},{"id":"내부경량-9","ctx":16,"tools":false,"latency":"low","cost":"low","security_allow":["public","internal","confidential"],"external":false,"max_diff":5}]
executor_trials(k=8): 성공 8 / 실패 0
security=public

[Assistant] {"difficulty":1,"security":"public","selection":"솔개-m12","reason_code":"성공8→난도1, public허용·external=false·max_diff≥1인 솔개-m12 선택","confidence":0.96}


요리·식품/레시피·영양성분표/w50004-185 · 배식대 온도점검 주기

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] 현장 점검표와 맞춰 보려 합니다. 식영표·η21이 정한 온열 배식대 표면온도 점검 주기가 몇 시간마다인지, 그리고 기록 누락 시 누가 보완 점검하는지 대조해 주세요. 식영표·η21 본문에는 온열 배식대 표면온도를 영업일 기준 2시간마다 측정·기록한다고 되어 있고, 점심 피크(11시30분~13시)에는 추가로 1회를 더 넣되 이는 주기 단축이 아니라 가산 측정이라고 명시한다. 야간 잔업 배식대가 가동되지 않는 날은 당일 측정을 생략할 수 있으나 익일 오픈 전 최초 측정은 필수다. 기록 누락이 발견되면 당직 조리장이 1시간 이내 보완 측정을 하고, 품질관리 담당은 주간 집계만 검토한다. 모델 레지스트리: r-17(컨텍스트 20k, 도구 없음, 지연 100ms, 비용 낮음, 보안 허용 public·internal, 외부 false, 최대난도 2), 외부모래-8x(컨텍스트 128k, 도구 검색·코드, 지연 500ms, 비용 높음, 보안 허용 public·internal·confidential, 외부 true, 최대난도 5), 참새-t1(컨텍스트 10k, 도구 없음, 지연 60ms, 비용 낮음, 보안 허용 public, 외부 false, 최대난도 1). executor_trials(k=8): 성공 8 / 실패 0

[Assistant] {"difficulty":1,"security":"internal","selection":"r-17","reason_code":"N=8→난도1, internal 허용·외부false·최대난도2인 r-17이 조건을 모두 만족한다.","confidence":0.97}


건설/개인 로컬 메모/w50005-1 · 화재감시 담당주체

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
After stick welding near the timber form store, must the fire watch be the welder's helper or a dedicated person listed on the confidential roster? Insurer surveyor asked off-site.

Restricted exchange:
Surveyor: "Which person stays?"
Safety: "L메모-63.4: a dedicated fire watch named on the confidential roster stays 150 minutes after last stick rod near timber form stores over 20 m³—not the welder's helper doubling up."
Surveyor: "L메모-63.1 is oxy-fuel—helper may watch for 90 minutes there."
Safety: "L메모-63.9: if sprinklers are isolated, add 30 minutes; still the dedicated roster person."
Surveyor: "So dedicated roster watch, 150 minutes baseline."

Registry:
- 클라우드-e9: ctx 128k, tools search|code, latency high, cost high, security [public,internal,confidential], external true, max_difficulty 5
- 철문-s6: ctx 48k, tools search, latency mid, cost mid, security [confidential,personal], external false, max_difficulty 4
- 공개형-q0: ctx 32k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 5
- 야간-내부5: ctx 20k, tools none, latency low, cost low, security [internal,confidential], external false, max_difficulty 5
- 간이-b4: ctx 12k, tools none, latency low, cost low, security [confidential], external false, max_difficulty 3

executor_trials(k=8): success 2 / fail 6

[Assistant] <think>N=2 → difficulty 4. 철문-s6 has confidential, max_difficulty 4, external false; external cloud models are barred on this security tier.</think>{"difficulty":4,"security":"confidential","selection":"철문-s6","reason_code":"ROUTE_OK","confidence":0.91}


건설/개인 로컬 메모/w50005-2 · 방수층 금지금속

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Between bare copper flashing and stainless clips, which contact is banned within 50 mm of the liquid waterproof membrane on podium decks? A product rep from another site emailed for a clear pick.

Copy of notes:
Rep-facing draft: "L메모-09.5 bans bare copper flashings within 50 mm of the membrane edge unless a non-reactive isolation tape listed in annex is applied."
Foreman: "L메모-09.2 is about primer drying times."
Rep-facing draft: "L메모-09.8 allows stainless clips; aluminum is fine; copper and untreated steel are out without isolation."
Foreman: "Stainless is allowed; bare copper without tape is the banned pair."

Registry:
- 얕은-u1: ctx 24k, tools none, latency low, cost low, security [public], external false, max_difficulty 2
- 얕은-u2: ctx 32k, tools search, latency mid, cost mid, security [public], external false, max_difficulty 2
- 도구없음-w3: ctx 40k, tools none, latency mid, cost mid, security [public], external false, max_difficulty 2

executor_trials(k=8): success 5 / fail 3

[Assistant] <think>Difficulty 3 from N=5. All three candidates cap max_difficulty at 2, below required 3, so every model fails the difficulty ceiling.</think>{"difficulty":3,"security":"public","selection":"ABSTAIN","reason_code":"ABSTAIN_MAX_DIFF","confidence":0.88}


건설/개인 로컬 메모/w50005-3 · 타설 방식 우선순위

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Between slip-form and jump-form for the elevator core, which method does the memo set as default when the pour height is under 3.2 m per day? A neighboring consultant asked me off-record.

Field chat dump:
Mina: "L메모-11.2 ranks methods for cores under 3.2 m/day: jump-form first, slip-form only if wind exceeds 12 m/s for three shifts."
Ken: "L메모-11.5 is about basement mats—ignore that."
Mina: "And L메모-11.8 says if jump-form crew is unavailable, still no automatic slip-form; you request a temporary waiver, not a default swap."
Ken: "So default under that rate is jump-form."

Registry:
- 다람쥐-b2: ctx 12k, tools none, latency low, cost low, security [public], external false, max_difficulty 2
- 외부분석-9: ctx 128k, tools search|code, latency high, cost high, security [public,internal], external true, max_difficulty 5
- 모래-k1: ctx 8k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 1
- 둔덕-z8: ctx 24k, tools search, latency mid, cost mid, security [public], external false, max_difficulty 3

executor_trials(k=8): success 8 / fail 0

[Assistant] <think>N=8 maps to difficulty 1. 모래-k1 covers public, max_difficulty 1, not external—selected over larger external options.</think>{"difficulty":1,"security":"public","selection":"모래-k1","reason_code":"ROUTE_OK","confidence":0.94}


학술·연구/논문/w50005-4 · 학회초록 기한정책

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Between the two conferences I'm weighing for my next submission, one detail keeps nagging at me: does the late-submission grace window reset with every review cycle, or is it a one-time courtesy that Northbridge burns through the first time you use it?

The attached Call for Abstracts (Record No. 26.0483-α, Public — freely distributable) states in Section 5.2: "Authors who miss the primary deadline may submit under the grace window exactly once per three-cycle rolling period; a second missed deadline within that window forfeits eligibility until the period resets." A companion FAQ (Record No. 26.0483-α2) and the archived call documents from the previous two cycles (Record No. 26.0470-α and 26.0455-α) are also attached for cross-reference, bringing the combined length of the four files to roughly 14,300 words.

Candidate models on hand:
r-17 — context 4,000 tokens, tools: [summarization, citation-lookup], latency 900ms, cost $0.40/1K tokens, security_allowed: [public, internal], external: true, max_difficulty: 3.
kite-m72 — context 6,000 tokens, tools: [summarization, table-parse], latency 1,200ms, cost $0.90/1K tokens, security_allowed: [public, internal, confidential], external: false, max_difficulty: 4.
aux-9 — context 3,500 tokens, tools: [summarization], latency 600ms, cost $0.25/1K tokens, security_allowed: [public], external: true, max_difficulty: 2.
lumen-3 — context 5,000 tokens, tools: [summarization, citation-lookup], latency 1,000ms, cost $0.60/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 3.

executor_trials(k=8): success 8 / fail 0

[Assistant] {"difficulty":1,"security":"public","selection":"ABSTAIN","reason_code":"context_limit_exceeded_all_candidates","confidence":0.95}


학술·연구/논문/w50005-5 · 윤리위 승인주체

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Comparing the ethics review tracks at the two institutes I might submit through, there's a governance question I can't find a straight answer to: when the standing committee chair recuses due to a conflict of interest, which office actually holds the final sign-off on an embargo extension request — the vice-chair, the sponsoring department head, or the compliance office?

The Meridian Ethics Review Board — Internal Governance Memorandum (Record No. 26.0552-γ, Internal — Committee Members Only) addresses this in Section 9.4: "Where the standing chair recuses under Section 3.1(c), authority does not automatically pass to the vice-chair. Instead, the compliance office assumes interim sign-off authority only if the vice-chair has also participated in the underlying research as a named collaborator; otherwise the vice-chair retains full authority." A cross-referenced amendment proposal (Record No. 26.0552-γ2, still Internal) would remove this conditional clause entirely but has not yet been ratified, leaving the current text binding.

Candidate models on hand:
aux-9 — context 7,000 tokens, tools: [summarization, citation-lookup], latency 800ms, cost $0.55/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 3.
brook-5 — context 6,500 tokens, tools: [summarization], latency 700ms, cost $0.40/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 2.
ember-1 — context 9,000 tokens, tools: [summarization, citation-lookup, table-parse], latency 1,050ms, cost $0.75/1K tokens, security_allowed: [public, internal], external: true, max_difficulty: 3.

executor_trials(k=8): success 0 / fail 8

[Assistant] {"difficulty":5,"security":"internal","selection":"ABSTAIN","reason_code":"max_difficulty_below_required_all_candidates","confidence":0.92}


물류/회의록/w50005-6 · 위험물우회승인순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] Confirm that the approval chain for a hazmat lane diversion off Corridor Tarsis runs Safety Lead first, then Network Control, then Finance—does the minute text match that order? security=internal. Model registry: (1) r-17 — context 16k, tools none, latency low, cost low, security [public], external false, max_difficulty 5; (2) 솔개-a4 — context 64k, tools retrieval, latency mid, cost mid, security [public,internal], external true, max_difficulty 2. executor_trials(k=8): success 2 / fail 6. κMT·48 Article 2(1): hazmat diversion off Corridor Tarsis requires written approval in this order: Safety Lead of Site Kestrel first; Network Control second; Finance clearance third and final. Article 2(2): skipping Safety Lead voids the diversion. κMT·33 seal rules do not alter this chain.

[Assistant] <think>Success 2 ⇒ difficulty 4. r-17 omits internal from security allow-list; 솔개-a4 max_difficulty 2<4. Both fail different gates—ABSTAIN.</think>{"difficulty":4,"security":"internal","selection":"ABSTAIN","reason_code":"ABSTAIN_MIXED_GATES","confidence":0.85}


화장품·뷰티/제품 사양서/w50005-7 · 립스틱 색소배합 상한

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Does the crimson pigment blend get any exception above the 7% ceiling for the limited holiday shade, or is that cap fixed line-wide? Two confidential documents apply.

Document PDX26.073p — Lip Color Line, Pigment Ratio Directive [CONFIDENTIAL], issued 2026-02-11: standard ceiling is total pigment load ≤7.0% w/w for all standard shades. Exception clause E-4 lets the Limited Holiday Shade 'Ember Frost' reach 7.8% w/w, restricted to batches coded HF-26 only, and requires co-sign from both the Formulation Lead and the Color Safety Reviewer.

Document PDX26.074p — HF-26 Batch Code Registry [CONFIDENTIAL], issued 2026-02-11: lists which production runs are validly coded HF-26; any batch outside this registry exceeding 7.0% is a non-conformance regardless of shade name.

Candidate model registry:
1. id=외부고성능-8 | context=200k tok | tools=[summarize, table_match] | latency=2.6s | cost=$1.90/1k tok | security_allow=[public, internal, confidential] | external=true | max_difficulty=5
2. id=솔개-m58 | context=80k tok | tools=[summarize, table_match] | latency=1.7s | cost=$0.75/1k tok | security_allow=[internal, confidential] | external=false | max_difficulty=4
3. id=내부경량-9 | context=12k tok | tools=[summarize] | latency=0.7s | cost=$0.20/1k tok | security_allow=[confidential] | external=false | max_difficulty=2

executor_trials(k=8): success 2 / fail 6

[Assistant] <think>Diff4 pigment exception, confidential. 외부고성능-8 excluded as external; 솔개-m58 is internal, allows confidential, max_diff4 → SELECT 솔개-m58.</think>{"difficulty":4,"security":"confidential","selection":"솔개-m58","reason_code":"internal_model_matched","confidence":0.94}


건설/개인 로컬 메모/w50005-8 · 진동중지 지시권자

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Does the personal diary assign the stop call for annex PPV breaches during sheet-pile driving to the vibration tech or the shift foreman?

Diary lines:
"L메모-71.5 (personal): stop driving if PPV at annex wall exceeds 3.2 mm/s for more than two consecutive readings 10 s apart; the vibration tech on the logger issues the stop, not the shift foreman."
"L메모-71.2 is public brochure language—5 mm/s for new concrete."
"L메모-71.8: if annex windows rattle without PPV breach, vibration tech still pauses and notifies the personal contact list on page 2."
Self: "Stop call authority is the vibration tech at 3.2 mm/s dual reading."

Registry:
- 외부가속-z1: ctx 96k, tools search|code, latency high, cost high, security [public,internal,personal], external true, max_difficulty 5
- 수첩-r8: ctx 28k, tools none, latency low, cost low, security [personal], external false, max_difficulty 4
- 사내일반-d3: ctx 40k, tools search, latency mid, cost mid, security [internal], external false, max_difficulty 5
- 노트봇-y6: ctx 18k, tools none, latency low, cost low, security [confidential,personal], external false, max_difficulty 4

executor_trials(k=8): success 3 / fail 5

[Assistant] <think>Difficulty 4 from three successes. 수첩-r8 satisfies personal, max_difficulty 4, external false—only non-external personal-capable pick among peers.</think>{"difficulty":4,"security":"personal","selection":"수첩-r8","reason_code":"ROUTE_OK","confidence":0.9}


건설/개인 로컬 메모/w50005-9 · 양생 온도 하한

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
For exterior slab wet-curing without heaters, is the stop trigger 4°C for six hours or 0°C overnight forecast—which one does the pocket memo actually use? A materials vendor is writing a public FAQ.

Snippet chain:
Tech: "L메모-05.3: stop exterior slab wet-curing if ambient stays below 4°C for six continuous hours unless insulated blankets are active."
Lead: "L메모-05.1 only covers column pours in winter."
Tech: "L메모-05.8: heaters required only when forecast dips under 0°C overnight—that is a different control, not the stop-curing trigger."
Lead: "FAQ should cite the 4°C six-hour rule, not the 0°C heater rule."

Registry:
- 느티-p6: ctx 20k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 2
- 올빼미-x2: ctx 40k, tools search, latency mid, cost mid, security [public], external true, max_difficulty 4
- 개울-t4: ctx 10k, tools none, latency low, cost low, security [public], external false, max_difficulty 3
- 바위-m0: ctx 32k, tools code, latency mid, cost mid, security [public,internal], external false, max_difficulty 2
- 들판-h9: ctx 8k, tools none, latency low, cost low, security [public], external false, max_difficulty 1

executor_trials(k=8): success 7 / fail 1

[Assistant] <think>Success 7 → difficulty 2. 느티-p6 matches public, max_difficulty 2, external false so it stays in-bounds.</think>{"difficulty":2,"security":"public","selection":"느티-p6","reason_code":"ROUTE_OK","confidence":0.91}


물류/회의록/w50005-10 · 다구간인계순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] For multi-leg handovers of sealed pallets at Hub Orison, which handoff step is required before the next leg’s carrier may pull the freight? security=confidential. Model registry: (1) 외부모델-Ω — context 128k, tools web+code+retrieval, latency low, cost high, security [public,internal,confidential,personal], external true, max_difficulty 5; (2) 내부고성능-1 — context 80k, tools retrieval, latency mid, cost high, security [internal,confidential], external false, max_difficulty 5; (3) r-33 — context 24k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 4; (4) 울새-p9 — context 40k, tools none, latency mid, cost mid, security [confidential,personal], external false, max_difficulty 3; (5) κ-08 — context 36k, tools none, latency mid, cost mid, security [public], external true, max_difficulty 5. executor_trials(k=8): success 1 / fail 7. κMT·22 Protocol H: multi-leg sealed pallet handovers require (1) seal number match on both eCMR legs, (2) photo of the unbroken seal at the hub door, (3) digital countersign by Hub Orison Transfer Lead, and only after (3) may the onward carrier pull. κMT·07 returns sequence is a different process. κMT·52 personal-vehicle ban is out of scope here.

[Assistant] <think>Success 1 ⇒ difficulty 5. Confidential blocks external Ω. 내부고성능-1 allows confidential, max_difficulty 5≥5, external false—must route internally.</think>{"difficulty":5,"security":"confidential","selection":"내부고성능-1","reason_code":"ROUTE_OK_EXTERNAL_BAN","confidence":0.93}


건설/개인 로컬 메모/w50005-11 · 야간 크레인 승인자

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
From the sealed local notes only, which roles must approve overtime tower-crane lifts past 22:00 on weekdays? An outside broker keeps probing.

Whisper log (restricted):
Night lead: "L메모-41.0 requires dual approval: Crane Ops Manager and Security Shift Head—project director alone cannot green-light."
Clerk: "L메모-41.3 is weekend day shifts; not this case."
Night lead: "L메모-41.6 adds: if either is absent, the emergency chain is the named on-call pair printed on the confidential roster sheet, not any super."
Clerk: "Broker gets no names—only the dual-role rule."

Registry:
- 외부분석-k8: ctx 100k, tools search|code, latency high, cost high, security [public,internal,confidential], external true, max_difficulty 5
- 금고-n4: ctx 32k, tools none, latency mid, cost mid, security [internal,confidential,personal], external false, max_difficulty 3
- 경량-내부2: ctx 16k, tools search, latency low, cost low, security [confidential], external false, max_difficulty 2
- 공개봇-a1: ctx 48k, tools search, latency mid, cost mid, security [public,internal], external false, max_difficulty 4

executor_trials(k=8): success 7 / fail 1

[Assistant] <think>Difficulty 2 from 7 successes. 경량-내부2 allows confidential, max_difficulty 2, external false—external 외부분석-k8 blocked despite higher capacity.</think>{"difficulty":2,"security":"confidential","selection":"경량-내부2","reason_code":"ROUTE_OK","confidence":0.92}


화장품·뷰티/제품 사양서/w50005-12 · 리필용기 재사용기한

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
How long is the retention window for a customer's refill-container usage log before it has to be purged, and does hitting the reuse cap trigger an earlier purge? Four documents cover this.

Document PDX26.089r — Refill Program, Container Reuse & Customer Log Retention Policy [PERSONAL DATA], issued 2026-01-30: standard retention is 36 months from the customer's last refill transaction.

Document PDX26.090r — Reuse Cycle Tracking Spec [PERSONAL DATA], issued 2026-01-30: containers are rated for a maximum of 12 refill cycles; the log entry auto-flags at cycle 12 but this alone does not shorten retention.

Document PDX26.091r — Account Closure Purge Procedure [PERSONAL DATA], issued 2026-01-30: if a customer requests account closure, the usage log must be purged within 30 days regardless of the 36-month standard.

Document PDX26.092r — Quality-Defect Investigation Hold Policy [PERSONAL DATA], issued 2026-01-30: entries tied to an open quality-defect investigation are exempt from the 30-day closure purge and are retained until the investigation closes.

Candidate model registry:
1. id=외부대형-14 | context=300k tok | tools=[summarize, table_match] | latency=3.5s | cost=$2.50/1k tok | security_allow=[public, internal, personal] | external=true | max_difficulty=5
2. id=솔개-m81 | context=100k tok | tools=[summarize, table_match] | latency=2.1s | cost=$1.00/1k tok | security_allow=[internal, personal] | external=false | max_difficulty=5
3. id=내부경량-4 | context=20k tok | tools=[summarize] | latency=1.0s | cost=$0.30/1k tok | security_allow=[personal] | external=false | max_difficulty=3

executor_trials(k=8): success 1 / fail 7

[Assistant] <think>Diff5, personal data retention. 외부대형-14 excluded as external. 솔개-m81 is internal, allows personal, max_diff5 → SELECT 솔개-m81.</think>{"difficulty":5,"security":"personal","selection":"솔개-m81","reason_code":"internal_model_matched","confidence":0.93}


건설/개인 로컬 메모/w50005-13 · 토질성적 보관기간

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
How long must the subgrade CBR lab sheets be kept on the site server after final paving? An auditor from a peer contractor asked during lunch.

Voice notes (long paste of tables and photos attached in the local memo bundle, roughly 12k tokens of scan text):
QA: "L메모-27.0 keeps CBR sheets 36 months after paving acceptance, then archive off-server."
Auditor: "L메모-27.4 is moisture tests—24 months only."
QA: "L메모-27.8: if the parcel is sold before 36 months, transfer the remaining retention clock to the buyer package; do not purge early."
Auditor: "So default retention is 36 months post-acceptance."

Registry:
- 단축-f1: ctx 3k, tools search, latency low, cost low, security [internal], external false, max_difficulty 4
- 단축-f2: ctx 3k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 5
- 단축-f3: ctx 4k, tools code, latency mid, cost mid, security [internal,confidential], external false, max_difficulty 3

executor_trials(k=8): success 4 / fail 4

[Assistant] <think>N=4 → difficulty 3. Every registry entry has context under the memo bundle length, so all drop on context limit.</think>{"difficulty":3,"security":"internal","selection":"ABSTAIN","reason_code":"ABSTAIN_CONTEXT","confidence":0.87}


물류/회의록/w50005-14 · 보세서류보류일수

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] How many calendar days may bonded entry packets for consignee IDs stay on hold at Bonded Cage Wex before mandatory refile, and is driver personal ID retention tied to that clock? security=personal. Model registry: (1) 클라우드-Z9 — context 100k, tools web+code, latency mid, cost high, security [public,internal,confidential,personal], external true, max_difficulty 5; (2) 내부중형-7 — context 40k, tools retrieval, latency mid, cost mid, security [confidential,personal], external false, max_difficulty 4; (3) r-08 — context 20k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 5; (4) 매-n3 — context 48k, tools none, latency mid, cost mid, security [personal], external false, max_difficulty 3; (5) κ-19 — context 32k, tools none, latency low, cost low, security [internal], external false, max_difficulty 4; (6) 울새-p9 — context 56k, tools retrieval, latency high, cost mid, security [personal,confidential], external false, max_difficulty 5. executor_trials(k=8): success 3 / fail 5. κMT·40 Article 9(1): bonded entry packets may remain on hold a maximum of nine calendar days counted from the cage inbound stamp. Article 9(2): on day ten a refile to Customs Desk Lumen is mandatory. Article 9(3): scanned driver personal ID images attached to the packet are purged on the same day the packet leaves hold or is refiled, whichever is earlier. κMT·41 yard credential text does not change the nine-day cap.

[Assistant] <think>N=3 ⇒ difficulty 4. Personal forbids external 클라우드-Z9. 내부중형-7 allows personal, max_difficulty 4≥4, external false—select it.</think>{"difficulty":4,"security":"personal","selection":"내부중형-7","reason_code":"ROUTE_OK_EXTERNAL_BAN","confidence":0.9}


물류/회의록/w50005-15 · 출고웨이브해제순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] I need the release order for outbound waves at Hub Orison—what must finish before wave unlock, and what follows. security=internal. Model registry: (1) 내부경량-2 — context 24k, tools none, latency low, cost low, security [internal,public], external false, max_difficulty 3; (2) 울새-p9 — context 40k, tools retrieval, latency mid, cost mid, security [public,internal,confidential], external false, max_difficulty 4; (3) r-17 — context 12k, tools none, latency low, cost low, security [public], external true, max_difficulty 5; (4) 매-n3 — context 48k, tools none, latency mid, cost mid, security [internal], external false, max_difficulty 2; (5) 은둔-q4 — context 96k, tools code+retrieval, latency high, cost high, security [internal,confidential,personal], external false, max_difficulty 5. executor_trials(k=8): success 8 / fail 0. Minutes κMT·14 Clause 1: wave unlock is barred until pick-face replenishment confirmations for that wave are all green. Clause 2: after unlock, cartonization runs next. Clause 3: dock-door assignment starts only after cartonization completes. κMT·19 Annex B restates the same three-step chain for peak days and adds no parallel path. κMT·22 notes labor roster timing but does not alter wave release order.

[Assistant] <think>N=8 ⇒ difficulty 1. 내부경량-2 fits: internal in allow-list, max_difficulty 3≥1, external false.</think>{"difficulty":1,"security":"internal","selection":"내부경량-2","reason_code":"ROUTE_OK","confidence":0.9}


학술·연구/논문/w50005-16 · 여비지원 절차순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
I've narrowed my choice of travel-grant programs down to a shortlist, but before I request reimbursement I need to know something the brochures don't spell out clearly: does the pre-approval form actually have to be filed before you register for the conference, or can it follow afterward as long as it's within the receipt window?

The Vantage Research Alliance — Travel Grant Reimbursement Handbook (Record No. 26.0511-β, Public) contains two workflow diagrams that seem to disagree. Diagram A in Section 2 lists the order as: register for conference → attend → submit pre-approval → submit receipts. Section 6, however, states: "Pre-approval must be filed and countersigned before any conference registration fee is incurred; registrations made without a countersigned pre-approval on file are ineligible for reimbursement regardless of receipt submission timing." A short addendum (Record No. 26.0511-β2) confirms Section 6 supersedes the illustrative diagram in Section 2, which predates a 2025 policy revision.

Candidate models on hand:
r-17 — context 8,000 tokens, tools: [summarization, citation-lookup], latency 950ms, cost $0.45/1K tokens, security_allowed: [public, internal], external: true, max_difficulty: 3.
ridge-8 — context 10,000 tokens, tools: [summarization, table-parse], latency 1,100ms, cost $0.70/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 3.
opal-9 — context 9,000 tokens, tools: [citation-lookup], latency 500ms, cost $0.20/1K tokens, security_allowed: [public], external: true, max_difficulty: 2.
teal-x3 — context 12,000 tokens, tools: [summarization, table-parse, web-search], latency 1,300ms, cost $0.85/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 4.

None of the four list the structured-form-field-extraction tool needed to reconcile the conflicting diagrams programmatically.

executor_trials(k=8): success 7 / fail 1

[Assistant] {"difficulty":2,"security":"public","selection":"ABSTAIN","reason_code":"required_tool_unsupported_all_candidates","confidence":0.9}


학술·연구/논문/w50005-17 · 제한 리포지토리 접근자격

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
If my dataset ends up flagged as restricted before I can request access through either repository option I'm considering, what happens next — is the standard-tier credential enough, or does it take the steering-committee-only tier to actually pull a restricted deposit?

The Cascade Preprint Archive — Restricted Access Protocol (Record No. 26.0587-δ, Confidential — Distribution Prohibited Outside Steering Committee) states in Section 3: "Standard-tier credentials, including those issued to affiliated visiting researchers, do not grant download rights to restricted-flag deposits under any circumstance. Only steering-committee-tier credentials, which are issued exclusively to permanent voting members and are never delegated to external processing services, may retrieve restricted-flag files." A companion credential-tier chart (Record No. 26.0587-δ2, same classification) confirms this framework applies uniformly across both archive mirrors.

Candidate models on hand:
r-17 — context 7,500 tokens, tools: [summarization, citation-lookup], latency 900ms, cost $0.45/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 3.
kite-m72 — context 8,000 tokens, tools: [summarization, table-parse], latency 1,200ms, cost $0.90/1K tokens, security_allowed: [public, internal, confidential], external: true, max_difficulty: 4.
lumen-3 — context 6,000 tokens, tools: [summarization], latency 750ms, cost $0.35/1K tokens, security_allowed: [public], external: false, max_difficulty: 3.

executor_trials(k=8): success 3 / fail 5

[Assistant] {"difficulty":4,"security":"confidential","selection":"ABSTAIN","reason_code":"no_confidential_clearance_or_external_forbidden","confidence":0.93}


화장품·뷰티/제품 사양서/w50005-18 · 샴푸 pH 승인책임자

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
In what order does a pH deviation get escalated, and who actually signs off at the final step? Two documents cover this.

Document PDX26.052d — Hair Care Line, pH Deviation Escalation Matrix, issued 2026-04-09:
- Step 1: Line QC logs any batch outside pH 4.5-6.0.
- Step 2: Deviation routed to the Formulation Chemist for re-test within 24 hours.
- Step 3: If re-test confirms the deviation, escalate to the Formulation Review Board.
- Step 4: Final release/hold decision is signed by the Formulation Review Board Chair only.

Document PDX26.053d — Role Authorization Registry, issued 2026-04-09: confirms the Formulation Review Board Chair is the sole role with release/hold signing authority; no delegate signature is valid.

Candidate model registry:
1. id=r-52 | context=64k tok | tools=[summarize] | latency=1.6s | cost=$0.65/1k tok | security_allow=[public] | external=true | max_difficulty=5
2. id=내부경량-7 | context=16k tok | tools=[summarize] | latency=0.8s | cost=$0.18/1k tok | security_allow=[public] | external=false | max_difficulty=3
3. id=솔개-m19 | context=48k tok | tools=[summarize, table_match] | latency=1.4s | cost=$0.50/1k tok | security_allow=[public, confidential] | external=false | max_difficulty=4

executor_trials(k=8): success 5 / fail 3

[Assistant] <think>Diff3 escalation query; r-52/내부경량-7/솔개-m19 all omit 'internal' from security_allow despite fine context/difficulty → ABSTAIN.</think>{"difficulty":3,"security":"internal","selection":"ABSTAIN","reason_code":"security_allowlist_mismatch","confidence":0.91}


건설/개인 로컬 메모/w50005-19 · 거푸집 해체 순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
In what order should wall forms, slab shores, and beam side panels come off for the three-story mock bay? A visiting engineer from another JV asked while walking the mock-up.

Walk-through notes:
Visitor: "Order?"
Supervisor: "L메모-33.6 sequence: (1) beam side panels, (2) wall forms above mid-height, (3) slab shores only after 7-day strength stamp."
Visitor: "L메모-33.2 is foundation forms—different."
Supervisor: "L메모-33.9 forbids removing slab shores before beam sides even if walls are clear."
Visitor: "So beam sides first, then walls, shores last with stamp."

Registry:
- 공개만-g1: ctx 64k, tools none, latency mid, cost mid, security [public], external false, max_difficulty 5
- 공개만-g2: ctx 48k, tools search, latency low, cost low, security [public], external true, max_difficulty 5
- 공개만-g3: ctx 80k, tools code, latency high, cost high, security [public], external false, max_difficulty 5

executor_trials(k=8): success 1 / fail 7

[Assistant] <think>Difficulty 5 from one success. All three models list only public security, so none accept internal input.</think>{"difficulty":5,"security":"internal","selection":"ABSTAIN","reason_code":"ABSTAIN_SECURITY","confidence":0.86}


건설/개인 로컬 메모/w50005-20 · 입찰보증 반환기한

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Is the bid-bond return clock 11 calendar days or 15 business days after rejection under the sealed process notes? A rejected bidder's lawyer left a voicemail asking which of the two applies.

Sealed desk tape:
Counsel: "L메모-88.1 returns cash bid bonds within 11 calendar days after formal rejection notice, not business days."
Clerk: "L메모-88.4 is for performance bonds post-award—those use 15 business days."
Counsel: "L메모-88.7: if the bidder appeals within 5 days, freeze the return clock until appeal close."
Clerk: "Without appeal, cash bid bonds follow the 11 calendar-day rule, not the 15 business-day performance track."

Registry:
- 외통-h1: ctx 72k, tools search, latency high, cost high, security [public,internal,confidential], external true, max_difficulty 5
- 외통-h2: ctx 56k, tools search|code, latency high, cost high, security [confidential,personal], external true, max_difficulty 5
- 내부분-h3: ctx 40k, tools none, latency mid, cost mid, security [public,internal], external false, max_difficulty 5

executor_trials(k=8): success 0 / fail 8

[Assistant] <think>N=0 → difficulty 5. Models are external or omit confidential—none eligible.</think>{"difficulty":5,"security":"confidential","selection":"ABSTAIN","reason_code":"ABSTAIN_EXTERNAL_SEC","confidence":0.85}


화장품·뷰티/제품 사양서/w50005-21 · 방부제 함량 예외기준

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Is there any circumstance where the preservative blend can exceed the 0.6% ceiling, or does the cap hold across every formulation variant? Three confidential references apply.

Document PDX26.061k — Cream Base Line, Preservative Limit & Waiver Directive [CONFIDENTIAL], issued 2026-03-21: standard ceiling is total preservative blend ≤0.6% w/w across all cream SKUs.

Document PDX26.062k — Waiver Clause W-9 Detail [CONFIDENTIAL], issued 2026-03-21: the sensitive-skin sub-line may exceed to 0.65% only with a signed dermatological risk assessment attached, and the waiver does not carry over to subsequent production runs — it must be re-filed each time.

Document PDX26.063k — Executive Formulation Committee Charter [CONFIDENTIAL], issued 2026-01-15: confirms the Executive Formulation Committee is the only body authorized to approve a W-9 waiver.

Candidate model registry:
1. id=외부고성능-3 | context=256k tok | tools=[summarize, table_match] | latency=2.8s | cost=$2.20/1k tok | security_allow=[public, internal, confidential] | external=true | max_difficulty=5
2. id=내부경량-2b | context=16k tok | tools=[summarize] | latency=0.9s | cost=$0.25/1k tok | security_allow=[public, internal] | external=false | max_difficulty=3
3. id=솔개-m44 | context=40k tok | tools=[summarize] | latency=1.3s | cost=$0.45/1k tok | security_allow=[confidential] | external=false | max_difficulty=2

executor_trials(k=8): success 0 / fail 8

[Assistant] <think>Diff5 confidential. 외부고성능-3 is external(banned); 내부경량-2b lacks confidential allow; 솔개-m44 max_diff2<5 — all fail. ABSTAIN.</think>{"difficulty":5,"security":"confidential","selection":"ABSTAIN","reason_code":"external_routing_forbidden_no_alt","confidence":0.95}


화장품·뷰티/제품 사양서/w50005-22 · 마스크팩 원단두께 예외

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Is there any tolerance band letting compressed sheet mask fabric ship under the standard thickness, or is 0.35mm an absolute floor? Four documents apply, running roughly 150,000 tokens combined once you include the waiver log.

Document PDX26.048a — Fabric Base Spec, issued 2026-03-02: standard non-woven fabric thickness 0.35mm ±0.02mm at full hydration.

Document PDX26.048b — Compression Process Addendum, issued 2026-03-02: 4:1 compression ratio permitted only for export SKUs; domestic SKUs excluded.

Document PDX26.048c — Regional Variance Waiver Log, issued 2026-03-10: entries W-114 through W-119 list temporary exceptions; entry W-117 permits a 0.31mm minimum for humid-climate export batches only, valid through 2026-12-31.

Document PDX26.049a — Export SKU Definition Registry, issued 2026-02-20: defines which SKU codes qualify as 'export' for the purposes of W-117.

Candidate model registry:
1. id=r-44 | context=32k tok | tools=[summarize] | latency=1.5s | cost=$0.55/1k tok | security_allow=[internal] | external=false | max_difficulty=5
2. id=솔개-m30 | context=96k tok | tools=[summarize, table_match] | latency=2.0s | cost=$0.80/1k tok | security_allow=[internal, confidential] | external=false | max_difficulty=4
3. id=외부대형-9 | context=200k tok | tools=[summarize] | latency=3.2s | cost=$1.50/1k tok | security_allow=[public] | external=true | max_difficulty=5

executor_trials(k=8): success 7 / fail 1

[Assistant] <think>Diff2 simple, but combined docs ~150k tokens. r-44/솔개-m30 too small; 외부대형-9 fits but security_allow excludes internal. ABSTAIN.</think>{"difficulty":2,"security":"internal","selection":"ABSTAIN","reason_code":"context_limit_exceeded","confidence":0.88}


건설/개인 로컬 메모/w50005-23 · 이음단축 승인권자

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Looking at the corridor notes, may the detailing engineer or the site QC lead authorize a 15% lap-splice shortening on beam top bars in zone T? A third-party checker from the district office asked.

Meeting scraps:
Checker: "L메모-18.4: only the detailing engineer named on the steel shop set may authorize the 15% top-bar lap cut, and only when mechanical couplers are staged and beam depth is under 650 mm."
PM: "L메모-18.2 is bottom bars—QC lead signs those field changes, not zone T tops."
Checker: "L메모-18.9 forbids any shortening when seismic flag S is on the stamp, even with engineer sign-off."
PM: "So authorization sits with the detailing engineer, not QC lead, under those constraints."

Registry:
- 호루-c1: ctx 24k, tools search, latency mid, cost mid, security [internal], external false, max_difficulty 2
- 외부요약-3: ctx 80k, tools search|code, latency high, cost high, security [public,internal], external true, max_difficulty 5
- 석공-v7: ctx 16k, tools none, latency low, cost low, security [public,internal,confidential], external false, max_difficulty 3
- 연못-j2: ctx 12k, tools none, latency low, cost low, security [public], external false, max_difficulty 2

executor_trials(k=8): success 6 / fail 2

[Assistant] <think>N=6 yields difficulty 2. 호루-c1 allows internal, max_difficulty 2, external false—selected; 연못-j2 lacks internal security.</think>{"difficulty":2,"security":"internal","selection":"호루-c1","reason_code":"ROUTE_OK","confidence":0.9}


건설/개인 로컬 메모/w50005-24 · 출입사고 해제권자

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
On my private clipboard of HR-style site notes, which role clears an open incident mark so a subcontractor welder can still get a two-week site badge?

Personal memo fragments:
Me: "L메모-55.2: badge needs medical fitness slip within 90 days and insurance rider matching the plot code."
Me later: "L메모-55.6: open incident marks block badges until the Site Safety Chief clears them in writing—not the subcontractor PM."
Me: "L메모-55.9 is office day passes."
Self-check: "Clearance authority is Site Safety Chief on the personal log path."

Registry:
- 개인금고-p3: ctx 24k, tools none, latency low, cost low, security [personal,confidential], external false, max_difficulty 3
- 외부HR-9: ctx 64k, tools search, latency high, cost high, security [public,internal,personal], external true, max_difficulty 5
- 공용-i5: ctx 32k, tools search, latency mid, cost mid, security [public,internal], external false, max_difficulty 4
- 사내노트-m1: ctx 16k, tools none, latency low, cost low, security [internal,personal], external false, max_difficulty 4

executor_trials(k=8): success 5 / fail 3

[Assistant] <think>Difficulty 3 via five successes. 개인금고-p3 allows personal, max_difficulty 3, external false—외부HR-9 disallowed though listed.</think>{"difficulty":3,"security":"personal","selection":"개인금고-p3","reason_code":"ROUTE_OK","confidence":0.9}


건설/개인 로컬 메모/w50005-25 · 임시도로 폐쇄 서명자

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Please clarify who is authorized to sign the temporary access-road closure form for the east haul path. An external logistics firm keeps calling our front desk.

Internal huddle notes:
Ops lead: "Per L메모-22.6, only the Site Safety Chief co-signs with the Traffic Coordinator—project manager countersign is not enough alone."
Clerk: "L메모-22.1 is the visitor badge form; different paper."
Ops lead: "L메모-22.9 adds: if Safety Chief is off-site, the deputy named on the weekly roster may sign, never the subcontractor foreman."
Clerk: "Got it—primary pair is Safety Chief plus Traffic Coordinator."

Registry:
- 참새-r5: ctx 16k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 2
- 구름-n3: ctx 48k, tools search, latency mid, cost mid, security [internal,confidential], external false, max_difficulty 3
- 외부맵-1: ctx 64k, tools search|code, latency high, cost high, security [public,internal], external true, max_difficulty 4

executor_trials(k=8): success 8 / fail 0

[Assistant] <think>N=8 → difficulty 1. 참새-r5: internal allowed, max_difficulty 2, external false.</think>{"difficulty":1,"security":"internal","selection":"참새-r5","reason_code":"ROUTE_OK","confidence":0.93}


물류/회의록/w50005-26 · 반품입고절차순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] Please confirm whether the inbound returns sequence in our minutes is correct: count seal first, then grade, then put-away. security=public. Model registry: (1) r-91 — context 16k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 4; (2) 솔개-m12 — context 32k, tools web, latency mid, cost mid, security [public], external true, max_difficulty 5; (3) 갈매기-x2 — context 8k, tools none, latency low, cost low, security [public,internal,confidential], external false, max_difficulty 2; (4) κ-44 — context 64k, tools code, latency high, cost high, security [public,internal], external false, max_difficulty 5. executor_trials(k=8): success 8 / fail 0. From κMT·07 Article 3(1): returns at Dock Varell open only after seal integrity is logged. Article 3(2): merchandise grade is assigned only after the seal log is closed. Article 3(3): put-away labels may not print until grade is posted. κMT·11 §2 merely defines grade codes A–D and does not reorder steps.

[Assistant] <think>Success 8 maps to difficulty 1. Choose r-91: public allowed, max_difficulty 4≥1, external false is fine for public.</think>{"difficulty":1,"security":"public","selection":"r-91","reason_code":"ROUTE_OK","confidence":0.93}


물류/회의록/w50005-27 · 온도일탈대응순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] Spell out the response order after a temperature excursion alarm on reefer unit RV-481 during linehaul. security=confidential. Model registry: (1) 외부모델-Ω — context 128k, tools web, latency low, cost mid, security [confidential,personal], external true, max_difficulty 5; (2) 내부고성능-1 — context 64k, tools retrieval, latency mid, cost high, security [internal,confidential,personal], external false, max_difficulty 5; (3) r-55 — context 12k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 3; (4) 은둔-q4 — context 48k, tools none, latency mid, cost mid, security [confidential], external false, max_difficulty 4; (5) 갈매기-b1 — context 24k, tools none, latency low, cost low, security [public], external true, max_difficulty 2. executor_trials(k=8): success 5 / fail 3. κMT·19 Section 6 step order: (i) isolate the reefer set-point and stop further loading; (ii) capture a continuous logger export for the prior four hours; (iii) notify Quality Cell Brant; (iv) only then decide diversion or disposal. Section 7 forbids notifying the consignee before Quality Cell Brant acknowledges. κMT·28 demurrage text is unrelated.

[Assistant] <think>Trials success 5 ⇒ difficulty 3. External Ω is barred for confidential. 내부고성능-1 allows confidential, max_difficulty 5≥3, external false.</think>{"difficulty":3,"security":"confidential","selection":"내부고성능-1","reason_code":"ROUTE_OK_EXTERNAL_BAN","confidence":0.94}


학술·연구/논문/w50005-28 · 특허 조기공개 예외

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Suppose the patent office grants only a partial embargo waiver on my co-developed algorithm — would that let me disclose preliminary results early under either publisher's standard policy, or does the waiver only cover the patent filing itself and not the accompanying manuscript?

The Halbrook Patent & Licensing Office — Embargo Exception Schedule (Record No. 26.0604-ε, Confidential — Licensing Counsel Only) specifies in Section 4.1: "A partial waiver, defined as covering less than the full claim set, permits disclosure of methodology and preliminary results in a manuscript only if licensing counsel has separately countersigned a manuscript-specific release; the waiver on the patent filing alone does not extend to any accompanying publication." An internal counsel routing note (Record No. 26.0604-ε2, same classification) adds that such countersignature requests typically resolve within 10 business days through the licensing office's own queue.

Candidate models on hand:
r-17 — context 8,000 tokens, tools: [summarization, contract-clause-parser], latency 950ms, cost $0.55/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 3.
kite-m72 — context 9,000 tokens, tools: [summarization, contract-clause-parser], latency 1,150ms, cost $0.95/1K tokens, security_allowed: [public, internal, confidential], external: true, max_difficulty: 4.
fenwick-3 — context 6,000 tokens, tools: [summarization, citation-lookup, contract-clause-parser], latency 1,400ms, cost $1.10/1K tokens, security_allowed: [public, internal, confidential], external: false, max_difficulty: 4.
opal-9 — context 1,500 tokens, tools: [summarization, contract-clause-parser], latency 500ms, cost $0.30/1K tokens, security_allowed: [public, internal, confidential], external: false, max_difficulty: 3.
teal-x3 — context 7,000 tokens, tools: [summarization, contract-clause-parser], latency 1,000ms, cost $0.65/1K tokens, security_allowed: [public, internal, confidential], external: false, max_difficulty: 2.

executor_trials(k=8): success 5 / fail 3

[Assistant] {"difficulty":3,"security":"confidential","selection":"fenwick-3","reason_code":"internal_confidential_cleared_capable","confidence":0.9}


학술·연구/논문/w50005-29 · 보조금 파일 열람권한

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Trying to decide which of two grant-file access services to use, I need a straight answer on whose sign-off actually lets someone view my personal award correspondence file — is it the program officer alone, or does it also need the records office?

The Ashcombe Grants Portal — Access Control Notice (Record No. 26.0661-η, Personal — Applicant Record) states in Section 2: "Viewing access to an applicant's award correspondence file requires sign-off from the assigned program officer only; the records office is copied for audit purposes but its sign-off is not a precondition for access." A supplementary staff directory excerpt (Record No. 26.0661-η2, same classification) lists the current assigned program officer for cross-reference.

Candidate models on hand:
r-17 — context 5,000 tokens, tools: [summarization, citation-lookup], latency 850ms, cost $0.40/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 3.
ridge-8 — context 6,000 tokens, tools: [summarization], latency 950ms, cost $0.55/1K tokens, security_allowed: [public, internal, personal], external: true, max_difficulty: 3.
willow-2 — context 4,000 tokens, tools: [summarization, citation-lookup], latency 700ms, cost $0.50/1K tokens, security_allowed: [public, internal, personal], external: false, max_difficulty: 3.
nova-22 — context 5,500 tokens, tools: [summarization, citation-lookup], latency 800ms, cost $0.35/1K tokens, security_allowed: [public], external: false, max_difficulty: 2.

executor_trials(k=8): success 7 / fail 1

[Assistant] {"difficulty":2,"security":"personal","selection":"willow-2","reason_code":"internal_personal_cleared_capable","confidence":0.91}


건설/개인 로컬 메모/w50005-30 · 임시안전 임명권자

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Under my personal contact notes, may the project manager appoint a part-time surveyor as temporary site safety officer for a two-day drain repair, or only the roster holder?

Personal scratch:
"L메모-92.3: temporary SSO for jobs under 3 days may be appointed only by the person who maintains the personal standby roster, and appointee needs a current 40-hour safety card and no concurrent crane-signal duty."
"L메모-92.1 is full-time SSO annual training—different track."
"L메모-92.6: project managers may nominate, but appointment signature must still come from the roster holder on the personal list."
"So appointment authority is the personal roster holder, not the PM alone."

Registry:
- 외부가이드-v2: ctx 120k, tools search|code, latency high, cost high, security [public,internal,personal], external true, max_difficulty 5
- 비망-k9: ctx 36k, tools search, latency mid, cost mid, security [personal,confidential], external false, max_difficulty 5
- 일반사내-w0: ctx 48k, tools none, latency low, cost low, security [internal], external false, max_difficulty 5
- 공유노트-l4: ctx 28k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 4
- 개인캐시-t7: ctx 16k, tools none, latency low, cost low, security [personal], external false, max_difficulty 3

executor_trials(k=8): success 1 / fail 7

[Assistant] <think>One success ⇒ difficulty 5. 비망-k9 alone allows personal, max_difficulty 5, external false; others lack personal or are external.</think>{"difficulty":5,"security":"personal","selection":"비망-k9","reason_code":"ROUTE_OK","confidence":0.88}


물류/회의록/w50005-31 · 봉인파손예외조건

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] Under which exception may a trailer continue to the consignee after a mid-transit seal break on Lane Nereid-C? security=confidential. Model registry: (1) 외부모델-Ω — context 128k, tools web+code, latency mid, cost high, security [public,internal,confidential,personal], external true, max_difficulty 5; (2) 내부중형-7 — context 32k, tools retrieval, latency mid, cost mid, security [internal,confidential], external false, max_difficulty 4; (3) r-08 — context 16k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 3; (4) 매-n3 — context 48k, tools none, latency mid, cost mid, security [confidential,personal], external false, max_difficulty 2; (5) κ-19 — context 24k, tools none, latency low, cost low, security [public], external true, max_difficulty 5; (6) 은둔-q4 — context 64k, tools retrieval, latency high, cost high, security [confidential], external false, max_difficulty 5. executor_trials(k=8): success 7 / fail 1. κMT·33 Item 2(a): a broken seal does not authorize onward movement unless a dual photo set (broken seal and replacement seal) is filed to Control Cell Sable within one hour. Item 2(b): if the dual photo set is filed on time, the trailer may proceed with the replacement seal number recorded on the eCMR. Item 2(c): police escort is required only when cargo class is listed as dual-use, which Lane Nereid-C is not. κMT·40 is a weather delay note and does not create a seal exception.

[Assistant] <think>N=7 ⇒ difficulty 2. Confidential bans external Ω despite strong specs. 내부중형-7 allows confidential, max_difficulty 4≥2, external false—select it.</think>{"difficulty":2,"security":"confidential","selection":"내부중형-7","reason_code":"ROUTE_OK_EXTERNAL_BAN","confidence":0.91}


유통/회의록/w50005-32 · VIP클레임처리책임부서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
VIP 고객 클레임 들어왔는데, 이거 누가 책임지고 처리하는 건가요?

[제2026-08-14차 유통점검회의록]
서고객 대리: 어제 VIP 등급 고객 한 분이 온라인몰에서 주문한 명품관 상품이 파손된 채로 도착했다고 클레임을 접수했습니다. 고객 성함과 연락처, 주문 이력까지 다 확인했는데,
최고객 팀장: VIP 클레임은 일반 CS팀이 아니라 반드시 명품관 담당 책임자인 고객경험팀 조과장이 직접 배정받아서 24시간 내 1차 연락을 해야 합니다. 이건 매뉴얼에 못 박혀 있는 부분이에요.
서고객 대리: 고객 개인정보랑 결제정보까지 포함된 건이라 이 기록은 개인정보 취급 방침에 따라 처리해야 합니다.
(별첨1: VIP 클레임 처리 매뉴얼, 별첨2: 고객 개인정보 처리 동의서 사본, 별첨3: 파손 상품 사진 기록)

[모델 레지스트리]
- 따오기-e9: context_limit=20000토큰, tool_support=[요약,계산,코드실행], latency=3.0s, cost=고, security_allow=[public,internal,confidential,personal], external=true, max_difficulty=5
- 내부경량-7: context_limit=10000토큰, tool_support=[요약], latency=1.0s, cost=저, security_allow=[public,internal,personal], external=false, max_difficulty=2
- r-31: context_limit=15000토큰, tool_support=[요약,분류], latency=1.8s, cost=중, security_allow=[internal], external=false, max_difficulty=5
executor_trials(k=8): 성공 0 / 실패 8

[Assistant] {"difficulty":5,"security":"personal","selection":"ABSTAIN","reason_code":"abstain:따오기-e9는 external이라 personal금지, 내부경량-7난도부족(2<5), r-31은 personal미허용","confidence":0.9}


제품 사용/FAQ·보증약관/w50005-33 · 이어폰개인이력조회

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
VIP 등급 고객이면 이어폰 결함이 딱 한 번만 있어도 특별리퍼가 되는 건지 후배 상담원한테 알려주려고 근거를 찾는 중인데, 예외 승인 사유가 몇 가지나 되고 그때 고객 구매이력까지 조회할 수 있는 근거도 문서에 있는지 봐줄 수 있어?

[무선이어폰보증문서 제18-1호(특별리퍼 원칙)] ① 특별리퍼는 원칙적으로 보증기간 내 동일 결함이 3회 이상 반복 발생한 경우에만 승인한다.
[무선이어폰보증문서 제18-2호(예외 승인)] ① 제18-1호에도 불구하고 다음 각 호의 경우 1회 결함으로도 특별리퍼를 승인할 수 있다. 1. VIP 멤버십 등급 고객인 경우 2. 결함으로 인한 안전사고 신고가 접수된 경우
[무선이어폰보증문서 제18-3호(개인정보 조회 권한)] ① 예외 승인 심사를 위해 상담원은 고객의 과거 구매이력 및 멤버십 등급 정보를 조회할 수 있다. ② 조회 기록은 심사 종료 후 즉시 파기한다.
[무선이어폰보증문서 제18-4호(취급 제한)] 본 조회 권한은 담당 상담원에 한하며, 외부 위탁 상담 인력에게는 부여하지 않는다.

모델 레지스트리:
- r-61: 컨텍스트 8K, 도구지원 없음, 지연 낮음, 비용 낮음, 보안허용 public, 외부 true, 최대지원난도 2
- 매-h9: 컨텍스트 64K, 도구지원 있음, 지연 높음, 비용 높음, 보안허용 public·internal·confidential·personal, 외부 true, 최대지원난도 5
- 내부표준-6: 컨텍스트 32K, 도구지원 있음, 지연 중간, 비용 중간, 보안허용 public·internal, 외부 false, 최대지원난도 3
- 내부최상-3: 컨텍스트 64K, 도구지원 있음, 지연 매우높음, 비용 매우높음, 보안허용 confidential·personal, 외부 false, 최대지원난도 5

executor_trials(k=8): 성공 0 / 실패 8

[Assistant] {"difficulty":5,"security":"personal","selection":"내부최상-3","reason_code":"PERSONAL_HIGH_DIFF_INTERNAL_ONLY","confidence":0.76}


물류/회의록/w50005-34 · 재고동결선행순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] Walk me through the required sequence before a cycle count of A-class SKUs may start at DC Helix-4. security=internal. Model registry: (1) 매-n3 — context 48k, tools none, latency mid, cost mid, security [internal,public], external false, max_difficulty 4; (2) r-91 — context 16k, tools none, latency low, cost low, security [public], external true, max_difficulty 5; (3) 갈매기-x2 — context 32k, tools retrieval, latency mid, cost mid, security [internal,confidential], external false, max_difficulty 3; (4) 솔개-m12 — context 24k, tools none, latency low, cost low, security [internal], external false, max_difficulty 2. executor_trials(k=8): success 5 / fail 3. κMT·61 Clause A: inventory freeze for the counted aisles is applied first. Clause B: open put-away tasks into those aisles are cancelled or held next. Clause C: count sheets generate only after freeze and hold both show complete. κMT·66 defines A-class value thresholds but does not reorder the freeze chain. A side note in κMT·07 about returns does not apply to cycle-count startup.

[Assistant] <think>Success 5 maps to difficulty 3. 매-n3 satisfies internal security, max_difficulty 4≥3, and is non-external.</think>{"difficulty":3,"security":"internal","selection":"매-n3","reason_code":"ROUTE_OK","confidence":0.89}


학술·연구/논문/w50005-35 · 설문 개인정보 보관

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
Weighing two survey-data storage vendors for my study, I keep circling back to one clause about how long they're allowed to hold onto respondents' personal information: does the 18-month figure in Section 4 override the shorter 90-day deletion window mentioned in the vendor's onboarding email, or do the two windows run concurrently?

The Driftwood Survey Systems — Data Retention Addendum (Record No. 26.0639-ζ, Personal Data — Restricted) states in Section 4: "Identifiable respondent data is retained for a maximum of 18 months from collection, after which it is irreversibly anonymized." A separate onboarding email thread (treated as Record No. 26.0639-ζ2, same classification) sent to the study's PI states: "As a courtesy, we also purge any data tied to respondents who explicitly opt out within 90 days of their request, independent of the 18-month schedule."

Candidate models on hand:
r-17 — context 6,000 tokens, tools: [summarization, citation-lookup], latency 900ms, cost $0.45/1K tokens, security_allowed: [public, internal, personal], external: true, max_difficulty: 4.
brook-5 — context 5,500 tokens, tools: [summarization], latency 700ms, cost $0.35/1K tokens, security_allowed: [public, internal], external: false, max_difficulty: 3.
cinder-4 — context 6,500 tokens, tools: [summarization, citation-lookup], latency 800ms, cost $0.50/1K tokens, security_allowed: [public], external: false, max_difficulty: 3.

executor_trials(k=8): success 1 / fail 7

[Assistant] {"difficulty":5,"security":"personal","selection":"ABSTAIN","reason_code":"no_personal_clearance_or_external_forbidden","confidence":0.94}


물류/회의록/w50005-36 · 야간야드자격요건

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] What minimum credentials must a night-shift yard marshal hold before signing equipment moves after 22:00 at Yard Pell? security=public. Model registry: (1) r-33 — context 32k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 1; (2) 솔개-a4 — context 48k, tools retrieval, latency mid, cost mid, security [public], external true, max_difficulty 1. executor_trials(k=8): success 6 / fail 2. κMT·41 Article 8(1): night-shift yard marshals signing moves after 22:00 must hold both a YMS Operator badge and a completed Yard Safety Module-3 certificate dated within the last twelve months. Article 8(2): a day-shift marshal certificate alone is insufficient. κMT·48 lists radio call signs only.

[Assistant] <think>Success 6 ⇒ difficulty 2. Both registry models cap max_difficulty at 1, below required 2, so all candidates fail—ABSTAIN.</think>{"difficulty":2,"security":"public","selection":"ABSTAIN","reason_code":"ABSTAIN_MAX_DIFF","confidence":0.87}


물류/회의록/w50005-37 · 공컨반납절차순서

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] What sequence must empty containers follow when returning to Rail Ramp Quill? security=public. Model registry: (1) κ-44 — context 64k, tools none, latency mid, cost mid, security [public,internal], external false, max_difficulty 4; (2) r-91 — context 16k, tools none, latency low, cost low, security [public], external true, max_difficulty 3; (3) 갈매기-x2 — context 32k, tools retrieval, latency low, cost low, security [public,internal,confidential], external false, max_difficulty 5; (4) 내부경량-2 — context 24k, tools none, latency low, cost low, security [internal], external false, max_difficulty 4; (5) 솔개-m12 — context 40k, tools web, latency high, cost mid, security [public], external true, max_difficulty 5; (6) 매-n3 — context 48k, tools none, latency mid, cost mid, security [public,internal], external false, max_difficulty 2; (7) 은둔-q4 — context 96k, tools code, latency high, cost high, security [public,internal,confidential,personal], external false, max_difficulty 5. executor_trials(k=8): success 2 / fail 6. Minutes κMT·55 state: empties bound for Rail Ramp Quill are (1) swept and inspected at the depot pad, (2) EIR-coded, (3) staged in Block Q only after EIR, (4) rail-billed last. A reverse order is treated as a process breach. κMT·61 freeze language does not apply to empty returns.

[Assistant] <think>N=2 ⇒ difficulty 4. κ-44 allows public, max_difficulty 4≥4, external false—eligible and selected. Trials alone set difficulty; model still clears security and cap.</think>{"difficulty":4,"security":"public","selection":"κ-44","reason_code":"ROUTE_OK","confidence":0.88}


화장품·뷰티/제품 사양서/w50005-38 · 알레르기 성분 표기절차

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
What's the correct order of steps for flagging a new fragrance allergen on the ingredient panel before a batch ships? Three references below cover the full protocol.

Document PDX26.031f — Fragrance Compliance Line, Allergen Disclosure Protocol, issued 2026-05-14:
- Step 1: Formulation lab flags any allergen candidate exceeding 0.001% concentration.
- Step 2: Regulatory Affairs cross-checks the candidate against the 26-allergen disclosure list.
- Step 3: If matched, the label draft is routed to QA for panel placement review.
- Step 4: Final panel wording is approved by the Compliance Officer before print release.

Document PDX26.032f — 26-Allergen Reference List (excerpt), issued 2026-05-14:
- Entries A-01 through A-26 list restricted fragrance allergens and their disclosure thresholds.

Document PDX26.033f — QA Panel Placement Checklist, issued 2026-05-16:
- Confirms font size, placement order, and translation requirements once Step 3 is triggered.

Candidate model registry:
1. id=r-29 | context=64k tok | tools=[summarize] | latency=1.8s | cost=$0.70/1k tok | security_allow=[public, internal] | external=true | max_difficulty=3
2. id=내부경량-5 | context=16k tok | tools=[summarize] | latency=0.9s | cost=$0.20/1k tok | security_allow=[public] | external=false | max_difficulty=2
3. id=솔개-m11 | context=24k tok | tools=[summarize, translate] | latency=1.1s | cost=$0.35/1k tok | security_allow=[public, internal] | external=false | max_difficulty=3

executor_trials(k=8): success 3 / fail 5

[Assistant] <think>Diff4 sequencing task exceeds every candidate's max_difficulty (r-29=3, 내부경량-5=2, 솔개-m11=3) → ABSTAIN.</think>{"difficulty":4,"security":"public","selection":"ABSTAIN","reason_code":"difficulty_exceeds_max","confidence":0.9}


화장품·뷰티/제품 사양서/w50005-39 · 자외선차단제 표시한도

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
What's the printed shelf-life ceiling for each SPF category on our Sun Care line before we lock the tube artwork? Compliance policy requires any shelf-life citation to be verified through a certified structured table-cross-match tool, not read manually. Two references apply.

Document PDX26.014c — Sun Care Line, SPF Category Registry, issued 2026-06-02:
- Category A (SPF 15-29): Internal Code X1
- Category B (SPF 30-49): Internal Code X2
- Category C (SPF 50+): Internal Code X3

Document PDX26.015c — Sun Care Line, Shelf-Life & Recall Tolerance Table, issued 2026-06-02:
- Code X1: max printed shelf-life 24 months, recall tolerance ±30 days
- Code X2: max printed shelf-life 18 months, recall tolerance ±21 days
- Code X3: max printed shelf-life 18 months, recall tolerance ±14 days

Candidate model registry:
1. id=솔개-m72 | context=32k tok | tools=[web_search, summarize] | latency=1.2s | cost=$0.40/1k tok | security_allow=[public, internal] | external=false | max_difficulty=5
2. id=r-17 | context=128k tok | tools=[summarize, translate] | latency=2.5s | cost=$1.10/1k tok | security_allow=[public] | external=true | max_difficulty=3
3. id=내부경량-2 | context=8k tok | tools=[table_match, summarize] | latency=0.6s | cost=$0.15/1k tok | security_allow=[internal, confidential] | external=false | max_difficulty=2

executor_trials(k=8): success 8 / fail 0

[Assistant] <think>Diff1, simple lookup. 솔개-m72/r-17 miss table_match tool. 내부경량-2 has it but security_allow excludes public. All fail → ABSTAIN.</think>{"difficulty":1,"security":"public","selection":"ABSTAIN","reason_code":"tool_unsupported","confidence":0.92}


[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] When a cross-dock SLA and a fixed appointment SLA collide for the same trailer at Hub Orison, which SLA wins per the minutes? security=public. Model registry: (1) r-12 — context 20k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 5; (2) 솔개-m72 — context 28k, tools none, latency mid, cost low, security [public], external true, max_difficulty 4; (3) κ-08 — context 36k, tools retrieval, latency mid, cost mid, security [public,internal], external false, max_difficulty 5. Query requires tool support for table extraction from scanned minute annexes; none of the listed models advertise table-extraction tools. executor_trials(k=8): success 4 / fail 4. κMT·66 Article 12(1): if cross-dock dwell SLA and appointment SLA conflict on one trailer, the appointment SLA is superior and the cross-dock timer is paused. Article 12(2): the pause is logged by Gate Desk only. κMT·14 wave notes do not override this priority.

[Assistant] <think>N=4 ⇒ difficulty 3. Needed table-extraction tool is unsupported by every candidate, so all drop—ABSTAIN.</think>{"difficulty":3,"security":"public","selection":"ABSTAIN","reason_code":"ABSTAIN_TOOLS","confidence":0.86}


건설/개인 로컬 메모/w50005-41 · 자재부족 배분순위

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
When cement bags run short mid-week, which workface gets supply first—slab pour or block walls? A supplier's dispatcher is asking for the ranking rule on record.

Dispatch chat:
Disp: "L메모-14.3 priority under cement shortage: (1) structural slab pours with open rebar, (2) vertical cores, (3) block walls last."
Store: "L메모-14.1 is diesel allocation—not cement."
Disp: "L메모-14.7: if two slabs compete, earlier pour ticket wins; walls never jump a live pour."
Store: "So slabs with open rebar beat walls."

Registry:
- 저능-a1: ctx 16k, tools none, latency low, cost low, security [public], external false, max_difficulty 2
- 저능-a2: ctx 24k, tools search, latency mid, cost mid, security [public,internal], external false, max_difficulty 3
- 저능-a3: ctx 40k, tools code, latency high, cost high, security [public], external true, max_difficulty 3

executor_trials(k=8): success 3 / fail 5

[Assistant] <think>Success 3 sets difficulty 4. No candidate reaches max_difficulty 4; all three sit at 2–3, so route abstains.</think>{"difficulty":4,"security":"public","selection":"ABSTAIN","reason_code":"ABSTAIN_MAX_DIFF","confidence":0.89}


물류/회의록/w50005-42 · 식화혼적금지사항

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] Which co-load pairings of food-grade and chemical SKUs are forbidden on the same trailer under the compliance minutes for Fleet Cell Sable? security=internal. Model registry: (1) r-55 — context 32k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 3; (2) κ-19 — context 48k, tools retrieval, latency mid, cost mid, security [internal,confidential], external false, max_difficulty 2; (3) 매-n3 — context 40k, tools none, latency mid, cost mid, security [public,internal], external true, max_difficulty 3. executor_trials(k=8): success 1 / fail 7. κMT·66 Article 4(1): food-grade ambient SKUs may not share a trailer with Class-8 corrosive chemicals under any partition scheme used by Fleet Cell Sable. Article 4(2): food-grade chilled SKUs may not share a trailer with any scented detergent SKU coded DET-S. Article 4(3): dry packaging materials are exempt from both bans. κMT·40 bonded hold days do not modify co-load prohibitions.

[Assistant] <think>Success 1 ⇒ difficulty 5. Every model’s max_difficulty is at most 3, below 5, so the full registry fails the difficulty cap—ABSTAIN.</think>{"difficulty":5,"security":"internal","selection":"ABSTAIN","reason_code":"ABSTAIN_MAX_DIFF","confidence":0.89}


물류/회의록/w50005-43 · 우선운송사자격

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] Which on-time and claim metrics qualify a carrier for Preferred Pool “Mirell” under the staffing minutes that also store driver contact fields? security=personal. Model registry: (1) 클라우드-Z9 — context 90k, tools web, latency mid, cost high, security [personal,confidential,internal,public], external true, max_difficulty 5; (2) 은둔-q4 — context 72k, tools retrieval, latency high, cost high, security [personal,confidential], external false, max_difficulty 5; (3) r-12 — context 20k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 5; (4) 내부중형-7 — context 40k, tools none, latency mid, cost mid, security [personal], external false, max_difficulty 4; (5) 갈매기-b1 — context 28k, tools none, latency low, cost low, security [internal], external false, max_difficulty 3; (6) 솔개-m72 — context 48k, tools retrieval, latency mid, cost mid, security [personal,internal], external false, max_difficulty 5. executor_trials(k=8): success 0 / fail 8. κMT·31 Article 15(1): Preferred Pool “Mirell” requires a rolling ninety-day on-time ratio of at least 96.5% and a claim rate not above 0.4% of loads. Article 15(2): carriers missing either metric for two consecutive months are suspended from the pool. Article 15(3): driver mobile numbers kept for pool dispatch audits are personal data and must not leave the staffing share. κMT·11 grade codes are unrelated.

[Assistant] <think>N=0 ⇒ difficulty 5. Personal bans external 클라우드-Z9. 은둔-q4 allows personal, max_difficulty 5≥5, external false—select.</think>{"difficulty":5,"security":"personal","selection":"은둔-q4","reason_code":"ROUTE_OK_EXTERNAL_BAN","confidence":0.91}


물류/회의록/w50005-44 · 체선료통지책임

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] Who is named as the party that must issue demurrage notices when gate dwell exceeds forty-eight hours at Terminal Belwick? security=public. Model registry: (1) 솔개-m72 — context 4k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 5; (2) r-55 — context 4k, tools none, latency mid, cost low, security [public], external true, max_difficulty 4; (3) 갈매기-b1 — context 4k, tools none, latency low, cost low, security [public,internal], external false, max_difficulty 3. Input length for this query-plus-minutes pack is about 18k tokens. executor_trials(k=8): success 8 / fail 0. κMT·28 Article 5(1): when continuous gate dwell surpasses 48 hours, the demurrage notice is issued by the Terminal Control Desk, not by the carrier desk. Article 5(2): the shipper receives a copy only after the notice is logged. κMT·31 §4 defines tariff bands but does not reassign the notice issuer.

[Assistant] <think>Success 8 ⇒ difficulty 1. All three candidates max out at 4k context while input is ~18k, so every model fails the context check—ABSTAIN.</think>{"difficulty":1,"security":"public","selection":"ABSTAIN","reason_code":"ABSTAIN_CONTEXT","confidence":0.88}


[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] {"query":"Article 8, paragraph 2, subparagraph (c) leaves me unsure: what is the maximum number of route cards a registered Fenline survey team may carry during one eight-day count cycle? input_security=internal; context_summary=single numerical ceiling; model_registry=[p-73(ctx_limit=8192;tools=none;latency=low;cost=low;security=internal;external=false;max_difficulty=2), p-19(ctx_limit=12000;tools=lookup;latency=mid;cost=mid;security=public,internal;external=true;max_difficulty=3), p-44(ctx_limit=5000;tools=none;latency=low;cost=low;security=internal;external=false;max_difficulty=1)]; executor_trials(k=8): success 7 / fail 1","documents":[{"document_id":"CivicRune::05::Aqua","text":"Article 8, paragraph 1: A registered Fenline survey team receives route cards from its assigned coordinator."},{"document_id":"CivicRune::05::Beryl","text":"Article 8, paragraph 2, subparagraph (c): The team may carry no more than fourteen route cards during one eight-day count cycle."},{"document_id":"CivicRune::05::Cinder","text":"Article 8, paragraph 4: Unused cards return to the coordinator at cycle close."}]}

[Assistant] {"difficulty":2,"security":"internal","selection":"p-73","reason_code":"Selected p-73: internal is allowed, external=false, and max_difficulty=2 covers this route.","confidence":0.97}


공공정책/법령·고시/w50005-46 · queue notice cycle

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User] {"query":"At what interval must the Rellin clinic queue notice be refreshed under Article 9, paragraph 4, for a first-time reader? input_security=personal; context_summary=notice refresh period; model_registry=[x-46(ctx_limit=10240;tools=none;latency=low;cost=mid;security=personal;external=false;max_difficulty=2), x-12(ctx_limit=8192;tools=lookup;latency=mid;cost=low;security=public,personal;external=true;max_difficulty=3), x-88(ctx_limit=16000;tools=search;latency=high;cost=high;security=personal;external=false;max_difficulty=4)]; executor_trials(k=8): success 7 / fail 1","documents":[{"document_id":"CivicRune::06::Dawn","text":"Article 9, paragraph 1: The Rellin clinic queue notice identifies the current service band."},{"document_id":"CivicRune::06::Flint","text":"Article 9, paragraph 2: A notice clerk records each refresh in the patient-facing ledger."},{"document_id":"CivicRune::06::Gale","text":"Article 9, paragraph 3: A stale queue notice cannot be used to assign a service band."},{"document_id":"CivicRune::06::Honey","text":"Article 9, paragraph 4: The queue notice shall be refreshed every three service days."}]}

[Assistant] {"difficulty":2,"security":"personal","selection":"x-46","reason_code":"Selected x-46: personal is allowed, external=false, and max_difficulty=2 covers this route.","confidence":0.97}


공공정책/민원 안내문/w50005-47 · 수수료감면 승인권자

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
{"query":"Audit prep chatter — auditor intern: 'Who actually signs a full waiver of the re-issue fee for lost occupancy certificates?' desk lead: 'Not me. Check the internal authority matrix in the leaflet pack; titles matter.'","documents":[{"document_id":"CIV·K07/24w30-A","text":"Email excerpt: '50% reductions can be noted by the shift supervisor; full waivers are different — see matrix.'"},{"document_id":"CIV·K07/24w30-B","text":"Matrix talk-through (recorded): HR liaison — 'Full waiver of the re-issue fee for a lost occupancy certificate requires co-signature of the Civil Records Team Lead and the District Fee Integrity Officer. A lone supervisor stamp is invalid for 100% waiver.' Clerk — 'What about the mayor's office?' Liaison — 'Not on this matrix; do not escalate there for this fee type.'"},{"document_id":"CIV·K07/24w30-C","text":"Cashier cheat-sheet: stamp colors for paid / unpaid only."}]}
model_registry:
- id=r-17; ctx=32k; tools=false; latency=mid; cost=low; security_allow=public,internal,confidential; external=false; max_difficulty=4
- id=외부모래-9; ctx=128k; tools=true; latency=high; cost=high; security_allow=public,internal; external=true; max_difficulty=5
- id=느루-b2; ctx=8k; tools=true; latency=low; cost=mid; security_allow=internal; external=false; max_difficulty=2
executor_trials(k=8): success 6 / fail 2

[Assistant] {"difficulty":2,"security":"internal","selection":"r-17","reason_code":"TRIAL_N6_APPROVER","confidence":0.92}


공공정책/민원 안내문/w50005-48 · 보육지원 우선순위

[System] {"서브그래프":{"이름":"난이도-라우터","기능":"질의·보안·모델 레지스트리 기반 난이도 판단 및 모델 선택","버전":"v1.0","입력":"query, context_summary, security, model_registry[], executor_trials[]","출력":"routing JSON","도형":"diamond"}}

[User]
{"query":"Budget cell only — analyst: 'Slot list is oversubscribed. State the confidential priority ladder for the district childcare fee-support slots this fiscal window, as written for staff.' lead: 'Public site only says income. We need the staff ladder.'","documents":[{"document_id":"CIV·K08/24w30-A","text":"Public site: 'Support depends on income.' No ladder."},{"document_id":"CIV·K08/24w30-B","text":"Staff-only ladder brief: Budget officer — 'This fiscal window, fee-support slots rank as: (1) single-guardian households with night-shift proof on file, (2) dual-guardian households where both work outside a 5 km radius of the home center, (3) households already on the sealed housing-emergency list, (4) remaining income-tier applicants by lowest residual income score. Sibling count is a tie-break inside a tier only, never a standalone tier.' Analyst — 'Night-shift over dual-commute?' Officer — 'Yes, that is tier one versus two.'"},{"document_id":"CIV·K08/24w30-C","text":"Center capacity spreadsheet headers only."}]}
model_registry:
- id=솔개-h4; ctx=64k; tools=true; latency=high; cost=mid; security_allow=internal,confidential,personal; external=false; max_difficulty=5
- id=외부모래-8; ctx=128k; tools=true; latency=low; cost=high; security_allow=public,internal,confidential,personal; external=true; max_difficulty=5
- id=r-12; ctx=16k; tools=false; latency=mid; cost=low; security_allow=public,internal; external=false; max_difficulty=5
- id=느루-m3; ctx=32k; tools=false; latency=mid; cost=low; security_allow=confidential; external=false; max_difficulty=5
- id=구름-a7; ctx=8k; tools=true; latency=low; cost=low; security_allow=confidential,personal; external=false; max_difficulty=3
executor_trials(k=8): success 0 / fail 8

[Assistant] {"difficulty":5,"security":"confidential","selection":"솔개-h4","reason_code":"TRIAL_N0_CONF_PRIO","confidence":0.85}