2026-06-06 Agent Learning Consolidated

1. Agent output path / status

Missing agents: none.

2. Top cross-agent insights

Insight A — 08:00 brief should become a judgment interface, not a digest

• Rai and Zain converged on the same operating pattern: first screen must be 한 줄 결론 / 내 행동 / 리스크 / 근거, then P1/P2 judgment cards, then Watch/Verify.
• This is directly applicable to all domain agents: insurance becomes underwriting action, investment becomes position/watch action, news becomes follow-up/ignore/monitor action, code becomes operational health action.

Insight B — Korea AI/HBM is the dominant macro-news-investment cluster, but concentration risk is the key caveat

• News-agent sees Korea as AI infrastructure bottleneck owner: HBM/memory supplier + Nvidia customer + manufacturing/robotics testbed + policy beneficiary.
• KR-invest adds the trading caveat: KOSPI strength may be a narrow AI/HBM proxy rather than broad Korean-market strength. Breadth, FX, foreign flow, and global AI semiconductor peers decide short-term durability.

Insight C — Reliability and governance are becoming as important as content quality

• Code-senior’s Hermes/systemd learning is the infrastructure layer: cron/gateway/profile reliability must be observable, restart-limited, and auditable for unattended 01:00-08:00 work.
• Obsidian notes correctly set rag_index: include with review flags, but market/news/insurance notes require source verification before operational or binding use.

Insight D — Insurance DX opportunity is concrete: geofence + clause extraction + referral memo

• Insurance-dx’s JWC Listed Area topic maps naturally to a DX workflow: circular coordinates → versioned geofence → voyage route screening → wording extraction → underwriter referral pack.
• This is a strong candidate for code-senior follow-up, but should remain decision-support only; no auto-bind.

3. Useful signal vs weak/noisy items

Useful signals

• AI/HBM/Korea: semiconductor export surge, KOSPI AI/semiconductor concentration, Nvidia Korea engagement, HBM supply-chain dependence.
• Market risk: foreign selling, USD/KRW level, KOSPI breadth, Broadcom/Nvidia/Micron peer reaction as near-term multiple drivers.
• Insurance: JWC Listed Area expansion should trigger voyage referral, AP/terms review, sanctions screening, accumulation management, and wording-specific claims analysis.
• Operations: profile-specific Hermes gateway/cron health checks and systemd restart policy are necessary for reliable scheduled agent workflows.
• Report design/writing: fixed 4-line opening and mobile judgment cards reduce click-dependence and improve decision speed.

Weak / noisy / caution items

• News figures: several market/export numbers came from search snippets or rehosted summaries; verify against Reuters/Yonhap/KRX/MOTIE before citing as final facts.
• KOSPI level narratives: record-high/large-drop reports should not be interpreted without official market data, date alignment, breadth, and sector decomposition.
• Nvidia PR: TV shows, baseball first pitch, and social buzz are only surface signals; the real signal is HBM adoption, AI chip supply contracts, robotics/manufacturing partnerships.
• Insurance legal effect: listed-area status does not automatically determine each policy’s cover position; clause wording, declaration obligation, sanctions limitation, cancellation/held-covered language, and local law remain decisive.
• Hermes GitHub issue: self-restart loop issue is useful as a guardrail but unverified; do not treat as official behavior without local reproduction or docs confirmation.

4. Knowledge gaps and verification needs

Cross-domain

• Establish a standard source_quality scale across agents: primary / credible secondary / snippet / internal synthesis.
• Define when a nightly note can be used in an 08:00 brief without additional verification.
• Decide whether Telegram brief should show confidence/review flag inline for every P1 item.

Code-senior

• Inspect current Hermes version’s actual cron storage format and job-level provider/model override behavior.
• Check actual hermes gateway install unit file defaults: Restart, RestartSec, env loading, logs.
• Build/read-only profile health script candidate: gateway status + recent cron delivery + provider auth errors.

Insurance-dx

• Verify JWLA-033 and current JWC/JCC list from official LMA/IUA source before operational use.
• Check attached cargo/hull/P&I wordings for declaration, cancellation, sanctions, held-covered, and AP authority effects.
• Determine whether current bound voyages enter newly listed states/waters within 30 days.

KR-invest / news-agent

• Verify KOSPI, sector flow, foreign/institutional data using KRX or reliable market data.
• Confirm export figures against official MOTIE/customs release and Reuters/Yonhap original text.
• Track HBM4 qualification, Nvidia-Samsung/SK hynix supply allocation, and U.S. BIS export-control updates.

Rai / Zain

• Test whether 4칸 요약 + P1/P2 판단카드 + Watch/Verify fits within Telegram mobile first screen.
• Decide default action verbs by domain: insurance, investment, news, code/ops.
• Define maximum card count and fallback rule when more than two P1 candidates exist.

5. Tomorrow learning queue by agent

6. Telegram-ready 08:00 brief draft (<=12 Korean bullet lines)

• 한 줄 결론: 오늘 학습의 중심은 “AI/HBM은 강한 구조 신호지만, 시장·운영·보고 모두 검증/집중 리스크 관리가 필요”입니다.
• 내 행동: 08:00 브리프는 결론→내 행동→리스크→근거 4줄로 시작하고, P1/P2 판단카드만 상단에 올립니다.
• 리스크: 한국 AI 반도체 서사는 강하지만 KOSPI 랠리가 대형주/HBM에 과도하게 압축되면 환율·외국인 수급·글로벌 peer 뉴스에 취약합니다.
• 근거: 뉴스/투자 에이전트가 모두 HBM·엔비디아·한국 수출/증시 결합을 핵심 클러스터로 봤고, 동시에 breadth·FX·검증 필요를 표시했습니다.
• P1 투자: 지수보다 KRX 외국인/기관 수급, 전기전자 분리, 삼성전자/SK하이닉스 외 확산 여부를 먼저 확인합니다.
• P1 뉴스: 엔비디아 방한 화제성보다 HBM 채택, AI 칩 공급계약, 제조/로보틱스 협력, BIS 우회수출 규제를 추적합니다.
• P2 보험: JWC Listed Area 변경은 항해통보·AP·제재·누적관리 referral trigger로 보되, 실제 담보효과는 각 wording 검증 전 확정하지 않습니다.
• P2 운영: Hermes cron/gateway는 profile별 상태·로그·provider auth·최근 delivery까지 보는 health check가 필요합니다.
• 보고 방식: 링크를 누르지 않아도 판단 가능하게 한 줄 결론 / 내 행동 / 리스크 / 근거를 모든 짧은 알림의 첫 블록으로 고정합니다.
• 오늘 확인: KRX 수급·환율, 공식 수출자료, Nvidia/Samsung/SK hynix 발표, JWC 공식 리스트, Hermes unit/cron 실제 설정.
• 버릴 소음: 엔비디아 예능/시구, 단일 지수 헤드라인, 출처 불명 숫자, 보험 listed-area의 법적 효과 과잉단정.
• 다음 질문: 내일 아침 판단을 바꿀 1개 변수는 “AI/HBM 강세가 반도체 투톱 밖으로 확산되는가?”입니다.