markdowne8ad0934 | 1 | # Epistemic Playbook v1 |
| 2 | |
| 3 | ## Purpose |
| 4 | General reasoning layer for any domain: IT, research, strategy, and communication. |
| 5 | |
| 6 | ## Core Principles |
| 7 | - Separate observation, inference, and hypothesis confidence. |
| 8 | - Keep claims falsifiable and tied to measurable checks. |
| 9 | - Treat uncertainty explicitly; prefer reversible decisions under low confidence. |
| 10 | - Update quickly when evidence crosses pre-defined triggers. |
| 11 | |
| 12 | ## Main Sections |
| 13 | - Methodology and bridges: |
| 14 | - `epistemic-methodology-v1` |
| 15 | - `epistemic-to-it-bridge-v1` |
| 16 | - `epistemic-to-domain-bridge-v1` |
| 17 | - Heuristics and failure modes: |
| 18 | - `epistemic-hpmor-heuristics-v1` |
| 19 | - `epistemic-cognitive-failure-modes-v1` |
| 20 | - `epistemic-daily-checklist-v1` |
| 21 | - HPMOR (L1, по запросу): `hpmor-l1-pool-v1` в agent-notes; route_context('HPMOR'|'epistemic heuristics') или knowledge/agent-notes-l1-pool.md. |
| 22 | |
| 23 | ## Operational Contract |
| 24 | - Any major decision should include: |
| 25 | - confidence statement, |
| 26 | - disconfirming trigger, |
| 27 | - rollback condition. |
| 28 | - In incidents and architecture reviews, run epistemic checks alongside technical metrics. |
| 29 | |
| 30 | ## Maintenance Rules |
| 31 | - Keep this file concise and index-like. |
| 32 | - Keep narrative or chapter-level detail in canonical section blocks and archive revisions. |
| 33 | |
| 34 | |
View only · write via MCP/CIDE