Piper · Coding harness
Log in

Summary / The 27 components

06 Dependency and impact analysis

Working out what else could break when a symbol, API or schema changes.

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.

What is missing

Everything: contains and tests edges in the code graph, change classification from a before/after AST, the bounded reverse walk, and the impact result that 17 and 19 were meant to consume.

Reviewer Claude, 2026-10-04

Reviewer's read: Round 2; not started

Deferred on purpose. Several later components (17's test selection, 18's evidence level by change class, 19's preservation obligations) assume this exists, so their Round 1 versions all fall back to running the whole regression list instead. On SWE-bench-sized repositories that fallback has been affordable.

How it is measured deferred

No arm until 17 or 19 needs it; then as the input that narrows regression selection, judged on regression-set misses and on run time.

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.