# One machine that becomes a mesh and then assigns itself the audit logger.
#
# The substrate is first-node's — a store, a broker, the control plane — and one module image on
# top: the tool runtime carrying the audit-logger (mesh-catalog). The node enrols itself and the
# mesh assigns it the audit logger, so its events account is one the mesh delivered, not the
# broker's own (novox/hq ADR 0048).
scenario: audit-node

segments:
  hosting:
    kind: public
    cidr: [192.0.2.0/24]

machines:
  anchor:
    at: { segment: hosting, address: [192.0.2.10] }
    inbound: allow
    memory: 3GiB
    cpus: 2

images:
  - postgres:17-alpine
  - cloudamqp/lavinmq:latest
  - mesh-control:development
  # The tool runtime with the audit-logger, built by scripts/build-runtime-image.sh into the local
  # daemon and stocked into the scenario's own registry, which is where the host pulls it from.
  - mesh-runtime-audit:development

place:
  all: [host, runtime]