Work

Solana · simulateTransaction → response

The simulation that said no

Zero compute units and an empty log: none of the instructions ran. The RPC call itself succeeded, so the failure only shows up in value.err. Anything that asks a user to sign should check that field first, not the response status.

"value": {
  "err": "BlockhashNotFound",
  "logs": [],
  "unitsConsumed": 0
}

The note behind it

Data · pipes/daily_avg.pipe

Averages you can't add

When days have different volumes, the average of daily averages is not the weekly average. Storing the aggregate state instead of the finished number lets one materialised view answer any window correctly.

-- per day: keep the state, not the number
SELECT toStartOfDay(ts) AS day, city,
       avgState(latency_ms) AS latency
FROM events
GROUP BY day, city

-- any window: merge the states
SELECT toStartOfWeek(day) AS week, city,
       avgMerge(latency) AS avg_latency
FROM daily_latency
GROUP BY week, city

The note behind it

AI · evals/gate.ts (sketch)

A prompt change is a deploy

A sketch of the rule, not production code: a prompt or model change ships only if it scores at least as well as the current one on the same eval cases. Agents usually fail without throwing, so the comparison is the test.

const baseline = await runSuite(suite, { prompt: current });
const candidate = await runSuite(suite, { prompt: next });

if (candidate.passRate < baseline.passRate) {
  throw new Error("regression: " + diff(baseline, candidate));
}