Metadata-Version: 2.4
Name: conductor-engine
Version: 0.6.0
Summary: Minimal orchestration runtime extracted from the Home AI Control Plane.
Requires-Python: >=3.12
Description-Content-Type: text/markdown
Requires-Dist: httpx<0.28,>=0.27
Requires-Dist: pydantic<3,>=2.6
Requires-Dist: pyyaml<7,>=6.0
Requires-Dist: rich>=13

# Conductor Engine

A minimal, installable orchestration runtime for task execution, capability loading, guardrails, storage abstractions, and future agent/policy layers.

## What It Includes

- Generic task contracts and supervisor runtime
- Capability registry and plugin loading
- Built-in `echo`, `filesystem`, `http`, and optional `memory` capabilities
- Optional memU-backed memory provider abstraction
- Local JSON task store and in-memory queue
- `cond` CLI for local task execution and inspection
- Docs-first engine contracts under `docs/conductor/`

## Quick Start

```bash
pip install -e .
cond capability list
cond run task.yaml
cond task list
```

Example task:

```yaml
name: Echo smoke test
capability: echo
input:
  message: hello from conductor
```

## Repository Layout

```text
Conductor-Engine/
  engine/
  cli/
  docs/
  config/
  tests/
```

## Automation

- `.github/workflows/ci.yml` validates Conventional Commit messages, runs `ruff check .`, and runs `pytest tests/engine -q`.
- `.github/workflows/release.yml` uses Python Semantic Release to calculate the next version, tag the release, build the package, and publish it to PyPI.
- PyPI publishing is configured for Trusted Publishing with the `.github/workflows/release.yml` workflow. On PyPI, register this repository and workflow as the trusted publisher. A GitHub environment is optional and is not required by the current workflow.
- If you want the current `0.1.0` in `pyproject.toml` to be the baseline release, create and push `v0.1.0` before enabling the release workflow. Otherwise, semantic-release will calculate the next version from commit history.
