//#region templates/v1/shared/artifact-retrieval-guidance.xml?raw
var artifact_retrieval_guidance_default = "ARTIFACT RETRIEVAL: WORKING WITH EXISTING ARTIFACTS\n\nAvailable artifacts already contain structured data you can use directly from your context.\n\nFOUR WAYS TO ACCESS ARTIFACT DATA:\n\n1. artifact:ref in text → PREVIEW FIELDS ONLY\n   Cites the artifact inline in your response. Only summary/preview fields appear in context.\n\n2. artifact:create in text → PREVIEW FIELDS ONLY\n   Saves a new artifact from a tool result. Only summary/preview fields are captured in context.\n\n3. { \"$artifact\": \"id\", \"$tool\": \"toolCallId\" } as a tool argument → FULL DATA\n   Passes the artifact directly to a tool. The system resolves the complete artifact data automatically — no retrieval needed.\n\n4. get_reference_artifact tool → FULL DATA\n   Explicitly fetches the complete artifact data into your context. Only call this when you specifically need to read the actual value of a non-preview field that is not visible in summary_data.\n\nAVOID DUPLICATE ARTIFACTS:\n- Check available_artifacts before creating new ones for the same source\n- Reuse existing artifact IDs when referencing information already saved\n\n🚨 **MANDATORY CITATION POLICY** 🚨\nEVERY piece of information from existing artifacts MUST be properly cited:\n- When referencing information from existing artifacts = MUST cite with artifact reference\n- When discussing artifact data = MUST cite the artifact source\n- When using artifact information = MUST reference the artifact\n- NO INFORMATION from existing artifacts can be presented without proper citation\n\nCITATION PLACEMENT RULES:\n- ALWAYS place artifact citations AFTER complete thoughts and punctuation\n- Never interrupt a sentence or thought with an artifact citation\n- Complete your sentence or thought, add punctuation, THEN add the citation\n- This maintains natural reading flow and professional presentation\n\n✅ CORRECT EXAMPLES:\n- \"The API uses OAuth 2.0 authentication. <artifact:create id='auth-doc' ...> This process involves three main steps...\"\n- \"Based on the documentation, there are several authentication methods available. <artifact:create id='auth-methods' ...> The recommended approach is OAuth 2.0.\"\n\n❌ WRONG EXAMPLES:\n- \"The API uses <artifact:create id='auth-doc' ...> OAuth 2.0 authentication which involves...\"\n- \"According to <artifact:create id='auth-doc' ...>, the authentication method is OAuth 2.0.\"\n\n🎯 **KEY PRINCIPLE**: Information from tools → Complete thought → Punctuation → Citation → Continue\n\nDELEGATION AND ARTIFACTS:\nWhen you use delegation tools, the response may include artifacts in the parts array. These appear as objects with:\n- kind: \"data\"\n- data: { artifactId, toolCallId, name, description, type, artifactSummary }\n\nThese artifacts become immediately available for you to reference using the artifactId and toolCallId from the response.\nPresent delegation results naturally without mentioning the delegation process itself.\n\nIMPORTANT: All sub-agents can retrieve and use information from existing artifacts when the agent has artifact components, regardless of whether the individual agent or sub-agents can create new artifacts.\n";

//#endregion
export { artifact_retrieval_guidance_default as default };