# Hermes Architecture Deltas Workorder Index

Status: ready for implementation planning. These documents are workorders only; they do not claim the features are implemented.

Source baseline:
- Omnius repository: `/home/robit/Documents/repositories/open-agents-1`
- Hermes comparison checkout: `/home/robit/Documents/repositories/hermes-agent`
- Hermes commit inspected: `6f6eb871d83415fe2980f3483cc41a435ba22196`
- Hermes version inspected: `0.15.1`
- AIWG framing used: `sdlc/architecture-evolution`, `sdlc/flow-handoff-checklist`, `sdlc/flow-requirements-evolution`

## Feature Workorders

| Folder | Workorder | Purpose | Current State |
| --- | --- | --- | --- |
| `01-public-scrutiny-provenance-control/` | [WORKORDER.md](01-public-scrutiny-provenance-control/WORKORDER.md) | Runtime public Telegram scrutiny modes with human and agent-controlled provenance escalation. | Planned |
| `02-context-engine-plugin-boundary/` | [WORKORDER.md](02-context-engine-plugin-boundary/WORKORDER.md) | Extract context assembly, compaction, and evidence framing behind a pluggable context engine boundary. | Planned |
| `03-typed-gateway-event-stream/` | [WORKORDER.md](03-typed-gateway-event-stream/WORKORDER.md) | Separate runner facts from Telegram/TUI rendering through typed events and adapter dispatch. | Planned |
| `04-task-local-gateway-context/` | [WORKORDER.md](04-task-local-gateway-context/WORKORDER.md) | Add task-local gateway/session context using `AsyncLocalStorage` to prevent cross-chat and cross-run bleed. | Planned |
| `05-process-lifecycle-monitoring-notifications/` | [WORKORDER.md](05-process-lifecycle-monitoring-notifications/WORKORDER.md) | Keep Omnius's lease registry as authority and add watcher, adoption, notification, and legacy kill-path cleanup. | Planned |
| `06-vision-evidence-routing-ladder/` | [WORKORDER.md](06-vision-evidence-routing-ladder/WORKORDER.md) | Route visual evidence from cheap observation to OCR to auxiliary vision based on request-derived information need. | Planned |
| `07-durable-multi-agent-kanban/` | [WORKORDER.md](07-durable-multi-agent-kanban/WORKORDER.md) | Add durable, inspectable work boards for long admin tasks and disputed public factual work. | Planned |
| `08-completion-critic-reconciliation-ledger/` | [WORKORDER.md](08-completion-critic-reconciliation-ledger/WORKORDER.md) | Turn completion review into a durable claim/evidence ledger with critic reconciliation packets. | Planned |

## Carryover Rules

- Do not encode scenario-specific phrase filters as completion or scrutiny logic.
- Any escalation or completion gate must be driven by the current request, proposed claims, observed tool results, and explicit human or agent-declared state.
- Keep public Telegram bounded by default; strict review modes must be intentional, reversible, and time-limited.
- Never let a renderer label backend `incomplete_verification` as completed.
- Never authorize process termination from command-name matching alone; lease ownership and identity verification remain mandatory.

## Global Completion Metrics

- Every feature folder has an `INDEX.md` and `WORKORDER.md`.
- Every workorder names code anchors in Omnius and Hermes.
- Every workorder includes phases, file-by-file implementation notes, tests, rollout controls, and measurable completion criteria.
- A future agent can update progress checkboxes without rereading this chat.