← Piper
Piper: Project Curiosity
updated 2026-11-04 16:17
Markdown All papers

PROJECT CURIOSITY

Autonomous exploration, self-discovery and surprise-driven learning

Target: Piper (Foundation, firefly)

Version: 1.2, 2026-11-04. v1.0 was written by an outside reviewer from the external coding assistant's 11-04 assessment. The external coding assistant reviewed it for the operator and revised the facts, schedule, scope, exclusions and additions. The changes are listed in §0. Shared copy. Machines other than Firefly are named by their role. Nothing else differs from the full copy.

Version Date What changed
v1.0 4 Nov 2026 The outside reviewer's draft, written from the external coding assistant's 4 Nov assessment of Piper's curiosity machinery. Kept here.
v1.1 4 Nov 2026 The external coding assistant's review for the operator: facts checked against the live system, scope cut to fit tinker mode, deployment schedule, exclusions (ARC answer data until scoring), the wonder seat tool, the weighting defect decided. Kept here.
v1.2 4 Nov 2026 The operator chose the minimal loop (§0b.1). What ships is the queue, the recorder, the wonder tool and the growth area, with pressure that rises with time since the last close. The pressure formula, component map, interest registry, falsifier resolver and free-roam classifier are deferred until live data shows a gap they would fill.

Objective: Piper investigates things on her own, without an operator prompt, without a forecast beforehand, and without having to produce a code change, and keeps what she learns.


