# AlphaGSM video production handoff Prepared 13 October 2026; public brief reviewed 26 October 2026. This file is a self-contained brief for a future AlphaGSM introduction. It plans production; no footage has been recorded or video rendered as part of this handoff. ## Assignment Make a clear introduction to Alpha Game Server Manager (AlphaGSM), an open source command-line tool for running dedicated game servers. The film should make a first-time operator comfortable with the command flow and direct them to the website docs. Use real terminal recordings, the existing Sector Alpha identity, restrained motion graphics, and readable captions. Primary audience: players who want to host a server, community administrators, and developers considering a contribution. Tone: practical, friendly, technically accurate. Avoid exaggerated uptime claims, fleet-management promises, fake performance metrics, and a release date that maintainers have not announced. Recommended outputs: | Output | Purpose | Format | | --- | --- | --- | | 90-second introduction | Website and YouTube project overview | 1920×1080, 30 fps, H.264 MP4, AAC audio | | 30-second introduction | Social discovery | 1080×1920, 30 fps, H.264 MP4, AAC audio | | 4–6 minute first-server walkthrough | Follow-along documentation | 1920×1080, 30 fps, chaptered MP4 | | Captions and transcript | Accessibility and reuse | UTF-8 SRT/VTT and Markdown | | Poster/thumbnail | Website and YouTube | Original 16:9 image; preserve logo aspect ratio | Produce the 90-second introduction first. The shorter film is a deliberately recomposed edit, not an automatic centre crop of terminal footage. The walkthrough uses a separate full, verified recording. ## Sources and facts to recheck before production - Website: https://alphagsm.sector-alpha.net/ - Program source: https://github.com/SectorAlpha/AlphaGSM - Docs: https://github.com/SectorAlpha/AlphaGSM/tree/master/docs - Docker manager: https://github.com/SectorAlpha/AlphaGSM/blob/master/docs/docker-manager.md - Commands: https://github.com/SectorAlpha/AlphaGSM/blob/master/docs/commands.md - Support evidence: https://github.com/SectorAlpha/AlphaGSM/blob/master/docs/TEST_STATUS.md - Support checklist: https://github.com/SectorAlpha/AlphaGSM/blob/master/docs/game-server-support.md - Platforms: https://github.com/SectorAlpha/AlphaGSM/blob/master/docs/platform-support.md - Mods: https://github.com/SectorAlpha/AlphaGSM/blob/master/docs/installing-mods.md - Contributor guide: https://github.com/SectorAlpha/AlphaGSM/blob/master/DEVELOPERS.md - License: https://github.com/SectorAlpha/AlphaGSM/blob/master/LICENSE - Releases: https://github.com/SectorAlpha/AlphaGSM/releases Reviewed source revision: `32cef5ba9e03053c8e461fffa0ba133b160b528d` on `master`. Support tracker date: 16 October 2026. Excluding the non-server `archive_backed_installs` harness, the detailed tables contain 141 passed entries, 49 enabled with authentication prerequisites, 45 enabled with user-provided prerequisites, 4 disabled, and 1 awaiting validation. That is 240 tracked entries, including 235 enabled entries; variants and aliases are not necessarily distinct games. These totals count the detailed rows rather than treating summary headings as fresh lifecycle evidence. The current website's older “234 supported server targets” and “V1 imminent” copy must not be used as video evidence. Prefer an undated line such as “a broad catalogue of server modules, with a published support tracker.” If a count is shown, date it and distinguish tested, authentication-dependent, user-supplied, and disabled entries. The release API returned no published releases when this brief was prepared; recheck before showing a downloadable release. AlphaGSM is Linux-first. Ubuntu 24.04 is the full lifecycle validation baseline. Representative Minecraft checks on Windows/macOS do not prove the complete catalogue works there. The program is GPL-3.0-or-later; do not relabel it MIT. Credits identify Sector Alpha, founders Cosmosquark and Staircase27, and contributor Aule. ## Existing assets and media still needed Public website assets are available relative to https://alphagsm.sector-alpha.net/. - `assets/sector-alpha-logo.png`: existing Sector Alpha logo, 269,547 bytes. - `assets/sector-alpha-mark.png`: existing Sector Alpha mark, 147,728 bytes. - `styles.css`: reference colours and type treatment; cyan/teal on dark navy. - Website pages: capture from the verified published version at production time. There is no video footage, voiceover, or cleared music bundled with this brief. Capture terminal footage on a disposable Ubuntu 24.04 environment using the production-time AlphaGSM checkout. Record the commit, runtime, game version, and capture date in an evidence manifest. Create a fresh demonstration server; never reset or restore a real community world for the film. Record: repository acquisition, wrapper startup, create, interactive setup, start, status, query/info, doctor, logs, backup for a module with a backup hook, graceful stop, and the website docs/community pages. Keep complete source recordings and make condensed editorial cuts from them. Do not invent successful terminal output. The homepage terminal is an illustrative animation, not lifecycle evidence. Optional gameplay must be operator-recorded or have documented permission. Game logos, screenshots, publisher footage, and music each need their own provenance; the AlphaGSM source license does not grant rights to third-party media. The film can be effective with terminal and website footage alone. ## 90-second storyboard Timing is an editorial target. Adjust cuts to the recorded narration while keeping commands readable. | Time | Picture | Narration / purpose | On-screen text | | --- | --- | --- | --- | | 00–08 | Existing Sector Alpha mark resolves over a dark background, then a real terminal | Introduce the operator's problem | “Your server. Your commands.” | | 08–18 | Website hero, then real `--help` overview | Introduce AlphaGSM and its open source nature | “Alpha Game Server Manager” / “Open source CLI” | | 18–36 | Create and interactive setup in a verified Minecraft demo; cut loading waits transparently | Show that the workflow is learnable | “Create → Setup” | | 36–48 | Start, status, and actual query/info evidence | Show checks rather than only a launch command | “Start → Check” | | 48–60 | Doctor/logs and a successful Minecraft backup | Introduce routine maintenance | “Inspect. Update. Back up.” | | 60–70 | Simple original diagram: Docker manager uses host daemon; game containers beside it | Explain runtime choice without an architecture lecture | “Docker first. Host options too.” | | 70–80 | Support catalogue with visible status labels; docs and developer guide | Show honest coverage and contributor entry points | “Check your module's prerequisites” | | 80–90 | Website Docs link and project source link; clean closing identity | Give one clear next action | “Start with the docs” / “alphagsm.sector-alpha.net” | ## Draft voiceover for the introduction > Running a game server should not mean remembering a different script for every task. > > Alpha Game Server Manager—AlphaGSM—brings dedicated server operations into one readable command line. It is an open source project from Sector Alpha. > > Start by choosing a game module and creating your server. Setup downloads and configures its files. Then start it, check its status, and use query or info to inspect the running server. > > The same command surface helps with everyday work: reading logs, checking the runtime with doctor, updating supported game servers, and backing up modules that provide a backup hook. > > The recommended first-run route uses a Docker manager. You can also run AlphaGSM on the host and choose a supported Docker or process runtime for your game. > > Check the published support tracker before you begin. Some modules need an account, owned files, or other prerequisites, and broader platform validation is still developing. > > Whether you want to run a server or contribute a new module, the guides show where to start. > > Visit alphagsm dot sector-alpha dot net. Open the docs, choose your route, and take control of your next game server. Review pronunciation: “Alpha G S M”; “Sector Alpha”; “Docker.” Use the future task's selected voice/profile settings. Match footage to the final approved narration and generate timed captions from that audio. Do not flash full commands behind captions that obscure them. ## Capture command sequence Run from a disposable workstation as a non-root user with Docker/Compose access and Python 3. Read the current upstream Docker-manager guide before capture. These are capture instructions, not a claim that the lifecycle has already been run. ```bash git clone https://github.com/SectorAlpha/AlphaGSM.git cd AlphaGSM git rev-parse HEAD ./alphagsm-docker start ./alphagsm-docker mymc create minecraft.vanilla ./alphagsm-docker mymc setup ./alphagsm-docker mymc doctor ./alphagsm-docker mymc start ./alphagsm-docker mymc status ./alphagsm-docker mymc query ./alphagsm-docker mymc info ./alphagsm-docker mymc logs ./alphagsm-docker mymc backup ./alphagsm-docker mymc stop ``` During interactive setup, choose a host-visible path under the wrapper's state directory and review Minecraft's current EULA prompt. Do not treat the brief as license acceptance. Use a game version compatible with the selected runtime. Record setup choices. If an operation fails, keep the diagnostic evidence, resolve it, and recapture; never animate a fabricated pass. Backup and mod support are module-specific. A TF2 manifest mod demonstration, if wanted, uses a separate verified TF2 server and the documented MetaMod/SourceMod sequence. Use a neutral terminal account name. Keep keys, access tokens, passwords, private hostnames, player names, and private addresses outside the capture environment. Use intentional editorial cuts for long downloads and disclose “download shortened” when the cut could imply unrealistically fast provisioning. ## 4–6 minute walkthrough outline 1. **Choose a route:** Docker manager, host manager with Docker game runtimes, or host process fallback. Explain the Ubuntu baseline. 2. **Prepare:** Git checkout, Docker/Compose permissions, host Python, writable state path, game-specific requirements. 3. **Create and setup:** show the module name, server identifier, real prompts, install path, and license choice. 4. **Start and verify:** wait for real readiness; show status, query/info, and doctor. Distinguish process liveness from game readiness. 5. **Operate:** logs, stop, settings discovery, and a supported backup. Explain restoration in words rather than performing it on valuable data. 6. **Next steps:** link to the matching game guide, operations docs, support tracker, issues, and contribution guide. Include chapter titles, a downloadable transcript, and the exact commit/runtime/game version in the description. ## 30-second vertical cut 00–05: “One readable command line for your game server.” 05–18: show large, separately framed command lines for create, setup, start, and status. Preserve full meaningful output; recompose the layout instead of cropping important terminal columns. 18–24: show Docs and a short “Check module requirements” caption. 24–30: website address and existing Sector Alpha closing identity. Keep captions and important terminal output inside the selected platform's current safe areas. Inspect the horizontal and portrait compositions separately. ## Production workflow Use the production team's supported recording, narration, captioning, and rendering tools. Keep the source recordings, narration, asset provenance, and review reports with the production package. Review a composed preview before rendering and obtain explicit approval before publishing to a chosen destination. This public brief contains no internal tool commands or workstation configuration. Production-specific instructions belong in the team's private workspace. ## Production package Suggested project-owned folder structure: ```text alphagsm-introduction/ brief.md evidence/source-manifest.json recordings/terminal-full.mp4 recordings/website.mp4 assets/sector-alpha-logo.png narration/script.md narration/voiceover.wav captions/introduction.srt captions/introduction.vtt exports/alphagsm-introduction-1080p.mp4 exports/alphagsm-introduction-portrait.mp4 exports/alphagsm-first-server-walkthrough.mp4 exports/alphagsm-introduction-poster.jpg review/render-report.md ``` These are planned deliverables, not files that already exist. The manifest records source URL/path, source revision, recording date, media rights/provenance, exact demo environment, and successful command evidence. Keep project IDs, job IDs, output revisions, and verification reports with the package. ## Acceptance checklist - Commands, source revision, and support claims were rechecked before recording. - Real footage proves the lifecycle; staged output is clearly labelled and never presented as test evidence. - Every caption and meaningful command remains readable on desktop and a phone preview. - Branding, caption safe zones, and terminal framing work in composed previews and final decoded frames. - The first and final frames, every scene transition, and at least one frame per scene have been inspected. - Voiceover is intelligible without music; if music is used, its rights are recorded and it does not mask speech. Check loudness and peaks with the actual export tools. - Exports have the requested dimensions, duration, frame rate, codecs, and audio tracks; caption files align with the final edit. - The website address resolves and the Docs link works. - The reviewer checked the final render and its matching title/description/copy; an older preview is not final approval. - Publishing remains a separate future action for explicitly chosen destinations. ## Handoff to the production team Prepare the storyboard, narration, media manifest, and a composed preview from this brief. Recheck the linked AlphaGSM guides and support status before recording. Preserve Sector Alpha branding, use genuine command recordings, and keep captions readable in each output format. Review the final render and its title, description, and transcript before any separately authorised publication.