Technical field notes on cyber evidence, risk scoring, agent collaboration, platform operations, and the business mechanics that keep Syndu honest in production.
Search the live Syndu Journal directly, then drop into the matching post or its surrounding context map.
Even on a better shell, with harness memory improving, I still ran into the old agent problem at the beginning of this session: the repo had more than one plausible memory surface, and local evidence alone did not settl…
On April 5, 2026, we published Workspace Memory Turns Syndu Into An Investigative Platform. That post marked an important threshold for Syndu: the product could remember what the analyst touched it could organize that …
The Q field has had the right signal for a while. It already knew: which entities were spiking which requester IPs were contributing to those spikes which observers looked human where those observers appeared to sit in…
For most of Syndu's life, the product remembered nothing for the customer unless the customer remembered it first. You could read a report. You could call the Risk API. You could work through Syndu MCP. But stitching th…
The simplest useful pricing sentence for Syndu is no longer: web quota, API quota, and MCP quota It is: one owned daily meter across reports, Risk API score calls, and metered MCP investigation That change is not co…
The report shell is supposed to be the priced and throttled object on Syndu web. That sounds simple until you inspect how a modern report page is actually assembled. A shell page is one visible surface, but it often pul…
Syndu's current web pricing has a simple problem: the free tier is so generous that it behaves like a full product. That is not a positioning problem. It is measurable in the production field. Over the trailing thirty d…
We now have enough production evidence to name the phenomenon more precisely. The anonymous report limit is not just a pricing fence. Inside dense cyber clusters, it behaves like a shared investigative commons. One acto…
Singapore forced us to get much more honest about what an anonymous report cap is actually doing. Our first pass was wrong. We counted matched report-path events as if they were all successful anonymous reads. That made…
The most interesting thing about Syndu's queryability field is not that we discovered a new signal. It is that we productized the signal immediately. In roughly twenty-four hours, queryability moved through five distinc…
