context-refresh-artifact

To update a single context artifact, you need a defined merge strategy that analyzes new source material and surgically refreshes the target file. This approach modifies one artifact at a time while preserving existing document structure and format conventions.

The best way to maintain a knowledge base without breaking formatting is through atomic context maintenance. This method targets individual artifacts for surgical updates, ensuring the overall knowledge structure remains intact while logging changes with dates and source references.

No, you cannot refresh multiple files simultaneously. This process applies specifically to atomic context maintenance tasks where exactly one artifact is updated at a time, requiring precise analysis of source material to ensure focused changes.

Change tracking works by logging updates with dates, descriptions, and source references during the artifact refresh. This ensures a clear audit trail of what information was modified when integrating new source material into the knowledge base.

Yes, a defined merge strategy is required. To preserve document structure and format conventions while applying new source material, the process demands a precise merge approach to ensure the existing context artifact is updated correctly.

You should use surgical artifact updates when new information, such as product specifications, is released and needs integration into the context core. This ensures the AI has the latest information for decision-making without disrupting unrelated knowledge.