---
title: Enablement
generated: true
---

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

# Enablement

7 words that belong together: Slingshot, Sling, Mob, Tally, Enablement, Manifest, Artefact bucket.

## Slingshot

*The rudiment for this is recorded and not yet published.*

**Plain word:** 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.

Also written: client kit, Slingshot kit, the app.

Related: [Fleet](/concepts/fleet) · [MCP](/01-start/claude-code).

Where it is used: [Put something in your own cloud](/01-start/bays) · [Use it from Claude Code](/01-start/claude-code) · [Before you stop](/04-operate/before-you-stop) · [Sessions](/04-operate/sessions) · [Support](/04-operate/support).

[In the glossary](/glossary#slingshot).

## Sling

*The rudiment for this is recorded and not yet published.*

**Plain word:** 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.

Also written: slings, sling it, slung.

Related: [Ghost](/concepts/fleet) · [Replicant](/concepts/fleet) · [Tool](/01-start/claude-code) · [MCP](/01-start/claude-code).

Where it is used: [Put something in your own cloud](/01-start/bays) · [Use it from Claude Code](/01-start/claude-code).

[In the glossary](/glossary#sling).

## Mob

**Plain word:** 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.

Also written: SV mob, joey-mob.

[In the glossary](/glossary#mob).

## Tally

**Plain word:** The record of what your work did, kept as it happens.


Also written: beats, the recorder.

[In the glossary](/glossary#tally).

## Enablement

**Plain word:** 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.

Also written: enable, enabling.

Related: [Fleet](/concepts/fleet).

Where it is used: [Support](/04-operate/support).

[In the glossary](/glossary#enablement).

## Manifest

**Plain word:** 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.

Also written: Slingshot manifest, launch manifest.

Related: [Replicant](/concepts/fleet).

Where it is used: [Use it from Claude Code](/01-start/claude-code) · [StellarView](/index).

[In the glossary](/glossary#manifest).

## Artefact bucket

**Plain word:** 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.

[In the glossary](/glossary#artefact-bucket).

