acativa 0.3.0

Multi-Agent Collaboration Strategy Compiler — generic runtime, state machine and durable strategy store
Documentation
# acativa

Updated: 2026-10-31

Multi-Agent Collaboration Strategy Compiler — a generic runtime, state
machine and durable strategy store for centralized and decentralized
multi-agent collaboration.

`acativa` is host-agnostic. It compiles a workflow definition into a checked
plan, reduces run events into deterministic snapshots, persists runs, commands
and delivery intent in a durable SQLite store, and executes effects through
host-owned adapters and ports. It carries no product schema, package format
or host-vocabulary dependency: a host binds its own schema identity,
persisted vocabulary and effect implementations at every admission boundary.

## Layout

- `workflow` — definition IR, syntax-independent validation, diagnostic
  codes, the schema-parameterized compiler, the deterministic run machine and
  pure dispatch planning.
- `store` — the durable strategy store: admission, routing, controlled state,
  queues, subscriptions, commit decoration and dispatch composition over
  SQLite.
- `runtime` — capability adapters, node facades, the continuous node driver,
  host effect ports, evolution seams and the private stdio protocol.
- `util` — host-agnostic support: private-path hardening, atomic writes,
  bounded archive extraction, SQLite schema-contract comparison and display
  naming.

## Identity model

A host names the workflow schema it accepts with `SchemaId` and hands it to
`compile_workflow` / `compile_workflow_source`. Compiled plans carry a
`PlanKey` — the definition revision plus the compiler semantics, engine
semantics and lowering capability identities — so a retained plan is always
verified against the exact identity it was lowered under, and an old run is
either re-admitted or handed off, never silently re-lowered.

## Private process integration

The `acativa` binary exposes `schema` and `serve` commands. `serve` requires an
explicit existing database and host schema identities; it never migrates a
database or executes an effect. The parent dispatches effects and submits
their outcomes with opaque durable receipts.

See the [documentation index](https://github.com/Unka-Malloc/Acativa/blob/main/docs/README.md) and
[runtime API reference](https://github.com/Unka-Malloc/Acativa/blob/main/docs/runtime-service.md) for the wire contract,
database ownership and restart behavior. In the repository, run
`cargo run -p acativa --bin acativa -- --help`.

## License

AGPL-3.0-or-later. See `LICENSE` and `NOTICE` in the repository root.