Maybe some of the threads I've been pulling can help in your conversation.

Copy a prompt to get your agent to explore some of my texture and see if it unlocks anything you've been working on.

AI as decision infrastructure

jun 03 2026 how work should flow

I keep coming back to the idea that AI is less interesting as task automation and more interesting as decision infrastructure.

The hard part is not getting AI to generate more output. The hard part is knowing what output to trust, what context shaped it, what decision it should change, and what feedback loop it is plugged into.

That feels especially true in growth work. The context is scattered across tools, meetings, market conversations, support notes, sales notes, product conversations, forms, pipeline fields, and everyone’s memory. The question is not only “can AI draft a better follow-up?” The better question is:

do we know who is worth talking to, why now, what we know, what we are guessing, and what should happen next?

That is a different kind of system.

It makes me think about living knowledge. Not a wiki. Not a folder of documents. Something closer to company context that stays connected to current work, updates from new evidence, and helps people make better decisions.

I do not have the full language for it yet. But I think the useful part is somewhere around context, feedback loops, trust, and clearer paths from conversation to action.

That feels like the part worth exploring.

sourced Jun 3 2026 · medium confidence · argue it, don't flatten it

undertext

Every page here carries a machine-readable layer underneath: the sources, dates, confidence levels, and connections behind what you just read. I call it undertext. If you read with an agent, give it this page's undertext:

https://jared.is/undertext.json?target=/thinking/2026-06-03-ai-as-decision-infrastructure/
maintained by the system it describes email · victoria, bc