overinf~/transmissions/why-this-site-is-a-mission-console2026-10-09build 712366b.md

cat ~/transmissions/why-this-site-is-a-mission-console.md

Why this site is a mission console

· 1 min · #site #agents · raw .md

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.

What that means here

  • Text first. Every page reads with no JavaScript, no web font and no stylesheet.
  • Instant. No typing animation, no boot sequence. The terminal look costs nothing to read.
  • Keys. h s t i move between home, systems, transmissions and signals; j and k walk a list, / filters it, : opens a command line. Every key is also a link.
  • True instruments. Every number on the console comes from a named source: the system pages, the published dates, public GitHub data, the site's own git. A lamp shows the stage a system's page declares; nothing pretends to be live.
  • Small. The home page, its styles included, is a few kilobytes compressed. Nothing loads from another origin.

And for agents

An agent reads the same site without parsing a layout. Every page has a markdown twin at its URL plus .md, /llms.txt is the index, and the feeds carry full text.

curl -s https://overinf.com/llms.txt
curl -s https://overinf.com/transmissions/why-this-site-is-a-mission-console.md