capture-feature-evidence

Capturing product evidence during live app exploration involves structuring observations, inferences, and blockers for a bounded feature area. This process produces an artifact that defines explicit boundaries and required next steps for downstream planning.

A feature evidence artifact is used to own observed product evidence and blockers for a scoped area. It informs downstream planning by providing structured observations and inferences without performing feature decomposition or writing coverage plans.

Structure exploration reports by clearly defining observations, inferences, blockers, and scoped boundaries. Save these artifacts in `e2e-plan/exploration-report.md` or a scoped file under `e2e-plan/exploration/` to ensure safe, bounded live exploration.

You need a feature map or map-feature-scope to identify a bounded area to investigate before capturing evidence. This prerequisite ensures the live exploration remains safely bounded and produces clearly scoped boundaries for downstream use.

The best way to document blockers is to capture them within a structured evidence artifact alongside observations and inferences. This approach clearly scopes boundaries and defines required next steps without framing exploratory charters or prioritizing risks.

You should not use this approach when you need to perform feature decomposition, frame exploratory charters, prioritize risks, or write coverage plans. It strictly owns observed product evidence and blockers for a scoped feature area.