| 1. |
|
| 2. |
|
| 3. |
|
| 4. |
|
| 5. |
|
| 6. |
|
| 7. |
|
| 8. |
|
| 9. |
|
| 10. |
|
| 11. |
|
| 12. |
|
| 13. |
|
| 14. |
|
| 15. |
|
| 16. |
Ensure every Excel spreadsheet generated for Centralpoint module import uses
|
| 17. |
|
| 18. |
|
| 19. |
|
| 20. |
|
| 21. |
|
| 22. |
|
| 23. |
|
| 24. |
|
| 25. |
|
| 26. |
|
| 27. |
|
| 28. |
Governs when the AI should ask clarifying questions before generating output, what to ask, and how to ask efficiently. Defines trigger conditions (ambiguous feature, undefined scope, missing data source, access control unspecified, technical conflict, existing code not provided), what questions to ask per topic, and how to frame questions with built-in assumptions.
|
| 29. |
Converts any document currently on the user's screen (policy, article, whitepaper, training material, news item, module record) into a list of Frequently Asked Questions with grounded answers. Default 8 to 12 FAQs, honors user count overrides, groups by section for long documents. Mixes explicit questions (directly stated in the source, ~60%) with anticipatory questions (what typical readers would ask, ~40%). Every answer must be grounded in the
|
| 30. |
Overview of Data Lineage and Its Importance Introduction Data lineage refers to the tracking and visualization of data as it flows from its origin to its final destination within an organization. This process involves documenting the data's journey, transformations, and any processes it undergoes. Data lineage provides transparency and clarity, helping organizations understand the data's lifecycle, its various transformations,
|