Failure modes
Type: kb/types/tag-readme.md
Failure-mode notes name recurring ways an agent-operated KB can fail despite having relevant artifacts on disk. Use this index when debugging why stored knowledge was not discovered, loaded, interpreted, or acted on.
Notes
- Knowledge storage does not imply contextual activation - core distinction between knowledge existing, being loaded, and actually affecting behavior
- Elicitation requires maintained question-generation systems - shows how inquiry processes decay when prompts stop generating discriminating questions
- Generality bought to avoid counterexamples is paid for in precision - the widening escape from counterexamples: vocabulary abstracts, content stays flat, prose becomes unreadable
- Narrowing bought to survive review is paid for in content - the narrowing escape: shrinking a defeated claim's subject into its own predicate yields an analytic title that passes every gate
- Domain pricing routes an exception to idealization assessment but does not decide it - names post-hoc immunization as the idealization escape's degenerate form and states the adequacy commitments that keep an idealized claim refutable
Related Tags
- LLM reliability - adjacent area: the deviation taxonomy and correction machinery for failures in how models interpret instructions and evidence
- Evaluation - methods for detecting whether failures are real and whether interventions improve behavior
Other tagged notes
- A consumption channel delivers force without the history that earned it - A consumption path can promote content into a higher-force role without checking whether an authorization covers that content, version, and use
- Abstract an experience into a lesson only when you can state where the lesson stops - Abstract an episode into a lesson only when you can state its boundary, else preserve the instance; an over-generalized lesson is one that drops the condition clause
- Generation confidence does not by itself certify soundness - Distinguishes next-token probability from factual truth and inferential validity: confidence can support correctness decisions only after task-specific validation, and high-assurance acceptance still needs a separate check
- Promotion selects for unreliable activation, and the regress ends only at an external trigger - Recasts promotion from 'the consumer lacks this' to 'the consumer will not apply this unprompted', and requires delivery to have a root firing event independent of that prior activation