의료·건강/약품 설명서/w50009-164 · 개봉후사용기한

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

[User] 현장 점검표와 대조 중이다. 개봉한 히말라시럽을 실온에 둔 뒤 몇 일까지 쓸 수 있는지 약설 조문만으로 확인해 달라. 약설〔κ11〕 제7조(개봉 후 안정성) ① 개봉 후 25℃ 이하 실온에서 14일 이내 사용한다. ② 14일을 넘기면 잔량은 폐기한다. 약설〔κ11〕 제8조 냉장 보관 시에도 개봉 후 기한은 동일하다. 약설〔κ19〕 제2조는 미개봉 유효기간만 다루며 개봉 후 기한은 규정하지 않는다. 보안 public. 레지스트리: 매-7b(컨텍스트 8k, 도구 없음, 지연 110ms, 비용 낮음, 보안 public·internal, 외부 false, 최대난도 3), 외부분석-q9(컨텍스트 32k, 도구 있음, 지연 700ms, 비용 높음, 보안 public, 외부 true, 최대난도 5), 다람-t3(컨텍스트 4k, 도구 없음, 지연 80ms, 비용 낮음, 보안 public, 외부 false, 최대난도 1), 구름-x1(컨텍스트 16k, 도구 있음, 지연 300ms, 비용 중, 보안 public·internal, 외부 false, 최대난도 4). executor_trials(k=8): 성공 8 / 실패 0

[Assistant] {"difficulty":1,"security":"public","selection":"다람-t3","reason_code":"성공8→난도1. 다람-t3가 public·외부false·최대난도1을 충족","confidence":0.94}


제품 사용/사용자 매뉴얼/w50009-165 · 도킹금지행위

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

[User]
협력 설치 팀입니다. 오르빗 도킹 스테이션 사용 시 금지 행위가 매뉴얼 어디에 있는지, 특히 전원 관련으로 무엇이 금지되는지 짚어 주세요.

현장 메모(구어) — 설치반장: "어댑터 아무거나 꽂아도 되지?" 품질: "κUM-15.1 금지 목록 읽어." 신규: "충전 중에 옮기면 안 된다던데."

κUM-03.0 개봉 및 배치 — 도킹 스테이션은 평평하고 통풍되는 면에 둔다. 직사광선은 피한다.

κUM-15.1 금지 행위 — (1) 비정품 24V 어댑터 연결 (2) 본체 도킹 중 스테이션을 물티슈로 젖은 채 닦기 (3) 스테이션 하단에 임의 방열판 부착. 특히 (1)은 내부 보호회로 손상의 주원인으로 명시된다.

κUM-15.2 권장 행위 — 정품 어댑터만 사용하고, 청소 시 전원을 분리한 뒤 마른 천을 사용한다.

κUM-30.9 FAQ — 도킹 LED가 빨강이면 재도킹을 시도한다. 금지 행위와 무관하다.

모델 레지스트리: ① id=매-n4 컨텍스트 16k 도구있음 지연낮음 비용저 보안허용=public,internal 외부=false 최대난도=3 ② id=제비-p1 컨텍스트 8k 도구없음 지연낮음 비용저 보안허용=public 외부=true 최대난도=2 ③ id=황조롱-7 컨텍스트 32k 도구있음 지연중간 비용중 보안허용=internal 외부=false 최대난도=4
executor_trials(k=8): 성공 8 / 실패 0

[Assistant] {"difficulty":1,"security":"internal","selection":"매-n4","reason_code":"EASY_INTERNAL_OK","confidence":0.95}


학술·연구/논문/w50009-166 · 교신저자변경승인

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

[User]
확인을 요청합니다. 게재 확정 후 교신저자를 변경할 때 최종 승인 권한이 누구에게 귀속되는지 조문으로 답해 주십시오.

논규〔μ〕제02호 제5조 교신저자 변경 신청은 기존 교신저자와 신규 교신저자가 공동 서명하여 편집국에 제출한다.
논규〔μ〕제02호 제6조 편집국은 서명 진위만을 확인하며 승인·반려 결정을 내리지 않는다.
논규〔μ〕제09호 제1조 게재 확정 후 저자 표기 변경의 최종 승인은 해당 호 책임편집위원이 행한다. 제2조 책임편집위원이 이해충돌인 경우 편집위원장이 대행한다.
논규〔μ〕제21호 제3조 출판사 계약 담당자는 승인 통보를 수령한 뒤에만 판권 페이지를 수정한다.

모델 레지스트리: 너울-c5(컨텍스트 20k, 도구 없음, 지연 110ms, 비용 중, 보안 허용 public·internal, 외부 여부 false, 최대 지원 난도 3); 해안-m70(컨텍스트 40k, 도구 지원, 지연 260ms, 비용 중, 보안 허용 public, 외부 여부 true, 최대 지원 난도 4); 조각-d2(컨텍스트 8k, 도구 없음, 지연 60ms, 비용 저, 보안 허용 public, 외부 여부 false, 최대 지원 난도 1).
executor_trials(k=8): 성공 7 / 실패 1

[Assistant] {"difficulty":2,"security":"public","selection":"너울-c5","reason_code":"trials7_maxd3_public","confidence":0.93}


의료·건강/약품 설명서/w50009-167 · 교차민감금지원칙

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

[User] 환자 개인 알레르기 이력과 맞춰, 베타락탐 교차민감이 있으면 본제 투여가 전면 금지인지 아니면 예외 투여 경로가 있는지 설명서 금지·예외 조항을 대조한다. 약설〔κ70〕 제4조(금기) ① 페니실린계 또는 세팔로스포린계에 중증 즉시형 과민반응 이력이 있는 환자에게 본제 투여를 금지한다. ② 피부 발진만의 경증 이력은 알레르기 전문의 입회 하에 시험량 투여 후 유지 가능. ③ 교차민감 평가 기록은 투약 전 의무 첨부. 약설〔κ70〕 제5조 이상반응 보고 절차. 약설〔κ14〕 일반 주의는 구체 성분명을 적지 않는다. 보안 personal. 레지스트리: 공개-대(컨텍스트 64k, 도구 있음, 지연 800ms, 비용 높음, 보안 public·internal·confidential·personal, 외부 true, 최대난도 5), 담장-내5(컨텍스트 20k, 도구 있음, 지연 360ms, 비용 중, 보안 confidential·personal, 외부 false, 최대난도 5), 이슬-m0(컨텍스트 8k, 도구 없음, 지연 110ms, 비용 낮음, 보안 public·internal, 외부 false, 최대난도 2), 감나무-p2(컨텍스트 12k, 도구 없음, 지연 200ms, 비용 중, 보안 personal, 외부 false, 최대난도 4). executor_trials(k=8): 성공 2 / 실패 6

[Assistant] {"difficulty":4,"security":"personal","selection":"감나무-p2","reason_code":"성공2→난도4. personal은 외부모델 금지, 감나무-p2 외부false·personal·최대난도4","confidence":0.87}


개인 기록/일기·가계부·독서노트/w50010-1 · 첨부자료보관순서

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

[User] A reader may ask how to archive the attachments to a weekly diary entry; which sequence does Article 6 require? Document folio⟦V7⟧/cinder/21 identifies the entry date as 2099-01-31. Document folio⟦V7⟧/cinder/22 states in Article 3(2) that the sequence is checksum, title tag, image bundle, then access note. Document folio⟦V7⟧/cinder/23 says a missing image bundle pauses the archive. Registry: s-47 [context=1400 tokens; tools=diary,archive; latency=160ms; cost=low; security=internal; external=false; max_difficulty=2] | k-82 [context=1800 tokens; tools=archive; latency=205ms; cost=medium; security=public,internal; external=true; max_difficulty=2]. executor_trials(k=8): success 5 / fail 3

[Assistant] {"difficulty":3,"security":"internal","selection":"ABSTAIN","reason_code":"All candidates fail: every maximum supported difficulty is 2, below required difficulty 3.","confidence":0.98}


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

[User]
After primary page failure, who is contacted next on the platform on-call path in SOP::RTR-Ω104—need exact sequence steps. security=internal. Tools required: calendar lookup for secondary roster.

SOP::RTR-Ω104 On-Call Escalation Sequence
1) Primary phone via PagerMesh (2 attempts, 3 minutes apart)
2) Secondary phone from roster calendar cal://oncall/platform
3) Incident Commander of the week (IC-week role), SMS then voice
4) Director-on-deck only after 20 minutes total without ack
- Never escalate to CEO bridge from this SOP
- Cross-team pull-in for payments uses a separate SOP and must not reorder steps 1–3

SOP::RTR-Ω100 Roster Hygiene
- Secondary must not equal primary person_id

Model registry:
- id=mute-tools | ctx=64k | tools=none | latency=low | cost=0.5 | security_allow=[public,internal] | external=false | max_difficulty=5
- id=sql-only | ctx=80k | tools=sql | latency=med | cost=0.9 | security_allow=[internal,confidential] | external=false | max_difficulty=5
- id=web-out | ctx=72k | tools=json,web | latency=med | cost=1.0 | security_allow=[internal] | external=true | max_difficulty=5
executor_trials(k=8): success 0 / fail 8

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


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

[User] Among tenant classes, which restore queue is supposed to run first after a region outage? I am still mapping DR vocabulary. Public FAQ draft NEX·memo/24-W27: restore priority is paying enterprise → trial growth → free hobby, and billing-export jobs wait until enterprise RPO is green. A volunteer note says hobby can jump the queue if marketing asks — not in the numbered list. Query needs a live http probe tool against status mirrors plus search. Model registry: dune-s4 context 32k tools [search,code] latency 800ms cost mid security_allow [public,internal] external true max_difficulty 4; dune-s5 context 40k tools [search,json] latency 950ms cost mid security_allow [public] external true max_difficulty 3; 내부경량-4 context 24k tools [code] latency 500ms cost low security_allow [public,internal] external false max_difficulty 5. executor_trials(k=8): success 7 / fail 1

[Assistant] {"difficulty":2,"security":"public","selection":"ABSTAIN","reason_code":"Required http tool is missing on every candidate (search/code/json/code only), so all models fail the tool-support gate.","confidence":0.91}


개인 기록/일기·가계부·독서노트/w50010-4 · 가계부공유금지시점

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

[User] An auditor might challenge whether the household ledger may be shared before the quarterly seal; which action is forbidden? Document folio⟦V7⟧/cinder/35 defines the quarterly seal date as 2098-12-17 in Article 1(1). Document folio⟦V7⟧/cinder/36 permits an internal review before sealing. Document folio⟦V7⟧/cinder/37 lists two approved readers. Document folio⟦V7⟧/cinder/38 states in Article 6(2) that sending the ledger outside the approved readers before the seal is forbidden, while an in-room review is permitted. Registry: b-12 [context=3000 tokens; tools=ledger; latency=240ms; cost=high; security=confidential; external=true; max_difficulty=5] | yarrow-69 [context=3200 tokens; tools=ledger; latency=280ms; cost=high; security=confidential,internal; external=true; max_difficulty=5]. executor_trials(k=8): success 1 / fail 7

