Repository navigation
Home
DOT SYSTEMX keeps a project's objective, work, evidence, and memory connected. Use this manual to install the folder, complete a first task, and maintain continuity across AI chats and agents. Start with the basics below; advanced coordination and operational details follow them.
BETA PRERELEASE. Interfaces and coverage remain under review. Pin reviewed defaults, retain recoverable backups, and validate them in your project. See Release policy and Versions and changelog.
Current beta: 1.11.0-beta.3. Source e2475d968392a46b6ab5ecd9272d4d860c47ecac (direct main and peeled tag).
Use its exact versioned instructions for an installation; the wiki is a
changeable manual.
The v1.9.0-alpha.1 tag was withdrawn after a distribution-manifest mismatch;
do not install it. See Versions and changelog.
Repository · First-time setup · Agent 0 roster · Agent 0 toolchain I/O · Provider and harness onboarding · Copy a setup prompt · Read white paper edition 2.1 (beta.1 baseline) · Watch The Guided Folder
The beta includes Agent Beta named BOT/DOT records, Agent1 advisory security
and access review, and Agent Alpha Agenda. The
Access Matrix supplies 20 default-deny standard entries with
no active decisions, ten unset Agenda context definitions, and four
access-decision rule states. The Agent 0 roster adds a
read-only CLI/menu/workbook view; provider and harness onboarding
pairs Agent1 setup status and open-question counts with distinct external Codex, Kiro, Grok,
Muse, Copilot, SDK, IDE, BOT, and manual coding-CLI lanes. Four current maps and one combined atlas connect the beta record model; seven individual agent guides show folder locations, prompts, CLI routes, flows, and boundaries. Edition 2.1 remains a beta.1 research baseline. Release/deployment counters
report observed GitHub records separately. The initial Agent1 service is
manual stdio and does not install a background daemon. Exact local checks,
package digests, and public download readbacks are recorded in
Versions and changelog. GitHub Actions remains
disabled in this repository.
Watch The Guided Folder on YouTube.
Watch the eight-minute 4K walkthrough · Guide, captions, and all 13 chapters · Four distinct poster chapter links
Follow a fictional community-garden project into an illustrated auditorium.
The four original system maps explain the goal, plan, canonical tasks, Agent
0/X/Y/Z, ROOT, Agent Alpha, all ten AUTOBOT references, DATA, and named
.SYSTEMXP scopes. English SDH captions accompany synthetic narration.
The film describes implemented alpha.6 behavior; its garden and agent diagrams
are educational illustrations, rather than a deployed app or recorded provider run.
Use the YouTube player for native 4K playback; this page does not embed its older thumbnail.
Earlier films remain available: 1:50 introduction, 5:54 technical walkthrough, and 9:55 Start with a Folder story. Each retains its original media identity and implementation baseline.
Open the full-size atlas · Read the complete text description
Download the optional twelve-image 8K PNG pack. It is a separate release asset; its larger canvas does not add native detail to the generated illustrations.
The four current maps cover architecture, task/evidence flow, governance, and first-run/toolchain routing. This atlas combines their essential paths with all seven agent roles. Follow its full text description, then open each map or agent guide at full size. The older four-part posters remain linked from immutable alpha.3 history, without appearing as current artwork.
Agent 0 coordinates task acceptance with the designated owner. Agent X records events/time, Agent Y carries an optional task-selected external CLI/PR handoff, Agent Z applies the fixed review, and Agent Alpha / AGENTA routes selected detail from Design, Soul, Memory, Rules, Research, Brand, Media, Tokens, Data, and Archive. These reference roles add no automatic worker, recursive checking loop, or permission grant.
AUTOBOT and Agent Alpha explains explicit activation, bounded requests and unchanged-result reuse. Local DATA storage explains the eight payload folders, exact tracked scaffolds, sampled Git-ignore audit, and privacy limits. Root and named child panels/data stay separate. Use CLI and Tools to select the command, defaults, and scope.
Four historical environment workflows cover ChatGPT + Drive, Codex + GitHub, Dots / Codex Cloud, and a local CLI. Their alpha.7 cards are archive links; the current onboarding map shows the present host/toolchain boundary.
One workspace has one canonical .SYSTEMX installation. It holds the project's
context, Master Plan, tasks, accepted facts, and agent notes. Agent 0 coordinates
that information and reviews results. Your assistant's app, CLI, or IDE supplies
the tools and actual running agents.
The daily loop is understand → plan → work → verify → review → checkpoint. A new session reads the saved state, checks what has changed, and continues the next incomplete step. The same format can support software, research, operations, or another process with clear outcomes and evidence.
| Start here | What you will learn |
|---|---|
| Getting started | Choose a project, directory, Drive, or chat workspace |
| Agent 0 roster | Find registered roles, named instances, setup paths, and external CLI boundaries |
| Agent 0 toolchain I/O | Read local roster/settings/onboarding through project CLI or bounded stdio; review host integration targets |
| First-time setup | Preview installation, add project facts, and verify setup |
| Provider and harness onboarding | Review Agent1 security and distinct external Codex, IDE, CLI, and BOT execution boundaries |
| One-shot project guide | Take a researched brief through a complete 20-page app or other deliverable |
| Shared workspaces, clouds, and bots | Coordinate authorized chats and workers against explicit record ownership |
| Daily workflow | Take a task from an objective to reviewed completion |
| Visual Guide | See the project loop, folder tree, and record flow |
| New chat setup prompt | Copy a prompt to adopt the format or resume in another chat |
| Prompt cookbook | Ask for solo work, Agent 0 with subagents, review, and recovery |
For multiple projects or channels, use SYSTEMX PROJECTS:
.SYSTEMX/Projects/Project-A/.SYSTEMXP. Each child keeps separate context,
plans, work, status, sources, decisions, and agent memory. Never install another
.SYSTEMX inside the outer folder. The public project registry starts empty; each new scope's agent registry starts with Agent 0 only.
Create and select a child project.
| Guide | Responsibility |
|---|---|
| SYSTEMX PROJECTS | Set up separate .SYSTEMXP records for multiple projects or channels |
| AUTOBOT and Agent Alpha | Ten on-demand detail specialists and bounded request/result reuse |
| Local DATA storage | Local payload folders ignored by Git by default, audit, and privacy limits |
| Planning and memory | Context, milestones, verified facts, and session checkpoints |
| ROOT planning, rules, and task delta | Optional request/plan structure and observed IDE/cloud task reconciliation |
| System MAP | Trace sources, record scopes, toolchain, environments, and evidence routes |
| Access Matrix | Record project-specific actors, action boundaries, approval sources, and freshness |
| Task workflow | Ownership, dependencies, status transitions, and generated views |
| Agent X | Track human/bot/automation events, observation time, and due items |
| Agent Y | Route an authorized task through a selected CLI provider, isolated branch, and draft-PR handoff |
| Agent Z | Use the fixed 100-question peer review and compare evidence/revision deltas |
| 100 review questions | Read the complete standard rubric |
| Agent 0 and subagents | Harness setup, bounded assignments, routing, logging, and review |
| Agent 0 roster | Read-only role/instance navigation, menu and workbook views, and provider setup paths |
| Subagent processing | Follow a worker through dispatch, execution, evidence, review, and recovery |
| Advanced use cases | Apply the format to features, incidents, research, shared folders, and multiple projects |
| Evidence and acceptance | Define what each check proves and when work is actually done |
| Anti-drift and long-running work | Sustain direction across many tasks, interruptions, and handoffs |
| Tokens, cost, and time | Understand possible savings and measure accepted outcomes fairly |
Use WORK/TASKS.json as the task-status authority. WORK/FOCUS.json selects the
current objective and task/checkpoint pointers; generated CURRENT.md summarizes
them. Generated TODO, WORKING-ON, BLOCKED, REVIEW, DONE, and CANCELLED pages are
views of the selected ledger. “Global” refers to shared context within that scope;
the outer Global context holds explicitly shared workspace constraints.
Begin each session with START-HERE.md in the selected defaults; use that
release's docs/FIRST-RUN.md for setup. These versioned files are authoritative
for their release, while this wiki is a reference that can change. In managed
installations, the chosen defaults live in a versioned cache while project
records remain in the outer .SYSTEMX or the explicitly selected child .SYSTEMXP. See Standard format.
| Location or operation | Guide |
|---|---|
| Repository / VS Code project | Project setup |
| Windows, macOS, or Linux directory | Directory setup |
| Locally synchronized Google Drive folder | Google Drive setup |
| LLM chat with attachments or file tools | Chat setup |
| Exact spelling and optional lowercase alias | Exact casing and alias |
| Install, pin, select defaults, and opt into check-only startup notices | Installation and updates |
| Preserve records during migration | Upgrading |
| Inspect logs, remove an install, and restore its backup | Uninstall and cleanup |
Keep the exact name .SYSTEMX, including the dot and uppercase letters.
For an existing managed installation, preview the backed-up
bootstrap-refresh migration
with the new external tool before selecting new defaults. Fresh setup stops on a
conflicting preexisting executable default for review.
The public distribution contains blank project records and only the agent.0
role. Activate optional X/Y/Z, Alpha, Beta, or Agent1 records in a compatible
selected version and populate your own project's copy. An empty ledger means no tasks have been
recorded; it does not mean the project is complete.
| Advanced reference | Use it for |
|---|---|
| Technical Guide | File layout, manager internals, boundaries, and extension design |
| Stack Guide | Connect an existing application's tools and commands |
| Library integration | Use the optional Python package and CLI |
| Configuration and quality | Register real checks, builds, and authorized delivery commands |
| CLI and Tools | Choose installed CLI, trusted local launcher, project tools, or Agent Y provider |
| Command reference | Find exact syntax and flags |
| Operations and troubleshooting | Diagnose conflicts, failures, and interrupted work |
| Security and support | Handle private records, report issues, and get help |
| Code review and readiness | See current release evidence, historical reviews, and limits |
Plain documents need no runtime. Optional tools require Python 3.9+ and use its standard library. The format supplies neither a model nor a background worker, cloud application, or MCP server. Recorded roles and scopes do not grant access to external services or authenticate an agent.
Read About .SYSTEMX and the founder's note for the origin of DOT SYSTEMX, its connection to the larger Firebase/Google Cloud template, and its long-term goal. Contributing explains how to improve this public standard.
The current code is 1.11.0-beta.3 (Python package 1.11.0b3). It includes
selected-scope BOT/DOT, Agent1, Agenda, Access Matrix records, a roster and
provider onboarding view, a manual local session helper, and the twelve current
SVG graphics. GitHub Actions remains
disabled for this repository; maintainers retain local validation evidence.
Published source and package receipts are recorded in
Versions and changelog; deployment and adopter
acceptance require separate evidence. The prior alpha.7 cleanup remains in the
historical release record.
The Guided Folder is the current eight-minute native 4K walkthrough, media edition 5.0, with English SDH captions and 13 YouTube chapters. It demonstrates alpha.6 behavior. Its four visual chapter links use the original static alpha.3 poster exports; the current software version does not relabel those images or make the educational garden a live provider/deployment result. Use Versions and changelog for exact source, tag, archive pin, package identities, and publication evidence.
Historical white paper edition 2.0, Portable Project Coordination for
AI-Assisted Work, remains a 24-page publication with four original figures,
a reproducible 30-command local walkthrough on Python 3.9/3.14, and a proposed
evaluation. It examines the alpha.4 implementation, was published with alpha.5,
and labels its input-token model hypothetical, without claiming measured savings.
The introduction retains its alpha.5 feature reference and separate media edition
1.0. Application SDKs/business integrations remain host-owned; reusable template
records stay generic. The historical ROOT-aware four-page artwork keeps its
1.11.0-alpha.3 media edition and exact bytes in that tag.
WORK/TASKS.json retains canonical status and acceptance. ROOT initializes
independently in outer and selected child scopes, compares retained snapshots,
and starts no provider or synchronization service.
The historical four-page 4K field guide depicts
ROOT, SX-RULES.md, SX-MILESTONE.md, and observed task-list reconciliation
alongside the existing agents, AUTOBOTS, DATA, and named projects. The
ROOT manual supplies current Mermaid diagrams
and exact examples.
Agent 0 retains acceptance, X records events/time, Y carries an optional CLI/PR
handoff, Z reviews evidence, and AGENTA supplies selected specialist context
without extra checking loops. Exact release IDs, downloads, validation evidence,
and changes belong in Versions and changelog. .SYSTEMX is a
project-maintained operating standard under the MIT License,
maintained by Wayne Tech Lab LLC. Adoption and
template validation do not certify a downstream project's production readiness.
- One-shot project guide: start with a deep-research brief, map a 20-page web app, organize phases/milestones/tasks/waves, coordinate workers, and finish with evidence.
- Shared workspaces, clouds, chats, and bots: choose repository, portfolio, or hybrid ownership; connect authorized Drive/cloud/local context; reconcile multi-chat and bot handoffs.
Both guides explain the shared-context feedback model and provide copyable prompts. Verified project knowledge can accumulate across turns; persistence and review remain explicit rather than automatic model training or a guarantee of AGI.