Showcase study notes
Chapter notes.
Use these videos as a study aid by watching each clip once for sequence, then replaying it
with pauses at prompts, command output, and screen transitions. Each chapter maps visible
behaviour to the subsystem involved and gives source files for follow-up reading. The command
notes are reading cues; prompts and event IDs can vary with image and disk state.
01. Boot identity 02. SlFS persistence 03. Productivity 04. External ELF and HEW 05. Timeline notes 06. Actors and mesh 07. DOOM Chapter 01
Boot identity 01 / clip Open MP4 / poster /media/showcase/01-boot-identity.jpg
Demonstrates
Multiboot entry, early CPU setup, memory initialization, device discovery, service registration, and arrival at an interactive shell prompt.
Subsystems involved
Boot path CPU tables interrupts memory manager console shell
Likely commands and observations make run or make run-nographic QEMU starts the multiboot image and the kernel prints staged initialization lines. help The shell command table is available after the scheduler and console are online. neofetch The system reports its identity, build target, memory, and runtime shape. events 5 Recent boot and shell activity enters the causal event ring.
Chapter 02
SlFS persistence 02 / clip Open MP4 / poster /media/showcase/02-slfs-persistence.jpg
Demonstrates
The persistent filesystem path from VirtIO block I/O through SlFS metadata and file commands.
Subsystems involved
PCI scan VirtIO transport VirtIO block SlFS file commands causal logging
Likely commands and observations ls, cat, write, append File commands exercise the mounted SlFS tree through the shell. sync or reboot cycle Data written to the block device is visible after a later boot. events or trace <event-id> Filesystem work leaves causal records for operator inspection. disk-backed paths Persistent paths refer to the block-backed namespace.
Chapter 03
Productivity 03 / clip Open MP4 / poster /media/showcase/03-productivity.jpg
Demonstrates
The operator workflow around filesystem navigation, editor use, simple browser output, compiler activity, and user program launch.
Subsystems involved
Shell applications keyboard console TCP/IP ELF loader syscalls
Likely commands and observations browser or wget Network-facing tools fetch or display HTTP material through the kernel network stack. edit or typewriter Text entry moves through keyboard, console, and application code. slc <source> A small compiler path produces an executable artifact for the loader. ls, cat, run <program> File inspection and program launch share the shell and syscall surface.
Chapter 04
External ELF and HEW 04 / clip Open MP4 / poster /media/showcase/04-external-elf-hew.jpg
Demonstrates
Loading an external ELF and using the HEW SDK path to connect a small program with SlOS services.
Subsystems involved
ELF loader user runtime syscall ABI task lifecycle actor SDK examples
Likely commands and observations run hello or run argdemo The loader maps an executable and enters the program through the syscall ABI. hew_actor_hello The SDK example shows actor-oriented program structure in the examples directory. strace or events Program activity can be correlated with syscall and causal records. exit status line The task lifecycle returns control to the shell after the program finishes.
Chapter 05
Timeline notes 05 / clip Open MP4 / poster /media/showcase/05-timeline-notes.jpg
Demonstrates
Notes as timeline-backed application state, with search, tags, export, cursor movement, and causal parentage.
Subsystems involved
Causal graph timeline framework replay engine notes application SlFS snapshots
Likely commands and observations note add <text> A note append creates application state and a timeline event. note tag last <tag> Metadata is attached to the current note record. note search <term> Search reads reconstructed note state from the application model. tl show notes, tl rewind notes <n> Timeline commands inspect or move the cursor for replay study.
Chapter 06
Actors and mesh 06 / clip Open MP4 / poster /media/showcase/06-actors-mesh.jpg
Demonstrates
Named local actors, mailbox delivery, route inspection, mesh peers, and federated graph or message state.
Subsystems involved
Actor mailboxes routing table Noise crypto mesh transport federation causal merge
Likely commands and observations actors Registered actor names and mailbox owners are visible from the shell. send <actor> <message> A message enqueue creates actor and causal records. recv or dead-letter checks Mailbox handling exposes delivered and unroutable traffic. mesh, federation, remote Peer and federation commands show distributed routing state.
Chapter 07
DOOM 07 / clip Open MP4 / poster /media/showcase/07-doom.jpg
Demonstrates
Launching a larger graphical program through the SlOS user-program path, framebuffer adapter, input handling, and runtime shims.
Subsystems involved
External program registration ELF loading syscalls keyboard VGA/framebuffer DOOM platform layer
Likely commands and observations doom The shell transfers control to the registered DOOM program. keyboard input Input travels through the keyboard driver into the game adapter. VGA mode or framebuffer output The display path presents game frames through the platform layer. return to shell The process boundary keeps the operating surface available after the program exits.