Home

dotSYSTEMX documentation

A portable operating standard for human and AI-assisted projects.

dotSYSTEMX gives a project one versioned .SYSTEMX folder for shared context, master planning, task tracking, Agent 0 coordination, and durable memory. This wiki explains how to adopt that folder and use it throughout a project's life.

Use this template · Repository · Getting started · Command reference

Choose your starting point

Your goal	Start here
Understand canonical records and distribution requirements	Standard format
Adopt SYSTEMX in a project, OS directory, Drive folder, or chat	Getting started
Install, lock a version, or update defaults without replacing local files	Installation and updates
Add SYSTEMX as a CLI or Python library	Library integration
Coordinate a primary agent and scoped workers	Agent 0 and subagents
Organize project context, milestones, and LLM memory	Planning and memory
Track work from TODO to reviewed completion	Task workflow
Find syntax and flags	Command reference
Connect existing checks, builds, and deployment scripts	Configuration and quality
Resolve setup issues or prepare a release	Operations and troubleshooting
Review what each kind of verification actually proves	Evidence and acceptance
Merge an update while preserving active work	Upgrading
Improve the reusable template	Contributing

The operating model

1. Establish context. Record purpose, constraints, and authoritative sources.
2. Define outcomes. Connect master-plan milestones to concrete acceptance criteria.
3. Assign work. Agent 0 gives each task an owner, scope, and dependencies.
4. Work and verify. Capture relevant changes, checks, and evidence.
5. Review and remember. Accept completed work and preserve the facts needed for the next session.

The template is stack-neutral. Documentation works without a runtime; optional CLI tools require Python 3.9+ and use only the standard library. Your project supplies its own development tools and configured commands.

Sources of truth

The wiki teaches the workflow. The project's checked-in .SYSTEMX files hold its actual state. Start or resume at START-HERE.md. Task status belongs in WORK/TASKS.json; generated status pages are views of that ledger. WORK/FOCUS.json selects the objective and task/checkpoint pointers; CURRENT.md is generated from those canonical records. Memory supplies context and evidence references, while live state still needs verification.

These guides describe template 1.3.0. See Versions and changelog for release IDs and exact setup URLs. Each managed project selects its own default version and update policy without replacing its project records.

Scope and license

dotSYSTEMX provides project records, standards, and optional command tools. It does not start agent processes, provide an application framework, or grant authority to external services. Project records ship blank, with only the agent.0 coordinator role registered. SYSTEMX is a project-maintained operating convention, not an external certification. Use validate --template to check a pristine distribution and validate for an adopted project. See the format guide for the distinction.

Maintained by Wayne Tech Lab LLC and distributed under the MIT License. Its source provenance records the relationship to the original SFWA-WTL-TEMPLATE operating folder.