workweaver 0.1.0

AI for business operations — open-source, self-hostable

Workweaver

Workweaver is an AI business operating system built around one codebase and multiple deployment profiles:

• managed_saas for managed cloud runtime
• self_host_production for customer-managed deployments
• standalone and local-first development paths

For standalone/self-host first-run setup, use:

ww init --email operator@local --password "SelfHost1!" --tenant-name "My Workspace"
ww start

ww init now writes first-run bootstrap defaults (admin + tenant + demo seed) alongside profile/server/storage settings.

Packaged-install path (pip install workweaver) is controlled by .github/workflows/release-pypi.yml. The package builds from the repo root and publishes from v* tags through PyPI/TestPyPI Trusted Publishing.

Until the first trusted-published PyPI release appears at https://pypi.org/project/workweaver/, use the repo-local proof path:

python -m pip install .
workweaver init --non-interactive --force --email operator@local --password "SelfHost1!" --tenant-name "My Workspace"
workweaver start --no-learning-service

After the tagged PyPI release workflow publishes the package, the first command becomes python -m pip install workweaver. The same wheel exposes both workweaver and ww entry points.

PyPI release automation lives in .github/workflows/release-pypi.yml. Configure pending trusted publishers for project workweaver with owner bitfoundry-ai, repository workweaver, workflow release-pypi.yml, and environments testpypi and pypi. Tags matching pyproject.toml pre-release versions publish to TestPyPI; final versions publish to PyPI.

After TestPyPI is configured, validate prereleases with:

python -m pip install --index-url https://test.pypi.org/simple/ workweaver

Then verify the runtime contract:

curl http://127.0.0.1:8080/health
curl -i http://127.0.0.1:8080/dashboard

Docker self-host proof path:

make self-host-smoke

The self-host smoke starts Postgres, Valkey, and the backend with no AWS credentials, verifies the self_host_production profile, dashboard serving, WorkMemory remember/recall, and mission/task read paths. If Docker is not available it skips cleanly unless SELF_HOST_SMOKE_REQUIRED=1 is set.

Cost posture proof path:

make cost-guard

The cost guard checks the committed deployment-profile ceilings, managed cost_tier Terraform controls, and AWS resource-type cost-review coverage without calling paid cloud APIs.

Canonical architecture and product truth live in:

• policy/docs-index.yaml
• docs/RUNTIME.md
• docs/PRODUCT.md
• docs/audit/doc-code-capability-map.md

The managed SaaS runtime direction is frozen in docs/RUNTIME.md:

• serverless edge compute for the public path
• portable relational core for stateful intelligence
• provider-specific adapters only at the boundary