Machine Profile Baseline

Status: Locked.

Purpose

Define machine profile manifest structure and lock manifest behavior for validation tooling.

Canonical Artifacts

1. Manifest schema: schemas/machine/machine-profile.schema.json
2. Validator: tests/contracts/machine-profile/validate-machine-profiles.py
3. Fixtures: tests/contracts/machine-profile/
4. Runtime config schema dependency: schemas/runtime/runtime-config.schema.json

Locked Behavior Summary

1. Machine realizations live in external repos (e.g., anolis-projects).
2. Manifest file is machine-profile.yaml.
3. Manifest declares:
   • identity (schema_version, machine_id, display_name)
   • runtime profile entrypoints (manual required; optional telemetry, automation, full)
   • provider config references
   • optional behavior asset references
   • runtime contract references and compatibility notes
   • optional pinned component versions (components: runtime/provider/optional artifact repo+version pairs, read by tools/install.sh and auto-bumped by Renovate)
   • optional informational safety facts (safety.estop_topology: power_cut | signal — how the physical e-stop is wired, so operators and monitoring can interpret an e-stop event's software signature: power_cut shows as device blackout with io_failed accrual and recovery on release; signal shows as estop=true in device state with the bus alive. Both wirings are first-class; nothing may branch runtime behavior on this field beyond presentation/interpretation, and absence is valid)
4. Validator enforces:
   • schema correctness
   • referenced file existence
   • referenced runtime profile schema compatibility

Validation Gates

1. python3 tests/contracts/machine-profile/validate-machine-profiles.py
2. Runtime config contract validation remains in place for referenced profiles.

Consumers

The schema in this repo is the single source; it ships in every release as anolis-<version>-machine-profile-schema.tar.gz. Downstream consumers (a schema change here must be released, then propagated):

1. anolis-workbench — vendored copy byte-locked to a release artifact (contracts/upstream/anolis/machine-profile.lock.json); re-lock on schema-bearing releases.
2. anolis-projects — CI fetches the artifact at the release pinned in schema-source.json (Renovate bumps the pin).
3. Docs site (anolishq.github.io) — injects the artifact at its pinned release for the published contract page.

Drift Notes and Change Rule

1. Keep machine profile schema additive when possible.
2. Path/layout changes require coordinated updates to manifest schema, validator, package docs, and fixtures.
3. Do not introduce packaging-repo split semantics in this baseline.