Do this first

15 words. 10:57.

Not a signup, not a call. Learn the vocabulary. These are Walkthrough Rudiments — named for the drum rudiment, the small figure you drill until it is automatic and out of which everything longer is built. One runs show, name, stop.

Each clip carries two layers. The first is what the tool calls it. The second is the practice underneath — the craft that was true before any of this existed and stays true after. If you never buy anything, take the second layer and go.

15 recorded · 10:57 in total

Where these words came from

The Stellarverse is the work, not the pitch

Every term below was named while building something that had to run. The Stellarverse is that body of work: the applications, the films, the documentation and the sites. All of it was produced by the platform this vocabulary describes. It is open, in one place, twelve films and sixty-nine minutes of it, so you can judge the output rather than the claim.

That is also how this page exists. These clips are not screen recordings somebody made afterwards. They were rendered by the walkthrough engine that ships inside the product, from lesson files in the repository. It is the same engine a customer receives and points at their own system, to make their own. If you want to watch that happen from a cold container rather than take it on trust, the Unboxing is the one to watch.

So these are not marketing words. Each one names a problem that had to be solved before the next thing could be built, and they run in the order the problems arrive: what you are looking at, what it is made of, how work gets planned, and who ends up running it. Where a term needs more than forty seconds, it is written out on the vocabulary page.

  1. 01 Repository or project 44s

    Galaxy

    In the product

    A repository held with its configuration, credentials, analysis state and history as one thing, so opening it means opening all of that.

    The practice underneath

    A working set. Everything needed to work on a codebase kept together, rather than scattered across a README, a password manager and somebody’s memory.

  2. 02 Layer of the architecture, drawn 42s

    Ring

    In the product

    One of five concentric circles in the 3D view. A file sits on a ring by the job it does, not the folder it is in.

    The practice underneath

    Architectural layering. Core, services, APIs, UI, infrastructure. Drawing a system by responsibility is how you find the file that is in the wrong place.

  3. 03 Where an epic is built 42s

    Big Bang

    In the product

    The screen that turns a document or a description into phases, work units, gaps and an architecture drawing per phase.

    The practice underneath

    Planning from a requirement instead of from a backlog. The decomposition happens before anyone writes code, and it is written down where it can be argued with.

  4. 04 A body of work, broken down 37s

    Epic

    In the product

    A feature large enough that it has to be decomposed into phases and work units before anyone starts.

    The practice underneath

    Decomposition. Split the work until each piece is small enough to estimate honestly and small enough to review in one sitting.

  5. 05 A single implementable task 45s

    Work Unit

    In the product

    The smallest piece of an epic that one person can pick up, with its own acceptance criteria.

    The practice underneath

    Decomposition. Estimating a phase is guessing. Estimating something one person can finish, with a written definition of done, is not.

  6. 06 A question the plan cannot answer on its own 44s

    Gap

    In the product

    Something the work needs decided that the documents did not say. It is listed with an owner instead of being guessed at.

    The practice underneath

    Requirements analysis. Analysis does not invent what it was not told. A gap is that refusal written down, so it gets answered by a person.

  7. 07 One epic delivered across several repositories 43s

    Constellation Epic

    In the product

    A single body of work planned and executed across several repositories at once, with the seams between them resolved deliberately rather than discovered late.

    The practice underneath

    Cross-repository release coordination. The hard part of multi-repo work is never the code in any one repo, it is the order and the contracts between them.

  8. 08 Generate a working project from a description 44s

    Vibe

    In the product

    A description in, a project that runs out.

    The practice underneath

    The spike. Build the throwaway to learn the shape, then decide whether the real one is worth building. The mistake is keeping the spike.

  9. 09 A packaged capability for Claude Code 36s

    Skill

    In the product

    A capability packaged with its instructions and its resources, so it runs the same way for the next person.

    The practice underneath

    The runbook. A procedure written down well enough that the person who did not invent it can run it correctly at three in the morning.

  10. 10 A reusable AI prompt template 48s

    Smart Prompt

    In the product

    The instruction held as a file with variables, inheritance and versions, so behavior changes without touching code.

    The practice underneath

    Configuration management. Whatever decides behavior belongs under version control, where it can be read, reviewed and rolled back.

  11. 11 An automated workflow 47s

    Mission

    In the product

    A run in named phases. It keeps the full record of what the AI was asked and what it answered.

    The practice underneath

    Process. The value is that the run has phases with names, and afterwards you can read what was asked.

  12. 12 A recorded or live demonstration 43s

    Walkthrough

    In the product

    A run of the real product, captured, so the demonstration is of the thing rather than of a slide about the thing.

    The practice underneath

    The review at the end of an increment. Show the work running. Describing it is not the same act and everyone in the room knows it.

  13. 13 What each AI call carried, and what it cost 55s

    Spectrograph

    In the product

    Every model call of a build, split into what it carried in, layer by layer, with the ledger of what each call cost. You can see where the context filled, where it was compacted and where the work was handed on.

    The practice underneath

    Measurement. Find out where the work actually went before you change the process. Profilers, time studies and retrospectives with numbers did this long before anyone had a context window.

  14. 14 The cloud instances you run 43s

    Fleet

    In the product

    The instances you have running, and what each of them is for.

    The practice underneath

    Environment management. Knowing what is deployed where, who it belongs to, and which one you are about to break.

  15. 15 A teammate's cloud dev environment 44s

    Ghost

    In the product

    A teammate’s own instance, running in the cloud rather than on their machine.

    The practice underneath

    The development environment that is not a laptop. It is the step everything in the demo economy skips, and it is the step that decides whether the work survives the person who did it.

Then

Now watch the words do something →

Six films in order, each settling one question, every number spoken legible on the screen at the moment it is said.