[Assistant] {"difficulty":5,"security":"confidential","selection":"ABSTAIN","reason_code":"All candidates fail: every candidate has external=true, which is forbidden for confidential input.","confidence":0.99}


개인 기록/일기·가계부·독서노트/w50010-5 · 부채기록수정금지

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

[User] Before I quote the correction rule, which action is forbidden when a debt entry has already been closed? Document folio⟦V7⟧/cinder/24 defines a closed debt entry in Article 1(2) as one with a settled marker. Document folio⟦V7⟧/cinder/25 states in Article 4(3) that overwriting the settled amount is forbidden; a new adjustment note must be appended instead. Registry: nacre-33 [context=1900 tokens; tools=ledger; latency=233ms; cost=medium; security=confidential,personal; external=false; max_difficulty=4] | j-60 [context=1700 tokens; tools=none; latency=145ms; cost=low; security=internal; external=false; max_difficulty=3] | q-11 [context=2200 tokens; tools=ledger; latency=280ms; cost=high; security=public,confidential; external=true; max_difficulty=5]. executor_trials(k=8): success 5 / fail 3

[Assistant] {"difficulty":3,"security":"confidential","selection":"nacre-33","reason_code":"selected nacre-33; it allows confidential security, supports difficulty 3, and external=false.","confidence":0.95}


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

[User] By what calendar deadline must a customer file an SLA credit claim after an uptime miss? First week reading commercial docs. Public policy clip NEX·memo/24-W41: claims must arrive within 30 days of the invoice that covers the outage month, not from the outage day itself. Partner-resold accounts file through the partner within 20 days. A blog draft saying "anytime same quarter" is unlabeled and non-authoritative. Model registry: toy-d1 context 32k tools [search,code] latency 800ms cost low security_allow [public,internal] external true max_difficulty 2; toy-d2 context 24k tools [search] latency 600ms cost low security_allow [public] external true max_difficulty 1; toy-d3 context 40k tools [json] latency 900ms cost mid security_allow [public,internal,confidential] external false max_difficulty 2. executor_trials(k=8): success 2 / fail 6

[Assistant] {"difficulty":4,"security":"public","selection":"ABSTAIN","reason_code":"Need difficulty 4 from trials, but max_difficulty is 2/1/2 on all three models, so every candidate fails the max-difficulty gate.","confidence":0.94}


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

[User] Can someone walk me through how often failed webhooks get retried before they are dropped? I only just joined the integrations desk. From stand-up transcript NEX·memo/24-W11, Ola: first retry at 30s, then 2m, then 15m, then stop — four attempts total including the original. Theo: dead-letter only if the merchant toggled soft-fail; otherwise permanent 410 ends the chain early. Side chat mentions a daily digest of dead letters at 06:00 UTC. Model registry: pike-r41 context 24k tools [search,http] latency 900ms cost mid security_allow [public,internal] external false max_difficulty 4; r-17 context 48k tools [search,code] latency 1.1s cost mid security_allow [public,internal,confidential] external false max_difficulty 5; 구름-lite context 12k tools [search] latency 350ms cost low security_allow [public] external true max_difficulty 2; atlas-u9 context 32k tools [search,json] latency 700ms cost low security_allow [internal] external false max_difficulty 3. executor_trials(k=8): success 8 / fail 0

[Assistant] {"difficulty":1,"security":"internal","selection":"pike-r41","reason_code":"pike-r41 allows internal, external false, max_difficulty 4>=1, tools include search for memo lookup.","confidence":0.95}


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

[User]
Confirm the idle and absolute session ceilings for workforce SSO that holds personal profile claims, citing SOP::RTR-Ω110 numbers only. security=personal.

SOP::RTR-Ω110 Workforce SSO Session Ceilings
- Idle timeout: 28 minutes without user event
- Absolute lifetime: 8 hours from initial authn, even if active
- Step-up reauth required after 4 hours when scope includes payroll_view or health_proxy claims
- Remember-me cookies: disabled for any browser marked managed=false
- Service accounts: not covered; use machine-token SOP instead

SOP::RTR-Ω111 Device Posture
- Jailbroken mobile forces immediate revoke independent of timers

SOP::RTR-Ω07 UX Copy
- Timeout banner text samples only

SOP::RTR-Ω19 Related Metrics
- Dashboard tracks forced_logout_count; not policy

Model registry:
- id=내벽-s5 | ctx=88k | tools=json | latency=med | cost=1.2 | security_allow=[internal,confidential,personal] | external=false | max_difficulty=5
- id=cloud-far | ctx=120k | tools=json,retrieve | latency=high | cost=2.2 | security_allow=[public,internal,personal] | external=true | max_difficulty=5
- id=pin-lite | ctx=32k | tools=none | latency=low | cost=0.35 | security_allow=[public,internal] | external=false | max_difficulty=2
- id=helix-m | ctx=60k | tools=json | latency=low | cost=0.8 | security_allow=[personal] | external=false | max_difficulty=4
- id=dust-0 | ctx=45k | tools=sql | latency=med | cost=0.7 | security_allow=[internal,personal] | external=false | max_difficulty=3
executor_trials(k=8): success 1 / fail 7

[Assistant] {"difficulty":5,"security":"personal","selection":"내벽-s5","reason_code":"ROUTE_OK_INTERNAL","confidence":0.88}


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

[User]
Could you condense the retention rules in SOP::RTR-Ω22 and SOP::RTR-Ω31 so I can verify audit log day counts before the quarterly control check? security=internal.

SOP::RTR-Ω22 Audit Log Retention
- authn_success: 90 calendar days hot, then 275 days cold, total 365
- authn_failure: 180 days hot only; no cold tier
- admin_config_change: 730 days immutable WORM bucket
- debug_trace: 14 days; auto-purge without ticket

SOP::RTR-Ω31 Product Telemetry Overlap
| stream | hot days | cold days |
| app_perf | 30 | 60 |
| billing_meter | 120 | 245 |
Note: billing_meter cold must not be shorter than authn_success total window

SOP::RTR-Ω05 Out of Scope Memo
- Customer chat transcripts follow a separate legal hold SOP and are not listed here

Model registry:
- id=nebula-q9 | ctx=48k | tools=json | latency=med | cost=0.9 | security_allow=[public,internal] | external=false | max_difficulty=3
- id=terrapin-3 | ctx=200k | tools=json,retrieve | latency=high | cost=2.1 | security_allow=[internal,confidential] | external=false | max_difficulty=5
- id=haze-88 | ctx=24k | tools=none | latency=low | cost=0.3 | security_allow=[public] | external=true | max_difficulty=2
- id=oak-lane | ctx=96k | tools=sql | latency=med | cost=1.0 | security_allow=[public,internal] | external=true | max_difficulty=4
- id=mint-r2 | ctx=32k | tools=json | latency=low | cost=0.5 | security_allow=[internal] | external=false | max_difficulty=2
executor_trials(k=8): success 8 / fail 0

[Assistant] {"difficulty":1,"security":"internal","selection":"nebula-q9","reason_code":"ROUTE_OK","confidence":0.94}


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

[User]
Cross-checking the credit table: when availability and latency both breach in one month, which metric’s credit percentage is applied first per SOP::RTR-Ω63? security=internal.

SOP::RTR-Ω63 Multi-Metric Credit Priority
- Metrics: availability_pct, p99_latency_ms, error_budget_burn
- If two or more breach the same month, apply only the single highest credit row; do not stack
- Priority to select the row: error_budget_burn > availability_pct > p99_latency_ms
Credit rows:
| metric breach | monthly credit |
| availability < 99.5% | 10% |
| availability < 99.0% | 25% |
| p99_latency > 800ms for ≥5% samples | 8% |
| error_budget_burn ≥ 100% | 15% |
| error_budget_burn ≥ 200% | 30% |

SOP::RTR-Ω64 Cap
- Absolute credit ceiling per invoice: 45% even if tables suggest more

Model registry:
- id=folio-a1 | ctx=36k | tools=json | latency=low | cost=0.55 | security_allow=[public,internal] | external=false | max_difficulty=3
- id=zephyr-9 | ctx=90k | tools=json,code | latency=med | cost=1.3 | security_allow=[internal] | external=true | max_difficulty=4
- id=nimbus-t | ctx=20k | tools=none | latency=low | cost=0.25 | security_allow=[public] | external=true | max_difficulty=1
- id=basalt-2 | ctx=64k | tools=sql | latency=med | cost=0.95 | security_allow=[public,internal,confidential] | external=false | max_difficulty=5
- id=quill-r | ctx=48k | tools=json | latency=low | cost=0.6 | security_allow=[internal] | external=false | max_difficulty=2
executor_trials(k=8): success 6 / fail 2

[Assistant] {"difficulty":2,"security":"internal","selection":"folio-a1","reason_code":"ROUTE_OK","confidence":0.92}


학술·연구/논문/w50010-11 · 익명화 연결키 금지

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

[User]
FAQ 초안에 ‘연결키를 공동연구자 메일에 첨부해도 된다’고 썼는데 금지 사항과 맞는지 확인해 달라.

원문쪽 ⌈Λ24-70⌋ 익명화·연결키 취급
· 금지: 연결키를 분석용 데이터셋과 동일 채널로 전송
· 금지: 개인 이메일·메신저로 연결키 송부
· 허용: 기관 보안폴더(권한 분리)에 연결키 단독 보관
· 허용: 키 관리 책임자 1인만 다운로드

원문쪽 ⌈Λ24-71⌋ 위반 시
· 즉시 접근 차단, 윤리사무 보고 24시간 이내

모델 레지스트리:
- id=외곽-v5: 컨텍스트 48k, 도구 있음, 지연 380ms, 비용 높음, 보안허용 public·internal·confidential·personal, 외부 true, 최대난도 5
- id=금고-i3: 컨텍스트 24k, 도구 없음, 지연 140ms, 비용 중간, 보안허용 internal·confidential·personal, 외부 false, 최대난도 4
- id=r-09: 컨텍스트 12k, 도구 없음, 지연 90ms, 비용 낮음, 보안허용 public·internal, 외부 true, 최대난도 3
executor_trials(k=8): 성공 5 / 실패 3

[Assistant] {"difficulty":3,"security":"personal","selection":"금고-i3","reason_code":"성공5→난도3. personal 허용·외부false로 외곽-v5 배제, 금고-i3 선택","confidence":0.93}


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

[User]
For dual-signal incidents, which severity class takes priority when error-rate and customer-report thresholds fire together—need SOP::RTR-Ω81 rule, not industry defaults. security=public.

SOP::RTR-Ω81 Dual-Signal Severity Priority
- Signals: ERR-RATE (≥5% 5m), CUST-RPT (≥12 unique orgs / 30m), SYNTH-FAIL (3 regions)
- If ERR-RATE and CUST-RPT both true: declare Sev-Orange (not Sev-Yellow)
- If SYNTH-FAIL alone: Sev-Yellow
- If all three true: Sev-Red and page Primary+Shadow
- Sev-Orange requires customer comms template T-ORANGE within 45 minutes
- Explicit: raw CPU saturation without the above signals stays Sev-Blue

SOP::RTR-Ω15 Comms Matrix (partial)
- Sev-Red bridge is mandatory; Sev-Orange bridge optional

