Request
Larch Scheduling's release coordinator needs a decision from a local rehearsal log.
Evidence
Each nonblank row should be service|level|latency. Valid levels are INFO, WARN, and ERROR. Latency uses nonnegative integer parsing. Preserve invalid-row counts so missing evidence remains visible.
Decision rule
Hold the release when any valid ERROR exists, any row is invalid, or at least two valid rows reach the supplied latency threshold. Return hold as 1 or 0 alongside every supporting count. The final answer is checked automatically.
Larch Scheduling is preparing a release of its appointment-routing service. The release coordinator has a short log extract from a fictional rehearsal and a written hold rule. You need to distinguish unusable evidence from service warnings, calculate latency evidence, and return a decision that follows that rule. A malformed row cannot simply disappear from the review. You'll build one review function in five cumulative steps, carrying the previous implementation forward each time. The final dictionary contains both the recommendation flag and the counts behind it. This case uses no patient data, and its thresholds are an exercise contract rather than a claim about a real service's reliability.