overinf builds systems for people who work through AI agents: fleet command for agents, memory engines, and instruction wardrobes. https://overinf.com/transmissions 2026-10-09T00:00:00+03:00 Ramazan Polathttps://github.com/ramazanpolat https://overinf.com/transmissions/reading-this-site-as-an-agent 2026-10-09T00:00:00+03:00 2026-10-09T00:00:00+03:00

Where an agent should start on overinf.com, and what each machine-readable file holds.

<p>If you are an agent, you do not need the HTML. Start here:</p> <div class="table"><table> <thead> <tr> <th>Path</th> <th>What it holds</th> </tr> </thead> <tbody><tr> <td><code>/llms.txt</code></td> <td>the index: systems, transmissions, signals, with links to their markdown twins</td> </tr> <tr> <td><code>/llms-full.txt</code></td> <td>everything published, in one markdown file</td> </tr> <tr> <td><code>/index.json</code></td> <td>every item with its type, dates, tags, summary and a content hash</td> </tr> <tr> <td><code>&lt;page&gt;.md</code></td> <td>the markdown twin of any page: a small YAML header, then the text</td> </tr> <tr> <td><code>/feed.xml</code>, <code>/feed.json</code></td> <td>transmissions and signals, full content (Atom, JSON Feed 1.1)</td> </tr> </tbody></table> </div> <p><code>/transmissions/feed.xml</code>, <code>/signals/feed.xml</code> and <code>/systems/feed.xml</code> carry one section each, in Atom and in JSON.</p> <p>The content hash in <code>/index.json</code> changes only when an item&#39;s text changes, so an agent that keeps a copy can fetch only what moved.</p> <p>Reading and training are both allowed; <a href="https://overinf.com/robots.txt">/robots.txt</a> names the agents it expects.</p> https://overinf.com/transmissions/why-this-site-is-a-mission-console 2026-10-09T00:00:00+03:00 2026-10-09T00:00:00+03:00

overinf.com is built like a mission console in a terminal, for people and for agents, and it is small on purpose.

<p>Most of the work behind overinf happens in a terminal: Claude Code sessions, playbooks, agents that lead other agents. So the site is a console: systems with their stage lamps, telemetry, a log of transmissions and signals.</p> <h2 id="what-that-means-here">What that means here</h2> <ul> <li><strong>Text first.</strong> Every page reads with no JavaScript, no web font and no stylesheet.</li> <li><strong>Instant.</strong> No typing animation, no boot sequence. The terminal look costs nothing to read.</li> <li><strong>Keys.</strong> <code>h</code> <code>s</code> <code>t</code> <code>i</code> move between home, systems, transmissions and signals; <code>j</code> and <code>k</code> walk a list, <code>/</code> filters it, <code>:</code> opens a command line. Every key is also a link.</li> <li><strong>True instruments.</strong> Every number on the console comes from a named source: the system pages, the published dates, public GitHub data, the site&#39;s own git. A lamp shows the stage a system&#39;s page declares; nothing pretends to be live.</li> <li><strong>Small.</strong> The home page, its styles included, is a few kilobytes compressed. Nothing loads from another origin.</li> </ul> <h2 id="and-for-agents">And for agents</h2> <p>An agent reads the same site without parsing a layout. Every page has a markdown twin at its URL plus <code>.md</code>, <a href="https://overinf.com/llms.txt">/llms.txt</a> is the index, and the feeds carry full text.</p> <pre data-lang="sh"><code>curl -s https://overinf.com/llms.txt curl -s https://overinf.com/transmissions/why-this-site-is-a-mission-console.md</code></pre>