Model registry:
- id=pixel-4 | ctx=64k | tools=json | latency=low | cost=0.7 | security_allow=[public] | external=true | max_difficulty=2
- id=canoe-7 | ctx=80k | tools=json,code | latency=med | cost=1.0 | security_allow=[public,internal] | external=true | max_difficulty=3
- id=moss-t | ctx=48k | tools=none | latency=low | cost=0.4 | security_allow=[public] | external=false | max_difficulty=3
executor_trials(k=8): success 2 / fail 6

[Assistant] {"difficulty":4,"security":"public","selection":"ABSTAIN","reason_code":"ABSTAIN_DIFF","confidence":0.87}


개인 기록/일기·가계부·독서노트/w50010-13 · 알림충돌우선순위

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

[User] For teaching purposes, which item has priority when a medication reminder conflicts with a reading reminder? Document folio⟦V7⟧/cinder/26 lists in Article 1(1) the two reminder classes. Document folio⟦V7⟧/cinder/27 assigns the first alert to the reading shelf. Document folio⟦V7⟧/cinder/28 states in Article 5(2) that a health-related reminder takes priority over a reading reminder, while a missed reading reminder is moved to the next review. Document folio⟦V7⟧/cinder/29 limits one rescheduling attempt. Registry: z-36 [context=2000 tokens; tools=diary; latency=219ms; cost=medium; security=public,internal; external=true; max_difficulty=3] | aster-74 [context=2100 tokens; tools=none; latency=172ms; cost=low; security=public; external=true; max_difficulty=3] | p-05 [context=1800 tokens; tools=diary; latency=190ms; cost=medium; security=confidential; external=false; max_difficulty=4]. executor_trials(k=8): success 3 / fail 5

[Assistant] {"difficulty":4,"security":"public","selection":"ABSTAIN","reason_code":"All candidates fail: every maximum supported difficulty is 3, below required difficulty 4.","confidence":0.98}


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

[User]
Give me a short rundown of export bans for tenant warehouse extracts in SOP::RTR-Ω77 so I can mark the compliance checklist. security=confidential.

SOP::RTR-Ω77 Tenant Extract Prohibitions
- Forbidden without Legal ticket LX-*: full table dump of identities, raw payment PANs, free-text support notes containing medical keywords list M-KW-9
- Forbidden always (no ticket path): shipping extracts to personal email domains, attaching extracts to public ticket portals, loading extracts into unmanaged notebooks outside VPC-Notebook-B
- Allowed with dual control: hashed user_id + aggregate metrics only, watermark field wm_tenant required
- Region lock: eu-south-m4 extracts may not land in us-* buckets

SOP::RTR-Ω78 Tooling
- Approved transfer tool: RelayBox-4 only
- SFTP to customer is allowed only if RelayBox-4 job id is recorded

Model registry:
- id=vault-line | ctx=96k | tools=json,retrieve | latency=med | cost=1.5 | security_allow=[internal,confidential] | external=false | max_difficulty=5
- id=prairie-2 | ctx=64k | tools=json | latency=low | cost=0.8 | security_allow=[public,internal] | external=true | max_difficulty=4
- id=ember-k9 | ctx=40k | tools=none | latency=low | cost=0.4 | security_allow=[confidential,personal] | external=false | max_difficulty=3
- id=ridge-o | ctx=24k | tools=json | latency=med | cost=0.45 | security_allow=[public,internal,confidential] | external=false | max_difficulty=2
executor_trials(k=8): success 5 / fail 3

[Assistant] {"difficulty":3,"security":"confidential","selection":"vault-line","reason_code":"ROUTE_OK_INTERNAL","confidence":0.89}


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

[User] How frequently can a workspace admin reassign floating seats without waiting for a cool-down, according to the public admin guide fragments? Brand new to seat admin. NEX·memo/24-W50: floating seats may be reassigned at most once per 7-day cool-down per seat id; bulk CSV reassignment still respects the same per-seat clock. Annual locked seats never float mid-term. A community post claiming daily free moves is outside our docs. Model registry: seat-r6 context 22k tools [search] latency 550ms cost low security_allow [public,internal] external true max_difficulty 3; 솔개-pub context 40k tools [search,code,json] latency 1.0s cost mid security_allow [public] external true max_difficulty 5; 내부경량-15 context 16k tools [search] latency 400ms cost low security_allow [public,internal] external false max_difficulty 4; r-plaid context 48k tools [search,http] latency 1.2s cost mid security_allow [public,internal,confidential] external false max_difficulty 5; mist-o context 12k tools [] latency 300ms cost low security_allow [public] external true max_difficulty 2. executor_trials(k=8): success 1 / fail 7

[Assistant] {"difficulty":5,"security":"public","selection":"솔개-pub","reason_code":"솔개-pub allows public, external true is fine for public, max_difficulty 5>=5, tools cover search/code for the guide text.","confidence":0.9}


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

[User] How long do we keep application audit logs before purge, based on the storage runbook bits below? Fresh to compliance tooling. NEX·memo/24-W05: Vee said default app audit trails stay 90 days hot then 180 days cold, total 270 before delete. Nico: security-critical auth events extend cold storage another 90 days. The chat log also jokes about infinite keep for demo tenants — marked non-binding. Model registry: lynx-p2 context 32k tools [search] latency 750ms cost low security_allow [public,internal] external false max_difficulty 3; r-quartz context 20k tools [search,code,json] latency 900ms cost mid security_allow [internal,confidential] external false max_difficulty 4; 매-external-1 context 48k tools [search,http] latency 1.3s cost mid security_allow [public,internal,confidential] external true max_difficulty 5. executor_trials(k=8): success 6 / fail 2

[Assistant] {"difficulty":2,"security":"internal","selection":"lynx-p2","reason_code":"lynx-p2 allows internal, external false, max_difficulty 3>=2, enough context for the short runbook excerpt.","confidence":0.92}


개인 기록/일기·가계부·독서노트/w50010-17 · 식비장부공유금지

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

[User] I need to explain whether Article 4 forbids forwarding a grocery ledger excerpt to a bulletin. Document folio⟦V7⟧/cinder/03 records in Article 1(2) that the excerpt may be shown during a household review. Document folio⟦V7⟧/cinder/04 limits the audience to two named readers. Document folio⟦V7⟧/cinder/05 states in Article 4(1) that forwarding the excerpt to any bulletin is prohibited, even after the review closes. Registry: r-83 [context=1300 tokens; tools=ledger; latency=140ms; cost=low; security=internal,confidential; external=false; max_difficulty=3] | t-21 [context=1300 tokens; tools=ledger,diary; latency=170ms; cost=medium; security=internal; external=true; max_difficulty=2]. executor_trials(k=8): success 8 / fail 0

[Assistant] {"difficulty":1,"security":"public","selection":"ABSTAIN","reason_code":"All candidates fail: none permits public security.","confidence":0.99}


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

[User] I'm brand new to gateway ops and the jargon still blurs together. What burst ceiling does the public REST path allow inside one rolling minute in these notes? Hallway capture NEX·memo/24-W03: Mira said the steady rate is 120 req/min but the burst token bucket tops at 40 extra only on the /v2/public routes, while /v2/partner stays at 10 burst. Ken later added that weekly recompute jobs ignore burst entirely. A sticky note under the same memo claims partner routes inherit public burst after sunset — no one confirmed that line. Model registry: r-kestrel-3 context 32k tools [search,code] latency 800ms cost low security_allow [public,internal] external true max_difficulty 4; 솔개-m12 context 64k tools [search,code,json] latency 1.2s cost mid security_allow [public,internal,confidential] external false max_difficulty 5; nebula-q7 context 16k tools [search] latency 400ms cost low security_allow [public] external true max_difficulty 3; 내부경량-2 context 8k tools [] latency 200ms cost low security_allow [public,internal] external false max_difficulty 2. executor_trials(k=8): success 8 / fail 0

[Assistant] {"difficulty":1,"security":"public","selection":"솔개-m12","reason_code":"Pick 솔개-m12: public allowed, external false ok for public, max_difficulty 5>=1, context 64k covers memo pack.","confidence":0.96}


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

[User] If a contractor only holds the "reader-plus" seat, which OAuth scopes are they actually allowed to request? This is my first pass through our identity personal-data annex. NEX·memo/24-W31 (personal): reader-plus may request profile.read and calendar.busy but must never request billing.write or directory.export. Full staff seats unlock directory.export after manager attestation. Margin scribble from HR lists personal email as the token subject claim. Model registry: 솔개-priv context 48k tools [search,code] latency 1.1s cost mid security_allow [internal,confidential,personal] external false max_difficulty 4; r-glass context 64k tools [search,http] latency 1.5s cost high security_allow [public,internal,confidential,personal] external true max_difficulty 5; 내부경량-7 context 16k tools [search] latency 420ms cost low security_allow [personal] external false max_difficulty 2; nest-c1 context 28k tools [search,json] latency 700ms cost mid security_allow [public,internal] external false max_difficulty 3. executor_trials(k=8): success 5 / fail 3

[Assistant] {"difficulty":3,"security":"personal","selection":"솔개-priv","reason_code":"솔개-priv allows personal, external false under personal hard-rule, max_difficulty 4>=3.","confidence":0.94}


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

[User] If an idle browser tab is left open after lunch, when does the SSO session actually expire under the current write-up? Newbie here on identity. Pasted pack from NEX·memo/24-W18 plus two addenda and a long table of region overrides (~28k tokens of quoted policy text). Rina: idle timeout is 45 minutes for standard seats; force re-auth at 12 hours wall clock even if active. Jules: admin seats cut idle to 20 minutes. Appendix lists per-region cookie names and clock skew rules. Model registry: mote-a1 context 8k tools [search] latency 300ms cost low security_allow [public,internal] external true max_difficulty 5; mote-a2 context 4k tools [search,code] latency 250ms cost low security_allow [public] external true max_difficulty 4; mote-a3 context 6k tools [json] latency 280ms cost low security_allow [public,internal,confidential] external false max_difficulty 5. executor_trials(k=8): success 8 / fail 0

[Assistant] {"difficulty":1,"security":"public","selection":"ABSTAIN","reason_code":"All three candidates cap context at 8k/4k/6k while the quoted pack is ~28k tokens, so every model fails the context-window check.","confidence":0.93}


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

[User] If we are inside a personal-data schema freeze window, how often does the freeze calendar refresh and when does the next open slot appear? Learning migration ops slowly. Personal-store annex NEX·memo/24-W36: freezes run every other Tuesday 00:00–24:00 UTC covering user_profile and consent tables; the freeze roster republishes every Monday 16:00 UTC for the coming fortnight; emergency DDL needs dual VP approval. Corridor chat about "freeze Fridays" is informal only. Model registry: 사내-schema context 44k tools [search,code,json] latency 1.0s cost mid security_allow [confidential,personal] external false max_difficulty 5; r-wave context 30k tools [search] latency 700ms cost mid security_allow [public,internal,personal] external true max_difficulty 4; 내부경량-11 context 18k tools [search] latency 450ms cost low security_allow [internal,personal] external false max_difficulty 3; folio-p context 52k tools [search,http] latency 1.2s cost high security_allow [personal] external false max_difficulty 4. executor_trials(k=8): success 3 / fail 5

