Skip to content
HUEHUE Docs

HUE-002 — ADR: choose HUE product boundary, app shell and control-plane stack

Canonical source: docs/roadmap/issues.json · HUE-002

Specification status: TBD · Readiness: agent:ready

Goal

Section titled “Goal”

Decide HUE’s owned personal-workspace boundary and the replaceable relationship to Hermes/OpenCode plus the application shell and control plane.

Scope

Section titled “Scope”
  • Spike Tauri, browser+daemon and existing Hermes WebUI extension packaging paths around the accepted SvelteKit frontend
  • Compare TypeScript, Rust, Python/Hermes-derived and split daemon control-plane options
  • Document HUE ownership of Spaces, Sessions, context packs and task state
  • Document reuse/adapter boundaries for Hermes and OpenCode
  • Honor ADR-0001: SvelteKit + Svelte 5 + shadcn-svelte is fixed; do not reopen React versus Svelte inside the shell decision

Acceptance criteria

Section titled “Acceptance criteria”
  • ADR covers the unresolved packaging portion of TBD-001 plus TBD-002 and TBD-004
  • At least one runnable thin spike per packaging/control-plane finalist
  • Every finalist hosts or serves the accepted SvelteKit frontend without making backend-native session/memory canonical
  • Decision scores recovery, packaging, native integration, reuse, accessibility and contributor ergonomics
  • Consequences and migration path are explicit
  • ADR-0001 and resolved TBD-020 remain authoritative unless a documented revisit trigger fires

Dependencies

Section titled “Dependencies”
  • HUE-001

Non-goals

Section titled “Non-goals”
  • Implement production shell

Product contract

Section titled “Product contract”

Implementation handoff requirements

Section titled “Implementation handoff requirements”
  • Preserve the documented security, project, memory and event boundaries.
  • Add or update automated tests for every observable acceptance criterion.
  • Provide real verification output; do not rely on a worker/agent self-report.
  • Update only the exact documentation sections whose status changed.
  • Include screenshots or a recording for user-interface changes.
  • Include migration, rollback and recovery notes for data/state changes.
  • Link the pull request to this issue with Closes #<issue-number>.