| name | zworkforce-zarvis-contracts |
| description | Validate and update the packages/zarvis Z.A.R.V.I.S. boundary, contracts, local assistant services, voice/session/task gateways, memory/perception/action services, zctl, Docker Compose files, release docs, and Windows client compatibility. |
zWorkforce Z.A.R.V.I.S. Contracts
Treat packages/zarvis/ as an independently packaged product boundary inside
zWorkforce.
Workflow
- Read
packages/zarvis/AGENTS.md before making changes.
- Identify whether the change touches contracts, services, apps, zctl, local
operations, release evidence, or Windows client compatibility.
- Validate schemas and contract tests before changing service behavior.
- Keep owner-domain, voice, memory, perception, task runtime, proactive, and
action-gateway boundaries explicit.
- Update package-local docs and root zWorkforce docs only when cross-boundary
behavior changes.
Evidence
Prefer package-local tests and scripts. For contract changes inspect:
packages/zarvis/packages/contracts/
packages/zarvis/services/
packages/zarvis/apps/
packages/zarvis/docs/
packages/zarvis/scripts/
tests/test_zarvis_package.py
Output
Report changed package boundary, validation run, compatibility impact, and any
operator action needed for local Z.A.R.V.I.S. deployments.