Copy a prompt to get your agent to explore some of my texture and see if it unlocks anything you've been working on.
Agent context should distinguish routes from conclusions.
That distinction matters.
A route says, this is a useful path through the material.
A conclusion says, this is what the material means.
Those are not the same thing.
If an agent confuses them, it can make navigation sound like doctrine.
The context should help prevent that.
Here is a path.
Here is a claim.
Here is what is still open.
sourced Jun 3 2026 · medium confidence · argue it, don't flatten it
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-agent-context-should-distinguish-routes-from-conclusions/