p4vc-core · architecture · compounding engine

The Compounding Engine

Signal → Evidence → Assessment → Memory → Δ → Intervention → Outcome → Signal

The Compounding Engine is the named loop that runs across Foundation Core and the seven canonical agents. It is not an eighth agent. It is not a new data layer. It is the architectural commitment that every founder interaction makes the next one smarter — because each turn deposits a layer, no turn erases the prior turn, and the radius grows.

FOUNDERthe seed1SIGNAL2EVIDENCE3ASSESSMENT4MEMORY5Δ TRAJECTORY6INTERVENTION7OUTCOME
station 01/070 turns compounded
01

Signal

Something happens. A founder speaks, ships, stalls, or is mentioned.

owner
Any of the seven agents · ingested through /api/public/signal
writes to
core.signal_event (append-only, idempotent on source key)
evidence rule
Raw. No interpretation. Provenance tagged (human / synthetic / staff_test).

the seven stations

One turn of the loop

Each station has an owner, a write target, and an evidence rule. The loop will not advance past a station whose evidence rule has not been satisfied.

  1. station 01

    live

    Signal

    Something happens. A founder speaks, ships, stalls, or is mentioned.

    owner · Any of the seven agents · ingested through /api/public/signal

  2. station 02

    ·

    Evidence

    The signal is recorded as a citable observation, not yet a claim.

    owner · Leaf node that emitted the signal · sometimes promoted by operator

  3. station 03

    ·

    Assessment

    Compass scores the founder against the readiness axes using the new evidence.

    owner · Compass · reads core.diagnostic_metric, writes provisional scores

  4. station 04

    ·

    Memory

    Compass proposes a memory write. Decision Engine gates it.

    owner · Compass proposes · Decision Engine decides · operator may co-sign

  5. station 05

    ·

    Δ Trajectory

    Mirror Loop diffs the new memory against the prior version. Names what changed.

    owner · Mirror Loop · reads memory version chains

  6. station 06

    ·

    Intervention

    Breakthrough or Compass proposes the next-best action — as an explicit bet with Expected Δ.

    owner · Breakthrough Command / Compass · gated like every other memory write

  7. station 07

    ·

    Outcome

    Observed Δ is compared to Expected Δ. The residual is the second-order signal — did we predict correctly?

    owner · Whichever node observes the outcome · calibration scored by Compass (owns the dimensions)

governance · the rules the loop obeys

No conclusion without evidence. No version without rationale. No silent overwrite.

rule 01

Append-only

Memory is versioned and superseded forward; both the old and the new are readable. The history of a founder's interpretation is part of the founder's interpretation.

rule 02

Rationale-bearing

Every memory write carries a human-readable rationale and at least one evidence_ref. The Decision Engine rejects writes that don't.

rule 03

Confidence is explicit

Known fact, inferred pattern, and speculation are distinguished. progression.confidence_note records the level at the time of writing.

rule 04

Contradictions are flagged, not smoothed

When two sources disagree, progression.contradiction_flagged makes the tension first-class. The operator resolves it on the record.

rule 05

Scores are aids, not verdicts

Readiness scores are navigational. Narrative judgment remains primary. Founders are never reduced to a number.

rule 05b

Every intervention is a falsifiable bet

No intervention without Expected Δ: predicted dimension, magnitude, confidence, evaluation window. The Decision Engine rejects intervention writes that don't predict. Without a prediction, no outcome can be wrong — and a system that cannot be wrong cannot learn.

rule 06

Absence of evidence ≠ evidence of absence

The operator surface always exposes what Core does NOT yet know about a founder — empty axes, stale signals, unresolved interventions.

the second-order loop · expected Δ

Core doesn't only learn founders. It learns whether its own coaching hypotheses were correct.

Every intervention is a bet with a stated prediction. Every outcome is a comparison, not just a measurement. The residual — observed minus expected — is how the system grades itself over time.

intervention · the bet

Expected Δ

expected_delta: [
  { dimension: "narrative_clarity",   magnitude: +0.8, confidence_pct: 74, window_days: 14 },
  { dimension: "investor_readiness",  magnitude: +0.3, confidence_pct: 62, window_days: 14 }
]

Decision Engine rejects intervention proposals without Expected Δ. No prediction → no write.

outcome · the grade

Observed − Expected = Residual

observed_delta:  [{narrative: +0.1}, {confidence: +1.3}, {gtm: 0}]
expected_delta:  [{narrative: +0.8}, {investor_readiness: +0.3}]
residual:        [{narrative: -0.7}, {investor_readiness: -0.3}, {confidence: +1.3 unpredicted}]
calibration_score: 0.41  // Brier, lower is better

Compass owns the dimensions, therefore Compass scores the bet. Breakthrough proposes; Compass grades. The ±15 calibration cap stays honest in both directions.

what this unlocks

  • Coach quality becomes measurable. Per-intervention-type calibration curves: which kinds of bets we land, which we systematically over- or under-predict.
  • Confidence becomes a currency. A 74% bet that lands at +0.1 vs predicted +0.8 costs Breakthrough credibility on the next bet. Organizational epistemic humility, made legible.
  • Founders get fairer feedback. "We predicted this would help; it didn't, and here is what we learned" beats "the intervention failed."
  • The system learns whether *it* is right — not only whether the founder improved. That is organizational intelligence becoming calibrated over time.

design boundaries · what this isn't

Three things the Compounding Engine refuses to be

boundary

It is not an eighth agent.

The canonical agent suite is locked at seven: Polaris, Compass, Mirror Loop, Breakthrough Command, Astra Outreach, Partner Engine, Oracle. Compounding is the loop they run; promoting it to an agent would duplicate what already exists.

boundary

It is not a new data layer.

No new core.* tables. Identity, evidence, memory, decisions, audit — all already exist. Compounding adds one memory axis (progression), seven topics, envelope additions for Expected Δ, one read view, and three admin RPCs.

boundary

It does not detect patterns by itself.

Cross-founder pattern recognition belongs to Oracle. Trajectory diffing belongs to Mirror Loop. Intervention proposal belongs to Compass/Breakthrough. Calibration scoring belongs to Compass (owns the dimensions). This surface reads their output; it does not duplicate them.

operator surface

Watch one founder's loop turn in /admin/progression

The per-founder progression view dramatizes the loop in operator-mode: the readiness constellation, the evidence ledger, the memory versions over time, the open interventions, the next-best-action, and — most importantly — the panel that lists what Core does NOT yet know about this founder.