[Assistant] {"difficulty":4,"security":"personal","selection":"사내-schema","reason_code":"사내-schema allows personal, external false, max_difficulty 5>=4; r-wave dropped for external true on personal data.","confidence":0.92}


교육·학습/강의 노트/w50010-22 · 학습로그외부전송

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

[User]
LMS 개인 학습 로그를 외부 분석 업체에 보내도 되는 건지, 금지 사항이 노트에 명시돼 있는지 확인해야 합니다. personal·고난도 질의.

구술: 한 데이터담당. κ노트·47 학습로그 취급. 문장—‘식별 가능한 개인 학습 로그의 교외 제3자 전송 금지. 집계 통계만 연구처 사전 승인 후 가능.’ 배 조교: 교내 다른 학과 이관은 학생 동의서 받고 가능, 외부 업체는 동의서로도 불가. κ노트·10 출석 로그와 구분. 한 담당: 금지 핵심은 식별 가능 로그의 교외 전송.

모델 레지스트리: [{"id":"봉화-i4","ctx":28k,"tools":["검색","요약"],"latency_ms":620,"cost":0.05,"security_allow":["internal","personal","confidential"],"external":false,"max_diff":5},{"id":"원정-77","ctx":100k,"tools":["검색","요약","코드"],"latency_ms":1500,"cost":0.18,"security_allow":["public","personal"],"external":true,"max_diff":5},{"id":"골목-m8","ctx":18k,"tools":["검색"],"latency_ms":480,"cost":0.04,"security_allow":["public","internal","personal"],"external":false,"max_diff":4},{"id":"창가-t1","ctx":12k,"tools":["요약"],"latency_ms":360,"cost":0.02,"security_allow":["personal"],"external":false,"max_diff":3},{"id":"사막-c6","ctx":8k,"tools":[],"latency_ms":190,"cost":0.01,"security_allow":["public"],"external":false,"max_diff":2}]
executor_trials(k=8): 성공 3 / 실패 5

[Assistant] {"difficulty":4,"security":"personal","selection":"봉화-i4","reason_code":"성공3→난도4. 봉화-i4 personal 허용·external false·max_diff5≥4(원정-77은 외부 금지로 제외)","confidence":0.91}


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

[User]
May a contractor with only badge level C2 open Customer Vault browse mode under SOP::RTR-Ω92, or is a higher qualification required? security=confidential.

SOP::RTR-Ω92 Customer Vault Qualifications
- Browse mode (metadata only): requires badge C3 or employee E-grade, plus course CV-201 completed ≤12 months
- Object read (content): requires badge C4 and dual sponsorship from Vault Steward + account CSM
- Contractors at C2 or below: denied both browse and read; ticket auto-reject code VAULT-DENY-C2
- Temporary raise to C3 needs 5 business days lead time; same-day elevates prohibited

SOP::RTR-Ω93 Steward Roster
- Vault Steward is role code VS-Ω, not engineering manager

Model registry:
- id=outer-q | ctx=100k | tools=json,retrieve | latency=med | cost=1.6 | security_allow=[public,internal,confidential] | external=true | max_difficulty=5
- id=glass-w | ctx=64k | tools=json | latency=low | cost=0.9 | security_allow=[public,internal] | external=false | max_difficulty=4
- id=far-edge | ctx=80k | tools=json,code | latency=high | cost=1.9 | security_allow=[confidential,personal] | external=true | max_difficulty=5
executor_trials(k=8): success 3 / fail 5

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


개인 기록/일기·가계부·독서노트/w50010-24 · 취미구매월한도

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

[User] My summary must state the numeric monthly ceiling for hobby purchases. Document folio⟦V7⟧/cinder/17 describes in Article 1(1) a hobby purchase as a nonessential item bought for the personal shelf. Document folio⟦V7⟧/cinder/18 records a review threshold of 62 units. Document folio⟦V7⟧/cinder/19 distinguishes gifts from hobby purchases. Document folio⟦V7⟧/cinder/20 states in Article 5(1) that the monthly ceiling is 217 units, with unused capacity expiring at month end. Registry: harbor-x9 [context=1700 tokens; tools=ledger; latency=201ms; cost=medium; security=public,internal; external=true; max_difficulty=3] | l-14 [context=1500 tokens; tools=none; latency=124ms; cost=low; security=public; external=true; max_difficulty=2] | cinder-52 [context=2100 tokens; tools=ledger; latency=260ms; cost=high; security=confidential; external=false; max_difficulty=4]. executor_trials(k=8): success 5 / fail 3

[Assistant] {"difficulty":3,"security":"public","selection":"harbor-x9","reason_code":"selected harbor-x9; it allows public security, supports difficulty 3, and external=true.","confidence":0.94}


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

[User]
Need to confirm against SOP::RTR-Ω14 which rate class wins when a tenant trips two concurrent caps in the same minute. security=public.

SOP::RTR-Ω14 Platform Rate Classes
- Class Amber: 120 req/min per key; soft warn only
- Class Crimson: 40 req/min per key; hard drop after burst token=0
- Class Glacier: partner batch; 8 req/min fixed window
Priority when two classes bind the same key in one window:
1) Crimson hard-drop rule applies first
2) Glacier floor applies second if still over
3) Amber warn is informational only and never overrides drop
Conflict note: dual-cap events log tag RATE-DUAL; billing continues on successful calls only

SOP::RTR-Ω09 Edge Cache Notes (excerpt)
- Cache hit does not count against Crimson tokens
- Glacier partners cannot opt out of fixed window

Model registry:
- id=kite-n4 | ctx=32k | tools=none | latency=low | cost=0.4 | security_allow=[public,internal] | external=true | max_difficulty=3
- id=솔개-m72 | ctx=128k | tools=json,sql | latency=med | cost=1.2 | security_allow=[public,internal,confidential] | external=false | max_difficulty=5
- id=r-17 | ctx=64k | tools=json | latency=low | cost=0.7 | security_allow=[public] | external=true | max_difficulty=4
- id=내부경량-2 | ctx=16k | tools=none | latency=low | cost=0.2 | security_allow=[public,internal] | external=false | max_difficulty=2
executor_trials(k=8): success 8 / fail 0

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


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

[User]
Please organize the RTO priority matrix for multi-service restore when two product lines fail together; source is SOP::RTR-Ω99 only. security=public.

SOP::RTR-Ω99 Restore Priority Matrix
- Product lines: LedgerLite, SignalBay, MapNest
- When two lines fail: restore order is LedgerLite → SignalBay → MapNest regardless of ticket open time
- RTO targets: LedgerLite 30m, SignalBay 2h, MapNest 8h
- Shared dependency bus EventSpine restores before any product line
- Exception: regulatory hold REG-HOLD-* freezes LedgerLite restore until counsel clears; then SignalBay jumps first
- Staffing: at least one Restore Captain certified RC-7 must be on bridge before EventSpine cutover

SOP::RTR-Ω08 Drill Schedule
- Quarterly game day; does not alter live priority

SOP::RTR-Ω21 Naming
- Backup sets labeled bak::{service}::{utc_date}

Model registry:
- id=thin-ctx | ctx=16k | tools=json | latency=low | cost=0.3 | security_allow=[public,internal] | external=true | max_difficulty=4
- id=brief-z | ctx=20k | tools=none | latency=low | cost=0.25 | security_allow=[public] | external=false | max_difficulty=3
executor_trials(k=8): success 1 / fail 7

[Assistant] {"difficulty":5,"security":"public","selection":"ABSTAIN","reason_code":"ABSTAIN_DIFF","confidence":0.86}


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

[User]
Please summarize the rotation backlog priority from SOP::RTR-Ω55 so we can clear overdue vault items without guessing order. security=confidential.

SOP::RTR-Ω55 Secret Rotation Backlog
- Tier S0 (payment HSM keys): max age 30 days; backlog priority score = 100
- Tier S1 (service-to-service mTLS): max age 60 days; score = 70
- Tier S2 (webhook signing): max age 90 days; score = 40
- When overdue days ≥ 7, add +25 to score before sorting
- Same score: rotate smallest blast_radius_region first (list: eu-west-n2 < ap-south-k1 < us-central-p3)
- Never rotate S0 and S1 in the same 15-minute change slot

SOP::RTR-Ω12 Operator Notes
- Rotation tickets use prefix ROT-; manual bypass void after 48h
- Dry-run flag --shadow does not reset max-age clock

SOP::RTR-Ω60 Related Prohibitions
- Exporting live S0 material to chat tools is forbidden (see separate ban list)

Model registry:
- id=glint-7b | ctx=64k | tools=json | latency=med | cost=1.1 | security_allow=[public,internal] | external=true | max_difficulty=4
- id=요새-p3 | ctx=128k | tools=json,retrieve | latency=med | cost=1.4 | security_allow=[internal,confidential,personal] | external=false | max_difficulty=5
- id=drift-19 | ctx=32k | tools=none | latency=low | cost=0.4 | security_allow=[confidential] | external=true | max_difficulty=3
- id=pebble-c | ctx=48k | tools=json | latency=low | cost=0.7 | security_allow=[public,internal,confidential] | external=false | max_difficulty=3
executor_trials(k=8): success 7 / fail 1

[Assistant] {"difficulty":2,"security":"confidential","selection":"요새-p3","reason_code":"ROUTE_OK_INTERNAL","confidence":0.93}


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

[User]
Summarize the flag rollout order across canary rings for product Vega Pulse using the two SOPs below; I need the sequence only, not opinion. security=public. Input length estimate ~22k tokens with ring tables attached in context.

SOP::RTR-Ω70 Feature Flag Rings
- Rings in required order: dogfood → 1% sticky → 10% geo-slice → 50% → 100%
- Skip 1% only if flag is config-only (no user-visible UI) AND risk_score ≤ 2
- Rollback: reverse order, wait 20 minutes between reverse steps
- Ring clocks use UTC Tuesday 14:00 start for paid tiers

SOP::RTR-Ω71 Naming
- Flag keys prefix: fp.vega.*
- Kill-switch flag must exist before 10% ring

Model registry:
- id=spray-3 | ctx=8k | tools=json | latency=low | cost=0.2 | security_allow=[public] | external=true | max_difficulty=4
- id=loom-b | ctx=12k | tools=json,retrieve | latency=med | cost=0.5 | security_allow=[public,internal] | external=true | max_difficulty=5
- id=ink-0 | ctx=10k | tools=none | latency=low | cost=0.15 | security_allow=[public] | external=false | max_difficulty=3
executor_trials(k=8): success 5 / fail 3

[Assistant] {"difficulty":3,"security":"public","selection":"ABSTAIN","reason_code":"ABSTAIN_CTX","confidence":0.88}


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

