6 行
306 B
Markdown
6 行
306 B
Markdown
|
|
# Technical Spikes
|
||
|
|
|
||
|
|
Each Spike report must record its objective, environment, minimal implementation, actual commands and results, log summary, limitations, security impact, MVP blocking status, and recommended production approach.
|
||
|
|
|
||
|
|
Reports must distinguish verified behavior from planned or blocked work.
|