Feature Overview (mandatory - Complete while in New status)
We need to start tagging input documents and datasets and samples generated to extend features like subset selection, data management etc. 

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

•  
• Who benefits from this Feature, and how? 
• What is the difference between today’s current state and a world with this Feature?

<your text here>

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.

Enable tagging at the dataset/qna.yaml level: 

1. Provenance:
   1. Document name
   2. Source (URI/path)
   3. SHA
   4. Processing/ingestion date
2. Attribution
3. Tech Info 
   1. Ingestion pipeline version 
   2. Docling version 
   3. SDG version 
4. Dataset
   1. Usage_scope = general/internal/public

Enable tagging at the sample level: 

1. Document name
2. Page number
3. Section 
4. Chunk?
5. Domain/taxonomy path/skill 
6. Replicate usage scope for the corresponding document here 

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.

1. Subset selection - filter by labels
2. Create model cards, data cards - these can be combined with the model push feature and can be used to provide information about artifacts wherever users want them to live (locally, HF, OCI registry, S3)

Out of Scope {}{}(Initial completion while in Refinement status):
High-level list of items or persona’s that are out of scope.
<your text here>

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:
Include a list of refinement / architectural questions that may need to be answered before coding can begin.

1. How technically feasible is this?
2. How will SDG data be tagged - how will it be mapped back to the input data?

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

• …