F05

Context, Jev and cache

The source summary is shown as authored. Follow its evidence links for study-specific status and cohort limits.

Source-reported narrativeValues in this source section that are not tied to a claim-ledger record remain source-reported and are not promoted to verified results.

Findings source section · FINDINGS.md

Hypothesis: H51–H61 ask whether caching, context preparation, compaction, or code inspection reduces cost or improves downstream outcomes. The available records do not establish those live Build benefits.

What ran: R54 records an interim context handoff comparison; Jev and Tidewave pages are offline or partial diagnostics; T98 is a cache smoke and T100 is not run. Language cohorts remain separate from cache and context measures.

Result: Numerator/denominator: not recorded for a reconciled Build-success contrast. Unit: cache requests, context diagnostics, and official Build passes are separate. Date: no matched request or Build date is recorded. Status: interim diagnostics; T98 is telemetry only and T100 is not run.

What it does not show: The cache smoke does not establish a cache-fix effect on success, time, or cost; route agreement and context retrieval do not establish better Builds.

Evidence: F05 hypothesis page, R54, T98 cache smoke, T100 cache lane, E06 context, E09 Tidewave, Jev route context, Jev triage context. Spec map: provider requests and prompt caching.