1# Findings & Decisions
2<!-- 
3  WHAT: Your knowledge base for the task. Stores everything you discover and decide.
4  WHY: Context windows are limited. This file is your "external memory" - persistent and unlimited.
5  WHEN: Update after ANY discovery, especially after 2 view/browser/search operations (2-Action Rule).
6-->
7 
8## Requirements
9<!-- 
10  WHAT: What the user asked for, broken down into specific requirements.
11  WHY: Keeps requirements visible so you don't forget what you're building.
12  WHEN: Fill this in during Phase 1 (Requirements & Discovery).
13  EXAMPLE:
14    - Command-line interface
15    - Add tasks
16    - List all tasks
17    - Delete tasks
18    - Python implementation
19-->
20<!-- Captured from user request -->
21-
22 
23## Research Findings
24<!-- 
25  WHAT: Key discoveries from web searches, documentation reading, or exploration.
26  WHY: Multimodal content (images, browser results) doesn't persist. Write it down immediately.
27  WHEN: After EVERY 2 view/browser/search operations, update this section (2-Action Rule).
28  EXAMPLE:
29    - Python's argparse module supports subcommands for clean CLI design
30    - JSON module handles file persistence easily
31    - Standard pattern: python script.py <command> [args]
32-->
33<!-- Key discoveries during exploration -->
34-
35 
36## Technical Decisions
37<!-- 
38  WHAT: Architecture and implementation choices you've made, with reasoning.
39  WHY: You'll forget why you chose a technology or approach. This table preserves that knowledge.
40  WHEN: Update whenever you make a significant technical choice.
41  EXAMPLE:
42    | Use JSON for storage | Simple, human-readable, built-in Python support |
43    | argparse with subcommands | Clean CLI: python todo.py add "task" |
44-->
45<!-- Decisions made with rationale -->
46| Decision | Rationale |
47|----------|-----------|
48|          |           |
49 
50## Issues Encountered
51<!-- 
52  WHAT: Problems you ran into and how you solved them.
53  WHY: Similar to errors in task_plan.md, but focused on broader issues (not just code errors).
54  WHEN: Document when you encounter blockers or unexpected challenges.
55  EXAMPLE:
56    | Empty file causes JSONDecodeError | Added explicit empty file check before json.load() |
57-->
58<!-- Errors and how they were resolved -->
59| Issue | Resolution |
60|-------|------------|
61|       |            |
62 
63## Resources
64<!-- 
65  WHAT: URLs, file paths, API references, documentation links you've found useful.
66  WHY: Easy reference for later. Don't lose important links in context.
67  WHEN: Add as you discover useful resources.
68  EXAMPLE:
69    - Python argparse docs: https://docs.python.org/3/library/argparse.html
70    - Project structure: src/main.py, src/utils.py
71-->
72<!-- URLs, file paths, API references -->
73-
74 
75## Visual/Browser Findings
76<!-- 
77  WHAT: Information you learned from viewing images, PDFs, or browser results.
78  WHY: CRITICAL - Visual/multimodal content doesn't persist in context. Must be captured as text.
79  WHEN: IMMEDIATELY after viewing images or browser results. Don't wait!
80  EXAMPLE:
81    - Screenshot shows login form has email and password fields
82    - Browser shows API returns JSON with "status" and "data" keys
83-->
84<!-- CRITICAL: Update after every 2 view/browser operations -->
85<!-- Multimodal content must be captured as text immediately -->
86-
87 
88---
89<!-- 
90  REMINDER: The 2-Action Rule
91  After every 2 view/browser/search operations, you MUST update this file.
92  This prevents visual information from being lost when context resets.
93-->
94*Update this file after every 2 view/browser/search operations*
95*This prevents visual information from being lost*
96