Results for “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".

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

Turn an incident review into an HTML presentation covering the root cause, fix, and follow-up actions. Use a dedicated template with speaker notes to help engineering, reliability teams, and leadership discuss next steps.

• Presenting an incident review
• Explaining a bug's root cause and fix
• Discussing systemic follow-up actions

Investigate incidents and recurring defects with structured methods such as Five Whys and Fishbone cause maps. Identify multiple contributing conditions, build a blame-free account of what happened, and propose practical changes to prevent similar failures.

• Review a production outage
• Investigate recurring defects
• Compare failing and working environments

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.

The English summary is being prepared. Showing the original description.

Expert blueprint for stealth games (Splinter Cell, Hitman, Dishonored, Thief) covering AI detection systems, vision cones, sound propagation, alert states, light/shadow mechanics, and systemic design. Use when building stealth-action, tactical infiltration, or immersive sim games requiring enemy awareness systems. Keywords vision cone, detection, alert state, sound propagation, light level, systemic AI, gradual detection.

The English summary is being prepared. Showing the original description.

Expert blueprint for stealth games (Splinter Cell, Hitman, Dishonored, Thief) covering AI detection systems, vision cones, sound propagation, alert states, light/shadow mechanics, and systemic design. Use when building stealth-action, tactical infiltration, or immersive sim games requiring enemy awareness systems. Keywords vision cone, detection, alert state, sound propagation, light level, systemic AI, gradual detection.

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

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.

The English summary is being prepared. Showing the original description.

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

The English summary is being prepared. Showing the original description.

Review unresolved game bugs by separating impact from urgency, then recommend repair priorities and sprint assignments, meaning work planned for a development cycle. Reports also highlight recurring problems, older issues, and bugs in previously completed work.

• Prioritizing open bugs at the start of a sprint
• Organizing new bugs after a team QA review
• Reviewing a backlog with more than ten open bugs

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams

Build an AI system register for EU AI Act reviews. Track owners, deployment status, EU connections, and each system’s role and risk category through a guided discussion, preserving classification reasons and dates for future review.

• Register AI systems used or planned across an organization
• Review each system’s role and risk category
• Find systems approaching their next review date

Group bug reports by their underlying cause and plan shared fixes. This skill guides reproduction, checks for unnecessary complexity, and requires named test evidence before treating related issues as resolved.

• Grouping accumulated bug reports by root cause
• Planning one fix for several related issues
• Checking test evidence before closing issues

Develop security design improvements from vulnerability reports, incident documents, source code, or scan results. Compare architectural options with before-and-after diagrams, engineering tradeoffs, and migration plans to support a concrete design decision.

• Find structural causes shared by several vulnerabilities
• Compare security architecture options and costs
• Explain proposed changes with before-and-after diagrams