Knowledge: Stakeholder¶
Topic file for
stakeholderfacts. Updated by/tfw-knowledge. See KNOWLEDGE.md §4 for the index.
| # | Fact | Verified | Source(s) | Added |
|---|---|---|---|---|
| F1 | README positioning: business/operations audience FIRST, engineering second. "TFW is not about code. It's about making decisions visible and knowledge permanent." Business value > technical value in all public-facing messaging. «Бизнес валью важнее. Мы отличаемся тем, что думаем не про технику, а про валью» | ⚠️ 1 source | HL TFW-27/A S9 (user, README review session) | 2026-04-08 |
| F2 | File naming should encode execution order — external user feedback: «стадии лежат в алфавитном порядке и не всегда понятно что зачем читать». Numbered prefixes (1_briefing, 2_gather, etc.) are a UX principle for methodology artifacts, not just a naming convention. Implemented in TFW-42 | ⚠️ 1 source | HL TFW-42 §11 S2 (external user feedback relayed by author) | 2026-04-30 |
| F3 | Agents close tasks based on synthetic verification (tests pass, build OK) while real behavior is broken. Recurring pain across projects — direct motivation for Evidence Layer (TFW-46). Evidence = structural answer to "RF says done but it doesn't actually work" | ⚠️ 1 source | HL TFW-46 §11 S1 (user, 2026-07-07) | 2026-07-07 |