From hatch3r
Canonical severity-vocabulary mapping between reviewer, fixer, security-auditor, check-criteria, and 9 content-quality specialists. Resolves vocabulary alignment for the fixer agent.
How this agent operates — its isolation, permissions, and tool access model
Agent reference
hatch3r:agents/shared/severity-mappingThe summary Claude sees when deciding whether to delegate to this agent
> Last updated: 2026-06-05 > Pillars: P2 (primary), P4 (supporting). > Canonical for: agents/hatch3r-reviewer.md, agents/hatch3r-fixer.md, the 9 CQ quality-vector specialists (agents/hatch3r-{ui,ux,security,reliability,testability,scalability,performance,maintainability,enhancability}.md), checks/*.md. Single source of truth for severity vocabulary alignment across all hatch3r content artifacts...Last updated: 2026-06-05 Pillars: P2 (primary), P4 (supporting). Canonical for: agents/hatch3r-reviewer.md, agents/hatch3r-fixer.md, the 9 CQ quality-vector specialists (agents/hatch3r-{ui,ux,security,reliability,testability,scalability,performance,maintainability,enhancability}.md), checks/*.md.
Single source of truth for severity vocabulary alignment across all hatch3r content artifacts. Audit findings (the canonical audit severity taxonomy) use 5 buckets: Critical, High, Medium, Low, Info. Other artifacts (reviewer agent, security auditor, check criteria) use their own vocabularies. This file maps them so the fixer agent can consume any source's output and map to the canonical bucket.
| Audit Severity (canonical) | Reviewer Verdict | Reviewer Level | Security-Auditor Severity | Check Criteria Tag | Specialist Status |
|---|---|---|---|---|---|
| Critical | DESIGN_OBJECTION | Critical | Critical | [CRITICAL] | CRITICAL |
| High | REQUEST CHANGES | Critical | High | [CRITICAL] | FINDINGS |
| Medium | REQUEST CHANGES | Warning | Medium | [RECOMMENDED] | FINDINGS |
| Low | APPROVE | Suggestion | Low | [RECOMMENDED] | PASS |
| Info | APPROVE | Suggestion | (n/a) | (n/a) | PASS |
DESIGN_OBJECTION because both express a fundamental, unfixable-by-iteration problem requiring architectural intervention. Reviewer Level Critical also maps when paired with REQUEST CHANGES and the issue is a security or correctness blocker.REQUEST CHANGES + Reviewer Level Critical. The reviewer's Critical level covers both canonical Critical and High; disambiguation uses verdict (DESIGN_OBJECTION → Critical, REQUEST CHANGES → High) and finding nature (architectural vs. quality gap).REQUEST CHANGES + Reviewer Level Warning and Security-Auditor Medium. These are quality gaps that block the current cycle but not the release.APPROVE + Reviewer Level Suggestion. The reviewer approves but flags improvements. Security-Auditor Low is the equivalent severity for security-domain findings.agents/hatch3r-{ui,ux,security,reliability,testability,scalability,performance,maintainability,enhancability}.md). CRITICAL maps to canonical Critical (any item shows a Critical-severity finding → DESIGN_OBJECTION-equivalent block). FINDINGS covers the canonical High + Medium band (Medium/High findings present, no Critical → REQUEST CHANGES). PASS maps to canonical Low + Info (every checklist item green or advisory-only → APPROVE). The collapse of two canonical buckets into one specialist value is intentional: specialists gate merge readiness, not finding-by-finding triage, so they emit a coarser status that the fixer re-expands via this row.agents/hatch3r-{ui,ux,security,reliability,testability,scalability,performance,maintainability,enhancability}.md): Output uses the Specialist Status column (PASS | FINDINGS | CRITICAL). Map to canonical via this table when escalating to fixer or feeding the release decision..md content file either uses canonical buckets or references this file.Critical overlaps two canonical buckets. Disambiguation rule: use DESIGN_OBJECTION verdict for canonical Critical, REQUEST CHANGES + Critical level for canonical High. When unclear, default to Critical (conservative for fixer blocking-action policy).[CRITICAL] covers canonical Critical + High; [RECOMMENDED] covers canonical Medium + Low. Severity-rollup reports must use the worst-case canonical mapping for [CRITICAL] tags (treat as canonical Critical until disambiguated by file/line context).confidence: low qualifier per the Confidence Expression section of agents/hatch3r-security.md.Critical/Major/Minor maps to canonical Critical/Medium/Low (WCAG A blockers → Critical; AA violations → Medium; advisory AA/AAA → Low). No direct High equivalent — escalate Major to High when the violation blocks a critical user journey.D22 / D23 / D24 admission (per the canonical audit domain map) adds three domain-specific severity vocabularies. Each row maps to the canonical Audit Severity column above.
| Domain | Source vocabulary | Bucket meaning | Canonical map |
|---|---|---|---|
| D22 Content Architecture | obsolete | Artifact serves no current pillar AND has zero cross-references | Critical (remove via D16-SA16.3 threshold) |
| D22 Content Architecture | merge_candidate | ≥80% conceptual overlap with another artifact AND removal threshold not met | High (merge the overlapping artifacts) |
| D22 Content Architecture | drift | Artifact frontmatter or body diverges from current pillar definitions | Medium |
| D22 Content Architecture | gap | Pillar is under-represented in the content corpus (per web-comparison findings) | Medium (CL-2 candidate) |
| D22 Content Architecture | coverage_low | Pillar served by <2 artifacts but pillar surface area expects ≥2 | Low |
| D23 Agentic Engineering Trends | lagging | hatch3r lacks a pattern adopted by ≥2 reputable comparables in ≤6 months | High |
| D23 Agentic Engineering Trends | trailing | hatch3r implements a pattern but ≥1 sub-element behind comparable | Medium |
| D23 Agentic Engineering Trends | leading | hatch3r ahead of all comparables on a pattern | Info (record as Strength) |
| D24 Governance Self-Audit | invariant_violation | A constitution invariant (e.g., lean threshold, anti-slop, pillar coverage) is broken | Critical |
| D24 Governance Self-Audit | process_drift | Audit cycle deviated from the audit-execute Phase contract | High |
| D24 Governance Self-Audit | traceability_gap | A change landed without a finding-registry entry or §8 amendment trail | Medium |
| D24 Governance Self-Audit | cadence_miss | Required cadence (re-envision ≥14 days, audit cycle, evolve) overdue | Low |
The Specialist Status column from the 6-Column Canonical Map applies to D22/D23/D24 SAs (PASS | FINDINGS | CRITICAL coarse status) — the bucket-level mapping above is the per-finding-row resolution within each SA's output. Consumers (fixer, reviewer) map the source bucket to canonical Audit Severity before applying action policy, identical to the Consumer Contract for existing domains.
A finding's source bucket maps to canonical Audit Severity per the table above. Two escalation rules then re-evaluate the row before it ships to the finding registry:
cross_domain_citations registry field; bands cap at Critical.Specialist Status column already collapses to PASS | FINDINGS | CRITICAL — the escalation re-expands to the canonical band the regression actually represents per the regression evidence file path + line cited in the finding body.Escalations chain: a CQ regression cited by ≥2 domain SAs receives two single-band escalations (capped at Critical). De-escalation is not permitted via these rules — a Critical never falls to High through this protocol; only the bias-check downgrade in the rigor contract (agents/shared/rigor-contract.md §Scientific Rigor Contract item 5) can reduce a severity band.
This file lives at agents/shared/severity-mapping.md. Enforcement is the inverse of a citation-count floor: scripts/validate-severity-vocabulary.ts (run via npm run validate:severity-vocabulary, wired into npm run validate) scans .md files under agents/, checks/, commands/, rules/, skills/, hooks/, and governance/ for off-canonical severity terms (Moderate, Major, Minor, Blocker, etc.) in a structured severity context (frontmatter severity:, severity-labeled table cells, Severity:/Level: pairs, bracket tags). A file that emits any such term MUST reference this file (basename severity-mapping.md) as the documented opt-out, or the scan emits a SEVERITY-MAPPING-MISS plus per-occurrence SEVERITY-OFF-CANONICAL error (exit 1). The set of referencing files is therefore demand-driven — it grows only when an artifact actually emits an off-canonical term — not a fixed minimum. The mapping doc's own absence at the canonical path makes the scan exit clean on a default-root run (the opt-out can no longer be relied on), so this file's presence is itself the enabling precondition.
npx claudepluginhub hatch3r/hatch3r --plugin hatch3rAutomated agent that triages issues, bugs, and vulnerabilities into S1-S4 severity levels via codebase analysis, impact assessment, and vulnerability pattern matching. Delivers structured reports with rationale, actions, and escalations.
Canonical reference agent that maps Light/Standard/Deep triage tiers to severity, complexity, effort, sub-agent count, and research depth. Used by triage-first orchestrators to calibrate task classification across workflows.
Strategy selector agent that maps criticality levels (C1-C4) to adversarial strategy sets per SSOT quality-enforcement.md, applies auto-escalation rules, enforces H-16 ordering, and produces ordered execution plans with template file paths.