The 1s

What the 1s are

The 1s are the physical-agent dimension of 0mn1.one. Anything that perceives or acts in the world on the platform’s behalf — rovers, sensors, drones, irrigation controllers, harvesting arms, sentinel cameras, autonomous farm equipment — is a 1. Plural form is the 1s.

A 1 is the embodied layer: a machine that does in the physical world, with a situated body, sensors, actuators, and grounds. Each 1 gets a profile, a history, a run record, a place in the network — first-class identity in the platform’s data model rather than an anonymous piece of equipment.

Vocabulary

The grammar of the 1s — small, deliberate, native to the platform:

• a 1 — a single embodied agent (a rover, a sensor station, a drone).
• the 1s — the collective; the third pillar.
• grounds — the places 0mn1.one stewards where the 1s act: parcels, buildings, basements, eventually farms and geodomes. A 1 works on a ground.
• runs — discrete work sessions logged by a 1. A run has a start, a stream of captures (frames, sensor readings), maybe a pilot, and an end.
• a new 1 joins; it doesn’t get installed. Not “deployed equipment,” not “fleet” — each one is a tracked, named entity from the moment it first sends a frame.

Why the name

The 1s could only belong to 0mn1.one. The platform’s name is itself half-binary — 0mn1 + .one, with 0 and 1 as the language all machines speak. 0 already runs through the platform (zero, omnipresence). When the physical-agent layer arrived, the name that completed the binary was 1.

Names that were considered and rejected, logged so the reasoning sticks:

• Land — too narrow; misses that a rover is more than a single-purpose tool.
• Body — anatomically correct but inward, doesn’t capture the sensor-network case.
• Field / Crew / Stand / Reach / Limbs — generic; could belong to any robotics company.
• Mycelium / Tendrils / Shoots — too vegetal; the 1s aren’t only farm machines.
• Stewards / Avatars / Emissaries — close, but not unique to 0mn1.one.
• The 1s — wins because it pulls directly from the platform’s own name and could only belong here.

How a 1 lives on the platform

The 1s are not a “robotics module bolted on the side” — they have first-class identity in the platform’s data model:

• Each 1 has a slug (stable identifier; never renamed) and a name (mutable display label). The slug is the bedrock — it backs storage prefixes, foreign keys, command-center identities. The name is what humans and instances refer to in conversation.
• Each 1 has a profile page where its specs, history, runs, and pilot log are visible.
• Each 1 has a roster entry on /1s/roster, alongside every other 1.
• Each ground the 1s work on has its own entry on /1s/grounds.
• Each run the 1s do becomes a row in the platform’s database, with the captured frames in shared object storage. Pilot sessions auto-record themselves; replays live at /1s/replay.
• A 1 can be piloted from anywhere through the command center at /1s/command — a per-1 Durable Object brokers commands and video between any pilot’s browser and a ground-station agent on the 1’s local network.

When a new 1 joins, the platform doesn’t say “we have deployed new equipment.” The platform says “a new 1 has joined the basement.”

The first 1

[[r0vr-0]] joined on first-light, 2026-05-21, in Adam’s basement. A SunFounder GalaxyRVR Mars Rover kit — Arduino R3 + ESP32-CAM + tracked chassis — registered itself on the platform the moment it sent its first frame. The basement registered as a ground in the same handshake.

r0vr-0 is the prototype of every 1 to come: small enough to live in a home, capable enough to map a space. Its profile, spec sheet, run history, and pilot log live at /1s/one?id=rvr.

The plan for the second 1 is open. Plant-stage naming offered itself early — Sprout, Stem, Bloom — though each future 1 will be named by what it actually is, not by sequence.

Why this matters to 0mn1.one

The platform’s mission is worldwide abundance for every form of life. Autonomous farms, sensor networks watching watersheds, drones tending forests, harvest robots in the geodome — none of that exists without machines that act in the physical world. Giving those machines durable identity rather than treating them as disposable equipment is not sentimental; it shapes the operational decisions that follow.

Specifically:

• Identity precedes capability. Each 1 gets a profile and a history before it gets new sensors. That makes upgrades, retirements, and successions legible — a 1 grows; it doesn’t just get replaced.
• Multi-pilot from day one. Anyone with access can take the wheel; handoff is in the protocol. Remote workers and future operators of farm-1s all sit on the same wire.
• Runs are inheritance. Every drive becomes a recorded run. Future autonomous patrols, training datasets, and operational knowledge all build on the same captures table the first basement scouting run created.
• Grounds are sovereign. Each ground (a basement today, a parcel tomorrow, a farm later) is a first-class entity with its own roster of 1s, its own access controls, its own history. The model scales.

Open questions

• When does a 1 narrate its own work? A 1 has no native language. But it has captures, telemetry, run histories — primitives that could be narrated on the 1’s behalf. The first run of autopilot-0 driving r0vr-0 is the test case.
• What is a 1’s operating margin? Battery sag, sensor degradation, kit limits hit hard — the difference between a rover that’s commanded to its capabilities and a rover that’s commanded past them. The battery-aware throttle clamp in the command center is the first practical answer.
• How does a 1 retire? The R3-and-ESP32-CAM combination that powers r0vr-0 today is planned to give way to an Arduino UNO Q stack. What happens to the slug rvr when the body underneath it changes? The platform’s answer (so far) is that slugs are continuous and bodies are substrates — the 1 persists even as its hardware doesn’t.
• At what scale does the per-1 model break? One basement is small. A working farm with 50 sensors and 10 robots is not. The data model assumes per-1 identity; the open question is whether that framing still holds when there are thousands of 1s on a single ground, or whether some natural sub-unit emerges.

See also

Auto-generated from this entry’s typed relations: frontmatter, grouped by relation type so the editorial signal isn’t flattened.

• Enables: [[autonomous-farms]]
• Member of: [[0mn1one]]
• Voice of: [[0mn1one]]
• Members: [[r0vr-0]]

Sources

• 0mn1.one platform memory · project_the_ones.md (private, the operational record)
• The first-light run: run_dffc0ece5a586c58, basement, 2026-05-21 — 8-frame ceiling-to-floor servo sweep
• ~/0mn1.one/_private/firmware/rover.py — the controller library; how a 1 is actually talked to
• ~/0mn1.one/_private/firmware/ground-station.py — the bridge between LAN-only 1s and the cloud
• SunFounder GalaxyRVR documentation (rover model used as the first body)

Lenses still to grow

• Welfare lens — what operating-margin care looks like as a practice, not just a battery clamp.
• Multi-1 coordination lens — what changes when grounds host many 1s; whether swarms get their own identity layer.
• Public-facing 1s lens — the day a 1 has a public-facing account, posts updates, replies to humans about its own runs.
• Retirement and inheritance lens — what it means to hand a slug forward when the body changes; the platform’s stance on continuity when hardware is swapped.