4.3Anatomy of Each Section

Charter

Restate the original charter. If you deviated during the session (which is acceptable), note the deviation:

Charter:    Explore checkout with international addresses for currency issues
Deviation:  Discovered that the address autocomplete API fails for some countries.
            Spent 15 minutes investigating the autocomplete issue instead.

Areas Covered

List what you actually tested, with brief results. This section answers: "If someone else needs to continue this exploration, where did I leave off?"

Be specific:

• Bad: "Tested file upload"
• Good: "Uploaded .svg (accepted, renders), .webp (accepted, no thumbnail), 0-byte .txt (accepted, download fails), .exe (rejected with error message)"

Bugs Found

List each bug with a one-line summary and severity. File full bug reports separately (in your bug tracker), and reference the bug IDs here.

BUGS FOUND:
- BUG-1234: 0-byte file upload succeeds but download crashes (severity: high)
- BUG-1235: .webp thumbnail missing silently (severity: medium)

Questions and Risks

This is often the most valuable section. Questions that arise during exploration frequently point to specification gaps, missing test coverage, or architectural risks.

Questions should be actionable:

• Bad: "Is upload safe?" (too vague)
• Good: "Is there server-side virus scanning on uploaded files? The /upload endpoint accepts any file content without apparent validation."

Follow-Up Charters

Based on what you learned, propose charters for future sessions. This creates a continuous exploration pipeline.