
# Baseline Gap Report

The baseline supplies useful interface and mission-loop references but cannot prove the resident target operational. Hermes must implement and verify authentication, server persistence, migrations, data admission, purpose-bound scopes, partition isolation, ATTEND receipts and invalidation, exact catalogs, source records, consent memory, one-run agents, genuine streaming/cancellation, diagnostics, backup/restore/update/rollback/removal/uninstall, accessibility, and executable tests.

The ROUNDS sources are written programs. Their 17 “schemas” are logical names, not JSON Schema implementations. They provide no local app runtime, SQLite store, stable PWR/WF/TPL/AGT IDs, EDENA, machine data classes, four-level capability model, streaming UI, or full-stack verifier. Every such asset in this build layer is labeled implementation-generated.

Canonical checks remain 160 unique rows from the dedicated release-assurance file. The duplicate `A2` label in foundation prose and repeated embedded checkboxes in the one-file program are not additional tests. The old 57/57 package validator proves source/package structure only, not runtime execution.
