2.6 KiB
Compact final diagnosis requests
New modern final/early diagnosis operations use diagnosis_v3 and
diagnosis_early_v3. Their output schema, causal-evidence gates, countercheck
requirements and early-review acceptance rules remain unchanged.
The package retains the complete immutable diagnosis context. A deterministic
model view omits case.inputs, the refs catalogs of source/database context,
and budget seen_evidence deduplication bookkeeping. Other case fields remain,
including runtime facts, entities, reproduction, research, human observations,
expected behavior and data-quality warnings. All investigation state is retained:
every proposal, confidence, disposition, note, question, evidence reference and
early-review/deferred status. Evidence content and provenance are retained,
including query filters, coverage, truncation, scope and actual database values.
Budget accounts remain visible.
The existing deterministic model-context encoding shortens long storage identifiers and factors repeated provenance into shared metadata. Database row values are copied unchanged. Presentation aliases are not output evidence IDs. JSON is compactly serialized; the response schema stays visible to JSON-object endpoints. There is no extra LLM summary or provider call.
Previously saved requests keep their original v1/v2/v3 prompt and request hash, including crash recovery and explicit provider retries. Only new operations use the new view. Completed diagnoses and handoffs are not regenerated. Rejection feedback remains scoped to earlier attempts of the same diagnosis/early-review operation, and portable replay reconstructs the bound request version.
Offline size comparison using the local accepted early-diagnosis test context: 223,750 -> 67,148 user-message characters (70.0% less), 242,515 -> 80,586 serialized request bytes (66.8% less). This is not a provider token measurement. Semantic quality and actual token use will be assessed in a later complete live run, without separate paid experiments.
Suitable remediation data
New handoff operations use change_request_v4, retaining the compact v3 data
view and reference validation. Missing-data descriptions, coding constraints and
human tasks should request suitable, reviewed remediation data. Canonical data
research is recommended where useful, not imposed as the sole source unless
verified project requirements mandate original values. Human-selected and
reviewed placements may suffice. No unknown coordinates are invented and template
placeholders remain explicit. Previously completed assignment documents retain
their original content; BugAnalysis does not supervise downstream decisions.