بنقرة واحدة
loop-documentation
SOP for documenting a feedback loop — classify, describe dynamics, identify break points.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
SOP for documenting a feedback loop — classify, describe dynamics, identify break points.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
SOP for detecting and resolving concept aliases — merge duplicate pages, redirect edges.
SOP for creating a claim page in the vault — atomic proposition with type classification, source attribution, and initial confidence.
SOP for creating a new concept page with proper frontmatter, content, and initial edges.
SOP for flagging contradictions in the causal model — identify conflicting evidence or mechanism claims.
SOP for creating a dimension page — documents an axis of variation with its values and semantics.
SOP for creating multiple edges in a batch — efficient bulk relationship creation.
| name | loop-documentation |
| description | SOP for documenting a feedback loop — classify, describe dynamics, identify break points. |
| execution | sop |
| used-by | feedback-loop-detection |
Document an identified feedback loop in the causal graph.
CC file write + vault_add_edge
relations/<loop-slug>.md with frontmatter (type: relation, tags: [feedback-loop])[[dir/slug]] pointing to the target variable (dir/slug = target path minus .md). Place inline where the variable is mentioned. Skip if already present.Returns: { path: string, loop_type: string, variables: string[], break_points: string[] }