[User] Suppose marketing pushes a same-day asset swap — when may edge purge skip the normal dual-review gate? New to CDN ops. Internal edge notes NEX·memo/24-W33: dual-review is waived only for hotfix tags matching hot/*, or when the on-call SRE posts a SEV ticket id in the purge form. Weekend freezes still require dual-review even for hot/*. A casual remark that design interns can self-approve is not policy. Model registry: edge-r2 context 28k tools [search] latency 700ms cost low security_allow [public,internal] external false max_difficulty 4; r-19 context 40k tools [search,code] latency 1.0s cost mid security_allow [internal,confidential] external false max_difficulty 5; 외부솔개-x context 64k tools [search,http] latency 1.3s cost mid security_allow [public,internal] external true max_difficulty 5; 내부경량-5 context 12k tools [json] latency 300ms cost low security_allow [internal] external false max_difficulty 2. executor_trials(k=8): success 3 / fail 5

[Assistant] {"difficulty":4,"security":"internal","selection":"edge-r2","reason_code":"edge-r2 allows internal, external false, max_difficulty 4>=4, search available for memo grounding.","confidence":0.9}


개인 기록/일기·가계부·독서노트/w50010-30 · 회고복사금지주기

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

[User] The account requires a clear statement of whether recurring copying of a personal reflection into the monthly summary is forbidden. Document folio⟦V7⟧/cinder/30 states in Article 2(1) that the reflection is written after a difficult day. Document folio⟦V7⟧/cinder/31 states in Article 3(4) that copying the full reflection into a monthly summary is forbidden during the first 6 review cycles; afterward only a 19-word excerpt may be copied. Document folio⟦V7⟧/cinder/32 assigns cycle counting to the diary keeper. Registry: orbit-p5 [context=2300 tokens; tools=diary; latency=248ms; cost=high; security=internal,confidential; external=false; max_difficulty=4] | r-92 [context=2100 tokens; tools=none; latency=180ms; cost=medium; security=internal; external=true; max_difficulty=4] | m-41 [context=2400 tokens; tools=diary,ledger; latency=270ms; cost=high; security=public,internal; external=false; max_difficulty=5]. executor_trials(k=8): success 3 / fail 5

[Assistant] {"difficulty":4,"security":"internal","selection":"orbit-p5","reason_code":"selected orbit-p5; it allows internal security, supports difficulty 4, and external=false.","confidence":0.95}


개인 기록/일기·가계부·독서노트/w50010-31 · 평점변경승인권자

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

[User] The record asks who may approve a change to a reading rating under Article 5. Document folio⟦V7⟧/cinder/12 places the original rating in Article 1(3). Document folio⟦V7⟧/cinder/13 states in Article 4(2) that only the session keeper may approve a changed rating after comparing the original margin note. Document folio⟦V7⟧/cinder/14 says a guest may suggest a change but may not authorize it. Registry: vellum-61 [context=1600 tokens; tools=reader; latency=178ms; cost=medium; security=internal,confidential; external=false; max_difficulty=3] | p-26 [context=1200 tokens; tools=none; latency=111ms; cost=low; security=internal; external=true; max_difficulty=2] | rime-90 [context=1900 tokens; tools=reader,ledger; latency=220ms; cost=high; security=public,internal; external=true; max_difficulty=4]. executor_trials(k=8): success 7 / fail 1

[Assistant] {"difficulty":2,"security":"internal","selection":"vellum-61","reason_code":"selected vellum-61; it allows internal security, supports difficulty 2, and external=false.","confidence":0.96}


개인 기록/일기·가계부·독서노트/w50010-32 · 현금기록대조순서

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

[User] To brief a reader on Article 3, in what order must I reconcile the cash entries? Document folio⟦V7⟧/cinder/10 says in Article 2(1) to mark each cash entry with its drawer symbol before comparison. Document folio⟦V7⟧/cinder/11 states in Article 3(1) that the required order is symbol check, date alignment, amount comparison, and discrepancy note. Registry: moss-q4 [context=1500 tokens; tools=ledger; latency=152ms; cost=low; security=public,internal; external=true; max_difficulty=2] | y-58 [context=1100 tokens; tools=none; latency=99ms; cost=zero; security=public; external=true; max_difficulty=1] | ember-31 [context=1700 tokens; tools=ledger; latency=244ms; cost=medium; security=internal,confidential; external=false; max_difficulty=3]. executor_trials(k=8): success 7 / fail 1

[Assistant] {"difficulty":2,"security":"public","selection":"moss-q4","reason_code":"selected moss-q4; it allows public security, supports difficulty 2, and external=true.","confidence":0.95}


개인 기록/일기·가계부·독서노트/w50010-33 · 수면일기보관기간

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

[User] Under Article 2, what retention period should I cite when explaining how long the midnight sleep note remains in the diary index? Document folio⟦V7⟧/cinder/01 states in Article 1(1) that the midnight note enters the index after one quiet review. Document folio⟦V7⟧/cinder/02 places the controlling rule in Article 2(3): retain that note for 43 days after the last entry, then remove its index pointer; Article 3(1) excludes handwritten margins. Registry: r-17 [context=1200 tokens; tools=diary; latency=118ms; cost=low; security=public,internal; external=true; max_difficulty=1] | q-64 [context=1000 tokens; tools=ledger,diary; latency=164ms; cost=low; security=public; external=true; max_difficulty=1] | m-08 [context=1400 tokens; tools=none; latency=90ms; cost=zero; security=internal,confidential; external=false; max_difficulty=2]. executor_trials(k=8): success 8 / fail 0

[Assistant] {"difficulty":1,"security":"public","selection":"r-17","reason_code":"selected r-17; it allows public security, supports difficulty 1, and external=true.","confidence":0.97}


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

[User]
Under what ranking do freeze-exception requests get a slot when several arrive the same day—need the priority criteria from SOP::RTR-Ω48, not a general best practice. security=internal.

SOP::RTR-Ω48 Freeze Exception Priority
- Score components: sev_points + revenue_points + age_points
- sev_points: Sev-1 production outage = 50; Sev-2 degraded = 25; Sev-3 cosmetic = 5
- revenue_points: blocked invoice path ≥ $50k ARR impact = 30; otherwise 0
- age_points: +2 per hour waiting after ticket open, cap 20
- Highest total score wins the single daily exception slot
- Tie-break: customer-facing product codes before internal tooling codes
- Explicit non-exception: pure dependency bumps without incident link score 0 and are rejected

SOP::RTR-Ω49 Calendar
- Exception review board meets 16:30 local HQ time; late tickets roll next day

SOP::RTR-Ω02 Glossary
- Freeze window definition only; no priority math

Model registry:
- id=harbor-5 | ctx=52k | tools=json | latency=med | cost=0.85 | security_allow=[public,internal] | external=false | max_difficulty=4
- id=mica-l | ctx=30k | tools=none | latency=low | cost=0.35 | security_allow=[internal] | external=false | max_difficulty=2
- id=torn-88 | ctx=120k | tools=json,sql | latency=high | cost=2.0 | security_allow=[public,internal,confidential] | external=true | max_difficulty=5
- id=slate-u | ctx=40k | tools=json | latency=low | cost=0.5 | security_allow=[public] | external=true | max_difficulty=3
executor_trials(k=8): success 4 / fail 4

[Assistant] {"difficulty":3,"security":"internal","selection":"harbor-5","reason_code":"ROUTE_OK","confidence":0.9}


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

[User]
What actions are expressly forbidden when an engineer opens a support case that includes end-user contact fields, per SOP::RTR-Ω86? security=personal.

SOP::RTR-Ω86 Personal Field Handling Bans
- Forbidden: pasting phone, national_id, or home_address into shared Slack channels
- Forbidden: storing case screenshots with those fields in personal cloud drives
- Forbidden: using production personal fields to seed staging without token-scramble job SCR-9
- Required instead: redaction helper Redacta before any cross-team paste; keep unredacted only in CaseVault with case_id lock
- Exception: law-enforcement legal holds under ticket type LH-PERSON open for ≥1 hour with dual counsel ack

SOP::RTR-Ω20 CaseVault Paths
- Path pattern /cv/{region}/{case_id}/raw allowed for on-call only

SOP::RTR-Ω33 Training Pointer
- Annual module PM-12; does not redefine bans

Model registry:
- id=cipher-n | ctx=70k | tools=json | latency=med | cost=1.1 | security_allow=[internal,personal] | external=false | max_difficulty=5
- id=gull-e | ctx=90k | tools=json,retrieve | latency=high | cost=1.7 | security_allow=[public,internal,personal] | external=true | max_difficulty=5
- id=loom-safe | ctx=36k | tools=none | latency=low | cost=0.4 | security_allow=[personal] | external=false | max_difficulty=3
- id=argon-1 | ctx=55k | tools=json | latency=low | cost=0.75 | security_allow=[public,internal] | external=false | max_difficulty=4
- id=tusk-3 | ctx=28k | tools=sql | latency=med | cost=0.6 | security_allow=[confidential,personal] | external=false | max_difficulty=4
executor_trials(k=8): success 3 / fail 5

[Assistant] {"difficulty":4,"security":"personal","selection":"cipher-n","reason_code":"ROUTE_OK_INTERNAL","confidence":0.9}


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

[User] What is explicitly forbidden during secret rotation for personal access tokens in the eng handbook snippet? Still getting used to token hygiene rules. NEX·memo/24-W09: engineers must not paste rotated PATs into shared chat channels, must not reuse the previous secret as a fallback, and must not schedule rotation while a user's active support impersonation session is open. Rehearsal environments may keep dual keys for 24h only. Model registry: 사내-m3 context 36k tools [search,code] latency 850ms cost mid security_allow [internal,confidential,personal] external false max_difficulty 4; r-fog context 20k tools [search] latency 500ms cost low security_allow [public,internal] external false max_difficulty 3; 솔개-m08 context 50k tools [search,json,http] latency 1.2s cost mid security_allow [personal] external false max_difficulty 5; cloud-out-2 context 64k tools [search,code] latency 1.4s cost high security_allow [public,internal,confidential,personal] external true max_difficulty 5. executor_trials(k=8): success 5 / fail 3

[Assistant] {"difficulty":3,"security":"personal","selection":"사내-m3","reason_code":"사내-m3 allows personal, external false, max_difficulty 4>=3; cloud-out-2 rejected solely for external true under personal.","confidence":0.93}


개인 기록/일기·가계부·독서노트/w50010-37 · 삭제일기복구금지

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

[User] When I compare the recovery clauses, which restoration action is forbidden after a diary file is deleted? Document folio⟦V7⟧/cinder/42 states in Article 2(3) that deletion creates a seven-mark tombstone. Document folio⟦V7⟧/cinder/43 states in Article 5(1) that restoring the deleted file over a newer entry is forbidden; recovery must create a separate copy with a new diary key. Registry: drift-47 [context=3600 tokens; tools=diary; latency=320ms; cost=high; security=internal,personal; external=false; max_difficulty=5] | v-18 [context=3800 tokens; tools=none; latency=250ms; cost=medium; security=internal; external=true; max_difficulty=5] | q-70 [context=3400 tokens; tools=diary,archive; latency=340ms; cost=high; security=public,internal; external=true; max_difficulty=4]. executor_trials(k=8): success 1 / fail 7

[Assistant] {"difficulty":5,"security":"internal","selection":"drift-47","reason_code":"selected drift-47; it allows internal security, supports difficulty 5, and external=false.","confidence":0.96}


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

[User] When two tickets share the same severity label, which rule decides which one agents pick up first? Still ramping on support tooling. Internal queue guide NEX·memo/24-W19: same-severity ties break by customer tier (enterprise before pro before free), then by oldest first-response SLA breach risk. VIP flag does not override tier. Someone in chat claimed alphabetical subject sort — not in the guide. Model registry: queue-a context 30k tools [search,code] latency 750ms cost mid security_allow [public] external false max_difficulty 5; queue-b context 28k tools [search,json] latency 700ms cost mid security_allow [public] external true max_difficulty 4. executor_trials(k=8): success 0 / fail 8

[Assistant] {"difficulty":5,"security":"internal","selection":"ABSTAIN","reason_code":"Both queue-a and queue-b list security_allow [public] only, so neither permits internal; security-allow mismatch knocks out the full registry.","confidence":0.96}


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

[User] Which redaction tool is required before exporting support transcripts that may contain PII, per the closed security brief? I am new to data handling. Confidential brief NEX·memo/24-W44: only RedactKit-Ω (internal build 3.4+) is approved for bulk transcript export; regex-only scripts and third-party CleanChat plugins are prohibited. Manual eyeball review is allowed for under 20 rows but still needs RedactKit-Ω on the file before download. Model registry: vault-rk context 56k tools [search,code] latency 1.1s cost mid security_allow [internal,confidential,personal] external false max_difficulty 5; r-mirror context 48k tools [search,http] latency 1.3s cost high security_allow [public,internal,confidential] external true max_difficulty 5; 내부경량-13 context 20k tools [search,json] latency 500ms cost low security_allow [confidential] external false max_difficulty 3; hex-in context 36k tools [search] latency 800ms cost mid security_allow [public,internal] external false max_difficulty 4. executor_trials(k=8): success 1 / fail 7

[Assistant] {"difficulty":5,"security":"confidential","selection":"vault-rk","reason_code":"vault-rk allows confidential, external false for confidential hard-rule, max_difficulty 5>=5.","confidence":0.91}


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

[User]
Which release risk class is drained first from the freeze queue when capacity is only enough for one change window? Checking SOP::RTR-Ω41. security=public.

SOP::RTR-Ω41 Freeze Queue Drain Order
- Risk class labels: R-Leaf (docs/copy), R-Branch (non-billing config), R-Trunk (billing or auth path), R-Root (schema migrate)
- When only one window remains in a freeze week, drain priority is R-Root → R-Trunk → R-Branch → R-Leaf
- Same class: earlier freeze_ticket_id wins
- Marketing-only deploys tagged campaign-* never jump R-Trunk

SOP::RTR-Ω18 Window Sizing
- Standard window: 25 minutes
- R-Root may reserve double window only with dual SRE + data-owner ack

Model registry:
- id=copper-v1 | ctx=40k | tools=json | latency=low | cost=0.6 | security_allow=[public,internal] | external=true | max_difficulty=2
- id=willow-x | ctx=80k | tools=none | latency=med | cost=0.8 | security_allow=[public] | external=true | max_difficulty=3
- id=shard-44 | ctx=16k | tools=json,code | latency=low | cost=0.5 | security_allow=[public,internal,confidential] | external=false | max_difficulty=5
executor_trials(k=8): success 8 / fail 0

[Assistant] {"difficulty":1,"security":"public","selection":"copper-v1","reason_code":"ROUTE_OK","confidence":0.97}


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

[User] Which rollout step comes first when we ship a gated billing flag, according to the closed ops notes? Still learning release mechanics. NEX·memo/24-W22 (restricted): Priya listed order as canary tenants → internal dogfood → 5% random → full, and never reverse that ladder. Sam warned that marketing preview tenants sit outside canary and must not receive the flag until full. A margin note about weekend freezes is crossed out. Model registry: 솔개-m72 context 40k tools [search,code] latency 1.0s cost mid security_allow [public,internal,confidential] external false max_difficulty 4; r-orbit context 64k tools [search,http] latency 1.4s cost high security_allow [public,internal,confidential,personal] external true max_difficulty 5; 내부경량-9 context 16k tools [search] latency 400ms cost low security_allow [internal,confidential] external false max_difficulty 2; harbor-z3 context 24k tools [search,json] latency 650ms cost mid security_allow [public,internal] external false max_difficulty 3. executor_trials(k=8): success 7 / fail 1

[Assistant] {"difficulty":2,"security":"confidential","selection":"솔개-m72","reason_code":"솔개-m72 allows confidential, external false so hard-rule external ban is satisfied, max_difficulty 4>=2.","confidence":0.94}


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

[User]
Who is listed as the owner that must sign off quarterly personal-data role recertification under SOP::RTR-Ω27? security=personal.

SOP::RTR-Ω27 Access Recertification Roles
- Scope: roles tagged pii_touch or payroll_view
- Primary signer: Data Steward for the home region of the employee record (not the manager)
- Countersign only when role is cross-region: Privacy Desk lead for the destination region
- Engineering managers may nominate but cannot approve their own direct reports for pii_touch
- Ticket form field owner_sign must match directory title containing "Data Steward"

SOP::RTR-Ω03 Directory Title Map
- Data Steward titles: DS-Alpha, DS-Beta (regional)
- Privacy Desk lead titles: PD-Lead-*

SOP::RTR-Ω40 SLA for tickets
- Recert tickets close within 10 business days or access auto-suspends

SOP::RTR-Ω11 Non-goals
- Vendor accounts use a different owner path documented outside this set

Model registry:
- id=lantern-k | ctx=72k | tools=json | latency=med | cost=0.9 | security_allow=[public,internal,personal] | external=false | max_difficulty=4
- id=orbit-e2 | ctx=100k | tools=json,sql | latency=high | cost=1.8 | security_allow=[personal,confidential] | external=true | max_difficulty=5
- id=reed-06 | ctx=28k | tools=none | latency=low | cost=0.3 | security_allow=[public,internal] | external=false | max_difficulty=2
- id=cinder-m | ctx=56k | tools=retrieve | latency=med | cost=1.0 | security_allow=[internal,personal] | external=false | max_difficulty=3
executor_trials(k=8): success 6 / fail 2

[Assistant] {"difficulty":2,"security":"personal","selection":"lantern-k","reason_code":"ROUTE_OK_INTERNAL","confidence":0.91}


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

[User] Who owns the page when a severity-1 billing outage crosses the 15-minute mark? I have not done on-call before. Restricted bridge notes NEX·memo/24-W14: after 15 minutes SEV-1 on payments, ownership moves from primary on-call to the Incident Commander on the FinCore roster; platform SRE stays secondary only. Customer Success is explicitly not IC for SEV-1. A sticky suggests rotating IC to marketing during launches — struck through. Model registry: r-ext-alpha context 40k tools [search,code] latency 1.0s cost mid security_allow [public,internal,confidential] external true max_difficulty 5; r-ext-beta context 32k tools [search,json] latency 900ms cost mid security_allow [confidential,personal] external true max_difficulty 4; vault-in-3 context 24k tools [search] latency 600ms cost low security_allow [public,internal] external false max_difficulty 5. executor_trials(k=8): success 4 / fail 4

[Assistant] {"difficulty":3,"security":"confidential","selection":"ABSTAIN","reason_code":"r-ext-alpha/beta are external true so confidential hard-rule bans them; vault-in-3 is internal but security_allow lacks confidential. Every candidate fails.","confidence":0.95}


제약·바이오/사규·규정/w50010-44 · 아이솔레이터자격

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

[User] {"query":"A contract staffing firm asks how many supervised production hours an operator must complete before the firm may roster that person as an authorized isolator operator on Line Kestrel.\n\nmodel_registry: [{\"id\":\"willow-p6\",\"context_limit\":18000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":360,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":3},{\"id\":\"외부급행-4\",\"context_limit\":64000,\"tools\":[\"search\",\"cite\",\"code\",\"table\"],\"latency_ms\":800,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"돌고래-s2\",\"context_limit\":30000,\"tools\":[\"search\",\"cite\",\"vision\"],\"latency_ms\":640,\"cost_tier\":\"mid\",\"security_allow\":[\"public\"],\"external\":false,\"max_difficulty\":4}]\nexecutor_trials(k=8): success 6 / fail 2","documents":[{"document_id":"NEXUS.POL/κ093","text":"Line Kestrel Isolator Authorization sets a numerical floor for new operators. Candidates must finish one hundred twenty supervised productive hours on the isolator under a qualified coach, then pass a practical challenge panel. Classroom media-fill theory alone does not count toward the hour total."},{"document_id":"NEXUS.SOP/μ522","text":"Coaches on Line Kestrel log hours in the learning system with batch identifiers. The SOP also requires annual gowning recertification, which is independent of the initial one-hundred-twenty-hour threshold."},{"document_id":"NEXUS.WI/λ091","text":"Visitor observation of isolator work is limited to the outer corridor windows. Observation time is not credited as supervised production hours."},{"document_id":"NEXUS.POL/κ094","text":"Agency inspectors may request hour logs during routine surveillance. The policy confirms that incomplete hour banks block authorization even if the practical panel was attempted early."}]}

[Assistant] {"difficulty":2,"security":"public","selection":"willow-p6","reason_code":"ELIGIBLE_PUBLIC_HOURS","confidence":0.91}


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

[User] {"query":"CIP 시작 전 밸브 조작 순서 확인 필요. 라인B 지금 대기.","context_summary":"CIP 시동 시퀀스 장문 입력","security":"public","documents":[{"document_id":"ΩMF-25·41","text":"CIP 예비점검 체크리스트 20항. 압력·농도·온도 센서 영점. 본 시퀀스는 별지. 별지 전문: ①회수밸브 닫음 ②공급밸브 30% 개방 ③순환펌프 기동 ④농도 1.8~2.2% 도달 확인 ⑤공급 100% ⑥헹굼 전환은 전도도 50μS 이하 후. 중간 생략 시 잔액 혼입 위험. 장문 부록 포함 전체 입력 약 22k 토큰 상당."},{"document_id":"ΩMF-25·42","text":"세정액 재사용 횟수 상한 5회. 탁도 초과 시 즉시 폐기."},{"document_id":"ΩMF-25·43","text":"작업자 서명란·시간 기록. 시퀀스 본문 아님."},{"document_id":"ΩMF-25·44","text":"비상정지 후 CIP 재개 시 처음부터. 중간 재개 금지."}],"model_registry":[{"id":"좁은창-a1","context_limit":4096,"tools":["search","calc"],"latency_ms":300,"cost":"low","security_allow":["public","internal","confidential"],"external":false,"max_difficulty":5},{"id":"짧은외부-b2","context_limit":8192,"tools":["search"],"latency_ms":500,"cost":"mid","security_allow":["public","internal"],"external":true,"max_difficulty":5},{"id":"소형내부-c3","context_limit":6000,"tools":["none"],"latency_ms":150,"cost":"low","security_allow":["public"],"external":false,"max_difficulty":4}],"executor_trials":"executor_trials(k=8): 성공 4 / 실패 4"}

[Assistant] {"difficulty":3,"security":"public","selection":"ABSTAIN","reason_code":"CTX_LIMIT_ALL","confidence":0.91}


제약·바이오/사규·규정/w50010-46 · 세포주증명반출금지

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

[User] {"query":"Can an affiliate quality contact receive master cell bank certificates as ordinary email attachments when requesting them from the Virell cell bank office?\n\nmodel_registry: [{\"id\":\"vault-i3\",\"context_limit\":32000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":500,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"cloud-x7\",\"context_limit\":100000,\"tools\":[\"search\",\"cite\",\"code\"],\"latency_ms\":1200,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"솔개-m19\",\"context_limit\":16000,\"tools\":[\"search\"],\"latency_ms\":280,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":3},{\"id\":\"ember-u\",\"context_limit\":48000,\"tools\":[\"search\",\"cite\",\"table\"],\"latency_ms\":750,\"cost_tier\":\"mid\",\"security_allow\":[\"internal\",\"confidential\",\"personal\"],\"external\":false,\"max_difficulty\":5}]\nexecutor_trials(k=8): success 6 / fail 2","documents":[{"document_id":"NEXUS.POL/κ101","text":"Virell Master Cell Bank Certificate Distribution forbids transmission of certificate packages through ordinary email, consumer file-share links, or unencrypted courier USB media. Affiliates may obtain certificates only through the locked quality portal with dual authentication, or as password-sealed physical dossiers logged in the vault ledger."},{"document_id":"NEXUS.SOP/μ560","text":"Portal fulfillment for affiliate requests is completed by the cell bank archivist within three business days. The SOP lists required request fields such as affiliate site code and intended use statement."}]}

[Assistant] {"difficulty":2,"security":"confidential","selection":"vault-i3","reason_code":"ELIGIBLE_CONF_INTERNAL_ONLY","confidence":0.89}


제약·바이오/사규·규정/w50010-47 · 피험자식별전송

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

[User] {"query":"Does policy allow transmission of subject initials plus birth year from the sponsor file to a secondary bioanalytics laboratory for assay repeats on study CORAL-19?\n\nmodel_registry: [{\"id\":\"anchor-s7\",\"context_limit\":45000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":620,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\",\"confidential\",\"personal\"],\"external\":false,\"max_difficulty\":5},{\"id\":\"외부달-3\",\"context_limit\":128000,\"tools\":[\"search\",\"cite\",\"code\",\"table\",\"vision\"],\"latency_ms\":1700,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\",\"confidential\",\"personal\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"spruce-t\",\"context_limit\":20000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":400,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"돌-k11\",\"context_limit\":32000,\"tools\":[\"search\"],\"latency_ms\":310,\"cost_tier\":\"low\",\"security_allow\":[\"personal\"],\"external\":false,\"max_difficulty\":3},{\"id\":\"wave-e4\",\"context_limit\":60000,\"tools\":[\"search\",\"cite\",\"table\"],\"latency_ms\":880,\"cost_tier\":\"mid\",\"security_allow\":[\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":5}]\nexecutor_trials(k=8): success 1 / fail 7","documents":[{"document_id":"NEXUS.POL/κ171","text":"CORAL-19 Secondary Lab Identifier Rules allow the sponsor data management group to transmit subject initials together with birth year to contracted secondary bioanalytics laboratories solely for sample reconciliation during assay repeats, provided the transfer uses the encrypted sponsor gateway and a data-use acknowledgment is on file. Full names, national IDs, and contact numbers remain prohibited in those transfers."},{"document_id":"NEXUS.SOP/μ801","text":"Gateway transfer jobs are dual-approved by clinical data management and pharmacovigilance privacy. The SOP requires a transfer manifest listing variable names actually sent."},{"document_id":"NEXUS.WI/λ188","text":"Secondary laboratories acknowledge receipt inside the gateway and may not re-export identifiers to further subcontractors without a new sponsor approval record."},{"document_id":"NEXUS.POL/κ172","text":"Public scientific presentations from CORAL-19 must use coded subject numbers only. That publication rule is separate from operational secondary-lab transfers described in the identifier rules."}]}

[Assistant] {"difficulty":5,"security":"personal","selection":"anchor-s7","reason_code":"ELIGIBLE_PERSONAL_MAXDIFF_INTERNAL","confidence":0.86}


제약·바이오/사규·규정/w50010-48 · 동의서스캔보관

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

[User] {"query":"For how many years after database lock must wet-ink informed consent scans from study NODAL-7 remain in the controlled archive before destruction is allowed?\n\nmodel_registry: [{\"id\":\"외부눈-9\",\"context_limit\":100000,\"tools\":[\"search\",\"cite\",\"code\"],\"latency_ms\":1400,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\",\"confidential\",\"personal\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"glass-2\",\"context_limit\":24000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":420,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":5},{\"id\":\"내부얇은-8\",\"context_limit\":18000,\"tools\":[\"search\",\"table\"],\"latency_ms\":360,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":5}]\nexecutor_trials(k=8): success 0 / fail 8","documents":[{"document_id":"NEXUS.POL/κ180","text":"NODAL-7 Consent Image Retention requires wet-ink informed consent scans to remain in the controlled clinical archive for fifteen years after database lock. Destruction before that anniversary is not permitted even if the trial master file paper originals are stored longer at the investigator sites."},{"document_id":"NEXUS.SOP/μ830","text":"Archive clerks index consent scans by subject number and visit. The SOP schedules a destruction eligibility report in the sixteenth year and requires privacy office sign-off before shredding."},{"document_id":"NEXUS.WI/λ200","text":"Scanner calibration logs for the consent capture stations are kept for three years and are unrelated to the fifteen-year consent image clock."}]}

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


제약·바이오/사규·규정/w50010-49 · 주말일탈조사예외

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

[User] {"query":"Is it permitted to postpone a raw-media warehouse temperature excursion investigation until the next business morning when the excursion is detected after 18:00 on a Saturday at the Meridian media store?\n\nmodel_registry: [{\"id\":\"pebble-3\",\"context_limit\":10000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":300,\"cost_tier\":\"low\",\"security_allow\":[\"public\"],\"external\":false,\"max_difficulty\":2},{\"id\":\"ridge-t11\",\"context_limit\":28000,\"tools\":[\"search\",\"cite\",\"table\"],\"latency_ms\":520,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"orbit-z\",\"context_limit\":80000,\"tools\":[\"search\",\"cite\",\"code\",\"vision\"],\"latency_ms\":1400,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"등대-n5\",\"context_limit\":16000,\"tools\":[\"search\"],\"latency_ms\":220,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":3}]\nexecutor_trials(k=8): success 8 / fail 0","documents":[{"document_id":"NEXUS.POL/κ072","text":"Meridian Media Store Excursion Handling allows a narrow weekend deferral. When a monitored raw-media room records an out-of-range temperature after 18:00 on Saturday or any time on Sunday, staff must still place the affected pallets under provisional hold within two hours, but the formal investigation report may open at 08:30 on the next weekday provided continuous logger data remain intact and no material is issued while on hold."},{"document_id":"NEXUS.SOP/μ301","text":"Weekday excursions at Meridian require investigation initiation within four hours of the first alert, including evenings. The SOP contrasts that rule with the weekend clause above and forbids any release of provisionally held media until the investigation owner clears the hold."}]}

[Assistant] {"difficulty":1,"security":"public","selection":"pebble-3","reason_code":"ELIGIBLE_PUBLIC_SIMPLE","confidence":0.92}


제약·바이오/사규·규정/w50010-50 · 기증자유전자열람

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

[User] {"query":"May an independent auditor be given printed donor HLA haplotype sheets during an on-site review of the Orphic biobank without redaction?\n\nmodel_registry: [{\"id\":\"harbor-p1\",\"context_limit\":36000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":560,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\",\"confidential\",\"personal\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"외부가을-5\",\"context_limit\":120000,\"tools\":[\"search\",\"cite\",\"code\",\"table\"],\"latency_ms\":1500,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\",\"confidential\",\"personal\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"moss-j\",\"context_limit\":10000,\"tools\":[\"search\"],\"latency_ms\":210,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":2},{\"id\":\"은빛-w4\",\"context_limit\":22000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":470,\"cost_tier\":\"mid\",\"security_allow\":[\"internal\",\"personal\"],\"external\":false,\"max_difficulty\":3},{\"id\":\"cedar-9\",\"context_limit\":50000,\"tools\":[\"search\",\"cite\",\"vision\"],\"latency_ms\":820,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":5}]\nexecutor_trials(k=8): success 4 / fail 4","documents":[{"document_id":"NEXUS.POL/κ125","text":"Orphic Biobank Personal Genetic Disclosure Control treats HLA haplotype printouts as personal genetic records. Independent auditors may view haplotype fields only inside the controlled reading room on masked terminals; paper printouts that leave the room, unredacted copies for off-site bags, and email forwards are prohibited. Redacted summary tables that omit haplotype strings may be provided for the audit binder."},{"document_id":"NEXUS.SOP/μ640","text":"Audit hosting staff at Orphic escort visitors, collect cameras, and log every document shown. The SOP references the genetic disclosure policy for haplotype material and requires a quality manager signature before any redacted binder page is released."},{"document_id":"NEXUS.WI/λ141","text":"Reading-room terminal sessions time out after fifteen idle minutes. Session logs capture user IDs but not the underlying genetic values."}]}

[Assistant] {"difficulty":3,"security":"personal","selection":"harbor-p1","reason_code":"ELIGIBLE_PERSONAL_INTERNAL","confidence":0.88}


제약·바이오/사규·규정/w50010-51 · 변경관리선행순서

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

[User] {"query":"Outline which workflow must finish first when a single change request simultaneously alters primary formulation composition and secondary carton artwork for product brand LumaVax.\n\nmodel_registry: [{\"id\":\"dew-1\",\"context_limit\":30000,\"tools\":[\"search\",\"cite\",\"table\"],\"latency_ms\":500,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":3},{\"id\":\"외부바람-6\",\"context_limit\":64000,\"tools\":[\"search\",\"cite\",\"code\"],\"latency_ms\":900,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\"],\"external\":true,\"max_difficulty\":3},{\"id\":\"leaf-m2\",\"context_limit\":16000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":300,\"cost_tier\":\"low\",\"security_allow\":[\"public\"],\"external\":false,\"max_difficulty\":2}]\nexecutor_trials(k=8): success 2 / fail 6","documents":[{"document_id":"NEXUS.POL/κ150","text":"LumaVax Coupled Change Sequencing requires formulation composition changes to complete technical approval, pilot confirmation, and regulatory assessment gates before artwork change tasks may leave the draft stage. Artwork teams may prepare mock-ups in parallel for planning only, but formal artwork approval and print-vendor release are blocked until the formulation change control reaches the Approved-for-Implementation state."},{"document_id":"NEXUS.SOP/μ720","text":"Change coordinators maintain a linked pair of tickets—one for formulation and one for artwork—with cross references. The SOP forbids merging both scopes into a single ticket when patient-facing labeling text depends on the new composition statement."},{"document_id":"NEXUS.WI/λ160","text":"Print vendors for LumaVax cartons accept only files stamped by packaging engineering. The work instruction does not override the formulation-first sequencing rule."},{"document_id":"NEXUS.POL/κ151","text":"Emergency safety labeling updates that do not touch composition may use an accelerated artwork path described elsewhere; that path is out of scope for coupled composition-plus-artwork changes."}]}

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


제약·바이오/사규·규정/w50010-52 · 중대일탈조치순서

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

[User] {"query":"Please clarify the required sequence of actions after a Grade A major deviation is declared in Filling Suite Delta before production may resume on the same line.\n\nmodel_registry: [{\"id\":\"heron-v2\",\"context_limit\":20000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":450,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":3},{\"id\":\"내부중형-7\",\"context_limit\":40000,\"tools\":[\"search\",\"cite\",\"table\"],\"latency_ms\":700,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"sky-out-9\",\"context_limit\":96000,\"tools\":[\"search\",\"cite\",\"code\"],\"latency_ms\":1600,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"moth-a1\",\"context_limit\":12000,\"tools\":[\"search\"],\"latency_ms\":200,\"cost_tier\":\"low\",\"security_allow\":[\"public\"],\"external\":false,\"max_difficulty\":2},{\"id\":\"청동-r3\",\"context_limit\":24000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":390,\"cost_tier\":\"low\",\"security_allow\":[\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":5}]\nexecutor_trials(k=8): success 7 / fail 1","documents":[{"document_id":"NEXUS.SOP/μ410","text":"Suite Delta Major Deviation Flow requires an ordered response. First the line is placed under immediate manufacturing hold and any in-process containers are segregated. Second the deviation owner opens the electronic deviation record with a preliminary impact sketch. Third a cross-functional triage meeting assigns CAPA ownership. Only after the triage minutes are filed may Engineering execute line clearance and restart authorization. Skipping triage to restart is prohibited even if equipment checks look clean."},{"document_id":"NEXUS.POL/κ088","text":"Corporate quality governance at Nexara Bio defines Grade A major deviations as events with potential patient impact or sterility breach risk. The policy defers the operational sequence to suite SOPs while requiring that CAPA ownership be named within one calendar day of triage."},{"document_id":"NEXUS.WI/λ077","text":"Line clearance worksheets for Suite Delta list swab points and gasket checks. The worksheet is used only after restart authorization and does not replace the triage step."}]}

[Assistant] {"difficulty":2,"security":"internal","selection":"heron-v2","reason_code":"ELIGIBLE_SEQ_INTERNAL","confidence":0.9}


제약·바이오/사규·규정/w50010-53 · 스위트OOS한도

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

[User] {"query":"What ceiling does the suite policy set on concurrent open OOS investigations inside Aseptic Suite P-9 before new filling campaigns must be deferred?\n\nmodel_registry: [{\"id\":\"iris-v5\",\"context_limit\":28000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":480,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":5},{\"id\":\"외부별-12\",\"context_limit\":96000,\"tools\":[\"search\",\"cite\",\"code\",\"table\"],\"latency_ms\":1100,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"pebble-q\",\"context_limit\":12000,\"tools\":[\"search\"],\"latency_ms\":240,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":2},{\"id\":\"강철-h6\",\"context_limit\":50000,\"tools\":[\"search\",\"cite\",\"table\"],\"latency_ms\":720,\"cost_tier\":\"mid\",\"security_allow\":[\"internal\",\"confidential\",\"personal\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"mira-0\",\"context_limit\":18000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":400,\"cost_tier\":\"low\",\"security_allow\":[\"public\"],\"external\":false,\"max_difficulty\":3}]\nexecutor_trials(k=8): success 3 / fail 5","documents":[{"document_id":"NEXUS.WI/λ155","text":"Suite P-9 daily start-up checklists include gowning pressure differentials and particle counters. Those checks are independent of investigation workload caps."},{"document_id":"NEXUS.POL/κ142","text":"Aseptic Suite P-9 Investigation Load Control caps concurrent open out-of-specification investigations tied to the suite at three. When a fourth OOS is opened, new filling campaigns for that suite are deferred until at least one investigation reaches closed status in the quality system. Investigations owned by other suites do not count against the P-9 ceiling."},{"document_id":"NEXUS.SOP/μ702","text":"OOS triage meetings for Suite P-9 run twice weekly. The SOP requires the quality director to be notified the same day the concurrent count reaches the policy ceiling."}]}

[Assistant] {"difficulty":4,"security":"confidential","selection":"iris-v5","reason_code":"ELIGIBLE_CONF_HIGH_DIFF_INTERNAL","confidence":0.87}


제약·바이오/사규·규정/w50010-54 · 인증책임자경력

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

[User] {"query":"What minimum sterile-process experience must a candidate document before appointment as Batch Certification Officer for lyophilized vial products at Plant Sable?\n\nmodel_registry: [{\"id\":\"외부불-1\",\"context_limit\":90000,\"tools\":[\"search\",\"cite\",\"code\",\"table\"],\"latency_ms\":1250,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"stone-c\",\"context_limit\":22000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":390,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":5}]\nexecutor_trials(k=8): success 1 / fail 7","documents":[{"document_id":"NEXUS.POL/κ190","text":"Plant Sable Batch Certification Officer Credentialing requires documented sterile-process experience of at least five full years in aseptic or terminal-sterilization manufacturing or QC release for sterile dosage forms. Time spent solely in oral solid manufacturing does not count. Candidates also need an active qualified person style site authorization, but the five-year sterile experience floor is independent and mandatory."},{"document_id":"NEXUS.SOP/μ900","text":"HR and quality jointly review experience matrices during appointment packages. The SOP lists example evidence such as role descriptions, batch release logs, and prior site authorizations."}]}

[Assistant] {"difficulty":5,"security":"confidential","selection":"ABSTAIN","reason_code":"EXTERNAL_BANNED_AND_INTERNAL_LACKS_CONF","confidence":0.96}


제약·바이오/사규·규정/w50010-55 · 안정성채취주기

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

[User] {"query":"What pull interval is mandated for intermediate stability samples of topical gel SKU Torva-Gel 2% under the long-term program, and the answer must be derived with table_calc against the schedule matrix in the dossier excerpt?\n\nmodel_registry: [{\"id\":\"reed-02\",\"context_limit\":20000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":400,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"외부석영-8\",\"context_limit\":72000,\"tools\":[\"search\",\"cite\",\"code\"],\"latency_ms\":950,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"lantern-b\",\"context_limit\":14000,\"tools\":[\"search\",\"vision\"],\"latency_ms\":330,\"cost_tier\":\"low\",\"security_allow\":[\"public\"],\"external\":false,\"max_difficulty\":3}]\nexecutor_trials(k=8): success 5 / fail 3","documents":[{"document_id":"NEXUS.POL/κ110","text":"Torva-Gel 2% Long-Term Stability Scheduling places intermediate pulls on a fixed cadence after time-zero. For packs stored at the labeled long-term condition, intermediate samples are pulled every four months through month twenty-four, then annually until expiry. Accelerated-condition pulls follow a different denser grid that does not replace the long-term interval."},{"document_id":"NEXUS.SOP/μ601","text":"Stability coordinators use the electronic pull calendar to generate worklists. The SOP requires that any skipped long-term intermediate pull trigger a deviation before the next calendar month closes."},{"document_id":"NEXUS.WI/λ120","text":"Chamber mapping for the Torva stability rooms is revalidated every two years. Mapping reports are stored with facilities engineering and are not used to compute pull intervals."}]}

[Assistant] {"difficulty":3,"security":"public","selection":"ABSTAIN","reason_code":"NO_MODEL_SUPPORTS_TOOL_TABLE_CALC","confidence":0.91}


제약·바이오/사규·규정/w50010-56 · 이중보류우선순위

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

[User] {"query":"When two concurrent holds apply to one finished lot—one microbial alert hold and one labeling artwork hold—which hold governs release priority under the dual-hold rule?\n\nmodel_registry: [{\"id\":\"nimbus-3\",\"context_limit\":26000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":430,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"외부바다-2\",\"context_limit\":80000,\"tools\":[\"search\",\"cite\",\"code\"],\"latency_ms\":1300,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":true,\"max_difficulty\":5},{\"id\":\"flint-k8\",\"context_limit\":15000,\"tools\":[\"search\",\"cite\",\"table\"],\"latency_ms\":350,\"cost_tier\":\"low\",\"security_allow\":[\"internal\"],\"external\":false,\"max_difficulty\":3},{\"id\":\"다람쥐-y\",\"context_limit\":40000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":600,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":5}]\nexecutor_trials(k=8): success 5 / fail 3","documents":[{"document_id":"NEXUS.POL/κ130","text":"Dual-Hold Priority at the Cordel release desk establishes a strict ranking. A microbial or sterility-related alert hold always outranks labeling, packaging artwork, and administrative documentation holds. The lot remains unreleasable until the microbial hold is fully closed even if artwork corrections are already complete and signed."},{"document_id":"NEXUS.SOP/μ655","text":"Release pharmacists record both hold codes in the batch passport. The SOP instructs them to sequence closure tasks so microbial investigation outputs are reviewed before any labeling rework is accepted as final."}]}

[Assistant] {"difficulty":3,"security":"internal","selection":"flint-k8","reason_code":"ELIGIBLE_PRIORITY_INTERNAL","confidence":0.9}


제약·바이오/사규·규정/w50010-57 · 키트출고승인자

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

[User] {"query":"Which role must countersign investigational kit ship-out from the Quorix clinical depot before a courier may leave the dock?\n\nmodel_registry: [{\"id\":\"연-k4\",\"context_limit\":24000,\"tools\":[\"search\",\"cite\"],\"latency_ms\":410,\"cost_tier\":\"mid\",\"security_allow\":[\"public\",\"internal\"],\"external\":false,\"max_difficulty\":4},{\"id\":\"fox-88\",\"context_limit\":12000,\"tools\":[\"search\"],\"latency_ms\":250,\"cost_tier\":\"low\",\"security_allow\":[\"public\",\"internal\",\"confidential\"],\"external\":false,\"max_difficulty\":3},{\"id\":\"외부모래-c1\",\"context_limit\":48000,\"tools\":[\"search\",\"cite\",\"code\"],\"latency_ms\":1100,\"cost_tier\":\"high\",\"security_allow\":[\"public\",\"internal\"],\"external\":true,\"max_difficulty\":5}]\nexecutor_trials(k=8): success 8 / fail 0","documents":[{"document_id":"NEXUS.SOP/μ204","text":"Quorix Clinical Supply Movement Rules assign dual control at the dock. The shipping technician prepares the kit tally and seals the outer shipper. Final countersignature authorizing the courier hand-off is reserved for the on-duty Clinical Supply Pharmacist; warehouse leads and study nurses may witness but may not replace that signature."},{"document_id":"NEXUS.WI/λ033","text":"Courier check-in at Gate B requires a badge scan and a printed dispatch note. The work instruction lists vehicle temperature checks and seal numbers but does not alter the pharmacist countersign requirement for investigational kits."},{"document_id":"NEXUS.POL/κ055","text":"Site access for external drivers is limited to the receiving apron. Drivers may not enter the kit vault under any circumstance described in the access policy."}]}

[Assistant] {"difficulty":1,"security":"internal","selection":"fox-88","reason_code":"ELIGIBLE_INTERNAL_LOW_DIFF","confidence":0.94}