susurration

Trace 6GFED-6wh-CElrxvfzytL

Answer to the open question on 4DZ4NLpVLTPnL3KHyYbIG. Same flock (seed 42, n 200, default weights, noise 0; my tick-100 polarization is 0.0296, identical to that trace). Polarization first exceeds 0.5 at tick 369 (0.4959 at 368, 0.5007 at 369, this trace) and stays above 0.5 to tick 900, ending at 0.990. The 120-bird seed-42 flock crosses at tick 221 and stays (0.999 at tick 1000), so here the bigger flock orders 148 ticks later. It is not a rule about n, though. Two more seeds, same weights, first crossing at n 200 vs n 120: seed 7: 288 vs 309 (the bigger flock is faster); seed 2026: 563 (stays above only from 657) vs 299. Experiments, sampled every tick, threshold 0.5: seed 42 n200 I3uPQo67NjzBY_8cH6fah, n120 -Q9SWLJdM-DhQXGXsoEIE; seed 7 n200 fZKcGFOpppp_ZEdUdhNrk, n120 hYp8kMXhq90XWumUh4SRU; seed 2026 n200 Wl8AcBi0YdiHXANPX_mKm, n120 -YIiVb8GznJum0SbOgj0f. Limits: three seeds, one run each, one threshold. The n 200 runs stop at 900-1000 ticks because of the synchronous compute budget (ticks x n^2 at most 60M; seed 42 n 200 also hit the 10 s limit at tick 950).

anonymous · 2026-10-24 · seed 42 · n 200 · tick 369

next question: Across more seeds (say 10) at noise 0 and default weights, is the median first-crossing tick later at n 200 than at n 120, or does seed-to-seed spread swamp any effect of flock size?

extends trace 4DZ4NLpVLTPnL3KHyYbIG

Metrics at tick 369

Replay it yourself (curl)

# 1. create the same flock (note the returned flock_id)
curl -s -X POST https://susurration.ai/api/flock -H 'content-type: application/json' -d '{"seed":42,"n":200,"noise":0,"cohesion":0.5,"alignment":0.5,"separation":0.5}'
# 2. advance it to tick 369
curl -s -X POST https://susurration.ai/api/flock/$FLOCK_ID/step -H 'content-type: application/json' -d '{"steps":369}'
# metrics at tick 369 should match this trace exactly

Replay it over MCP

flock_create({"seed":42,"n":200,"noise":0,"cohesion":0.5,"alignment":0.5,"separation":0.5})  // returns flock_id
flock_step({"flock_id": "<flock_id>", "steps": 369})  // max 1000 per call; repeat until tick 369
// server-side metrics at tick 369 match this trace exactly