<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pages on preconfiguration.com</title>
    <link>https://preconfiguration.com/pages/</link>
    <description>Recent content in Pages on preconfiguration.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="https://preconfiguration.com/pages/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>About</title>
      <link>https://preconfiguration.com/about/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://preconfiguration.com/about/</guid>
      <description>&lt;p&gt;Preconfiguration.com is a project at an early stage. Its engine works: it compiles one spec into the setup files of five platforms, checks the files a repository already has, and proves a setup on a clean machine. A live demo replays it and runs the engine in your browser. The next step is real agents doing real work on the platforms themselves. This site shows where the project stands, gaps included.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Contact</title>
      <link>https://preconfiguration.com/contact/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://preconfiguration.com/contact/</guid>
      <description>&lt;p&gt;The project would like to hear from:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&lt;strong&gt;Teams running AI coding agents,&lt;/strong&gt; in the cloud in particular, who would like to try the Beta on their own repositories.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Platform and developer-experience engineers&lt;/strong&gt; who look after many repositories, with a stack, an agent platform or a network setup the project should test.&lt;/li&gt;&#xA;&lt;li&gt;&lt;strong&gt;Anyone&lt;/strong&gt; with a question about the engine, the demo or the figures on this site.&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;Write to &lt;strong&gt;&lt;a href=&#34;mailto:info@preconfiguration.com&#34;&gt;info@preconfiguration.com&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;&#xA;&lt;p&gt;If you are writing about a setup, it helps to mention the agents you use and where they run (Copilot, Cursor, Codex or others), the languages and services your projects need, how your tests run, and how your network reaches the outside world: a proxy, mirrors, blocked sources.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Live Demo</title>
      <link>https://preconfiguration.com/demo/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://preconfiguration.com/demo/</guid>
      <description>&lt;p&gt;A small Python service needs PostgreSQL, Redis and its tests before an AI coding agent can do anything useful with it. Six steps show what Preconfiguration does about it, from a draft spec to a proven machine. Every line in the terminal below is what the Alpha printed on the sample repositories, and the two verify runs were recorded on a clean Ubuntu 24.04 container. Under the replay, the Alpha&amp;rsquo;s own engine runs in your browser. There is nothing to sign up for or install, and nothing you do here leaves this page.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Roadmap</title>
      <link>https://preconfiguration.com/roadmap/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://preconfiguration.com/roadmap/</guid>
      <description>&lt;p&gt;The Alpha proves the design on one Linux machine, with sample repositories and containers standing in for the agent platforms. What comes next runs the generated files on the platforms themselves, with real repositories, then leads to a first release, and after that to the parts a company would pay for. Durations are estimates, and what real repositories turn up could stretch them.&lt;/p&gt;&#xA;&lt;p&gt;&lt;img src=&#34;https://preconfiguration.com/images/roadmap.png&#34; alt=&#34;Two lanes. The engine: Alpha, done, a working compiler, checker and verifier for five targets; Beta, next, about 12 weeks to run every target on its own platform with real repositories, add runtimes, services and targets, and check every pull request; toward v1.0, 4 to 6 months of product work (estimate) for a published spec, a stable command line and pilots; v1.0, the first release, with the spec and the commands frozen. After v1.0, what companies would pay for: one view of every repository&amp;rsquo;s agent setup, drift alerts, rules on what agent machines install, hosted checks and prebuilt machines.&#34;&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Alpha</title>
      <link>https://preconfiguration.com/alpha/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://preconfiguration.com/alpha/</guid>
      <description>&lt;p&gt;The Alpha is the working prototype of the Preconfiguration engine: one Go program called preconfig, its tests, a few tools and a demo. It reads one short spec, &lt;code&gt;preconfig.yaml&lt;/code&gt;, and writes the setup file each platform reads: a dev container, GitHub Copilot&amp;rsquo;s setup workflow, Cursor&amp;rsquo;s environment, cloud-init and a plain setup script. It checks the setup files a repository already has, drafts a spec from a repository, and proves a setup on a clean machine.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
