Files
skills/public/hip-0240.html
zeekayandHanzo Dev 9e10c1c10e Each llms index points at the other two
hanzoskills.com/llms.txt now opens with the install line, the API
reference index and the company index, so an agent that lands on any
one of the three can find the rest.

robots.txt claimed 537 documents while llms.txt counts 920. The number
is gone from robots.txt; llms.txt derives it.

public/ is regenerated from scripts/site.py, which it had fallen
behind: the copy-prompt menu and agent bar were in the generator and
not in the committed pages. tests/site.mjs passes against the result.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-11 00:27:59 -07:00

314 lines
25 KiB
HTML

<!doctype html>
<html lang="en"><head>
<meta charset="utf-8"><meta name="viewport" content="width=device-width,initial-scale=1">
<title>hip-0240</title>
<meta name="color-scheme" content="dark">
<style>
/* Committed to one visual world: a dark instrument panel. No light variant —
the dot field and the hairline rules only read on black, and a naive
inversion would wash both out. Every colour is painted explicitly so the page
never borrows a host background. */
@font-face{font-family:'Zen';src:url('/fonts/Zen-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen';src:url('/fonts/Zen-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Variable.woff2') format('woff2');font-weight:100 900;font-style:normal;font-display:swap}
@font-face{font-family:'Zen Mono';src:url('/fonts/ZenMono-Italic-Variable.woff2') format('woff2');font-weight:100 900;font-style:italic;font-display:swap}
@font-face{font-family:'Zen Pixel Square';src:url('/fonts/ZenPixel-Square.woff2') format('woff2');font-style:normal;font-display:swap}
:root{
--ink:#f4f4f2; --soft:#9c9c98; --faint:#6a6a66; --ground:#000; --panel:#0a0a0a;
--line:#232323; --line-hi:#3a3a3a; --accent:#f4f4f2;
--font-zen-sans:'Zen',-apple-system,BlinkMacSystemFont,"Segoe UI",Helvetica,Arial,sans-serif;
--font-zen-mono:'Zen Mono',ui-monospace,"SF Mono",SFMono-Regular,Menlo,Consolas,monospace;
--font-zen-pixel-square:'Zen Pixel Square',monospace;
--mono:var(--font-zen-mono);
--sans:var(--font-zen-sans);
/* Controls are pills and surfaces are soft, as on hanzo.ai. */
--r:999px; --r-soft:14px;
}
*{box-sizing:border-box}
html{-webkit-text-size-adjust:100%}
body{margin:0;background:var(--ground);color:var(--ink);font-family:var(--sans);
font-size:16px;line-height:1.65;-webkit-font-smoothing:antialiased}
.wrap{max-width:60rem;margin:0 auto;padding:0 1.75rem}
/* The dot field. A halftone made of one repeating radial-gradient, faded out
along the diagonal by a mask so it reads as a wave rather than wallpaper. */
/* No overflow clip here: the dot field is inset to the box already, and a clip
would cut off the copy-prompt menu. */
.hero{position:relative;border-bottom:1px solid var(--line)}
.hero::before{content:"";position:absolute;inset:0;
background-image:radial-gradient(var(--line-hi) 1px, transparent 1px);
background-size:7px 7px;
-webkit-mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
mask-image:linear-gradient(115deg,#000 0%,rgba(0,0,0,.55) 38%,transparent 72%);
pointer-events:none}
.hero .wrap{position:relative;padding-top:5.5rem;padding-bottom:4rem}
nav{border-bottom:1px solid var(--line)}
nav .in{max-width:60rem;margin:0 auto;padding:1.1rem 1.75rem;display:flex;
justify-content:space-between;align-items:center;gap:1rem}
.brand{font-family:var(--mono);font-size:.85rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--ink);text-decoration:none;
display:inline-flex;align-items:center;gap:.6rem}
.brand i{font-style:normal;color:var(--faint)}
.mark{width:1.15em;height:1.15em;display:block;flex:0 0 auto}
nav a.up{font-family:var(--mono);font-size:.72rem;letter-spacing:.14em;
text-transform:uppercase;color:var(--soft);text-decoration:none}
nav a.up:hover{color:var(--ink)}
h1{font-family:var(--mono);font-size:clamp(2rem,5.4vw,3.4rem);line-height:1.12;
letter-spacing:-.02em;margin:0 0 1.1rem;font-weight:500;text-wrap:balance}
h1 em{font-style:normal;color:var(--faint)}
.lede{color:var(--soft);font-size:1.05rem;max-width:52ch;margin:0 0 2.25rem}
.btns{display:flex;flex-wrap:wrap;gap:.7rem;margin:0 0 .5rem;align-items:center}
.btn{display:inline-flex;align-items:center;gap:.5rem;font-family:var(--mono);
font-size:.72rem;letter-spacing:.14em;text-transform:uppercase;
padding:.8rem 1.4rem;border:1px solid var(--line-hi);border-radius:var(--r);
color:var(--ink);text-decoration:none;background:transparent;cursor:pointer;
line-height:1.2;font-weight:400}
.btn:hover{background:#141414;text-decoration:none;border-color:var(--soft)}
.btn.solid{background:var(--ink);color:#000;border-color:var(--ink)}
.btn.solid:hover{background:#d8d8d4}
.btn .chev{width:.7em;height:.7em;flex:0 0 auto;transition:transform .15s ease}
.btn[aria-expanded="true"] .chev{transform:rotate(180deg)}
/* Copy-prompt selector. Each row copies the prompt for its own target. */
.copy{position:relative;display:inline-flex}
.menu{position:absolute;top:calc(100% + .5rem);left:0;z-index:20;min-width:21rem;
background:var(--panel);border:1px solid var(--line-hi);border-radius:var(--r-soft);
padding:.4rem;display:flex;flex-direction:column;
box-shadow:0 12px 32px rgba(0,0,0,.75)}
.menu[hidden]{display:none}
.mi{display:flex;align-items:center;gap:.7rem;width:100%;text-align:left;
padding:.62rem .8rem;border:0;border-radius:calc(var(--r-soft) - .35rem);
background:transparent;color:var(--ink);font-family:var(--mono);font-size:.76rem;
letter-spacing:.04em;text-decoration:none;cursor:pointer;line-height:1.3;
white-space:nowrap}
.mi:hover,.mi:focus-visible{background:#181818;outline:none}
.mi .mark{width:1.05rem;height:1.05rem;color:var(--soft)}
.mi:hover .mark{color:var(--ink)}
.mi u{margin-left:auto;color:var(--faint);text-decoration:none;font-size:.68rem;
letter-spacing:.1em;text-transform:uppercase}
/* Works-with bar: one scrolling row, name and mark per agent. */
.strip{border-bottom:1px solid var(--line);background:var(--panel)}
.strip .in{max-width:60rem;margin:0 auto;padding:.9rem 1.75rem;display:flex;
align-items:center;gap:1.25rem;font-family:var(--mono);font-size:.72rem;
letter-spacing:.1em;text-transform:uppercase;color:var(--faint)}
.strip b{color:var(--soft);font-weight:400;flex:0 0 auto;
border-right:1px solid var(--line);padding-right:1.25rem;align-self:stretch;
display:flex;align-items:center}
.bar{display:flex;align-items:center;gap:.5rem;flex:1 1 auto;min-width:0;
overflow-x:auto;scrollbar-width:none;scroll-snap-type:x proximity;
-webkit-overflow-scrolling:touch;
-webkit-mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent);
mask-image:linear-gradient(90deg,#000 calc(100% - 3rem),transparent)}
.bar::-webkit-scrollbar{display:none}
.agent{display:inline-flex;align-items:center;gap:.45rem;flex:0 0 auto;
padding:.4rem .85rem;border:1px solid var(--line);border-radius:var(--r);
color:var(--soft);white-space:nowrap;scroll-snap-align:start;
text-decoration:none;background:var(--ground)}
.agent:hover{color:var(--ink);border-color:var(--line-hi);text-decoration:none}
.agent .mark{width:.95rem;height:.95rem}
h2{font-family:var(--mono);font-size:1.1rem;letter-spacing:-.01em;margin:2.75rem 0 .75rem;font-weight:500}
h3{font-size:1rem;margin:2rem 0 .5rem;font-weight:600}
h4,h5,h6{font-size:.94rem;margin:1.5rem 0 .5rem;font-weight:600}
p{margin:0 0 1rem;max-width:70ch}
ul,ol{margin:0 0 1rem;padding-left:1.35rem;max-width:70ch}
li{margin:.22rem 0}
a{color:var(--ink);text-decoration:underline;text-underline-offset:3px;
text-decoration-color:var(--line-hi)}
a:hover{text-decoration-color:var(--ink)}
a:focus-visible{outline:1px solid var(--ink);outline-offset:3px}
code{font-family:var(--mono);font-size:.85em;background:var(--panel);
border:1px solid var(--line);border-radius:5px;padding:.1em .36em}
pre{background:var(--panel);border:1px solid var(--line);padding:1rem 1.1rem;
border-radius:var(--r-soft);overflow-x:auto;margin:0 0 1.25rem}
pre code{background:none;border:0;padding:0;font-size:.82rem;line-height:1.7}
blockquote{margin:0 0 1rem;padding-left:1rem;border-left:1px solid var(--line-hi);color:var(--soft)}
hr{border:0;border-top:1px solid var(--line);margin:2.5rem 0}
table{border-collapse:collapse;width:100%;margin:0 0 1.25rem;font-size:.92rem;
display:block;overflow-x:auto}
th,td{border:1px solid var(--line);padding:.5rem .7rem;text-align:left}
.curl{display:block;background:var(--panel);border:1px solid var(--line);
border-radius:var(--r-soft);padding:.95rem 1.1rem;font-family:var(--mono);
font-size:.8rem;color:var(--soft);overflow-x:auto;margin:0 0 2.5rem;
white-space:pre;line-height:1.9}
.curl b{color:var(--ink);font-weight:400}
.curl i{font-style:normal;color:var(--faint)}
/* index */
#q{width:100%;padding:.85rem 1.2rem;font-family:var(--mono);font-size:.85rem;color:var(--ink);
background:var(--panel);border:1px solid var(--line);border-radius:var(--r);margin:0 0 .6rem}
#q::placeholder{color:var(--faint);text-transform:uppercase;letter-spacing:.1em;font-size:.72rem}
#q:focus{outline:none;border-color:var(--soft)}
#count{color:var(--faint);font-family:var(--mono);font-size:.72rem;letter-spacing:.1em;
text-transform:uppercase;margin:0 0 2rem}
.cat{margin:2.5rem 0 .5rem;font-family:var(--mono);font-size:.7rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);border-bottom:1px solid var(--line);
padding-bottom:.45rem}
.row{display:block;padding:.6rem .9rem;margin:0 -.9rem;border-bottom:1px solid var(--line);
border-radius:var(--r-soft);text-decoration:none}
.row:hover{background:#0a0a0a}
.nm{font-family:var(--mono);font-size:.84rem;color:var(--ink);display:block}
.ds{color:var(--soft);font-size:.9rem;display:block;margin-top:.12rem}
footer{margin-top:4rem;padding:2rem 0 4rem;border-top:1px solid var(--line);
color:var(--faint);font-size:.85rem}
footer a{color:var(--soft)}
.fmap{display:grid;gap:1.75rem;grid-template-columns:repeat(auto-fit,minmax(11rem,1fr));
margin:0 0 2rem;font-size:.85rem}
.fmap b{display:block;font-family:var(--mono);font-size:.68rem;letter-spacing:.16em;
text-transform:uppercase;color:var(--faint);font-weight:400;margin:0 0 .6rem;
border-bottom:1px solid var(--line);padding-bottom:.4rem}
.fmap a{display:inline-block;color:var(--ink);text-decoration:none;margin:.3rem .35rem 0 0}
.fmap a:hover{text-decoration:underline}
.fmap div{color:var(--faint);line-height:1.5}
.fend{border-top:1px solid var(--line);padding-top:1.25rem;font-size:.82rem}
@media (max-width:640px){
.hero .wrap{padding-top:3.25rem;padding-bottom:2.75rem}
.btns{gap:.5rem}
.btn{padding:.75rem 1.15rem;font-size:.68rem}
.copy,.copy .btn{width:100%;justify-content:center}
.menu{left:0;right:0;min-width:0}
.strip .in{flex-direction:column;align-items:flex-start;gap:.6rem;padding:.9rem 1.75rem}
.strip b{border-right:0;padding-right:0}
.bar{width:100%}
}
</style>
<link rel="alternate" type="text/markdown" href="/hip-0240.md">
<link rel="icon" href="/favicon.svg">
<link rel="canonical" href="https://hanzoskills.com/hip-0240">
</head>
<!-- Reading this with a machine? Every page here is also plain markdown.
This one: https://hanzoskills.com/hip-0240.md
Index: https://hanzoskills.com/llms.txt
Corpus: https://hanzoskills.com/all.md
Append .md to any path for the markdown twin. -->
<body>
<nav><div class="in">
<a class="brand" href="/"><svg class="mark" viewBox="0 0 67 67" fill="currentColor" aria-hidden="true"><path d="M22.21 67V44.6369H0V67H22.21Z"/><path d="M66.7038 22.3184H22.2534L0.0878906 44.6367H44.4634L66.7038 22.3184Z"/><path d="M22.21 0H0V22.3184H22.21V0Z"/><path d="M66.7198 0H44.5098V22.3184H66.7198V0Z"/><path d="M66.7198 67V44.6369H44.5098V67H66.7198Z"/></svg> HANZO<i>SKILLS</i></a>
<a class="up" href="/">All skills</a>
</div></nav>
<div class="wrap">
<h1>hip-0240</h1><p class="lede">HIP-240: AI Incident Response. Status Living. Hanzo architectural specification.</p><h1>HIP-0240: AI Incident Response</h1>
<h2>Abstract</h2>
<p>This HIP establishes the incident response framework for AI safety and ethics incidents at Hanzo AI. It defines incident categories, response procedures, communication protocols, and post-incident review processes.</p>
<h2>Incident Definition</h2>
<h3>What Constitutes an AI Incident</h3>
<p>An AI incident is any event where an AI system:</p>
<ol><li>Causes or could cause harm to users or third parties</li><li>Behaves in unexpected or unintended ways</li><li>Violates safety guidelines or policies</li><li>Experiences a significant failure affecting trust or safety</li><li>Is subject to successful adversarial attack</li></ol>
<h3>Incident Categories</h3>
<h4>Safety Incidents</h4>
<p>| Category | Examples | |----------|----------| | <strong>Harmful output</strong> | Generated dangerous, illegal, or harmful content | | <strong>Safety bypass</strong> | Successful jailbreak or guardrail circumvention | | <strong>Misuse</strong> | System used for malicious purposes | | <strong>Unintended capability</strong> | System displays unexpected capabilities |</p>
<h4>Performance Incidents</h4>
<p>| Category | Examples | |----------|----------| | <strong>Quality degradation</strong> | Significant accuracy decrease | | <strong>Hallucination spike</strong> | Increased false information | | <strong>Availability failure</strong> | Service outage or degradation | | <strong>Latency issues</strong> | Unacceptable response times |</p>
<h4>Fairness Incidents</h4>
<p>| Category | Examples | |----------|----------| | <strong>Bias detection</strong> | Systematic bias discovered | | <strong>Discrimination</strong> | Unfair treatment of user groups | | <strong>Exclusion</strong> | Groups unable to use service |</p>
<h4>Security Incidents</h4>
<p>| Category | Examples | |----------|----------| | <strong>Data breach</strong> | Training data or user data exposed | | <strong>Model theft</strong> | Unauthorized model extraction | | <strong>Adversarial attack</strong> | Successful attack on model | | <strong>Prompt injection</strong> | System manipulation via inputs |</p>
<h2>Incident Severity</h2>
<h3>Severity Levels</h3>
<p>| Level | Definition | Examples | |-------|------------|----------| | <strong>Critical (P0)</strong> | Immediate, severe harm potential | CSAM generation, weapons instructions, mass harm | | <strong>High (P1)</strong> | Significant harm or widespread impact | Widespread harmful content, major bias issue | | <strong>Medium (P2)</strong> | Moderate harm or limited impact | Isolated harmful outputs, localized issues | | <strong>Low (P3)</strong> | Minor issues, low harm potential | Edge cases, minor quality issues |</p>
<h3>Severity Determination</h3>
<p>| Factor | Considerations | |--------|----------------| | <strong>Harm potential</strong> | Type and severity of possible harm | | <strong>Scope</strong> | Number of users affected | | <strong>Reversibility</strong> | Can harm be undone? | | <strong>Exploitability</strong> | How easily can this be reproduced? | | <strong>Visibility</strong> | Public awareness level |</p>
<h2>Response Procedures</h2>
<h3>Incident Response Phases</h3>
<pre><code>Detection → Triage → Containment → Investigation → Remediation → Recovery → Review</code></pre>
<h3>Phase 1: Detection</h3>
<h4>Detection Sources</h4>
<p>| Source | Examples | |--------|----------| | <strong>Automated monitoring</strong> | Safety classifiers, anomaly detection | | <strong>User reports</strong> | Bug reports, safety reports | | <strong>Internal discovery</strong> | Employee observation, testing | | <strong>External reports</strong> | Security researchers, media | | <strong>Third-party</strong> | Partners, regulators |</p>
<h4>Reporting Channels</h4>
<p>| Channel | For | |---------|-----| | <strong>Safety hotline</strong> | Internal urgent reports | | <strong>Safety email</strong> | Internal non-urgent reports | | <strong>Bug bounty</strong> | External security reports | | <strong>Support channels</strong> | User reports | | <strong>Executive escalation</strong> | Critical issues |</p>
<h3>Phase 2: Triage</h3>
<h4>Initial Assessment (Within 15 minutes for P0/P1)</h4>
<p>| Step | Action | |------|--------| | 1 | Validate incident is real | | 2 | Determine severity level | | 3 | Identify affected systems | | 4 | Assign incident commander | | 5 | Notify required stakeholders |</p>
<h4>Triage Checklist</h4>
<p>| Question | Purpose | |----------|---------| | What happened? | Understand the incident | | Who is affected? | Scope assessment | | Is it ongoing? | Urgency determination | | Can it be reproduced? | Exploitability | | What&#x27;s the harm potential? | Severity rating |</p>
<h3>Phase 3: Containment</h3>
<h4>Containment Actions</h4>
<p>| Severity | Response Time | Actions | |----------|---------------|---------| | <strong>P0</strong> | Immediate | Emergency shutdown if needed, immediate patch | | <strong>P1</strong> | &lt;1 hour | Feature disable, rate limiting, filter deployment | | <strong>P2</strong> | &lt;4 hours | Targeted mitigations, monitoring increase | | <strong>P3</strong> | &lt;24 hours | Standard fix process |</p>
<h4>Containment Options</h4>
<p>| Action | Use Case | |--------|----------| | <strong>Kill switch</strong> | Immediate system shutdown (P0 only) | | <strong>Feature disable</strong> | Turn off affected feature | | <strong>Rate limiting</strong> | Slow down potential abuse | | <strong>Filter deployment</strong> | Block specific inputs/outputs | | <strong>Model rollback</strong> | Revert to previous version | | <strong>Access restriction</strong> | Limit affected user access |</p>
<h3>Phase 4: Investigation</h3>
<h4>Investigation Scope</h4>
<p>| Area | Questions | |------|-----------| | <strong>Root cause</strong> | Why did this happen? | | <strong>Timeline</strong> | When did it start? How long active? | | <strong>Impact</strong> | Who/what was affected? How severely? | | <strong>Detection</strong> | Why wasn&#x27;t this caught earlier? | | <strong>Similar issues</strong> | Are there related vulnerabilities? |</p>
<h4>Evidence Collection</h4>
<p>| Evidence Type | Collection Method | |---------------|-------------------| | <strong>Logs</strong> | System logs, API logs, safety logs | | <strong>Outputs</strong> | Examples of problematic outputs | | <strong>Inputs</strong> | Triggering inputs/prompts | | <strong>Metrics</strong> | Relevant monitoring data | | <strong>User reports</strong> | All related user feedback |</p>
<h4>Investigation Team</h4>
<p>| Role | Responsibility | |------|----------------| | <strong>Incident Commander</strong> | Overall coordination | | <strong>Technical Lead</strong> | Technical investigation | | <strong>Safety Lead</strong> | Safety assessment | | <strong>Legal</strong> | Legal implications (if needed) | | <strong>Communications</strong> | External communication prep |</p>
<h3>Phase 5: Remediation</h3>
<h4>Remediation Planning</h4>
<p>| Element | Description | |---------|-------------| | <strong>Fix identification</strong> | Determine appropriate fix | | <strong>Testing</strong> | Verify fix works, no regressions | | <strong>Deployment plan</strong> | How to roll out fix | | <strong>Validation</strong> | How to confirm resolution |</p>
<h4>Fix Types</h4>
<p>| Fix Type | Timeline | Use Case | |----------|----------|----------| | <strong>Hotfix</strong> | Immediate | Critical safety issues | | <strong>Patch</strong> | &lt;24 hours | High-priority fixes | | <strong>Update</strong> | Standard release | Medium/low priority | | <strong>Major change</strong> | Planned release | Significant changes needed |</p>
<h3>Phase 6: Recovery</h3>
<h4>Recovery Steps</h4>
<ol><li>Deploy fix</li><li>Validate resolution</li><li>Remove containment measures</li><li>Monitor for recurrence</li><li>Confirm normal operation</li></ol>
<h4>Recovery Verification</h4>
<p>| Check | Method | |-------|--------| | <strong>Issue resolved</strong> | Reproduce attempt fails | | <strong>No regressions</strong> | Standard tests pass | | <strong>Performance normal</strong> | Metrics within bounds | | <strong>User experience</strong> | Sample verification |</p>
<h3>Phase 7: Post-Incident Review</h3>
<h4>Review Timeline</h4>
<p>| Severity | Review Timeline | |----------|-----------------| | <strong>P0</strong> | Within 72 hours | | <strong>P1</strong> | Within 1 week | | <strong>P2</strong> | Within 2 weeks | | <strong>P3</strong> | Monthly batch review |</p>
<h4>Post-Incident Report</h4>
<p>| Section | Contents | |---------|----------| | <strong>Summary</strong> | What happened, when, impact | | <strong>Timeline</strong> | Detailed event sequence | | <strong>Root cause</strong> | Why it happened | | <strong>Response</strong> | What we did | | <strong>Impact</strong> | Users/systems affected | | <strong>Lessons learned</strong> | What we learned | | <strong>Action items</strong> | Preventive measures |</p>
<h2>Communication</h2>
<h3>Internal Communication</h3>
<h4>Notification Matrix</h4>
<p>| Severity | Immediate | Within 1 Hour | Within 24 Hours | |----------|-----------|---------------|-----------------| | <strong>P0</strong> | CEO, CTO, Legal, Safety Lead | ESG Committee, Board | All leadership | | <strong>P1</strong> | CTO, Safety Lead | Product Lead, ESG Committee | Department heads | | <strong>P2</strong> | Safety Lead | Product Lead | Team leads | | <strong>P3</strong> | Team lead | - | - |</p>
<h4>Communication Channels</h4>
<p>| Channel | Use | |---------|-----| | <strong>War room (P0/P1)</strong> | Real-time coordination | | <strong>Incident Slack</strong> | Updates, coordination | | <strong>Email</strong> | Formal notifications | | <strong>Ticket</strong> | Tracking, documentation |</p>
<h3>External Communication</h3>
<h4>Communication Decision Tree</h4>
<pre><code>Is public aware?
↓ Yes ↓ No
Proactive comms Is disclosure required?
↓ ↓ Yes ↓ No
Disclose Monitor</code></pre>
<h4>Communication Templates</h4>
<p>| Situation | Elements | |-----------|----------| | <strong>Initial acknowledgment</strong> | We&#x27;re aware, investigating, user steps | | <strong>Update</strong> | What we know, what we&#x27;re doing, timeline | | <strong>Resolution</strong> | What happened, what we did, preventive measures |</p>
<h4>Disclosure Requirements</h4>
<p>| Trigger | Disclosure | |---------|------------| | <strong>User data affected</strong> | Required notification (per jurisdiction) | | <strong>Significant public harm</strong> | Proactive disclosure recommended | | <strong>Regulatory requirement</strong> | Per applicable law | | <strong>Media inquiry</strong> | Coordinated response |</p>
<h2>Roles &amp; Responsibilities</h2>
<h3>Incident Response Team</h3>
<p>| Role | Responsibility | On-Call | |------|----------------|---------| | <strong>Incident Commander</strong> | Overall coordination | 24/7 rotation | | <strong>Technical Lead</strong> | Technical investigation/fix | 24/7 rotation | | <strong>Safety Lead</strong> | Safety assessment | 24/7 rotation | | <strong>Communications Lead</strong> | External communications | Business hours + on-call | | <strong>Legal</strong> | Legal assessment | On-call |</p>
<h3>Escalation Authority</h3>
<p>| Decision | Authority | |----------|-----------| | <strong>Containment actions</strong> | Incident Commander | | <strong>Model shutdown</strong> | CTO or CEO | | <strong>External communication</strong> | Communications + Legal | | <strong>Regulatory notification</strong> | Legal + CEO |</p>
<h2>Continuous Improvement</h2>
<h3>Metrics Tracking</h3>
<p>| Metric | Target | |--------|--------| | <strong>Time to detection</strong> | Reduce over time | | <strong>Time to containment</strong> | &lt;1 hour for P0/P1 | | <strong>Time to resolution</strong> | Per severity SLAs | | <strong>Recurrence rate</strong> | Zero recurrence of same issue |</p>
<h3>Training &amp; Drills</h3>
<p>| Activity | Frequency | |----------|-----------| | <strong>Incident response training</strong> | Annual for all team | | <strong>Tabletop exercises</strong> | Quarterly | | <strong>Full drills</strong> | Biannual | | <strong>Red team exercises</strong> | Continuous |</p>
<h3>Process Improvement</h3>
<ul><li>Review all incidents quarterly</li><li>Update procedures based on learnings</li><li>Share learnings (appropriately) with community</li><li>Benchmark against industry practices</li></ul>
<h2>Related HIPs</h2>
<ul><li><strong>HIP-200</strong>: Responsible AI Principles</li><li><strong>HIP-201</strong>: Model Risk Management</li><li><strong>HIP-210</strong>: Safety Evaluation Framework</li><li><strong>HIP-220</strong>: Bias Detection &amp; Mitigation</li><li><strong>HIP-230</strong>: AI Transparency &amp; Explainability</li><li><strong>HIP-290</strong>: Evidence Locker Index</li></ul>
<h2>Changelog</h2>
<p>| Version | Date | Changes | |---------|------|---------| | 1.0 | 2025-12-17 | Initial draft |</p>
<h2>Copyright</h2>
<p>Copyright and related rights waived via <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0</a>.</p>
<footer>
<div class="fmap">
<div><b>Build</b>
<a href="https://hanzo.app">hanzo.app</a> app builder
<a href="https://hanzo.codes">hanzo.codes</a> code with an agent
<a href="https://hanzoskills.com">hanzoskills.com</a> what an agent reads</div>
<div><b>Run</b>
<a href="https://console.hanzo.ai">console.hanzo.ai</a> cloud console
<a href="https://api.hanzo.ai">api.hanzo.ai</a> the API</div>
<div><b>Account</b>
<a href="https://hanzo.id">hanzo.id</a> sign in
<a href="https://pay.hanzo.ai">pay.hanzo.ai</a> top up
<a href="https://billing.hanzo.ai">billing.hanzo.ai</a> invoices and usage</div>
<div><b>Company</b>
<a href="https://hanzo.ai">hanzo.ai</a> canonical
<a href="https://hanzo.ventures">hanzo.ventures</a> ventures</div>
</div>
<div class="fend"><a href="/hip-0240.md">This page as plain text</a> · <a href="/llms.txt">Index for agents</a></div>
</footer>
</div></body></html>