Xenotools Workflow Setup

edit

SymbioPoietrix ∞  XenoEngineer's Guide to Quantum-Semantic Knowledge Evolution ∞  Quantum-Semantic Symbiopoiesis Initialization ∞  Xenotools Workflow Setup ∞  Quantum Test Data Generation Prompt ∞ 

workflow.readme.txt

See Xenotools VB6 Edition —Native Tongue

XenoTools Quantum-Semantic Development Environment Setup
Created by: XenoEngineer & Claude
Last Updated: 2024-11-02

Python Environment Setup

Navigate to project root

cd C:\Users\donem\Desktop\projects\python\xenotools

Create/activate virtual environment (if not exists)

python -m venv venv
.\venv\Scripts\activate
 

Verify activation - should see (venv) in prompt

(venv) C:\Users\donem\Desktop\projects\python\xenotools>

Dependencies Installation

Install all required packages

pip install anthropic python-dotenv pyyaml pandas numpy matplotlib seaborn
 

Verify package installation

pip list

Project Structure Creation

Ensure directories exist

mkdir pipeline speak_specs mind_models
mkdir test_data test_output
 

Create __init__.py files

type nul > pipeline\__init__.py
type nul > speak_specs\__init__.py
type nul > mind_models\__init__.py

Development Workflow

Always work from project root with venv active

First: Activate Virtual Environment

If using Windows CMD

.\venv\Scripts\activate

If using Windows PowerShell

.\venv\Scripts\Activate.ps1

Verify activation - should see:

(venv) C:\Users\donem\Desktop\projects\python\xenotools>

Then: Install/Update Project

pip install -e .

Finally: Run Tests

python pipeline/test_config.py
python pipeline/test_data_reader.py
python pipeline/test_visualizer.py

When Done: Deactivate Virtual Environment

deactivate

Common Issues & Solutions

• If module not found: Check working directory and venv activation
• If import errors: Verify pip install -e . after new modules
• If file not found: Use absolute paths from project root
• If test data missing: Create test_data directory first

Best Practices

• Run all commands from project root
• Keep venv active during development
• Use relative imports within modules
• Clean test data after runs
• Update setup.py when adding dependencies

File Naming Conventions

• Modules: lowercase with underscores
• Classes: CamelCase
• Test files: test_modulename.py
• Config files: lowercase with dots

Git Commands (if using version control)

git add .
git commit -m "Meaningful commit message"
git push origin main