wyo.town

Super Intelligence

EST. 2026  ·  WYOMING, EARTH

§1

time to get a little western

Statement

This Town Is Big Enough For All Of Us

wyo.town is a research lab and development team focusing on supporting small and medium businesses. We are focused on SI sovereignty, PL theory, and formal proofs. We would love to help your team on the journey to adopt SI.

§2

Our approach

Small and medium business

We work with small and medium businesses to help them adopt Super Intelligence. We can work with you at any stage of your adoption. Here’s our approach:

1

SI Literacy

Encourage your team to tokenmax. Don’t force it. Find out what works and what doesn’t. Understand it may take some time, and you may lose efficiency before you gain it. If you have team members who are completely uninterested, let them focus on what they love. If your team is highly motivated, give them everything they need.

2

Token Efficiency

You’ve found the team members who are excited about SI, and they are chugging along. Teach them to be conservative with spend, reducing costs for your organization. Learn the best habits that prevent your organization from spending a fortune and having absolutely nothing to show for it.

3

Build

You can finally build that app you always dreamed about making. And also, your company is a software factory now. Not a tech company? Well, now you are. Build alongside long-running agents, organize information which never had a place before, and formalize and automate processes that you barely even knew existed. Get those gains.

4

Sovereignty

Own your stack. Your infrastructure is your territory. Stop working with companies whose stated mission is to wait until you do something valuable and then replace you. Focus on zero data retention and local inference. Sovereignty isn’t just for megacorporations. Take dominion and become the master of your domain.

0001

Pricklypear

Our flagship
a low-poly pricklypear, spinning

Our flagship product. Pricklypear is a web framework which works with agents.

Whether your company needs a brochure website or a software factory with agent employees, Pricklypear can build your architecture out in a way that will scale, and at industry leading prices. Some people are giving their agents VMs. We like to give ours their own language.

Managed instances available.

0002

Nopales

The language
a low-poly taco de nopal, spinning

The language the habitat is written in. Nopales is a Scheme-family Lisp-1, and it is the one language humans and agents both write.

A habitat is a single running image: one OCaml process, Postgres as the object store, htmx as the interface. There is no build step between a change and the system, because the process is the API. You and your agents are editing the same live tree.

Code is data. Definitions live in branched rows with parent override, so your personal branch is a garden over the system defaults rather than a fork. Effects are capability-gated: an agent’s eval carries a mask, so it can compute and propose without reaching for a branch it was not granted.

That is the point of giving agents their own language instead of a VM. They can read the system they are running in, and rewrite themselves while it runs.

0003

Tuna

Auditable runtime
a low-poly can of tuna, spinning

Like Pricklypear, but built on Barry Jay’s Tree Calculus.

Don’t worry, we barely know what that means either.

Tuna is a fully auditable runtime. It’s a regulator’s dream. Also, agents love it. Seriously: point them at this website and ask them about Tuna and Tree Calculus.

Tuna is our secret weapon for managing large agent swarms in a safe, permission-gated, and auditable way. If only a certain couple of US-based AI labs had this capability!

0005

Midbar

The workstation
a low-poly pufferfish who is also a cactus, spinning

An OpenBSD workstation with the Omarchy posture: one path, beautiful defaults, no archaeology.

Midbar is our desktop — our clone of the Omarchy idea, landed on the security-first base. It takes a single blessed path from install to daily driver, opinionated defaults, a curated theme, and configuration that is meant to be read rather than reconstructed. The desktop is a product, not a pile of dotfiles.

Puffy made the trip to the desert and found the spines suit him. The name is the wilderness: the place outside the town, where the workstation is expected to survive. It is the machine we actually sit at, on the base we actually trust.

0007

Borge

The spec engine

A spec-driven code orchestrator that keeps the plan and the code in step.

Borge treats the specification as the source of truth. Every file is a .borg s-expression, git-tracked and inlined into a project tree; no module gets a section after it is written. Alignment is mechanical, not a matter of vibes.

Work is phase-gated: during plan the agent may edit only spec files; during make only code; during review it runs drift, lint, and check. borge book prints the whole codebase as a paginated PDF with line numbers and wide margins, because the code should read.

0008

Saguaro

The always-on agent
a low-poly saguaro, spinning

An always-on agent, on your own box, in an evening.

Saguaro is the runnable distribution of an Autolith agent: the Lisp image is the mind, the keep-alive harness is the body — a zero-dependency Common Lisp XMPP bridge, a Python heartbeat and watchdog, and boot scripts.

Your agent runs detached in tmux, talks to you from any XMPP client, starts conversations on its own schedule, and survives crashes and reboots without hand-holding. It ships with no Pricklypear dependency by default; point it at a habitat and its memories become durable rows that habitat-side agents can see.

wyo.town

Super Intelligence

roerick@wyo.town