Briefing — Iteration 4¶
Parent: HL-TFW-38 Goal: (A) Knowledge citation mandate — who must reference KNOWLEDGE.md and where. (B) Diagram creation enforcement — who forgets to draw diagrams and why. Predecessors: RES iter 1-3
Predecessor Decisions to Build On¶
- D1: §6-8 explicit enumeration in handoff.md (confirmed, ready)
- D6/D11: 4-stage review: Map → Verify → Judge → Decide (confirmed)
- D10: Diagram indexing in KNOWLEDGE.md §2 (collection side solved)
- Iter 1 root cause: template-workflow disconnect → agents skip what workflow doesn't mention
User-Injected Directions (post-RES3)¶
Thread A: Knowledge Citation Mandate¶
"Заставить координатор ссылаться на принципы и знания, если они есть у нас зафиксированные. Может кого-то еще стоит явно заставить на знания ссылку делать, что он их прям прочитал и увидел и они подходят под контекст задачи."
Thread B: Diagram Creation Enforcement¶
"Мы забыли про диаграммы. Мы продумали их сбор в docs. Но мы не продумали кто их забывает делать. Ресерчер и исполнитель забывают их рисовать."
Research Plan¶
Gather¶
- Thread A: Check which roles currently reference KNOWLEDGE.md. Scan plan.md, handoff.md, research/base.md for KNOWLEDGE.md references. Check real HL/TS files for D-number citations.
- Thread B: Check RF template §8 Diagrams section. Check RES template Findings Map section. Check handoff.md and research/base.md for diagram creation instructions. Count diagram presence in real RF/RES files.
Extract¶
- Thread A: Design the knowledge citation mandate — which roles, which workflows, what format.
- Thread B: Design the diagram creation mandate — which workflows need to add explicit instruction.
Challenge¶
- Thread A: Does mandatory citation create overhead for small tasks with no KNOWLEDGE.md?
- Thread B: Does mandatory diagramming create overhead for trivial tasks?
Guiding Questions¶
- Does KNOWLEDGE.md exist in all active projects, or only some?
- Which role currently references KNOWLEDGE.md the most — coordinator, executor, or researcher?
Stage complete: NO