# Phase 9: Timing Profiles - Discussion Log

> **Audit trail only.** Do not use as input to planning, research, or execution agents.
> Decisions are captured in CONTEXT.md — this log preserves the alternatives considered.

**Date:** 2026-04-13
**Phase:** 09-timing-profiles
**Areas discussed:** Profile contents, Tool interface, Preset/template profiles, start_capture merge

---

## Gray Area Selection

| Option | Description | Selected |
|--------|-------------|----------|
| Profile contents | What fields beyond the 4 timing params? Diagnostic flags? | |
| Tool interface | Three new MCP tools mirroring Phase 8. Differences? | |
| Preset/template profiles | Built-in timing presets like 'fast-scan', 'slow-watch'? | |
| start_capture merge | How timing_profile merges with inline params | |

**User's choice:** Full creative discretion — user selected no specific areas, granting Claude decision authority over all four.
**Notes:** User note: "For all features and phases of this milestone, you are free to ideate, decide, plan, and introduce any additional elements or feature extensions that improve the tool's power and flexibility in agents' proverbial hands."

---

## Profile Contents

Decided by Claude under creative discretion:
- Include all 4 timing params + all 3 diagnostic flags
- All fields optional (partial presets supported)
- Rationale: Diagnostic flags control how a session runs, not what it captures — natural fit for timing profiles

## Tool Interface

Decided by Claude under creative discretion:
- Mirror Phase 8 pattern exactly (save/list/delete)
- Same snake_case param names as start_capture
- Same validation ranges
- list returns parameter_summary one-liner per profile

## Preset/Template Profiles

Decided by Claude under creative discretion:
- 4 built-in presets: quick-glance, steady-watch, debug-flicker, slow-monitor
- Listed alongside user profiles with builtin: true flag
- User profiles can shadow built-in names
- Rationale: Agents need a vocabulary for common capture scenarios

## start_capture Merge

Decided by Claude under creative discretion:
- Same "inline wins" merge semantics as Phase 8
- Both screenshot_profile + timing_profile can be specified together
- Resolution: timing profile base -> screenshot profile base -> inline overrides

## Claude's Discretion

All areas resolved under full creative discretion grant.

## Deferred Ideas

- Profile composition/inheritance — over-engineering for current scope
- Profile validation against system capabilities — better at capture time