Files
LithosAnanke/docs/working/outreach/VIDEO_01.md
T
rajamesandClaude Opus 5.5 26c588792e docs(outreach): drafts of a sponsorship page, devlog #1 and video #1
For Captain Bob to edit into his own voice: the sponsorship pitch and tiers, the first devlog
('Building an OS that keeps its own receipts'), and a 5-7 minute video script with an OBS setup.
Claims limited to what is true today: QEMU on three ISAs, the stick in progress, hardware next.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-28 11:12:34 -04:00

2.9 KiB

Video #1: "An OS that proves it's itself" (5-7 minutes)

Draft script and OBS setup (2026-10-28). Captain Bob presents; speak it in your own words, the script is a guide.

OBS setup

  • Scene 1, "Talking": webcam full frame, a lower-third title: "Captain Bob · StarshipOS".
  • Scene 2, "Terminal": a screen capture of the terminal, with the webcam as a small corner inset. Use a large font (18-20 pt) and a dark theme so text reads on a phone.
  • Scene 3, "QEMU": a window capture of the QEMU display, webcam inset.
  • Audio: the microphone with OBS's noise suppression filter. Record at 1080p, 30 fps.
  • Before recording: run one boot so the build is warm. Use make -f kernel/Makefile ARCH=amd64 qemu (the default disks log Zuse in), and have the aarch64 and riscv64 logs from the last acceptance run ready to show.

Script

1. Hook (Talking, 0:00-0:30) "Most software can't prove it's the software you tested. This one checks itself every time it boots. I'm Bob, I spent years validating enterprise software, and this is StarshipOS."

2. What it is (Talking, 0:30-1:30)

  • Boots straight from firmware: no Linux, no libc.
  • Runs FORTH, on an engine modelled on Chuck Moore's F18.
  • Why a stack machine: small enough to understand completely, and to prove things about.

3. The demo (Terminal, then QEMU, 1:30-4:00)

  • Start the boot. While it runs: "It's emulating a PC from firmware up, so give it a minute."
  • Point out the POST line as it passes: PARITY:V4_POST tests=538 pass=538 fail=0. "538 self-tests, every boot."
  • Point out dict_hash=0xfec8c47cfc6f437f. Then show the same line in the ARM and RISC-V logs: "Three different CPUs. Same hash. Same system."
  • The prompt appears: [zuse@Hera] ok>. "It greets its owner. No identity stick, no prompt."
  • Type 3 4 + . and press Enter: 7 ok. "And it's FORTH: it adds."

4. Why it matters (Talking, 4:00-5:15)

  • The validation story: evidence produced while building, not dug up afterwards.
  • Content-hashed capsules: "Is this the approved version?" becomes a hash check.
  • The plan: real PC next week, FPGA in November, proven cores in silicon as the long goal.

5. Close (Talking, 5:15-6:00) "Next video: the first boot on real hardware, whichever way it goes. If you'd like to follow along or help, links are below. Captain Bob, signing off."

Description box

StarshipOS: a bare-metal FORTH operating system that tests and fingerprints itself on every boot. 538 self-tests; one dictionary hash across x86-64, ARM64 and RISC-V; no prompt without its owner's identity stick. Built by Captain Bob. Sponsor: [link] · Devlog: [link]

Honesty checklist (before publishing)

  • Say "in emulation (QEMU)" for anything not yet shown on real hardware.
  • Say "patent pending" only for the filed provisional (the Steady State Machine).
  • Say "being specified in Isabelle/HOL" for the proofs; the v4 proofs are not finished.