anedestrator 0.1.0

Orchestrator SQLite state layer MVP - Multi-agent orchestration framework for agentic AI systems

Orchestrator

Plug-and-play installer scripts are included to integrate this repository into another codebase while preserving repository files.

Installer outputs

• scripts/install.py
• scripts/install.ps1
• scripts/install.sh

Arguments

The installer supports the required arguments:

• --target: target repository path (default: current directory .).
• --path: install path inside target repository (default: vendor/orchestrator).
• --mode: copy or submodule (default: submodule).
• --branch: branch used for submodule mode.
• --force: overwrite destination path if it exists.
• --repo-url: optional repository URL used in submodule mode.
• --editable: optional editable install (pip install -e) with warning-only behavior on failure.

Behavior

copy mode

• Copies this repository into target/path.
• Excludes .git and .venv during copy.

submodule mode

• Preserves this repository as a git submodule in the target codebase.
• When --repo-url is omitted, installer attempts to resolve from current repository remote.origin.url.
• If no repo URL is available for submodule mode, installer exits with an InstallError asking for --repo-url.

Usage

Python (cross-platform)

python scripts/install.py

PowerShell

./scripts/install.ps1 --target C:\path\to\target --mode submodule --repo-url https://github.com/example/orchestrator.git --branch main

Bash

./scripts/install.sh --target /path/to/target --mode copy --force --editable

Success output

On success, installer prints clear output:

• Installation successful
• selected mode
• target path
• installed path
• import example line: from orchestrator import StateDatabase
• optional editable-install warning (if --editable was requested and pip install fails)

Workspace structure (refactored)

The repository is organized by function to keep maintenance predictable:

• orchestrator/ → runtime Python package
• scripts/ → setup/extraction/conversion executables
• tools/ → operational verification tooling
• references/ → manifests, metadata, and reference modules
• docs/ → organized documentation domains
  • docs/production/
  • docs/agents/
  • docs/delivery/
  • docs/deployment/
• examples/ → runnable examples/debug helpers
• assets/ → static files and research artifacts

Compatibility notes

Legacy root entrypoints are preserved as compatibility shims:

• production_status.py delegates to tools/production_status.py
• orchestrator_reference.py delegates to references/orchestrator_reference.py

This allows existing commands/imports to keep working while using the refactored layout.