REAPER HARNESSPUBLIC BETA · ADVISORY

PRE-FLIGHT CONTROL / CHANGE ROUTING

Put a boundary
around agent work.

Describe a proposed change. Reaper identifies the planning depth, lifecycle route, missing decisions and stop conditions to resolve before an agent writes.

DESCRIBE→ROUTE→PLAN CHECKS→EXPORT
01 / PROPOSED CHANGE0% DEFINED
0/800 · Be precise about the intended outcome.

No code, logs or credentials are needed. Inputs stay in this browser.

02 / ROUTE CARDAWAITING INPUT

No current route

Complete the proposal to receive a deterministic boundary pack. Reaper never starts the work.

01

Visibility is not authority.

A green route means the proposal is legible enough to plan. It does not grant permission to execute.

02

Lifecycle cannot expand scope.

A test or execution route stays inside the approved change boundary.

03

Ambiguity stops the line.

Unclear scope, write surfaces or authority produce a hold, not a guess.