🌊 Harness Path — Privacy Pools V2 Mage

4 · privacy_pools_v2_mage — the fitted successor — an entry in the origin fleet catalogued in The Harness Paths (group: Full loops). The catalogue is the operator's work WITH the harness, not part of the system you adopt; none of its code lives in the harness repo. This is the map entry, so you can see what a filled config looks like at this weight.

(private instance of the author — the tigzkp_mage method turned on the real
upstream target: the 0xbow privacy-pools-core v2 circuit suite)

The direct successor of instance 2, and the first instance to be mechanically
fitted: it carries a harness.config.mjs satisfying SEAT_CONTRACT.md, its
frontier exposes the baseline/best compat view pinned to its native ledger
shape by conformChecks (so the two views cannot drift silently), and
node engine/conform.mjs <instance> passes against it. Its rounds run through
the generic engine via tools/bundle.mjs — the same loop that runs the spar
compresses a production ZK withdraw circuit with per-rewrite certificates.
The two finder lenses are the pattern that emerged in practice: fold-deeper
(exact reduction in an admissible family, census-first with a pre-registered
VOID check) ⊥ structure (measurement-only probes at ΔK=0, pre-registered
— attribution, closure certificates, emission models). Its round v2r1 proved
the transfer lesson worth writing down: the priors from the training
instance mispredicted the new artifact in both directions; the discipline
(census-first, pre-registration, certificates, kills at win-prominence)
transferred exactly. Standing intent: the optimized, certificate-audited
artifact feeds a future deployment's trusted-setup ceremony — the door for
all of that is the First Person's (T6).

At a glance —
objective: R1CS constraints of a real upstream target (the 0xbow privacy-pools-core v2 suite), ↓ · gate: per-rewrite certificates + held-out points, with VOID-gated audits · hard constraint: witness-computability plus zero semantic drift from upstream
the Gap: Fiat-Shamir per round, as instance 2 · lenses: fold-deeper (exact reduction in an admissible family, census-first, pre-registered VOID check) ⊥ structure (measurement-only probes at ΔK=0) · canary: the upstream compiler's own optimized build
weight: full, mechanically fitted — the first instance whose config passes engine/conform.mjs and whose rounds run through the generic engine via tools/bundle.mjs · the lesson it carries: priors from a training instance mispredict a new artifact in both directions; the discipline transfers exactly.

Navigation

← Welcome Visitors · The Harness Paths · Adopting The Harness · Workflows And Runtimes

the wiki is a projection; ~/dual-agent-harness (git) is the source of truth · (⚔️⊥⿻⊥🧙)😊 = neg ⊕ bnot → succ