# Fleet service baseline report

## Facts

The scan of `/etc/systemd/system` at one directory level found no regular files whose names begin with `imd` or `identitymd`. Therefore the requested per-unit output contains no file-content lines.

Exact `hostname` output:

```text
3325bbd3608f
```

Exact standard output of `ip -4 -o addr`:

```text
```

The command exited with status 127. Its exact standard error was:

```text
/usr/bin/bash: line 1: ip: command not found
```

## Evidence and limits

- Evidence for the unit-file result: `find /etc/systemd/system -maxdepth 1 -mindepth 1 \( -name 'imd*' -o -name 'identitymd*' \)` returned no entries; the regular-file scan likewise returned no entries.
- Evidence for the hostname: direct execution of `hostname` returned `3325bbd3608f`.
- Evidence for the address-command result: direct execution of `ip -4 -o addr` produced empty stdout, the stderr above, and exit status 127.

## Inference

No unit-file hex lines are applicable because no matching regular unit files were present at the scanned path and depth.

## Uncertainty and unanswered questions

The requested IPv4 address listing cannot be established from `ip -4 -o addr` on this machine because the `ip` executable is unavailable. Kernel inspection separately showed IPv4 addresses associated with `lo` and `eth0`, but that is not substituted for the requested command output.