ZAIXOS Enterprise Workspace — Management Procedure

Document type: Engineering procedure
Version: 1.0
Date: 2026-06-30
Status: Official — EOS operational document
Owner: Knowledge Architect (maintainer) · Chief Executive Officer (accountable for baseline changes)

---

1. Purpose

The ZAIXOS Enterprise Workspace is the multi-root VS Code / Cursor workspace that loads all officially ratified repositories under one IDE session. It exists so engineers, architects, and AI-assisted tooling share a single folder tree aligned with WORKSPACE_BASELINE.md — fixed hierarchy, authority flow, and dependency direction.

This procedure defines how the workspace file is maintained, how repositories are onboarded or removed, sync rules, validation, and ongoing maintenance. Execution outcomes are recorded in WORKSPACE_SYNCHRONIZATION_REPORT.md.

Related authority:

Document	Role
WORKSPACE_BASELINE.md	Ratified four-repo architecture and roles
WORKSPACE_SYNCHRONIZATION_REPORT.md	Point-in-time sync execution report

---

2. Canonical workspace file

The only authorized multi-root workspace definition for local development is:

Path: ~/PhpstormProjects/ZAIXOS.code-workspace

Properties:

• Lives at the PhpstormProjects root, not inside any single repository.
• Folder path values are relative to that directory (sibling checkout folders).
• Settings block may hold shared IDE settings; repository-specific settings remain in each repo.
• Do not commit alternate .code-workspace files as competing baselines without executive ratification.

---

3. Official folder order

Folders MUST appear in baseline order (matches WORKSPACE_BASELINE repository table):

Order	Folder path	Repository role
1	zaixos-company	Corporate Operating System
2	zaixos-registry	Central Intelligence Layer
3	zaixos-engineering-platform	ZAIXOS Engineering Platform (ZEP)
4	Dental Clinic Revenue Operating System	Consumer product PRD-001

---

4. Repository onboarding

Onboarding a new repository into the workspace requires separate executive ratification amending WORKSPACE_BASELINE.md. Until then, do not add folders to ZAIXOS.code-workspace.

When ratification adds a repository:

1. Clone or place the repository as a sibling under ~/PhpstormProjects/.
2. Append (or insert at the ratified order) a folders[] entry with relative path.
3. Update WORKSPACE_SYNCHRONIZATION_REPORT.md with date, previous state, new state, and validation results.
4. Run the validation checklist (Section 6).
5. Notify contributors to re-open the workspace file once.

---

5. Repository removal

Removal follows the inverse of onboarding:

1. Confirm executive decision and WORKSPACE_BASELINE.md update (repository no longer in baseline).
2. Remove the corresponding folders[] entry from ZAIXOS.code-workspace.
3. Record the change in WORKSPACE_SYNCHRONIZATION_REPORT.md.
4. Run validation checklist.
5. Re-open workspace locally after edit.

Archived or read-only repos stay out of the workspace file even if directories remain on disk.

---

6. Synchronization rules

Rule	Requirement
Baseline alignment	Folder list MUST match WORKSPACE_BASELINE official repositories exactly (count, paths, order).
No shadow workspaces	Avoid personal .code-workspace files that omit registry or company repos for “convenience.”
Path relativity	Use sibling folder names only; do not embed absolute machine paths in JSON.
Single canonical file	Changes go to ~/PhpstormProjects/ZAIXOS.code-workspace only.
Documentation	Every structural change produces or updates WORKSPACE_SYNCHRONIZATION_REPORT.md.
Governance freeze	Workspace architecture is FROZEN; folder churn without baseline amendment is prohibited.

---

7. Validation checklist

Run after any edit to ZAIXOS.code-workspace:

#	Check	Pass criteria
1	JSON syntax	python3 -m json.tool ~/PhpstormProjects/ZAIXOS.code-workspace exits 0
2	Folder count	Exactly 4 entries in folders
3	Folder order	company → registry → engineering-platform → Dental Clinic ROS
4	Paths exist	Each relative path resolves to a directory under ~/PhpstormProjects/
5	Baseline match	Matches WORKSPACE_BASELINE.md repository table
6	Report filed	WORKSPACE_SYNCHRONIZATION_REPORT.md reflects current state

---

8. Future maintenance

• Routine: Re-run Section 7 after clone layout changes, disk moves, or baseline amendments.
• Release alignment: Reference workspace status in registry catalog updates when topology changes.
• IDE: After folder list changes, contributors must File → Open Workspace from File on ZAIXOS.code-workspace (or restart Cursor with that workspace) so all roots reload.
• Versioning: Bump this document’s version when procedure steps change; keep WORKSPACE_SYNCHRONIZATION_REPORT.md as append-only execution history per event.
• Index: Listed in ENGINEERING_INDEX.md under EOS operational documents.

---

Document history

Version	Date	Summary
1.0	2026-06-30	Initial official workspace management procedure