Every word, defined once.

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

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

also called Active Galaxy

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

also called Big Bang Creator, Epic Creator

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

also called Epic Creation, Epic Decomposition

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.

also called client kit, Slingshot kit, the app

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.

also called slings, sling it, slung

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.

also called gates

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

also called build deploy fleet document, the four

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.

also called wormholes, private reach

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

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

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

also called Constellation

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

also called WU

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

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

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

also called Companion

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.

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.

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.

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.

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.

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.

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.

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

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

also called Skill Builder, Skill Manager

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

also called Vibe Creator

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.

also called StellarFleet, Fleet Manager

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.

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.

also called sling a Replicant

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.

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

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.

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

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

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.

also called rigs

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.

also called bays

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.

also called tools, MCP tool

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

also called a Joey, remote unit, EC2 unit

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.

also called SV mob, joey-mob

Each person's standing record: every commit, push, test run and pull request becomes a beat with its fact, its link and a spoken line, so "where is Joe at?" is answered at any time, and a standup assembles itself from the beats since the last one.

also called beats, the recorder

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.

also called enable, enabling

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.

also called Slingshot manifest, launch manifest

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.

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.

also called clean snipe, reclaim

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.

also called cross-galaxy dependency, outbound seam

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

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

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

also called Agent Commander

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.

also called station, the line

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.

also called the build, station 11

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.

also called Ruum, the Ruum

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.

also called Casey, the conductor, Engagement Runner, the Runner

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

also called Rudiment

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

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

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

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

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

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

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

also called Planning

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

also called Grooming

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.

also called Review

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

also called Retro

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

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.

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

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.

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

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 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.

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

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.

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

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.

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.

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 counts the build's active work, apart from pauses and from the re-reading a person's restart caused.

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

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

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

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.

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.

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.

also called Sue, Mission Director

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

also called Roger Rodger, Commander Roger Rodger

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

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

The close-out pass that merges the stacked pull requests, retargets what is left, and leaves the repository clean.

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

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

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

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

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

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

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

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

also called Lane-Keeping Discipline

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

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

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

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

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

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

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

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

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

Search GitHub for repositories worth reading as references.

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

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