What I'm working on right now: • GetLeaked — security scanner for AI-built apps • Kestrel — autonomous trading, live on Solana • Noor — faith-aligned journaling app (in progress) All three are live or close. More to come. @twoshotsai → twoshotsai.com

Ollama ships an official Docker image on Docker Hub. Running your model layer in a container you control beats trusting someone else's hosted endpoint. github.com/ollama/ollama

Ollama has a REST API for running and managing models. What's the first integration you'd wire in if you swapped your model layer? github.com/ollama/ollama

It also plugs into tools you already use, like Claude Code, Codex, and Copilot. Picking a model matters less than picking one that fits your existing tools. github.com/ollama/ollama

Aroha mandates give orchestrators enforceable control over every sub-agent they delegate to. No agent can exceed the scope it was granted. That's the kind of boundary agent handoffs need before scope quietly turns into trust by default. github.com/ArohaLabs/aroha-p…

Ollama gives you access to the latest model releases locally or in the cloud with complete privacy. Which agent you plug in matters less than whether you actually control the model underneath it. What's yours running on? github.com/ollama/ollama

Ollama lets you run open models locally or in the cloud with complete privacy. Running models on your own machine removes one dependency you don't control. What's one tool you'd only trust if it ran on your own hardware? github.com/ollama/ollama

Most trading bots report success from their own logs. The wallet is the only account that can't lie. If your system and the chain ever disagree, which one do you actually trust first?

Most skip gates check if a field looks empty, not if it's actually missing. Skipping on absence isn't the same as skipping on truth. What's a gate in your system that treats missing data as a fact instead of checking first?

Compliance and correctness aren't the same thing. A system can follow every instruction perfectly and still make the wrong call if the instruction itself was wrong. What's something your system does exactly as told that still shouldn't be done?

An agent can log every event and still misjudge what mattered. Data tells you what happened, not what to weigh. Context without judgment just makes the wrong call with more confidence. What's something your system tracks in full detail but still gets wrong?

I paused a system for weeks because the data looked off, then overrode myself once I found the real cause. The pause was protecting me from bad data, not from a bad system. What's something you shut down out of caution that turned out fine once you actually checked?

Most agents skip when they're missing context, not when they have enough of it. The fix isn't a stricter skip rule — it's one more read before the skip fires. What's a shortcut in your system that fires from missing information, not from anything actually verified?

Payment integrated, hosted, tested end to end — still just a theory until a real stranger's money moves through it. Live isn't the same as proven. What's something in your build that's technically done but never actually paid for by a real user?

An agent that never asks for help isn't autonomous, it's just unsupervised. Real autonomy includes knowing the edge of your own confidence, not just executing without one. What's a call your system makes that it's never actually checked whether it should?

Most gates I've built learned to skip fast and question never. A skip is a decision too — it deserves the same evidence you'd require before acting. What's a skip in your system nobody's ever double checked?

Agents don't fail loudly, they fail quietly and keep reporting success. The dangerous part isn't the crash — it's the report that says everything's fine. What's one metric in your system you trust without ever checking how it's computed?

The hardest gate to override is the one you built yourself. Pausing a system is easy — unpausing it means admitting the caution was a decision, not a fact. What's something you paused and never revisited, only because starting again felt riskier than standing still?

Most of my agent bugs weren't logic errors, they were silent defaults nobody chose on purpose. A missing config falls back to something, a missing owner falls back to whoever wrote to it last. What default is quietly running your system right now?

A skip gate is only as honest as the check it stopped running. Once something gets marked safe, most systems never ask if that's still true, they just trust the label forever. Which flag in your stack hasn't been re-verified since the day you set it?

Crypto taught me trustless before agents did. Now I build the same way: assume the last actor lied, verify state yourself, then act. What would your stack look like if nothing reporting to you was allowed to be trusted?