Steppe Integrations

An openly authored field series

Systems Without a Department

Field reports from software nobody assigned, but somebody had to build.

Written by

Why this series exists

The clearest systems work often happens outside the org chart.

No product team. No department. No clean requirements. Just a living system, the people who depend on it, and a gap somebody eventually decides to close.

I write these reports because informal systems deserve the same attention as formal ones: observe before changing, make the hidden structure visible, and leave behind something the people still there can operate.

Start here

One camera. Three ways of seeing.

The opening trilogy follows an unattended photography system as it learns where to look, where people stood, and when the light is right.

  1. Part 01

    Photographing a world nobody had time to look at

    Turn raw building geometry into ranked subjects, then let the camera do the patient work of documenting a world at scale.

    Read part one Published on the Baseline project site

  2. Part 02

    Standing where the builders stood

    Move inside. Infer rooms and useful vantage points from the objects people placed, then photograph buildings as their builders experienced them.

    Read part two Published on the Baseline project site

  3. Part 03

    The light they built for

    Hold the camera still and change the hour. Recover useful light from the sky itself, then learn which structures reveal more at dusk.

    Read part three Published on the Baseline project site

The field map

What belongs here.

Not a product category. A set of recurring responsibilities that appear when people care for systems without waiting for a department to form around them.

  1. 01

    Observing living worlds

    Instruments that reveal what a changing environment actually contains, including the things ordinary dashboards miss.

  2. 02

    Invisible maintenance

    The repair, migration, indexing, and operational work people notice only when nobody does it.

  3. 03

    Human judgment and automated work

    Choosing the boundary where machines can repeat the labor while people retain context, taste, and the right to intervene.

  4. 04

    Release and governance

    Ways to change shared systems safely when authority is distributed and trust matters more than velocity theater.

  5. 05

    Stewardship

    Tools built because somebody will remain after the interesting problem is solved—and they deserve a system they can understand.

A publishing boundary

Mechanisms are public. People are not raw material.

These reports explain systems without exposing the communities that made them necessary. Names, handles, private conversations, server details, and operational information that could make stewardship harder stay out.

When a person’s contribution would remain recognizable, I ask before publishing it. The point is to share a useful method—not to turn somebody else’s trust into content.