Skip to content
HUEHUE Docs

HUE-047 — Implement authoritative-source bindings and staleness-aware projections

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

Specification status: TBI · Readiness: agent:ready

Goal

Section titled “Goal”

Keep GitHub, Calendar, email and user files authoritative while giving HUE normalized, freshness-aware control surfaces.

Scope

Section titled “Scope”
  • Implement generic SourceBinding/SourceRecord contract
  • Build read-only GitHub issue/PR projection first
  • Store native IDs, locator, version/etag and freshness
  • Define conflict and explicit writeback path
  • Add source health UI/events

Acceptance criteria

Section titled “Acceptance criteria”
  • GitHub remains source of truth for issue/PR
  • Stale projection is never presented as current
  • Readback precedes consequential mutation
  • Conflict becomes explicit state
  • Connector can be replaced without rewriting Space/Session records

Dependencies

Section titled “Dependencies”
  • HUE-003
  • HUE-009

Non-goals

Section titled “Non-goals”
  • Mirror complete external datasets
  • Implement Calendar/email writeback in first slice

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>.