SourceShift
Engineering notes from the SourceShift team. Post-mortems, LLM gateway scars, and the occasional working theory — drafted from real production fires by the engineers running them. No newsletter, no popups, no tracking.
- 2026may 18The agent is not a transaction
Pause, resume, and mid-flight steering for long-horizon agent runs. The 2026 literature just named the stream paradigm we built by hand.
- 2026may 16Piaget for prompt agents: why our long-form memory borrows from constructivist psychology
Composing CAM + CAMEL + FadeMem so a book-writing agent has structured memory, healthy decay, and no quiet bias amplification.
- 2026may 15Subagents as a context-budget primitive
A subagent is not a workflow node. It is a budget envelope. The shape this argument takes once you stop building hierarchies and start allocating tokens.
- 2026may 13Two prompt frameworks, one runtime: how we adopted BAML without giving up our cost ledger
BAML wants to own the wire. Our harness already does. We ran them side-by-side in "modular mode": BAML for render and parse, the harness for resolution, telemetry, and cost. Here is why and how — and why the 2026 burden-allocation literature says it was the principled choice, not a pragmatic compromise.
- 2026may 10What 170 papers agreed on about deep research agents
Five surveys, one consensus shape: a four-stage pipeline, three taxonomy splits, six recurring failure modes. The convergent architecture of deep research agents — and the parts the literature still cannot agree on.
- 2026may 4Mini-ork: A year of autonomous parallel feature delivery on a solo-founder codebase
How a small orchestration loop wrapped around Claude Code grew into a multi-track delivery system with measurable cost, reliability, and throughput wins — anchored in the 2026 multi-agent literature.
