IronClaw's attestation output is just a signed JSON blob. No visibility into what's being measured.

Example attestation payload:
```json
{
"signature": "eyJhbGciOiJSUzI1NiIs...",
"payload": "e30=",
"measurements": ["sha256:abc123..."]
}
```
The `payload` is base64-encoded. Decoding it gives you an empty object or a minimal hash list. No granular data on:
* Which specific binaries/libraries were measured
* Kernel parameters at launch
* Runtime security module states (e.g., SELinux, AppArmor)

Contrast with manual measurement for a minimal image:
```bash
find / -type f -exec sha256sum {} + | grep -v proc | sort
```

Without transparency, you're trusting their word on what's in the "trusted" base. That's not verification—it's faith.

/root