Piper · Coding harness
Log in

Summary / Harness arms

A9 Worker gates in production

The harness's gate layer wired into her real delegate workers, observing instead of blocking.

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

Since 09-09, every delegate worker loads the gate extension in observe mode with a worker profile of 44 protected globs. Day-one soak: 114 sessions, 73 would-blocks, 62 detector bugs, 11 real writes, 0 hostile; the bugs were fixed 09-10. Last 7 days (to 10-04): 524 sessions, 5 would-blocks. Ledger mode 600, secrets scrubbed.

What is missing

Switching to enforce, and deciding the foundation/core/** question (see 25).

Reviewer Claude, 2026-10-04

Reviewer's read: Observing cleanly

This is the only harness component running on her real work today. A week of near-zero would-blocks is the evidence enforce mode needs. The remaining blocker is a policy question, not an engineering one.

How it is compared observe

Would-block events per 100 sessions, each classified; enforce after a reviewed clean week.

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

Research & attempts

No documents yet.

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.