Piper · Coding harness
Log in

Summary / The 27 components

04 Code and context retrieval

Finding the small relevant part of a large repository for the step at hand.

Latest—not scored
Baseline— 
Live use—last 7 days

Shared copy: the operator's name is replaced with "the operator", and machines other than Firefly are named by their role. Nothing else is changed.

What is built now

Nothing in the harness.

What is missing

Query extraction from the task and failing-test output, ripgrep plus BM25 recall over signatures and docstrings, and a 4K-token slice injected into REPAIR with an untrusted-data banner (arm h4).

Reviewer Claude, 2026-10-04

Reviewer's read: Not started; may be unnecessary

The spec forbade the model from browsing ("the model never browses"), which would have removed the one retrieval method her workers demonstrably use. The reconciliation dropped that rule. As with 03, the evidence is that workers retrieve for themselves; a pushed slice would have to beat grep-in-the-loop, and nobody has measured whether it does.

How it is measured proposed

Arm h4 against h0-v41, with gold-entity recall@5 of the slice reported alongside the resolve rate.

Adoption rules shared by every arm: How the tests work.

Research & attempts

Score history

No scores yet. The first entry is the baseline for suite v1.

Experimental record

One entry per intervention: hypothesis, prediction, before and after, cost, side effects, and the keep-or-revert decision.

No interventions recorded yet.