# Eve / Hermes fusion scope — 2026-09

**Task:** 7.1<br /> **Machine record:**
[`eve-sota-hermes-fusion-scope/2026-09-09.json`](eve-sota-hermes-fusion-scope/2026-09-09.json)<br />
**Schema:**
[`eve-sota-hermes-fusion-scope.schema.json`](eve-sota-hermes-fusion-scope.schema.json)<br />
**Verifier:**
[`../../tools/eve-everywhere/verify-hermes-fusion-scope.mjs`](../../tools/eve-everywhere/verify-hermes-fusion-scope.mjs)

## Correct boundary

Hermes construction is complete in its bounded checklist: **23/23 checked, 0
open**. The implemented composition root includes real tools, Postgres
conversation memory, autonomous scheduling, Voyager-style skills, multi-channel
adapters, SSH/Modal/Singularity execution backends, and governed isolated
subagents.

That result is not Eve fusion. The production census finds 1 direct
`@oshun/assistant` package importer and 0 consumer of the assembled
`createAssistant()` entrypoint. The sole package consumer reuses
`createAssistantProvider` for the V10 Ori narrator; it does not assemble the
Hermes runtime. Eve's eval directory likewise has 0 package import and 0
reference to a Hermes runtime/scheduler/skill/channel entrypoint.

## Remaining fusion work

| Surface                | Current source-derived status                                   | Owning tasks           |
| ---------------------- | --------------------------------------------------------------- | ---------------------- |
| Eve measurement        | `not-wired`                                                     | `7.2`                  |
| Product runtime wiring | `provider-factory-reuse-only-is-not-assembled-assistant-fusion` | `7.2`, `7.4`, `7.8`    |
| Watchers               | `not-wired`                                                     | `7.3`, `7.4`, `7.5`    |
| Skill doctrine         | `unreconciled`                                                  | `7.6`                  |
| Semantic recall        | `not-present-behind-conversation-memory`                        | `3.7`, `7.7`, `9.4`    |
| Live channels          | `not-admitted`                                                  | `7.8`                  |
| Evaluation admission   | `remaining`                                                     | `12.7`                 |
| Security admission     | `remaining`                                                     | `4.8`                  |
| Operations admission   | `remaining`                                                     | `13.7`                 |
| Privacy admission      | `remaining`                                                     | `14.7`                 |
| Protocol integration   | `remaining`                                                     | `16.1`, `16.5`, `16.7` |

The existing scheduler is substrate for watcher work, not a watcher product
surface: the census finds 0 product scheduler consumer and 0 typed watcher tool
definition. The two skill systems remain distinct, and no ADR currently mentions
both `@oshun/assistant` and `@oshun/skill-system`. `ConversationMemory` exposes
history append/load only; semantic/vector recall remains explicitly deferred and
must reuse the governed embedding and memory policies.

Channel adapters exist for discord, email, signal, slack, telegram, but no
product channel runner is wired, no operator choice is recorded, and the
Security gate continues to assign live-channel admission to Task 7.8.

## Recorded infrastructure blockers

- **signal-live-channel:** signal-cli is absent and no dedicated registrable
  Signal number is available. Unblock: Provision signal-cli, a dedicated
  registered number, credentials and the Task 7.8 operator-selected live-channel
  gate.
- **singularity-live-exec:** Neither Apptainer nor Singularity is installed on
  the recorded compatible Linux host. Unblock: Provision Apptainer or
  Singularity on a compatible Linux execution host and run the live backend
  proof.

## What this closes

Task 7.1 closes the accuracy of the construction-versus-fusion boundary only. It
does not close Phase 7 or G3/G11–G18. No live runtime, model, channel, vector
store, container, security gate, privacy gate, operations gate, or protocol
admission is claimed here.

## Limitations

- This is a source-inspection and static-contract result. It does not prove live
  assistant, watcher, channel, vector-store, container, provider, security,
  privacy, protocol, or operational behavior.
- The 23/23 result means the bounded Hermes construction checklist is checked in
  full; it does not mean the assembled runtime is wired into Eve or covered by
  Eve measurement.
- The V10 Ori runtime reuses createAssistantProvider only. Provider-factory
  reuse is not evidence that createAssistant, its tools, schedules, skills,
  memory, subagents, or channels are fused into the product plane.
- Signal remains blocked on signal-cli plus a dedicated registered number and
  live-channel admission. Singularity remains blocked on a compatible host with
  an installed Apptainer/Singularity runtime and live proof.
- Task 7.1 closes only the accuracy of the recorded boundary. Phase 7 and every
  referenced gap remain open for the named owner tasks and later evaluation,
  security, operations, privacy, and protocol gates.