-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
[Lightspeed] "Deep Context" Retrieval - Backend Implementation
-
False
-
-
False
-
To Do
-
RHDHPLAN-849 - [Lightspeed] Spike: Technical Feasibility for Lightspeed "Deep Context" Awareness (Docked & Overlay Modes)
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
100% To Do, 0% In Progress, 0% Done
-
-
EPIC Goal
The EPIC simply takes it where the research EPIC (https://issues.redhat.com/browse/RHIDP-11549) end. That said we are looking into a PoC backend implementation for the "Deep Context" Retrieval feature.
The EPIC is scoping on the backend side, and it covers the following:
1. The implementation of the PoC
2. Provide metrics from different models and software.
Background/Feature Origin
This is the implementation phase for the Deep Context Retrieval functionality as defined here: https://issues.redhat.com/browse/RHDHPLAN-849
Why is this important?
The implementation will help the stakeholders understand the value of this feature.
User Scenarios
N/A
Dependencies (internal and external)
There's a dependency with https://issues.redhat.com/browse/RHIDP-11549 (investigation)
Acceptance Criteria
- A PoC has been created and shared with the rest of the team.
- All necessary metrcis have been shared too
Release Enablement/Demo - Provide necessary release enablement details
and documents
DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub
Issue>
DEV - Downstream build attached to advisory: <link to errata>
QE - Test plans in Playwright: <link or reference to playwright>
QE - Automated tests merged: <link or reference to automated tests>
DOC - Downstream documentation merged: <link to meaningful PR>
- depends on
-
RHIDP-11549 [Lightspeed] "Deep Context" Retrieval - Research Phase
-
- New
-