JB Ranch, a real build: the fields the flight plan sprays, in magenta, with the planned flight counting up.

Where are all the apps?

Your documents in. A running, supported company out.

A human view of the SDLC. The picture is from a real build: JB Ranch, and the fields its flight plan sprays.

How long have you got?

  1. 2 min

    What it is

    Coming

  2. 5 min

    A demo

    Coming

  3. 10 to 20 min

    The full detail

It is still you.

AI writes code. A chatbot will not build an enterprise, and the SDLC will not learn itself. Time is moving faster than anyone can learn Docker, git, node and python one at a time. A team that works the old way will not keep up. You still need all of the SDLC. You need to understand it, not every tool underneath it. StellarView brings a human view to the SDLC and carries the technical weight, in its own platform and in the platforms it builds, so the developer of tomorrow works at a higher level.

Welcome. There is a lot here: 57 articles, 38 films and 10 forty-second rudiments, with new ones most weeks. Wander, or follow a path: the claims on this page link to the films and articles behind them.

7:27 · one sprint, from setting up to the release, narrated by Sue, Roger Rodger and C D Cakes · the record behind it →

New: Agents in the ceremonies you already run: one sprint, on the record · Oct 12, 2026

What is StellarView?

Your documents in. A running, supported company out.

All the way there, on the tools you already use: your repositories, your issues, your board, your wiki. It is not a thin wrapper over Jira or GitHub. It is a modelled SDLC that carries development domain experience, with the automation, the infrastructure as code and the deliverables of a complete development practice. Teams and individuals come out of it understanding the SDLC, not just holding the output.

  1. StellarView reading a codebase as rings, one ring per architectural layer, every system labelled.

    01

    See it

    It reads a codebase out of its own repository and draws it as rings, one ring per architectural layer, every system labelled.

    Watch: Ring, the rudiment · 0:42 → Read: The Rings →

  2. One epic opened into the work: ten phases, one hundred and six work units, eight hundred and forty-eight hours.

    02

    Plan it

    Your documents go into the Big Bang. On the RealWorld Conduit build, one document came out as ten phases, one hundred and six work units, eight hundred and forty-eight hours, and 357 questions it would not answer for itself.

    Watch: The plan asked 357 questions · 5:06 → Read: StellarView Alpha, part one →

  3. Phase four stacked on phase three.

    03

    Build it

    The phases run unattended on your own repositories, a branch and a pull request per phase, each stacked on the one before.

    Watch: The run · 3:24 → Read: StellarView Alpha, part three →

  4. The launch report: seven units on one timeline, FABERI-341 held at sixteen of seventeen.

    04

    Launch it

    A launch can say no. Seven units, eighty-six checks, one held at sixteen of seventeen, and the six that passed went.

    Watch: Launch day · 5:36 → Read: Show HN: the whole horse →

  5. The Agent Room: Sue opening a launch, the seats down the right, the launch on the shared screen.

    05

    Run it together

    People and agents work in the same rooms on one record. In the sprint’s meetings, a claim that does not cite a fact is struck before it is said.

    Watch: The whole lifecycle, end to end · 19:42 → Read: Every claim cites a fact →

  6. The support desk running on the operated build.

    06

    Hand it over

    It stays on your repositories, your issues, your board and your wiki. The published RealWorld suite passes thirteen of thirteen, and it comes with its own support desk.

    Watch: Operated · 3:41 → Read: StellarView Alpha, part five →

What it has built

Companies, not demos.

Enterprise, consumer, and verticals from estate law to aerial spraying, every one grown the same way.

Go deeper

The long reads.

Field reports in parts, written the day it happened. Each one carries its screens and its numbers, what it cost and what did not work.

Judge the output

Six articles. Read them in order.

There is not enough time to try every AI builder. So do not try this one. Judge it by what it built and how much ground that covers. Each article has one film and one exit, and each one ends with a paragraph naming what it does not prove.

  1. 01 The demo is not the system attention
  2. 02 The SDLC didn't go away category
  3. 03 From talk to running system belief
  4. 04 The foundation is already there relevance
  5. 05 What it refuses trust
  6. 06 Who runs it purchase

Learn the language

Ten words, and the craft underneath each one.

Galaxy, Ring, Big Bang, Epic and the rest. 10 Walkthrough Rudiments, thirty to forty-five seconds each, 6:58 in total. Every one shows the thing, names it, and names the practice underneath it.

All ten, in teaching order →

Why

What does this process look like?

That is the question StellarView came from. Earthly concepts are used up and limited. Science and space have always pushed us with ideas, fantasy that becomes reality, so the work is drawn as galaxies, rings and stars: a codebase you can see, and a build you can watch.

Where the apps die.

They work on somebody’s laptop. The step after that is deployment. Running somewhere else, with support behind it, is where most apps stop. That step never got cheaper. This site is about the people who take it anyway, and how.

Few people have ever taken a developer solution all the way, so most cannot see how much stands between the fancy hello world they just made and something that runs for someone else. We do not say that from above. It was our plight first.

The founding essay: The Modern Principal → The Sunday Build →

Your turn

Bring your documents.

There is nothing to install, and it is not a trial. Send the requirements documents you already have.

Bring your documents