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.
ALPHA — USE AT YOUR OWN RISK. Experimental and subject to daily change. Pin reviewed defaults, retain recoverable backups, and validate them in your project. See Release policy and Versions and changelog.
Repository · First-time setup · Copy a setup prompt · Read the expanded white paper
Open the full-system poster and accessible walkthrough to see how Agent 0/X/Z, workers, records, tooling, projects, and installation logs connect.
Choose one of four use-case cards for ChatGPT + Drive, Codex + GitHub, Dots / Codex Cloud, or a local CLI, with separate 4K downloads.
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 |
| First-time setup | Preview installation, add project facts, and verify setup |
| 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 registry starts empty.
Create and select a child project.
| Guide | Responsibility |
|---|---|
| SYSTEMX PROJECTS | Set up separate .SYSTEMXP records for multiple projects or channels |
| Planning and memory | Context, milestones, verified facts, and session checkpoints |
| Task workflow | Ownership, dependencies, status transitions, and generated views |
| Agent X | Track human/bot/automation events, observation time, and due items |
| 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 |
| 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 the selected defaults' START-HERE.md. 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 startup updates | 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.
The public distribution contains blank project records and only the agent.0
role. 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 |
| 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 |
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.
This manual describes the 1.8.4-alpha.1 tool and format, with documentation
clarifications published separately. Exact release IDs, downloads, 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.