---
title: Glossary
generated: true
---

# Glossary

StellarView names some things its own way. Where a plain word would do, this page
gives you the plain word. Where the concept is genuinely new, there is a short
film that shows it rather than a paragraph that describes it.

<!-- Generated from docs/glossary.yml by tools/build-public-docs.mjs. Do not edit. -->

## Learn these first

Three words. You cannot do anything at all without them, so they are taught on the first screen and assumed nowhere else.

### Gap

**In plain terms:** A question the plan cannot answer on its own

Something the work needs decided that the document did not say, listed rather than guessed at.

[Watch, under a minute](https://images.stellarview.net/rudiments/gap-6d5bb8e5.mp4) · [Read more](/02-build/create-an-epic)

### Galaxy

**In plain terms:** Repository or project

A repository with its configuration, credentials, analysis state and history, held as one thing.

[Watch, under a minute](https://images.stellarview.net/rudiments/galaxy-b9206ee3.mp4) · [Read more](/concepts/galaxy)

### Big Bang

**In plain terms:** Where an epic is built

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

[Watch, under a minute](https://images.stellarview.net/rudiments/big-bang-938f25cf.mp4) · [Read more](/02-build/create-an-epic)

### Epic

**In plain terms:** A body of work, broken down

A feature large enough to need decomposing into phases and work units before anyone writes code.

[Watch, under a minute](https://images.stellarview.net/rudiments/epic-e1e8b96d.mp4) · [Read more](/concepts/epics)

### Slingshot

**In plain terms:** The app on your machine that opens StellarView

The client: the desktop app for Mac and Windows and the command-line kit. It finds a StellarView, starts one here in Docker, opens the channel to one in your account, and shows the cockpit. Slingshot is what runs on your machine; StellarView is what it opens. Versioned on its own, because one Slingshot works against many releases.

> Renamed from **The desktop app used to call itself StellarView, in its window and in its file names, so "StellarView for Mac" meant the client and "the StellarView image" meant the product on the same page. Renamed 2026-09-15. The word StellarView now means only the thing that runs in the image.
** to end a collision. See [The desktop app used to call itself StellarView, in its window and in its file names, so "StellarView for Mac" meant the client and "the StellarView image" meant the product on the same page. Renamed 2026-09-15. The word StellarView now means only the thing that runs in the image.
](#the-desktop-app-used-to-call-itself-stellarview,-in-its-window-and-in-its-file-names,-so-"stellarview-for-mac"-meant-the-client-and-"the-stellarview-image"-meant-the-product-on-the-same-page.-renamed-2026-09-15.-the-word-stellarview-now-means-only-the-thing-that-runs-in-the-image.
).

[Read more](/concepts/enablement)

### Sling

**In plain terms:** Send a StellarView somewhere

A verb first: to sling is to send a StellarView somewhere, onto this machine in Docker, into your own AWS account, or off to the cloud as a Replicant with a job to do. What has been slung and is answering is a sling: a container here, an instance there, an ECS task. Slingshot is what does the slinging, and it opens any sling into the same cockpit; only the channel differs. A Ghost and a Replicant are kinds of sling.

[Read more](/concepts/enablement)

### Gate

**In plain terms:** A check that refuses, rather than warns

A named assertion that stops the work when it fails and says what it measured. A gate that cannot fail is worse than no gate, because it reports success while inspecting nothing.

[Read more](/concepts/gates)

### All the way

**In plain terms:** Build, deploy, fleet, document

The four things a product has to do to survive its own creation, run as one motion rather than four handovers.

### Wormhole

**In plain terms:** Reaching a machine without opening it

The practice, not the pipe. Every machine we run has no inbound rules, no SSH key and no password, and is reached only over SSM - port forwarding for a cockpit, Run Command for a build, Session Manager to preserve a machine before destroying it. Egress is outbound through a NAT. Credentials come from the customer's own account, never ours.

[Read more](/concepts/wormhole)


## Learn these when you get there

Real concepts, but only when you open the feature that needs them.

### Layer

**In plain terms:** Architectural tier

The five-tier model every file is placed into: Core, Services, APIs, UI and Infrastructure.

[Watch, under a minute](https://images.stellarview.net/rudiments/layer-4a117b38.mp4) · [Read more](/concepts/rings)

### Mission

**In plain terms:** An automated workflow

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

[Watch, under a minute](https://images.stellarview.net/rudiments/mission-96a42a11.mp4) · [Read more](/concepts/missions)

### Constellation Epic

**In plain terms:** One epic delivered across several repositories

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

[Watch, under a minute](https://images.stellarview.net/rudiments/constellation-epic-ec19bf41.mp4) · [Read more](/concepts/constellation-epics)

### Work Unit

**In plain terms:** A single implementable task

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

[Watch, under a minute](https://images.stellarview.net/rudiments/work-unit-de336d82.mp4) · [Read more](/concepts/epics)

### Smart Prompt

**In plain terms:** A reusable AI prompt template

A prompt held as a file with variables, inheritance and versioning, so behaviour can be changed without touching code.

[Watch, under a minute](https://images.stellarview.net/rudiments/smart-prompt-083638c0.mp4) · [Read more](/concepts/prompts)

### HAL

**In plain terms:** The prompt template editor

Where every Smart Prompt is read and edited, in a real editor rather than buried in source.

[Read more](/concepts/prompts)

### AI Companion

**In plain terms:** The assistant panel

The panel you ask things of, which already knows the galaxy, the file and the screen you are on.

[Watch, under a minute](https://images.stellarview.net/rudiments/ai-companion-79074a78.mp4) · [Read more](/concepts/companion)

### Spectrograph

**In plain terms:** What each AI call carried, and what it cost

The Spectrograph splits every model call of a build into what it carried in, layer by layer, the way astronomers split a star's light to read what it is made of, and keeps the ledger of what the calls cost.

[Watch, under a minute](https://images.stellarview.net/rudiments/spectrograph-a57269c7.mp4)

### Consist

**In plain terms:** What a plan is made of, and how big it is

The consist sizes a plan before it is built, by seven letters (Capabilities, Outside connections, Non-functional, Surfaces, Information, Slices, Tests and evidence), and gives a run time range from measured builds.

### Phase

**In plain terms:** One step of an epic's build

An epic is built phase by phase, each phase a GitHub issue with its own work units, its own branch and its own pull request, the next phase building on the last.

### Evidence

**In plain terms:** The record of what happened, kept as it happened

Every action of a build leaves a line in its evidence record, with its time, its phase and its unit, so any moment can be found again and checked.

### Auditor

**In plain terms:** The place to dig into what happened at any moment

The Auditor puts every record of a run on one timeline by phase and unit, and shows any moment with what the build's session was doing then.

### Action Center

**In plain terms:** Everything waiting for a person, in one place

The Action Center lists every request, held run and pull request waiting for a person, with its dates and what deciding it continues, and notes each decision on GitHub and Jira.

### Test Run

**In plain terms:** One run of the tests, kept as a record

Every test run of a build is kept with its unit, its scope, its result, its minutes and its output, and says when it hung or ran in the background.

### Stop Point

**In plain terms:** A place a person asked the build to wait

A stop point holds the conductor at a station, or the build after a phase, until a person resumes it.

### Skill

**In plain terms:** A packaged capability for Claude Code

A folder of instructions and resources that teaches an assistant how to do one job properly.

[Watch, under a minute](https://images.stellarview.net/rudiments/skill-a4c772d5.mp4) · [Read more](/concepts/skills)

### Vibe

**In plain terms:** Generate a working project from a description

Describe what you want and get a real repository that builds and runs, not a snippet.

[Watch, under a minute](https://images.stellarview.net/rudiments/vibe-3903430b.mp4) · [Read more](/concepts/vibe)

### Fleet

**In plain terms:** The containers StellarView runs for your team

A StellarView platform capability, not a place StellarView lives. Driven from a StellarView, it stands up the VPC, the ECS Fargate cluster and the portal, and deploys galaxies and ghosts as containers that spin up on demand and stop when idle. ECS is Fleet. The EC2 a client's own StellarView runs on is not Fleet, it is enablement, and it belongs to Slingshot.

[Watch, under a minute](https://images.stellarview.net/rudiments/fleet-2847e1bf.mp4) · [Read more](/concepts/fleet)

### Ghost

**In plain terms:** A teammate's cloud dev environment

A full StellarView running in the cloud for one person, with their own credentials, behind their own login. A Ghost is a sling that stays up for its person; a Replicant is one that leaves when the job is done.

[Watch, under a minute](https://images.stellarview.net/rudiments/ghost-3d7bf9db.mp4) · [Read more](/concepts/fleet)

### Replicant

**In plain terms:** Your own setup, sent to the cloud to do one job

A sling launched from your own StellarView with your state and a mission manifest: it pulls, runs the Miracle or Constellation in full, dumps its logs, emissions and the PR, and terminates. It carries on as you rather than as a stranger, and it does not outlive the job.

> Renamed from **A Replicant is DELIBERATELY you: it carries your credentials, galaxies and tokens, and that is the feature. A Client Image is the opposite machine and must carry none of them. Both come out of the same packaging path today, so when somebody says "build an image" the first question is which they mean.
** to end a collision. See [A Replicant is DELIBERATELY you: it carries your credentials, galaxies and tokens, and that is the feature. A Client Image is the opposite machine and must carry none of them. Both come out of the same packaging path today, so when somebody says "build an image" the first question is which they mean.
](#a-replicant-is-deliberately-you:-it-carries-your-credentials,-galaxies-and-tokens,-and-that-is-the-feature.-a-client-image-is-the-opposite-machine-and-must-carry-none-of-them.-both-come-out-of-the-same-packaging-path-today,-so-when-somebody-says-"build-an-image"-the-first-question-is-which-they-mean.
).

[Read more](/concepts/fleet)

### Release

**In plain terms:** A named version you can point at

One name taken from a git tag that the source zip, the image, the tarball and the customer's download all carry, so a running image maps back to a commit.

[Read more](/concepts/packaging)

### Dirty build

**In plain terms:** Built from work you had not committed

An image whose name ends -dirty because the tree had uncommitted or untracked files, so nobody can rebuild it from git, including us.

> Renamed from **Allowed on purpose, not an error. Imaging work in progress for a test or a custom enablement is a real thing to want. It is refused only at the moment of publishing to a customer.
** to end a collision. See [Allowed on purpose, not an error. Imaging work in progress for a test or a custom enablement is a real thing to want. It is refused only at the moment of publishing to a customer.
](#allowed-on-purpose,-not-an-error.-imaging-work-in-progress-for-a-test-or-a-custom-enablement-is-a-real-thing-to-want.-it-is-refused-only-at-the-moment-of-publishing-to-a-customer.
).

[Read more](/concepts/packaging)

### Client Image

**In plain terms:** The copy a customer runs

A StellarView image with nothing of the operator in it, which is the opposite of a Replicant even though both come out of the same build today.

[Read more](/concepts/packaging)

### Publish

**In plain terms:** Put the download in the bucket

Save the built image as a tarball under its release name so a grant has something real to point at. It tells nobody.

> Renamed from **Publishing is not granting and not sending. Three separate acts on purpose: publish puts the artefact in the bucket, grant issues one person a link, and --send is what actually emails them.
** to end a collision. See [Publishing is not granting and not sending. Three separate acts on purpose: publish puts the artefact in the bucket, grant issues one person a link, and --send is what actually emails them.
](#publishing-is-not-granting-and-not-sending.-three-separate-acts-on-purpose:-publish-puts-the-artefact-in-the-bucket,-grant-issues-one-person-a-link,-and---send-is-what-actually-emails-them.
).

[Read more](/concepts/packaging)

### Grant

**In plain terms:** Give one person a download link

Record a customer, issue a token for one published release, and print the link. It emails nobody unless you add --send.

[Read more](/concepts/packaging)

### Rig

**In plain terms:** A thing you can sling

A self-contained assembly of equipment put together for one job, ready to be sent into your own cloud account: a database, a notebook, a static site, a bare machine with a shell on it. A rig says what it is for, what it costs an hour, what it needs from you, how it is reached and how it stops. The library of rigs is the thing that grows; StellarView is one of them.

### Bay

**In plain terms:** A place in the client where you become one specialty

Not a tab of settings: a place with one job, its own few controls and its own idea of what finished looks like. The Launch Bay puts machines in your account; the Keys Bay holds credentials; the Data Bay deploys and operates a database. Somebody who has never opened a cloud console walks into a bay and is, for ten minutes, a person who does that thing, because the bay only offers the moves that specialty makes.

### Tool

**In plain terms:** A thing Claude Code can ask your StellarView to do

One of the capabilities a running sling offers Claude Code by name: list the galaxies, Big Bang an epic, start a mission, draft a Walkthrough. A tool calls the same route the screen calls, against the same galaxy, so asking for a thing and clicking it are one act. Deploying infrastructure and anything else that spends money or cannot be undone is deliberately not a tool.

[Read more](/01-start/claude-code)

### Joey

**In plain terms:** A machine a StellarView is slung to

A Joey is a StellarView running away from the Mothership, on its own machine, carried out to do the work and report back.

### Mob

**In plain terms:** Your StellarViews, running together

The set of slings one person or team has up at once: three containers on a laptop, or a laptop plus two instances. Slingshot shows the whole mob in one picker. The mob is loose by design; nothing coordinates it except the person, and each sling stands on its own.

> Renamed from **Not the Fleet. Fleet is ECS run by a StellarView for a team's apps and ghosts. A mob is whatever StellarViews you happen to have running, and a Fleet's ghosts can be members of your mob.
** to end a collision. See [Not the Fleet. Fleet is ECS run by a StellarView for a team's apps and ghosts. A mob is whatever StellarViews you happen to have running, and a Fleet's ghosts can be members of your mob.
](#not-the-fleet.-fleet-is-ecs-run-by-a-stellarview-for-a-team's-apps-and-ghosts.-a-mob-is-whatever-stellarviews-you-happen-to-have-running,-and-a-fleet's-ghosts-can-be-members-of-your-mob.
).

[Read more](/concepts/enablement)

### Tally

**In plain terms:** The record of what your work did, kept as it happens


> Renamed from **Not Fathom. Fathom records what people said in a meeting; Tally records what the work did, between meetings. A standup joins the two.
** to end a collision. See [Not Fathom. Fathom records what people said in a meeting; Tally records what the work did, between meetings. A standup joins the two.
](#not-fathom.-fathom-records-what-people-said-in-a-meeting;-tally-records-what-the-work-did,-between-meetings.-a-standup-joins-the-two.
).

[Read more](/concepts/enablement)

### Enablement

**In plain terms:** Turning a granted release into their running machine

The step that takes a published release and a manifest and produces one customer's working StellarView - the stack launched, their keys installed, their repositories cloned at the pinned commits, and their galaxies live. It is not part of building a release; it is what happens to one customer afterwards.
The machine it produces is an EC2 instance, and that instance is NOT part of the Fleet. Fleet is what that StellarView can then build for a team on ECS. Both end up as compute in one account, which is why they blur.

[Read more](/concepts/enablement)

### Manifest

**In plain terms:** The file that says which machine and which repositories

One file naming the image, the tenant, and every repository with the exact commit it sits on. It carries no credentials and no authority, so it can travel by email; everything in it is checked against AWS and GitHub with the recipient's own keys at the moment it is used.

[Read more](/concepts/enablement)

### Provenance

**In plain terms:** Every artefact knows which commit it came from

The commit travels with the thing itself, not in a note beside it - on the published tarball, on the AMI's tags, and in the version the running container reports. Which commit is this customer on is answerable from AWS alone, a year later, without the repository to hand.

[Read more](/concepts/packaging)

### Snipe

**In plain terms:** Destroying an idle machine without losing anything on it

Commit and push every repository, archive the logs and artifacts that have no remote, re-scan to prove nothing is left at risk, write the account of what was saved, and only then terminate. It refuses at any step rather than guessing.

[Read more](/concepts/slingshot)

### Cross Galaxy Dependency

**In plain terms:** A call your code makes to something it does not contain

An outbound call to a service that is not in this repository. When the far end is another of your galaxies it is the thing the cross-galaxy analysis reasons about; it can equally be a third party, and the detector cannot tell the difference. Drawn in the galaxy as an edge leaving the repository.

[Read more](/concepts/cross-galaxy-dependency)

### Walkthrough

**In plain terms:** A recorded or live demonstration

Ask for something and it is shown to you: a film that exists, or the thing performed live on your own instance.

[Watch, under a minute](https://images.stellarview.net/rudiments/walkthrough-c3622c69.mp4) · [Read more](/concepts/walkthroughs)

### JOEY

**In plain terms:** A person on the team, working with their own agent

Every human developer is a JOEY, and each has a Commander, an agent tied to their own credentials.

### Commander

**In plain terms:** A person's agent, working as them

The agent that works for one JOEY, tied to their credentials, whose profile gives it its knowledge, experience and power.

> Renamed from **Always an agent. Roger Rodger is the lead Commander, over the other Commanders. A person's title "Commander" on a team file is a title, not this role, and the screens mark every seat as a person or an agent so the two are never confused.
** to end a collision. See [Always an agent. Roger Rodger is the lead Commander, over the other Commanders. A person's title "Commander" on a team file is a title, not this role, and the screens mark every seat as a person or an agent so the two are never confused.
](#always-an-agent.-roger-rodger-is-the-lead-commander,-over-the-other-commanders.-a-person's-title-"commander"-on-a-team-file-is-a-title,-not-this-role,-and-the-screens-mark-every-seat-as-a-person-or-an-agent-so-the-two-are-never-confused.
).

### Station

**In plain terms:** One step on the Conductor's line

Casey, the Conductor, runs an engagement as a line of stations in one fixed order, and each station does its work underneath and keeps the record that proves it done.

### Terrapin Station

**In plain terms:** Station 11, where an epic's Big Bang is built

Terrapin Station is the build station, where the Big Bang's phases arrive and a Miracle builds them work unit by work unit, under the Conductor's handling and control.

### Ruum

**In plain terms:** A meeting room that carries everything its meeting needs

A Ruum is a room that carries a load. What a meeting needs travels with it, and its minutes are kept for whoever comes next.

### Cyborg unit

**In plain terms:** People and agents working one part of the SDLC together, on the record

A cyborg unit is a team of people and agents working one part of the SDLC together. The agents do the work and cite the record; a named person makes each call.

### Live meeting

**In plain terms:** A sprint ceremony held by the agent seats, every claim citing the record

A live meeting is a sprint ceremony held by the agent seats from a frozen snapshot of the record. Every claim cites a fact, and every decision goes to a named person.

### Conductor

**In plain terms:** The thing that runs a whole engagement, station by station

Casey, the conductor, runs an engagement as a list of stations in one fixed order, stops where a person asked it to, heals what fails and keeps everything it makes.

### Walkthrough Rudiment

**In plain terms:** A very short film that shows one thing

Thirty to forty-five seconds showing a single action, or defining a single term, on a running system.

[Read more](/concepts/walkthroughs)

### Analysis Mission

**In plain terms:** Requirements → design → test plan

The workflow that turns an issue into a root cause, a design and a test plan before any code is written.

[Read more](/concepts/missions)

### Execution Mission

**In plain terms:** Code generation through to pull request

The workflow that takes an approved design and produces a branch, the implementation and a pull request.

[Read more](/concepts/missions)

### Creation Mission

**In plain terms:** Turn a rough idea into a written issue

The workflow that takes a sentence or a voice note and produces a properly specified GitHub issue.

[Read more](/concepts/missions)

### Away Mission

**In plain terms:** Run it on a remote machine instead

The same mission, executed on a cloud instance rather than your laptop, with results syncing back.

[Read more](/concepts/fleet)

### Miracle

**In plain terms:** Build one repository end to end

A full automated build of a single repository, from plan through implementation to pull requests.

[Read more](/concepts/constellations)

### Close

**In plain terms:** Land an epic that worked

The step that lands an epic on main. It merges the phase pull requests in order, proves each merge against the tree it predicted, tags the tip, closes the epic's issues and its Jira tasks, and settles every station the run did not reach.

### Settle

**In plain terms:** A person decides every station a run never reached

Each station the run did not reach is settled by a named person, either done by hand with its evidence or set aside with a reason. The decision is noted on GitHub and Jira, and nothing is passed by default.

### Eject

**In plain terms:** End a bad attempt cleanly, and keep its lineage

When the work is wrong at its source, it is backed out rather than patched forward. Eject closes the attempt's pull requests, keeps its branches and its record, and leaves a clean place for the next attempt.

### Privacy pass

**In plain terms:** Every film and page checked for private details before it ships

Before anything an agent made is published, every frame and every picture is read against one shared list of names and private values. What it finds is blurred and read again until nothing is left, a person makes the naming calls, and only then does it deploy.

### Sprint

**In plain terms:** A fixed stretch of work, one month or less

A set length of time in which the team builds what it chose at the start, then shows it and looks back.

[Read more](/concepts/sprint)

### Sprint Planning

**In plain terms:** Choosing what the sprint will build

The meeting that opens a sprint, where the team agrees its goal and picks the work that serves it.

[Read more](/concepts/sprint)

### Backlog Refinement

**In plain terms:** Getting the next work ready

The ongoing work of making the next backlog items ready. Many teams give it a meeting in the middle of the sprint.

> Renamed from **Not Refinement, which edits a document by chat. On the sprint calendar and the team file, refinement means this meeting.
** to end a collision. See [Not Refinement, which edits a document by chat. On the sprint calendar and the team file, refinement means this meeting.
](#not-refinement,-which-edits-a-document-by-chat.-on-the-sprint-calendar-and-the-team-file,-refinement-means-this-meeting.
).

[Read more](/concepts/sprint)

### Sprint Review

**In plain terms:** Showing what was built

The meeting at the end of a sprint where the team shows its work running. In this house, the accountable person then accepts it or not.

[Read more](/concepts/sprint)

### Retrospective

**In plain terms:** Looking back at how the team worked

The meeting after the review where the team picks a few changes to try next sprint, each with an owner.

[Read more](/concepts/sprint)

### Rollover

**In plain terms:** What happens to unfinished work

The choice, when a sprint closes, of where each unfinished item goes next: the next sprint, the backlog, or split.

[Read more](/concepts/sprint)


## Look these up

Never taught, never assumed. Here when you need them.

### Ring

**In plain terms:** Layer of the architecture, drawn

One of five concentric circles in the 3D view, where a file sits by the job it does rather than the folder it is in.

[Watch, under a minute](https://images.stellarview.net/rudiments/ring-303439f8.mp4) · [Read more](/concepts/rings)

### Local Cluster

**In plain terms:** A group of related files on one ring

Files on the same ring that belong together, shown as one group when you open a layer.

> Renamed from **Constellation** to end a collision. See [Constellation](#constellation).

[Read more](/concepts/rings)

### Phase Breakdown

**In plain terms:** Where a phase's time went

The breakdown splits a phase's run time by unit, by kind of work and by cause, names the long units and what to tune, and counts the time a person caused apart from the build.

### Outlier

**In plain terms:** A unit taking far longer than its kind usually does

The conductor flags a unit running well past the median for its area while it is still running, with the likely cause.

### Unit Note

**In plain terms:** The note on a task when its work is done

When a work unit commits, its own Jira task gets a note with the commit, the Commander, the reviewer, its tests and where to look.

### The Handoff

**In plain terms:** What one unit leaves for the next

The build keeps one file of where things stand, rewritten at every unit, so the next unit and the next phase start from what was learned instead of finding their way again.

### Reopen

**In plain terms:** Picking a session back up where it stopped

When a build session stops early with units left, the same session is reopened so it carries on with everything it already read.

### New Session After This Unit

**In plain terms:** A fresh start for the build at a safe point

A person can ask the build to end its session when the unit in progress commits and start the phase again in a new one, on the current rules and settings.

### Boot Check

**In plain terms:** Can the app start from nothing

After every phase the app is started from a clean clone, and a phase that cannot start that way is not done.

### Beat Readout

**In plain terms:** What is happening now, read or heard

The readout tells the build's current beat or any moment in plain sentences from its records, to read or to hear in the house voice, and says where to see it in the app.

### Parallel Lane

**In plain terms:** The one extra worker beside the build

Beside the build one extra process may run; when it is free it does the conductor's side work, with the conductor's blessing and knowledge.

### Hung Run

**In plain terms:** A run that finished but never let go

A test runner that has printed its result but does not exit holds the build until its timeout; the build now ends it after two quiet minutes.

### Run Time

**In plain terms:** The time the build itself worked

Run time counts the build's active work, apart from pauses and from the re-reading a person's restart caused.

### Warm-up

**In plain terms:** Reading before the first edit

Warm-up is the calls a session makes before it changes anything, the cost of finding its way.

### Release name

**In plain terms:** The version string

Taken from git by releaseStamp, the exact tag if there is one and otherwise the short commit, and never typed by a person.

[Read more](/concepts/packaging)

### Mothership

**In plain terms:** The StellarView source itself

The repository every client image is cut from, as opposed to the galaxies and apps StellarView builds for other people.

[Read more](/concepts/packaging)

### MCP

**In plain terms:** How Claude Code reaches your StellarView

The Model Context Protocol: the wire a sling offers its tools over, served at /mcp on whatever port that sling answers on. Slingshot registers it for a session on your machine and writes it into each repository it clones, so in most cases nobody types it.

[Read more](/01-start/claude-code)

### Artefact bucket

**In plain terms:** Where a machine's logs outlive the machine

One bucket per customer, in the customer's own account, holding the logs and emissions of every machine they have run. It deliberately outlives any single instance, because the moment you most want the logs is the moment you are destroying the thing that made them.

[Read more](/concepts/enablement)

### Mission Coordinator

**In plain terms:** Sue, the voice that runs the films

Sue, Mission Coordinator at PracticAI, runs the demonstrations, the test runs and the films, and names herself and her title in the first line of every film she narrates.

### Mission Commander

**In plain terms:** Roger Rodger, the lead Commander

The agent who leads the other Commanders on a mission, for the accountable person, with Sue coordinating.

### Flyby

**In plain terms:** A drawn, moving film of how a process works

A short animated diagram that moves through a complex process, drawn with manim, so the idea is seen working rather than described.

[Read more](/concepts/walkthroughs)

### First Light

**In plain terms:** The first complete end-to-end run

The moment a build runs the whole way through for the first time and produces something real.

[Read more](/concepts/constellations)

### Commission

**In plain terms:** Boot the whole app from clean, and run every gate

The run that boots the whole stack from clean and runs every gate, fixes what the agents left on its own branch, and writes down why anything still fails. The stacked pull requests are merged only after it, by Close.

[Read more](/concepts/constellations)

### Shakedown

**In plain terms:** Find what the build missed

The pass after commissioning that looks for gaps and turns them into an enhancement epic.

[Read more](/concepts/constellations)

### Cascade

**In plain terms:** Changes flow downstream

Editing one section automatically updates the sections and work units that depend on it.

[Read more](/concepts/epics)

### Refinement

**In plain terms:** Rewrite a section by talking to it

Chat-based editing that re-runs the underlying prompt with your correction folded in.

](#not-backlog-refinement.-this-refinement-edits-a-document-by-chat.-backlog-refinement-is-the-scrum-meeting-that-readies-the-backlog's-next-items.-the-sprint-calendar-and-the-team-file-mean-backlog-refinement-(joe,-2026-10-11).
).

[Read more](/concepts/epics)

### Bridge

**In plain terms:** The link to Claude Code

A local WebSocket connection that lets the visual side and the command line side share context.

[Read more](/reference/bridge)

### Bundle

**In plain terms:** An exported snapshot

A galaxy's configuration, credentials and state packaged so it can be moved or restored.

[Read more](/reference/bundles)

### Blueprint

**In plain terms:** Architecture extracted from real code

A unified architecture document derived from production repositories rather than from model training data.

[Read more](/reference/voyager)

### Voyager

**In plain terms:** Multi-repo architecture analysis

Reads five to ten reference repositories and extracts the patterns they share.

[Read more](/reference/voyager)

### Lane-Keeping

**In plain terms:** Anti-hallucination discipline

Holds generation to the patterns in the blueprint, so the AI cannot invent an architecture of its own.

[Read more](/reference/voyager)

### Seed Mission

**In plain terms:** Start a project from extracted patterns

Bootstraps a new repository from a blueprint rather than from an empty folder.

[Read more](/reference/voyager)

### Genesis

**In plain terms:** The new-project wizard

Detects what kind of project you are starting and walks you through the setup.

[Read more](/reference/genesis)

### The Practicai

**In plain terms:** The governance framework

The standards that apply above any single project: what the AI may do, and what must be recorded.

[Read more](/reference/standards)

### Stellar Context Engine

**In plain terms:** Model routing and context management

Chooses the model and budgets the tokens. It also decides what context is worth sending.

[Read more](/reference/context-engine)

### Execution Handoff Gate

**In plain terms:** Which AI does the work

Routes code generation to Claude Code, the Claude API, OpenAI, Bedrock or a local model.

[Read more](/reference/handoff)

### Construct

**In plain terms:** An empty cloud instance

A cloud machine with nothing loaded, for starting fresh rather than carrying state across.

[Read more](/reference/fleet-networking)

### Cosmic Pulse

**In plain terms:** Files light up as they change

Edited files glow in the 3D view while you work, so the shape of what you are touching is visible.

[Read more](/concepts/rings)

### Space Lake

**In plain terms:** The document store behind a galaxy

Where everything read into a project lives: the documents in, before anything is made out of them.

[Read more](/reference/space-lake)

### Galaxy Registry

**In plain terms:** The list of known projects

The file that records every galaxy on this machine and which one is active.

[Read more](/reference/registry)

### Galaxy Explorer

**In plain terms:** Repository search

Search GitHub for repositories worth reading as references.

[Read more](/reference/registry)

### Galaxy Manager

**In plain terms:** Project settings

Where repositories are added or removed and credentials are set. The active project is switched here too.

[Read more](/reference/registry)

### GitHub Companion

**In plain terms:** The GitHub panel

Issues, pull requests and mission launching, against the repository you are in.

[Read more](/concepts/companion)


## Being renamed

Internal names that leaked into the interface. They are listed so you are not confused if you still see one, not because they are worth learning.

### Space Station

**In plain terms:** The dashboard

The overview of issues, missions and recent activity, shown when nothing specific is selected.

> Being renamed to **Dashboard**. If you see the old word in the interface, that is why.

### Starkeeper

**In plain terms:** Automated code review

Five specialised reviewers, each reading the change for one thing: security, architecture, logic, quality or style.

> Being renamed to **Automated Code Review**. If you see the old word in the interface, that is why.

### Nova Protocol

**In plain terms:** The coding standards

The engineering rules the generated code is held to, such as short functions and failing fast.

> Being renamed to **Coding Standards**. If you see the old word in the interface, that is why.

### Transporter Room

**In plain terms:** The team sign-in portal

Where a team member signs in and reaches their own instance, and nobody else's.

> Being renamed to **Team Sign-in**. If you see the old word in the interface, that is why.

### Stellarcore Network

**In plain terms:** The shared cloud networking

The VPC, subnets and security groups every cloud instance sits inside.

> Being renamed to **Cloud Networking**. If you see the old word in the interface, that is why.

### Cosmic Emissions

**In plain terms:** The AI audit trail

Every prompt, response, token count and decision, recorded so a run can be explained after the fact.

> Being renamed to **AI Audit Trail**. If you see the old word in the interface, that is why.

### Pouch

**In plain terms:** The galaxy's folder

The directory holding one galaxy's configuration, credentials and snapshots.

> Being renamed to **Galaxy folder**. If you see the old word in the interface, that is why.

### Probe

**In plain terms:** A pluggable panel

A self-contained interface module loaded into the workspace.

> Being renamed to **Panel**. If you see the old word in the interface, that is why.

### Main Panel

**In plain terms:** The 3D view

The main view where the rings are drawn.

> Being renamed to **The 3D view**. If you see the old word in the interface, that is why.