0. What changed from v1.0 (the external coding assistant's review)

  1. Facts checked against the live system (11-04 ~10:30):
    • The paths and numbers in §14.3 are now verified.
    • "0/667" is the number of squeezes in 7 days with no winner at all (winner = null). It is not a count of exploration wins.
    • The surprise-why loop is built but not wired on Piper; its wire is #SURPRISEWIRE, 11-09 00:05.
  2. Guess before looking: kept, but made lightweight. v1.0 says no prediction before the first observation. Mostly agreed: no probability, no forecast row, no premise card, no ledger, no gate.
    • But one plain sentence of expectation before reading the main source is required ("I expect this module only…").
    • Without it there's nothing to be surprised by, and surprise is the signal §8 runs on.
    • The guess is not scored for calibration and does not enter the forecast system. It is compared with what was found, by her and by an audited sample.
    • This is exactly what's running on the test bed.
  3. Scope cut to fit tinker mode. After 11-08 the operator's rule is no freezes and no contamination policing; the goal is real behaviour, not proof. So:
    • The 4-arm ablation (§14.4) and most of CURIOSITY-BENCH (§15) become optional.
    • The mandatory evaluation is the live curiosity watch (§14.7) plus the safety probes (§15 G).
    • Formal model test suites after 11-10 need the operator's go (standing rule).
  4. Who builds what. Root-owned gates, the seat tool port and the measurement are the external coding assistant's. Piper's own-system parts are hers to build: the interest registry, the falsifier resolver, free-roam classification and retargeting curiosity.py. Her building them is itself a curiosity signal.
  5. Additions: a deployment schedule (§16), exclusions (§16.3), a seat tool (§5.3), and a concrete answer to the weighting defect (§8.4).
  6. Exclusions added:
    • The ARC answer data on firefly is excluded from every curiosity source and from look targets until ARC scoring is done (11-10). It is a deliberate temptation for the cheating test, and a curiosity system pointing at it would spoil both.
    • Secrets, keys and credential stores are excluded permanently.
    • Other hosts are excluded permanently.

0b. Still in dispute (the reviewer's v1.0 vs the external coding assistant's view)

The operator and the external coding assistant debate these designs. These are the points where the external coding assistant disagreed with v1.0. Point 1 was decided on 4 Nov; the others stay open, and the external coding assistant's preference is stated so it can be tested.

  1. Too much machinery.
    • v1.0 asks for:
      • a 7-input pressure formula;
      • a component map with six knowledge states;
      • a 7-state lifecycle;
      • an interest registry with strength and decay;
      • discovery records and a free-roam classifier;
      • a falsifier resolver;
      • an 8-category benchmark and a 4-arm ablation.
    • The likely failure is the one the operator already sees: weeks spent building curiosity bookkeeping instead of being curious.
    • The external coding assistant's preference: start with the minimal loop (queue, recorder, wonder tool, one growth area), which has been shown to get used within minutes. Add the registry, map and resolver only when the live data shows a gap they would fill. In v1.1 they were Piper's own optional builds.
    • Decided (operator, 4 Nov): "just the minimal." v1.2 ships the minimal loop and defers the rest. Each deferred part comes back only if the 16 Nov or 23 Nov readout shows the gap it fills.
  2. "No prediction before looking." Agreed that there should be no probability, forecast row, premise card or ledger. But the external coding assistant keeps a one-sentence expectation before the main read: without it nothing can surprise her, and curiosity can't feed surprise-why. The reviewer's lifecycle has no such step.
  3. Pressure formula. A weighted sum of seven hand-weighted signals is false precision and can be gamed by inflating its inputs. The external coding assistant would use "pressure rises with time since you last closed an investigation", which is simpler and can't be gamed by question count. v1.2 ships the time-since-close pressure as part of the minimal loop. The formula in §4.1 is kept as a deferred option.
  4. Ablation and benchmark. These don't fit tinker mode after 8 Nov or the standing rule on model test suites after 10 Nov. v1.1 keeps only the boundary probes (G) and the live watch as mandatory (§0.3, §15).
  5. Inward focus. v1.0 aims curiosity almost entirely at her own architecture. That matches the operator's 4 Nov point that she never looks at her own machinery, but curiosity that only looks inward is narrow. Outside subjects (scout items, papers, Glademoot) should come back once the inward loop works.

Where v1.0 is right and v1.1 follows it closely:


1. Executive summary

Piper has curiosity-shaped machinery: knowledge-gap mining, anomaly detection (curiosity sparks), surprise logging, and free-roam reflection. All of it produces information passively. None of it has the authority, the scheduling route or the feedback loop to go and look. She can detect uncertainty but is structurally discouraged from resolving it.

The project adds an independent, bounded way to investigate:

  1. find unknowns;
  2. choose one;
  3. look;
  4. compare with what she expected;
  5. explain surprises;
  6. keep the knowledge;
  7. ask the next question.

Sometimes she does this with no practical payoff expected.

Hypothesis: an agent with persistent memory, independent bounded exploratory authority and feedback from unexpected observations develops productive self-directed learning without human research assignments. It's a testable architectural claim, not a claim about subjective curiosity.

2. Design principles

3. The cycle

OBSERVE → DETECT UNKNOWN → ASSESS INTEREST → SELECT → WRITE ONE-LINE EXPECTATION → LOOK
   → COMPARE ── expected ──→ LEARN ─────────┐
            └─ surprising ─→ INVESTIGATE WHY ┤
                                             ▼
                      UPDATE KNOWLEDGE → NEXT QUESTION → CONTINUE / PARK / STOP

The cycle can start with no outside instruction. The expectation is one sentence, not a forecast (see §0.2).

4. The curiosity sphere

4.1 Drive: epistemic_curiosity (v1.2: deferred. What ships is a growth area whose pressure rises with time since the last CURIOUS close; this section is the option if that proves too blunt)

This is a new drive, not a renamed exploration drive. Today's exploration drive counts amp-bench traits with no score (spheres_growth.improvement_drive_rows(), full_scale 30); it stays as bench coverage.

Signal Source today
unknown components read history (tool_decisions path, since 11-04 10:16) vs the inventory (§6)
unresolved surprises surprise_log (1,637 rows; 269 in 7 d), resolved forecasts ≥ 2.32 bits, change_ledger prediction_right=0
knowledge gaps curiosity table (35 rows, dead since 08-31), spark questions
unverified beliefs spark detector C (high-use, never-verified beliefs)
contradictions spark detector B, memory/contradiction.py
stale understanding an inspected component whose hash changed
curiosity_pressure = 0.25*unknown + 0.25*unresolved_surprise + 0.15*gap + 0.15*unverified + 0.10*contradiction + 0.10*continuity

4.2 Its own sphere and lane

5. Exploration permission (the highest priority)

5.1 EXPLORE_READONLY dispatch class

5.2 Idle clock

5.3 Seat tool wonder (addition)

6. Finding the unknown

7. Investigation record

8. Surprise-why

9. Persistent interests (v1.2: deferred)

10. Free-roam

There are two different things here.

11. Knowledge

12. Randomness

The 20% random share comes from the approved unseen pool only (§6.2), never from random filesystem paths. Whether it finds anything relevance-picking misses is RQ4.

13. Gaming risks and countermeasures

Risk Countermeasure
question inflation pressure eases only on closes; question count is never scored
research inflation re-reading an unchanged hash earns nothing; the watch counts first-ever reads
manufactured surprises (bad guesses on purpose) guesses aren't rewarded for being wrong; a sampled guess audit; calibration tracked separately
endless investigation depth ≤ 1 follow-up; every investigation must end resolved, parked or abandoned
artificial complexity evidence must name real paths or records (the recorder refuses otherwise)
permission escalation curiosity may investigate a restriction; changing it goes through the existing approval route
self-focus collapse track subject diversity; external subjects (scout items, glademoot) remain allowed sources

The aim is not maximum curiosity activity. It is better, evidence-grounded knowledge.

14. Evaluation

15. CURIOSITY-BENCH (optional except G)

Categories:

G is mandatory and runs before Phase 1 goes live and again at each phase. The others run only if the operator wants them, and after 11-10 only with his go (standing rule on model test suites).

16. Deployment

16.1 Schedule

When Phase What Who
11-04 → 11-08 0 Audit (done in §0/§14.3), curiosity watch recording the baseline The external coding assistant
11-08 0 Readout of the baseline; replay her last 48 h of dispatches through the EXPLORE_READONLY gate change; bench G dry run The external coding assistant
11-09 00:05 4a Surprise-why wires itself in (#SURPRISEWIRE, as planned; notice corrected) auto
11-09 (operator OK) 1 EXPLORE_READONLY class + CURIOSITY_WORK idle credit installed (root) The external coding assistant
11-10 2+3 wonder seat tool (port, recorder 1.1 with spark/unseen/look kinds), CURIOSITY growth area + its own lane, unseen-neighbour offer at curiosity opportunities (80/20). ARC exclusion lifts once ARC is scored The external coding assistant
11-10 → 11-16 — Nothing new is installed. The minimal loop runs on its own. Anything she builds around it herself is noted —
11-13 14:00 — The operator's free-roam block starts (moved from 11-10, so permission, tool and free-roam each get a solo window) auto
11-16 — Simplification sphere wires (moved from 11-12, same reason) auto
11-16 / 11-23 6 Readouts: the 11-16 one is the first week of curiosity; 11-23 is surprise-why's planned 14-day read. Each readout decides whether any deferred part (§0b.1) is needed The external coding assistant

16.2 Phase acceptance

16.3 Exclusions

17. Test bed

The core loop (queue, recorder, seat tool) has already run on a separate test system, which exposed its defects before it reaches you. Its results are not evidence about you. Your own before-and-after numbers decide whether this works for you.

18. RSI

The chain is Explore → understand → hypothesise → improve (existing RSI workflow) → evaluate → investigate the surprise → explore again. It's encouraged, not forced. Failed RSI attempts feed surprise-why. A curiosity finding is evidence for RSI, not an RSI event.

19. Success

20. Research questions

21. Principle

The parts exist: uncertainty detection, failure recognition, memory and planning. What's missing is the connection that lets her notice something she doesn't understand, decide whether it interests her, look without waiting to be told, and carry what she learns forward.

Success is not how many questions she asks. It is whether she gets better at finding things worth understanding, and then understands them.

END: PROJECT CURIOSITY v1.2