frontend-patterns/research/bench/fixtures/candidates.md
tegwick cfa249ab13 Reduce research calls with screened reuse and draft VC-02 walkthrough
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a0cffe-206f-7323-89d3-b20ca4cf4bf9
2026-09-25 08:43:32 +02:00

57 lines
1.2 KiB
Markdown

# Local Draft State
## Definition
Keep a draft near the interaction while distinguishing it from committed data.
## Candidate Identity
P01; family affordance; scale L6; status draft; maturity hypothesis; evidence_kind synthetic.
## Context
An interrupted form session awaiting server acceptance.
## Problem
How can input remain intelligible before server confirmation?
## Forces
Interaction continuity improves; divergence-handling complexity increases.
## Solution
Hold a draft locally and display its uncommitted status.
## Dynamics
Submission may move from pending to rejected or accepted.
## Resulting Context
The application must decide retry, reconciliation and recovery behavior.
## Consequences
The user can keep typing but must understand what has actually been saved.
## Failure Modes
Confusing a local draft with committed data; losing a draft on restart.
## Source Evidence
C01 and C02; source/source.md, Scenario and Trade-off, paragraph 1.
## Counterevidence
This synthetic scenario establishes neither recurrence nor durability.
## Review Notes
Hypothesis only. No known uses. Do not promote from fixture evidence.
```json
{"candidates": [{"id": "P01", "known_uses": [], "recurrence": "unknown"}]}
```