knowledge_check_resolve
Manually resolve a knowledge-check warning by choosing a resolution type such as extend, create, or defer, adhering to the enforced priority order.
Instructions
Resolve a single knowledge-check warning manually. In most cases you do NOT need this tool anymore — the pre-tool-use hook on flow_update auto-calls POST /api/projects/:id/knowledge/auto-resolve which applies the Iron Law in bulk (extend > create > intent_defer; never dismiss). Use this manual tool only for surgical overrides.
Iron Law of the LLM-Wiki: extend > create > intent_defer > NEVER dismiss. The backend now ENFORCES this — calling resolutionType='dismiss' when an extend-target exists returns 400 'iron_law_dismiss_blocked' with the recommended slug.
Resolution types:
'extend' — PREFERRED. Append a dated update section to an existing ADR/pattern/runbook. Pass entityType + entityId + body + rationale. Backend appends '## Update YYYY-MM-DD — extended by '.
'adr' — link to a NEW/existing ADR (entityType='adr', entityId=).
'pattern' — existing pattern doc covers it (entityType='doc_page', entityId=).
'runbook' — existing runbook covers it.
'intent_defer' — defer to a later flow. Seeds an intent doc-page; horizon: 'next-quarter'|'later'.
'dismiss' — LAST RESORT. Backend rejects this whenever an extend-target exists; reserved for genuinely off-topic mentions.
flowId = the flow the warning is attached to. topic = the warning's topic string (e.g. 'billing').
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| flowId | Yes | Flow id the warning belongs to | |
| topic | Yes | Topic string from the warning | |
| resolutionType | Yes | How this warning is being resolved | |
| entityType | No | Linked entity type ('adr' or 'doc_page'); for 'extend' it must point at the existing entry to extend | |
| entityId | No | Linked entity id | |
| reason | No | Free-text note (recommended for dismiss) | |
| horizon | No | For intent_defer: 'next-quarter' | 'later' | |
| body | No | DF-310 — for resolutionType='extend': the markdown content to append to the existing entity (1-3 paragraphs) | |
| rationale | No | DF-310 — for resolutionType='extend': one short sentence why this update matters |