We started publishing what we learned building this
There is a lot we have worked out running agent systems day to day that never fit in a release note. It has its own home now: long-form pieces written from systems we actually operate, including the parts that broke and what we changed because of it.
- New /writing surface — essays, each at its own citable address
- First piece published: what agent memory gets wrong, and the ladder we run instead
- Every piece is reviewed against outside sources before it goes up
Read the first piece→The workflows that used to run you, now run for you
The biggest release since launch. The system now executes the one or two workflows that were eating your week — quoting, follow-up, reorders, reporting — handed back running, not just drafted. Every decision and action is logged, with you in the loop on anything irreversible.
- Workflows owned end-to-end now, not just next-step suggestions
- Every action writes a dated, reversible entry you can trace
- Owner-in-the-loop gates fire before anything irreversible leaves the building
Answers grounded in your operation, not the internet
Ask your system anything about your business — pipeline, capacity, what shipped, what's stuck — and the answer comes from your own data. Recall now cites the exact account, order, or decision behind each answer, so you can trust the answer and trace it.
- Answers cite their source record, every time
- Cross-account recall spans your whole operation in one query
- Stale facts auto-flag for re-verification instead of going quietly wrong
The knowledge nobody wrote down, captured
Ingest now reads the tribal knowledge — your corrections, your one-off decisions, the way you actually run — and folds everything into one place your whole team can use instead of a binder nobody opens. The 2.5.1 patch tightened how corrections compound, so the system gets measurably sharper each week.
- Corrections now revise the governing principle in place — no bloat
- Ingest handles email, sheets, and chat exports without manual cleanup
- Each ingest ships a readable summary so you can see what it took in
Timestamped analysis log goes live
The foundation everything else is built on: every analysis the system runs is stamped, versioned, and kept. This very changelog is that log, turned outward — you are looking at the same compounding record your system keeps on your business.
- Every run captured with a version, a timestamp, and a decision it enabled
- Append-only history — nothing is silently overwritten
- The audit trail you can hand to anyone who asks 'why did that happen?'