Repository navigation
About
.SYSTEMX is an open, reusable project operating format for people and AI
assistants. Its purpose is continuity: keep project context, accepted outcomes,
current work, evidence, and learned facts available across sessions and tools.
The name is the exact folder name, including the leading dot and uppercase letters.
Long conversations can bury decisions, split task status across messages, and
cause new sessions to repeat work. .SYSTEMX gives those facts explicit homes:
Global context for shared project knowledge, a Master Plan for outcomes, a task
ledger for state and evidence, and scoped memory for the project and its agents.
Focused handoffs can reduce repeated input and rework; see the
token, cost, and time guide for the mechanisms and limitations.
- Keep one canonical record for each responsibility and generate status views.
- Preserve user files, existing decisions, evidence, and task history during updates.
- Start new projects from blank records rather than inheriting someone else's backlog.
- Let Agent 0 coordinate review while keeping worker context scoped to assignments.
- Make version choice explicit, with manual updates and pins by default.
- Make installation changes inspectable and removal reversible, with local logs.
- Work across editors, operating systems, cloud folders, and LLMs without choosing a product stack or granting external-service authority.
The format is a project-maintained convention, not an externally certified industry standard. Agent role files do not launch processes, authorize delegation, create automatic cross-project memory, or guarantee delivery quality. The project must supply requirements, actual checks, and acceptance evidence.
Maintained by Wayne Tech Lab LLC, .SYSTEMX is
published under the MIT License. The standalone format was curated
from the operating folder in
SFWA-WTL-TEMPLATE.
SOURCE.json records the original scope and revision. The public
template excludes the original application's content and historical project state.
Preserve the license and attribution when redistributing it.
The repository is WayneTechLab/dotSYSTEMX.
The Python distribution is dotsystemx; its import and command are systemx.
Those identifiers do not change the canonical .SYSTEMX folder name.
Begin with first-time setup. Read the Technical Guide for architecture and the Stack Guide for integration boundaries. Release IDs and history live in the Versions and changelog wiki.
.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
- Getting Started Easy Mode
- Complete Synergy Map: inputs, processing, outputs
- Current beta product film: chapters and scenes
- The Guided Folder: historical 4K walkthrough
- 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
- Film engineering master: original companion
- 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