Repository navigation
Advanced Walkthrough
Current illustrated walkthrough: The Guided Folder opens the four original system maps with 13 YouTube chapters. This page preserves its earlier film edition, chapter links, and historical feature baseline.
Inside the coordination layer is a 5 minute 54 second narrated technical
walkthrough of the implemented .SYSTEMX alpha.6 format. Eighteen animated
Blender scenes explain the records, agent responsibilities, tools, task-list
observations, scoped projects, preservation, and evidence boundaries.
Watch the historical advanced walkthrough · Open its archived poster.
Watch on YouTube · Wayne Tech Lab channel
Download the original Full HD MP4 · Download the native 4K poster · Media release and checksums
English captions · Narration transcript · Copyable prompts · Chapter list · Editable Blender project · HTML media index · Third-party license and narration notices
The film is 1920 × 1080 at 24 fps, 353.916666 seconds long. Its separate
poster was rendered natively at 3840 × 2160. Synthetic English narration
uses Kokoro af_heart; it is not a recording of the creator's voice. Native
geometry, moving task packets, routes, transitions, visible captions, and an
original soundtrack carry the explanation.
For a short orientation first, watch the existing 1:50 introduction. Its edition, film, links, and publication history remain unchanged.
| Part | What to look for | Related manual |
|---|---|---|
| 1. Whole-system orientation | An accepted outcome, a useful plan, one canonical task ledger, a rich brief, and a bounded follow-up | Planning and memory, task workflow, setup prompt |
| 2. Coordinated execution | App-native workers, Agent Y's external CLI lane, Agent X events/time, Agent Z supplied-answer review, and ROOT observations | Agent 0, Agent Y, Agent X, Agent Z, ROOT |
| 3. Selected reference detail | Agent Alpha and ten AUTOBOT functions; owner-managed DATA with explicit access boundaries | AUTOBOT, DATA, Access Matrix |
| 4. Projects, tools, and measurement | Independent .SYSTEMXP scopes, setup profiles, input-context accounting, preserved updates, and a real local fixture |
SYSTEMX PROJECTS, CLI and Tools, installation, tokens and cost |
The archived alpha.3 four-part 4K field guide supplies the static reference layouts. Its alpha.3 media identity is separate from this film edition.
The native-worker and Agent Y diagrams explain supported responsibilities and controller behavior. The film does not show a recorded external Codex job or published pull request. The host provides running models, app-native workers, execution tools, credentials, and permissions. A role record does not start them. Agent Y's task opt-in, draft PR, review, acceptance, separately authorized merge, verified cleanup, and retained backup remain distinct gates. A Git worktree is not an operating-system sandbox.
The recorded local demonstration contains 39 actual CLI executions involving
20 synthetic HTML inventory files and local task/ROOT transitions. It shows
readiness, a local file check, review/acceptance, and a saved harness observation
that becomes stale after canonical task state changes. The displayed
liveSyncVerified: false and executed: false are deliberate: saved observations
are not a live external readback or a claim of provider execution. The fixture is
not a completed production web application.
The download below is the separate context-counting fixture. It does not include the 20 HTML files or 39 raw command receipts from the local record demonstration.
Download the context-counting fixture · Read its methodology
Agent Z scores supplied answers against its versioned hundred-question policy; it does not independently perform those checks. Agent 0 or the user records acceptance against the task's actual criteria. ROOT compares retained snapshots; authorized real tools perform reconciliation and fresh readback.
Scene 15 counts text in a constructed local fixture using
tiktoken 0.14.0 / o200k_base. There are zero benchmark model calls.
These are input-text counts, not provider billing, measured answer quality,
execution speed, or a universal savings result.
| Long-fixture condition | Per-resume input | Upfront setup and readback | First use including upfront |
|---|---|---|---|
| A. Full constructed history replay | 7,475 | 0 | 7,475 |
| B. SYSTEMX context-command condition | 1,008 | 8,547 | 9,555 |
| C. Ordinary compact-handoff control | 396 | 7,733 | 8,129 |
All three long-case inputs contain 12 of 12 accepted fact groups under the deterministic checker. Fact availability is not an LLM answer-quality score. The ordinary compact control is smaller than SYSTEMX; setup/readback makes both structured approaches larger than full replay on the first use in this fixture.
The small one-step counterexample uses 98 / 805 / 195 input tokens for A/B/C. SYSTEMX also has 1,009 setup/readback tokens in that small case. Tracking adds context overhead there. Choose records for the work's coordination needs and measure the whole workflow against a practical compact handoff. No projected future totals, billed savings, or productivity guarantee are part of this film.
-
One task authority:
WORK/TASKS.jsonis canonical; plans, views, event records, and observed harness/bot lists are not competing task ledgers. -
Selected detail: Alpha selects reference context from ten AUTOBOT functions; they are not ten automatically running models.
Tokens.MDconcerns design/CSS tokens. - Local material: DATA files are owner-managed, with no automatic ingestion. Git-ignore defaults do not establish privacy, encryption, cloud exclusion, or access control.
- Existing storage clients: the Drive profile uses a locally available folder and its authorized synchronization client. SYSTEMX supplies no native cloud connector or background sync service.
- Preserved adoption: ordinary updates retain adopted project files and older snapshots. Startup checks only notify. Stock bootstrap replacement is a separate backed-up operation; logged uninstall/restore is a bounded recovery workflow.
- Reviewable evidence: format validation does not establish application correctness, provider completion, production readiness, or owner acceptance.
The original film has 18 animated scenes and 18 native MP4 chapter markers. The prepared streaming chapter list has 17 navigation entries, combining the opening company/title scene with project context. The downloadable chapter list above retains the exact navigation text.
| Start | Chapter |
|---|---|
| 00:00 | Wayne Tech Lab presents .SYSTEMX |
| 00:23 | A headless coordination layer |
| 00:42 | Turn the idea into accepted work |
| 01:02 | A rich brief. A bounded follow-up. |
| 01:21 | Agent 0 and native subagents |
| 01:40 | Agent Y: the external CLI lane |
| 02:02 | Agent X: time and interruptions |
| 02:22 | Agent Z: repeatable evidence review |
| 02:44 | ROOT: three TODO surfaces |
| 03:04 | Agent Alpha and AUTOBOT |
| 03:25 | DATA and permission boundaries |
| 03:43 | One workspace, multiple projects |
| 04:02 | Current setup locations |
| 04:21 | Measure the context budget |
| 04:53 | Adopt reviewed defaults, keep project records |
| 05:13 | Inspect the recorded state |
| 05:35 | Begin with a small pilot |
Media edition: 2.0. Implemented feature reference: template
1.11.0-alpha.6, source f942daf38fc7f1661910912dbcf07faaec5ad7aa.
The media label media-advanced-v2.0 does not change the installer/defaults
version, add runtime capabilities, or relabel earlier media or white-paper files.
At the film's alpha.6 baseline, GitHub Actions was disabled; film authoring
and checks ran outside the portable template.
The media edition 2.0 release groups the original MP4, native 4K poster, English captions, narration, prompts, chapter list, context/demo fixture, methodology, optional editable Blender project, HTML media index, delivery metadata, and checksums. These media/authoring assets remain separate from the portable template payload. Use the linked delivery metadata and SHA256SUMS to check exact file identities; this media edition supplies no provider execution or downstream application verification.
Delivery metadata · SHA256SUMS · Versions and changelog
Start with first-time setup and one accepted outcome. Read the copyable setup prompt, select an exact reviewed version, and practice a small task before adopting advanced coordination. The one-shot guide explains the larger project workflow; the white paper supplies the technical argument and its limits.
For the beginner-paced native 4K story, continue with Start with a Folder, media edition 3.0. This film's original edition and publication history remain unchanged.
Created by Lucas (SatoshiUNO). A product of Wayne Tech Lab LLC.
.SYSTEMX · DOT SYSTEMX · Maintained by Wayne Tech Lab LLC · Repository · User manual · Prompt cookbook · MIT license
Beta 1.11.0-beta.4 prerelease — validate the selected release in your project. Release policy. Project records, configured commands, and verified evidence determine the state of each adopted project.
DOT SYSTEMX · User manual
1. Start here
- The Guided Folder: 4K walkthrough and visual chapter index
- Start with a Folder: 4K animated guide
- Introduction video and archived poster
- Advanced walkthrough: inside the coordination layer
- Choose a workspace
- Agent 0 roster: roles, bots, and CLI paths
- Agent 0 and toolchain direct I/O
- First-time setup
- Provider and harness onboarding
- Daily workflow
- One-shot project guide
- Shared workspaces, clouds, and bots
- Historical use-case workflows
- Four current system maps
- Current maps, seven agent guides, and atlas
- Agent guide text and CLI flows
- Visual guide and historical diagrams
- New chat setup prompt
- Prompt cookbook
2. Work and continuity
- SYSTEMX PROJECTS
- AUTOBOT and Agent Alpha: Tier 2
- Local DATA storage
- Planning and memory
- ROOT planning, rules, and task delta
- System MAP
- Access Matrix: 20 standard entries
- Agent Beta, Agent1, and Agenda
- Task workflow
- Agent X: events and time
- Agent Y: CLI and PR channels
- Agent Z: fixed review
- 100 review questions
- Agent 0 and subagents
- Subagent processing
- Advanced use cases
- Evidence and acceptance
- Anti-drift and long-running work
- Tokens, cost, and time
3. Setup and maintenance
- Project / VS Code
- OS directory
- Google Drive
- LLM chat
- Exact casing and alias
- Installation and updates
- Upgrading
- Uninstall and cleanup
4. Advanced reference
- Standard format
- Technical Guide
- Stack Guide
- Library integration
- CLI and Tools
- Command reference
- Configuration and quality
- Operations and troubleshooting
- Security and support
- Code review and readiness
5. Project information