<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Next Uses on VPN Works</title>
    <link>https://vpnw.com/tags/next-uses/</link>
    <description>Recent content in Next Uses on VPN Works</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://vpnw.com/tags/next-uses/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Next Uses: Seven Places Where a Network per Program Could Fit</title>
      <link>https://vpnw.com/next-uses-seven-places-where-a-network-per-program-could-fit/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://vpnw.com/next-uses-seven-places-where-a-network-per-program-could-fit/</guid>
      <description>&lt;p&gt;The four case studies share one pattern. A program that runs on its own, and can be talked into things, gets a network of its own: one way out, a path chosen for it, a policy a person can read and a record of every connection. Coding agents came first because they are the clearest case, and because the Alpha demo covers them.&lt;/p&gt;&#xA;&lt;p&gt;The pattern turns up well beyond coding agents. None of the seven uses below has been tested, and none is a goal of the Beta, though some would reuse pieces the Beta builds. This post sets out what each would ask of vpnw, what already carries over from the Alpha, and what would be new work. It is a map for choosing what to try after the Beta, ideally with the people who run these systems.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
