# Feature coverage

| Capability | Dashboard | CLI | Verified |
|---|---:|---:|---:|
| Encode/decode FLEXON v2 | Yes | Yes | Yes |
| None/GZip/Deflate/Brotli | Yes | Yes | Yes |
| AES-256-GCM encryption | Yes | Yes | Yes |
| ChaCha20-Poly1305 encryption | Yes | Yes | Yes |
| PBKDF2-SHA256 control | Yes | Yes | Yes |
| Header/hash/preview inspection | Yes | Yes | Yes |
| JSON Schema validation | Yes | Yes | Yes |
| ECDSA P-256 key generation | Yes | Yes | Yes |
| Detached sign/verify | Yes | Yes | Yes |
| Tamper rejection | Yes | Yes | Yes |
| JSON plus multiple binary bundle | Yes | Yes | Yes |
| `flexon-bundle/1` Explicit attachments | Yes | Yes | Yes |
| Deterministic `$flexonFile` Marked mode | Yes | Yes | Yes |
| Safe reference Discover / `--resolve-files` | Yes | Yes | Yes |
| Repeated logical-path attachments | Yes | Yes | Yes |
| Base-directory containment | Yes | Yes | Yes |
| Per-attachment byte limits | Yes | Yes | Yes |
| Dry-run resolution and hashing | Yes | Yes | Yes |
| Nested safe extraction | Yes | Yes | Yes |
| Path, length, media type, and SHA-256 proof | Yes | Yes | Yes |
| Nine use-case scenario gallery | Yes | Not applicable | Visual smoke tested |
| Truthful operation-stage narrator | Yes | Structured CLI output | Sequence acceptance tested |
| Core-independent bundle adapter | Yes | Yes | Build verified |
| Batch processing | Yes | Yes | Yes |
| Measured benchmarks | Yes | Yes | Yes |
| Inventory/history | Yes | Yes | Yes |
| Unattended monitor | Settings | Yes | Yes |
| Tray/OSD/Resource Pet | Yes | Not applicable | Visual smoke tested |

The Flexon 3.1 acceptance suite exercised Explicit, Marked, and Discover modes with two native binary payloads plus JSON and confirmed byte-for-byte recovery. It also proved dry-run behavior, nested containment, attachment limits, overwrite protection, tamper rejection, and the ordered narrator stages for reference scanning, attachment hashing, compression, encryption, atomic writing, extraction, and SHA-256 verification. The dashboard reports only measured files and recorded operations. It does not invent sensor values, package counts, benchmark throughput, or AI capability.
