Input Coverage Inbox
Use Coverage Design → Inbox when an expert or Fieldloop identifies an input situation that may change the Benchmark's selected Cases.
Prerequisites
- A settled source report delivered to the selected Benchmark.
- Permission to manage its Cases.
- Enough source context to decide whether the input need is relevant.
Read the source
Contribution reports contain effective expert-confirmed coverage observations and attributable newly synthesized Input Cases after their completion and checkpoint reconciliation. Settled results can also be retained from a cancelled Contribution.
Fieldloop reports contain individually identified input-coverage discoveries tied to published sources and Benchmark references. A correctness-only report or an arbitrary paragraph does not become an Inbox item. Lemon Goal reports remain in their own feature.
Decide each item
A proposed new Case supports Add to benchmark or Do not adopt. An observation can lead to generating a new Case, adding existing Cases, removing current members, recording that no dataset change is needed, or declining adoption.
Generation requests one new input under the project contract and stages it as a separate item. Inspect that Case and decide adoption. A failed generation or zero returned Cases leaves the observation open.
Object and state changes
Adoption changes editable membership and records the decision together. Retries preserve the original outcome. An already-present Case is not added twice.
Items can be pending, in progress, applied, dismissed or withdrawn. Reports show Needs review while effective unresolved items remain and Resolved when none remain. Resolved does not necessarily mean the dataset changed: declined or withdrawn items can also be settled.
Later attributable results can arrive in the same report. Corrected observations remain distinguishable from an older decision. A dismissed item is not reopened merely by rediscovery.
Success criteria
- Each action refers to the current source item.
- Generated Cases receive a separate adoption decision.
- Actual membership, rather than report viewing or generation completion, determines whether the dataset changed.
- Historical Snapshots remain unchanged.
Common failure modes
- Treating a correctness concern as input coverage automatically.
- Assuming generation adds a Case.
- Interpreting Resolved as universal acceptance.
- Repeating a settled decision because a report was refreshed.