ALT Page 1 of 4: .SYSTEMX whole-system overview. A human objective feeds context, Master Plan, canonical WORK/TASKS.json and memory. ROOT links planning and saved observations without owning task status. Agent 0 plans, assigns, integrates and accepts; X tracks events/time, Y runs a selected CLI task, Z reviews evidence, and Alpha supplies ten AUTOBOT reference functions. Tools execute within host permissions. DATA holds local payloads; registered child records use .SYSTEMXP. The bottom workflow compares saved harness/bot TODOs, then reconciles, reads back and checkpoints.
ALT Page 2 of 4: Three TODO surfaces, one task authority. WORK/TASKS.json holds canonical states and acceptance evidence; IDE/harness TODOs and optional bot TODOs are observed snapshots. ROOT/MIRRORS.json binds external items to task IDs many-to-many, retaining state, time, revisions and evidence. A seven-step flow selects scope, reads actual TODOs, saves snapshots, runs a read-only delta, reconciles through authorized tools, reads back and checkpoints. External completion or an Agent Z score does not accept done; Agent 0 or the user reviews evidence.
ALT Page 3 of 4: ROOT planning and on-demand references. Agent Alpha, AGENTA/agent.a, routes requests from Agent 0, X, Y, Z and Tools to ten AUTOBOT reference functions: Design, Soul, Memory, Rules, Research, Brand, Media, Tokens, Data and Archive. These are reference files, not ten models or running workers; Alpha is separate. ROOT keeps rules, planning structure and bounded tool cards. Task status stays in WORK/TASKS.json. Requests fingerprint sources, reuse matching results, or retain a new request and response with evidence. Cards do not execute tools automatically.
ALT Page 4 of 4: Scoped ROOT, DATA and toolchain. One outer .SYSTEMX shares tools with registered child projects, whose independent records live in .SYSTEMXP. Each child owns context, plan, tasks, memory and roles, with optional ROOT, AUTOBOT and DATA. Eight DATA folders: TEMP, LARGE, IMPORTS, RESEARCH, ASSETS, EXPORTS, CACHE and ARCHIVE. Payloads are ignored by Git by default; ignore rules are not encryption or cloud-sync control. CLI examples show scoped initialization and read-only delta. Recovery uses backups, receipts and logs. No automatic upload or background sync.
