remember

To log methodology friction in a SWARM vault, trigger the capture skill using specific phrases indicating a correction or friction. It records operational divergences and process mistakes, ensuring the system continuously learns and improves from the event.

Capturing operational learnings addresses rule zero by using methodology notes as the system's specification. Recording process deviations and corrections ensures continuous learning, preventing recurring mistakes like generating claims without proper run provenance.

You need to record a methodology correction when the system's actions are incorrect or when a better approach is discovered. It triggers on specific phrases to document unexpected behaviors, process mistakes, and better ways to perform tasks.

Yes, you can use this methodology capture approach to document better ways to perform tasks or cross-link information. It specifically records discoveries of improved operational procedures and cross-links them within the SWARM vault.

The best way to ensure learning from incorrectly assigned confidence is to log the process mistake using the capture skill. This records the correction, specifying that statistical backing is required, which updates the methodology notes.