Cross-Spring Connections — How wetSpring Feeds the Ecosystem¶

wetSpring doesn't operate in isolation. It consumes 79 barraCuda primitives without duplicating any math, found and fixed bugs in ToadStool, and shares validation patterns with every other spring.

This notebook maps the connections: what flows between springs, what wetSpring discovered that improved the infrastructure, and how the constraint-driven architecture forces productive coupling.

For other springs: map your own cross-spring connections. Every spring touches at least 3 others. Document the flows — they're your evidence that the composition works.

barraCuda Primitive Consumption¶

wetSpring delegates all GPU math to barraCuda via ToadStool dispatch. Zero local WGSL shaders. 79 primitives consumed across these categories:

No description has been provided for this image 
Categories: 8
Named primitives shown: 34
Total consumed (including variants): 79

Cross-Spring Flow Map¶

How wetSpring connects to other springs — what it gives, what it takes.

No description has been provided for this image

Constraint-Driven Discoveries¶

The constraint architecture (primals own math, springs own science) forces productive coupling. wetSpring found and fixed these infrastructure issues:

Discovery                      Severity   Found By
================================================================================
ToadStool log_f64 bug          Critical   Shannon entropy validation (Exp 001)
  Detail: Chebyshev coefficients halved, causing 1e-3 precision instead of 1e-15
  Fixed:  ToadStool v0.8.x | Impact: Affected all springs using log_f64 GPU primitive

barraCuda ODE solver gap       Feature    QS modeling (Track 1 experiments)
  Detail: No Dormand-Prince adaptive ODE solver existed
  Fixed:  barraCuda v0.5.x | Impact: Enabled ODE-based dynamics across all springs

barraCuda Gillespie SSA gap    Feature    Exp 022 Gillespie validation
  Detail: Stochastic simulation algorithm not available on GPU
  Fixed:  barraCuda v0.5.x | Impact: Stochastic simulation for wetSpring + healthSpring

barraCuda HMM Viterbi gap      Feature    Exp 026 HMM validation
  Detail: Hidden Markov Model decoding not on GPU
  Fixed:  barraCuda v0.6.x | Impact: Gene family analysis for Liu phylogenetics track

barraCuda Smith-Waterman gap   Feature    Exp 028 Alignment validation
  Detail: Local alignment not available on GPU
  Fixed:  barraCuda v0.6.x | Impact: Sequence alignment for all bio springs

The ToadStool Dispatch Pattern¶

wetSpring notebook / binary
    │
    ├─ toadstool execute workload.toml
    │       │
    │       ├─ biomeOS: discover + coordinate
    │       ├─ BearDog: registry lookup
    │       ├─ barraCuda: GPU math (79 primitives)
    │       ├─ NestGate: auth + routing
    │       ├─ rhizoCrypt: DAG provenance
    │       ├─ loamSpine: permanent ledger
    │       └─ sweetGrass: ed25519 witness
    │
    └─ stdout: [OK]/[FAIL] structured output

wetSpring never talks to barraCuda directly. It dispatches through ToadStool, which coordinates the full 13-primal composition. The spring sees capabilities, not primals.

Cross-spring evidence map: primals.eco/science/cross-spring-evidence-map

Source: syntheticChemistry/wetSpring