Beta Video Guide

.SYSTEMX Beta.4 Explained — video and source guide

Watch the public video · Source release · Media release · English captions · Transcript · Poster

This hosted explainer follows one fictional task through the portable .SYSTEMX record model. It explains software 1.11.0-beta.4, Python package 1.11.0b4, white-paper edition 2.2, and the twelve current SVGs whose art was published with beta.3. The source tag pins the implementation; this film has a separate media identity and does not update the software package. Read the white paper, current visual guide, and first-time setup for the full references.

Chapter and scene map

The authored film has 23 scenes under eleven chapters. The final YouTube player provides the verified chapter times; this guide uses labels so a later edit cannot leave incorrect timestamps here.

Chapter	Authored scenes	What the film explains	Source route
The problem	S01–S02	A project handoff needs objective, task, and evidence in one reviewable place	Overview
Architecture	S03–S04	Context, plan, canonical tasks, focus, memory, and explicit child scope	Architecture map
First run	S05–S06	Version-pinned preview, reviewed apply, provider/credential questions	First-Time Setup
Worked example	S07–S08	Fictional TASK-001, acceptance criteria, six task states, evidence	Task Workflow
Agent roles	S09–S12	Agent 0 coordinates; X records time; Y uses one selected CLI; Z reviews supplied evidence	Detailed agent guides
Context and governance	S13–S15	Alpha chooses AUTOBOT references; Agenda is unset; Access Matrix starts default-deny	Access Matrix
Optional workspaces	S16	Beta records an offline named BOT/DOT workspace	Agent Beta and Agenda
Security and secrets	S17–S18	Agent1 advisory questions, local key-name inventory, distinct secret consumers	Security and Support
Host toolchain	S19–S20	Direct CLI or bounded read-only stdio, with host-owned IDE and provider execution	Agent 0 Toolchain I/O
Evidence	S21–S22	Source/package versus adopter acceptance, and four maps plus seven guides plus atlas	Visual guide
Start here	S23	Pin the reviewed beta, select one project, and begin with one bounded task	Getting Started

One example you can try

The film's TASK-001 is a teaching example and is not seeded in the public template. After adopting the folder in your own project, ask your assistant:

Use this project's existing .SYSTEMX and select the root or named child
explicitly. Read its current focus, context, Master Plan, and canonical task
ledger. Show one incomplete task, its acceptance criteria, and the evidence
still needed. Keep provider and credential choices unset until I review them.

From the containing directory, the optional CLI can preview a pinned first run. Inspect the preview before any apply:

systemx first-run --target "$PWD" --profile project --version 1.11.0-beta.4

The exact tagged instructions cover installation, verification, Windows PowerShell, and managed updates. A selected project supplies its own real facts, permissions, and acceptance criteria.

What the film does and does not demonstrate

The animation illustrates files, commands, records, and decision points. It is not a recorded run of Codex, Muse, Grok, Kiro, Cursor, an IDE extension, a cloud deployment, or a malware scan. Agent 0 is a coordinator role; X records events but does not execute schedules; Y handles a selected CLI handoff but does not merge or accept; Z scores supplied evidence; Alpha selects reference files; Beta's named workspace stays offline; Agent1 reports advisory findings. The stock Access Matrix has 20 rows with no template grant and no project decisions. Ten Agenda setting definitions are present, all effectively unset. A reviewed row is recorded intent and does not grant OS, GitHub, IDE, or cloud permissions. GitHub Actions was disabled for the public source at beta.4 qualification. The film does not establish an adopter's account state, device security, installed host behavior, deployment, or measured token savings.

The visible twelve-image library has four system maps, seven detailed agent sheets, and one atlas. The SVGs declare a 7680 × 4320 canvas with selectable vector labels; generated illustration inside came from smaller native artwork. Open the full-size panels and reading-order text alternative for small print, commands, and exact authority boundaries.

Publication and reuse

Media release · Asset checksums · Transcript · English captions. Verify the hosted player, captions, chapter labels, downloads, and release hashes against the final export before relying on them. Source files and Blender production masters remain in the separately managed owner archive; the reusable repository carries no video or render cache. Earlier films retain their original identities: The Guided Folder, Start with a Folder, advanced walkthrough, and introduction.

Next step: Use the template, follow first-time setup, and review the white paper before adopting the beta in your project.