Feature Overview (mandatory - Complete while in New status)

At the end of 1.4, SDG and RAG will need to pass input documents through docling to transform them into jsonl files. However, SDG uses docling v2 - hierarchical chunking. RAG uses docling v3 to leverage hybrid chunking. In 1.5, SDG plans on moving to docling v3 and leverage the hybrid chunking capabilities. Since ingestion will now be a part of the Core, there will be work required to update the version of docling the SDG library calls and unify the ingestion process for both SDG and RAG.

Goals (mandatory - Complete while in New status)
Provide high-level goal statement, providing user context and expected user outcome(s) for this Feature

• Build a singular ingestion pipeline that allows both the SDG and RAG libraries to call docling and get the desired output. At the end of this phase, both libraries will still need to do their own pre-processing.

Requirements (mandatory -_ Complete while in Refinement status):
A list of specific needs, capabilities, or objectives that a Feature must deliver to satisfy the Feature. Some requirements will be flagged as MVP. If an MVP gets shifted, the Feature shifts. If a non MVP requirement slips, it does not shift the feature.

Done - Acceptance Criteria (mandatory - Complete while in Refinement status):
Acceptance Criteria articulates and defines the value proposition - what is required to meet the goal and intent of this Feature. The Acceptance Criteria provides a detailed definition of scope and the expected outcomes - from a users point of view
…
<your text here>

Use Cases - i.e. User Experience & Workflow: (Initial completion while in Refinement status):
Include use case diagrams, main success scenarios, alternative flow scenarios.
<your text here>

Out of Scope _{}(Initial completion while in Refinement status):{_}
High-level list of items or persona’s that are out of scope

1. Pre-processing data for both libraries 

Documentation . Considerations _{}(Initial completion while in Refinement status):{_}

Provide information that needs to be considered and planned so that documentation will meet customer needs. If the feature extends existing functionality, provide a link to its current documentation..
<your text here>

Questions to Answer _{}(Initial completion while in Refinement status):{_}
Include a list of refinement / architectural questions that may need to be answered before coding can begin.
<your text here>

Background and Strategic Fit (Initial completion while in Refinement status):
Provide any additional context is needed to frame the feature.
<your text here>

Customer Considerations _{}(Initial completion while in Refinement status):{_}
Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.
<your text here>

Team Sign Off (Completion while in Planning status)

• All required Epics (known at the time) are linked to the this Feature
• All required Stories, Tasks (known at the time) for the most immediate Epics have been created and estimated
• Add - Reviewers name, Team Name
• Acceptance == Feature as “Ready” - well understood and scope is clear - Acceptance Criteria (scope) is elaborated, well defined, and understood
• Note: Only set FixVersion/s: on a Feature if the delivery team agrees they have the capacity and have committed that capability for that milestone

• …