ONB — {PREFIX}-{N} / Phase {X}: {Title}¶
Date: YYYY-MM-DD Author: {executor} Status: 🟠 ONB — Awaiting answers Parent HL: HL-{PREFIX}-{N} TS: TS Phase {X}
1. Understanding¶
{One-paragraph summary of what needs to be done and why}
2. Entry Points¶
{Key files and code areas relevant to the task}
3. Questions (blocking — cannot proceed without answers)¶
| # | Question | Answer |
|---|---|---|
| 1 | {question} | {coordinator fills in} |
4. Recommendations (suggestions, not blocking)¶
- {suggestion and rationale}
5. Risks Found (edge cases, potential issues not in TS)¶
- {risk description}
6. Inconsistencies with Code (spec vs reality)¶
- {what TS says} vs {what code actually does}
7. Knowledge Citations¶
Executor: read coordinator's citations in HL §7.2. For each item: - Confirm you read it (link + item name) - State how you applied it OR why it doesn't apply to your work - Add any NEW items you found relevant that coordinator missed
| # | HL §7.2 ref | Read? | Applied / N/A | Notes |
|---|---|---|---|---|
| 1 | {D-number or F-number from HL §7.2} | ✅ | {how applied or why N/A} |
For new projects where HL §7.2 says "No applicable knowledge items": write "No applicable knowledge items — confirmed."
Cross-references: use Reference Format (e.g.
[RF TFW-18](../../tasks/TFW-18__knowledge_consolidation/RF__PhaseB__knowledge_quality.md),D24,[TD-72](../tech-debt.md)). See compilable_contract.md §2. Build script resolves to hyperlinks.
ONB — {PREFIX}-{N} / Phase {X}: {Title} | YYYY-MM-DD