Introducing Disruptek, Noted.

Updated: Oct 3
Announcement.
We spend a lot of time looking at technology. Inevitably, we spend even more time looking at the assumptions underneath it. Some are explicit. Most are not.
Connect two systems and you've integrated them. Change the identifier and you've broken a pattern. Add better technology and the operation gets better. Give AI more capability and it should get more authority. Maybe. Each of those ideas can be true, but none of them is automatically true.
Technology changes quickly. The assumptions surrounding it tend to have a much longer shelf life. Sometimes the interesting problem isn't whether a technology works. It's whether the environment around it still behaves the way we assumed when we designed it.
Disruptek, Noted. is where we'll explore those questions. These won't be white papers or product pitches, and we're not particularly interested in adding another stream of predictions about whatever technology happens to be having its moment. They'll be short observations about things we think deserve a second look.
WHERE WE ARE STARTING
We'll start with misattribution and observability: why changing an identifier may not change a pattern, why anonymity depends on the population around you, what happens when a privacy mechanism becomes observable, and how quickly correlation can rebuild what was deliberately separated.
Then we'll wander into the space between technology and operations. Why connectivity and integration aren't the same thing. Why humans so often become the integration layer. Why architecture should expect technologies to be replaced. Where AI capability ends and authority begins. And why the next technology may not be the hard part at all.
There will be other rabbit holes. That's rather the point. Noted. We're not trying to settle every question. We just want a place to pull on the threads that look more interesting the closer you get.
We notice things. Occasionally, they're worth writing down.

