「systemic」の検索結果

Assess compliance with the EU General-Purpose AI (GPAI) Code of Practice under the AI Act (Regulation (EU) 2024/1689). Use when asked to determine GPAI model provider obligations, assess Code of Practice compliance, evaluate transparency or copyright requirements for GPAI models, check systemic risk obligations, build a GPAI compliance roadmap, or prepare for AI Office requests. Covers all three Code chapters (Transparency, Copyright, Safety & Security), the 12 commitments and their measures, systemic risk classification (Article 51), provider obligations (Articles 53 and 55), open-source exemptions, enforcement timeline, Commission/AI Office supervision, and DACH-specific overlays such as BSI cybersecurity and works council implications. Triggers on phrases like "GPAI compliance", "Code of Practice assessment", "GPAI model obligations", "systemic risk evaluation", "AI Act transparency requirements", "GPAI copyright policy", "general-purpose AI compliance".

日本語の概要は準備中です。原文の説明を表示しています。

システム療法および解決志向アプローチの手法：ミラクル・クエスチョン、スケーリング、例外の探索、サーキュラー・クエスチョン、仮定の質問、悪化の質問、コーピング・クエスチョン。solution-focused-therapy および systemic-questioning から統合。

Systemic questioning techniques: Circular questions, scaling questions, miracle question, and exception questions for reflection and perspective expansion.

日本語の概要は準備中です。原文の説明を表示しています。

Systemic and solution-focused methods: miracle question, scaling, exception exploration, circular questions, hypothetical questions, worsening questions, coping questions. Merged from solution-focused-therapy and systemic-questioning.

日本語の概要は準備中です。原文の説明を表示しています。

Structured incident investigation using Five Whys, Fishbone, blameless Postmortem, Fault Tree, Kepner-Tregoe, and FMEA — traces failures to systemic root causes rather than blaming humans. USE WHEN root cause, RCA, 5 whys, fishbone, postmortem, incident analysis, fault tree, why does this keep failing, blameless, recurring bug. NOT FOR systemic loops (use SystemsThinking).

日本語の概要は準備中です。原文の説明を表示しています。

Determines whether a technology qualifies as an AI system under Art. 3(1) of the EU AI Act and classifies its risk tier (prohibited, high-risk, GPAI with systemic risk, limited risk, minimal risk). This skill should be used when the user asks to "classify an AI system under the AI Act", "determine the AI Act risk tier", "check if something is an AI system", "assess prohibited practices", "check high-risk classification", "determine Art. 6 exception applicability", or mentions "KI-Verordnung", "Risikoklassifizierung", Art. 5, Annex III, or GPAI systemic risk.

日本語の概要は準備中です。原文の説明を表示しています。

Conduct a blameless post-mortem analysis after an incident. Build timeline reconstruction, identify contributing factors, and generate actionable improvements. Focus on systemic issues rather than individual blame. Use after any production incident or service degradation, following a near-miss, when investigating recurring issues, or to share systemic learnings across teams.

日本語の概要は準備中です。原文の説明を表示しています。

Deep root cause analysis using the 5 Whys and Fishbone techniques. Use when systematic debugging hasn't found the cause, or for complex systemic issues. Keywords: root cause, why, underlying, fundamental, systemic, deep, origin

日本語の概要は準備中です。原文の説明を表示しています。

Системные и ориентированные на решение методы: чудесный вопрос, шкалирование, поиск исключений, циркулярные вопросы, гипотетические вопросы, вопросы на ухудшение, вопросы на преодоление. Объединено из solution-focused-therapy и systemic-questioning.

日本語の概要は準備中です。原文の説明を表示しています。

Техники системных вопросов: циркулярные вопросы, шкалирующие вопросы, вопрос о чуде и вопросы об исключениях для рефлексии и расширения перспектив.

日本語の概要は準備中です。原文の説明を表示しています。

Métodos sistémicos y enfocados en soluciones: pregunta del milagro, escala, exploración de excepciones, preguntas circulares, preguntas hipotéticas, preguntas de empeoramiento, preguntas de afrontamiento. Fusionado de solution-focused-therapy y systemic-questioning.

日本語の概要は準備中です。原文の説明を表示しています。

Técnicas de preguntas sistémicas: Preguntas circulares, preguntas de escala, la pregunta del milagro y preguntas de excepción para la reflexión y la ampliación de perspectivas.

日本語の概要は準備中です。原文の説明を表示しています。

系统提问技术：循环提问、刻度提问、奇迹提问和例外提问，用于自我反思与视角拓宽。

日本語の概要は準備中です。原文の説明を表示しています。

システム質問技法：リフレクションと視点の拡張のための循環質問、スケーリング質問、ミラクル・クエスチョン、例外質問。

系统化与焦点解决方法：奇迹提问、刻度提问、例外探索、循环提问、假设性提问、恶化提问、应对提问。合并自 solution-focused-therapy 与 systemic-questioning。

日本語の概要は準備中です。原文の説明を表示しています。

Comparison of the four guideline-approved psychotherapy approaches in Germany: Cognitive Behavioral Therapy, Psychodynamic Therapy, Psychoanalysis, Systemic Therapy — Orientation guide.

日本語の概要は準備中です。原文の説明を表示しています。

OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.

日本語の概要は準備中です。原文の説明を表示しています。

Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.

日本語の概要は準備中です。原文の説明を表示しています。

Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.

日本語の概要は準備中です。原文の説明を表示しています。

EU AI Act per-system inventory — track each AI system's role (provider, deployer, importer, distributor, authorized representative, product manufacturer) and risk tier (prohibited, high-risk, limited, minimal, GPAI, GPAI+systemic). Role and tier are assessed per system, not per company. Use when the user says "ai inventory", "add an ai system", "what systems do we have", "classify this ai system", "eu ai act register", or "ai system registry".

日本語の概要は準備中です。原文の説明を表示しています。

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

日本語の概要は準備中です。原文の説明を表示しています。

Develop evidence-backed structural and architectural security hardening proposals from vulnerability disclosures, supplied findings, incident or assessment documents, source code, or a completed Codex Security scan. Use when a user asks for systemic improvements, alternatives beyond per-finding patches, before-and-after security architecture views, engineering tradeoff analysis, or an implementation-ready plan for a selected hardening option. Also use automatically after a Codex Security scan with reportable findings when the top-level scan workflow requests final-report hardening guidance.

日本語の概要は準備中です。原文の説明を表示しています。

Experimental workflow for auditing recurring feedback, telemetry, errors, and brittle delivery paths to find systemic fixes. Use for periodic or requested cross-source lookbacks, not routine single-item intake.

日本語の概要は準備中です。原文の説明を表示しています。

Query the OFR (Office of Financial Research) Hedge Fund Monitor API for hedge fund data including SEC Form PF aggregated statistics, CFTC Traders in Financial Futures, FICC Sponsored Repo volumes, and FRB SCOOS dealer financing terms. Access time series data on hedge fund size, leverage, counterparties, liquidity, complexity, and risk management. No API key or registration required. Use when working with hedge fund data, systemic risk monitoring, financial stability research, hedge fund leverage or leverage ratios, counterparty concentration, Form PF statistics, repo market data, or OFR financial research data.

日本語の概要は準備中です。原文の説明を表示しています。