ingenious: Command for Claude Code

C4 Architecture Update

Update the existing hierarchical C4 model based on code changes.

Prerequisites

Existing model in codemap/<system-id>/. If not present, run /viz/c4-map first.

Orchestration

Phase 1: Detect Changes ──> Phase 2: Plan Updates ──> Phase 3: Apply ──> Phase 4: Verify ──> Phase 5: Finalize

Update order:

• Deletions: Code -> Component -> Container -> Context (bottom-up)
• Additions: Context -> Container -> Component -> Code (top-down)
• Modifications: Affected level + adjacent levels

---

Phase 1: Change Detection

Step 1A: Identify System

SYSTEM_ID=$(ls codemap/ | head -1)
echo "System ID: $SYSTEM_ID"
find codemap/$SYSTEM_ID -type f \( -name "*.md" -o -name "*.puml" \) | sort

Step 1B: Analyze Changes

LAST_UPDATE=$(git log -1 --format="%H" -- codemap/)
git diff --name-status $LAST_UPDATE..HEAD -- . ':!codemap' ':!*.md' | head -50

Step 1C: Categorize Changes

Tool: Task
Parameters:
  subagent_type: "Explore"
  description: "Detect C4 changes"
  prompt: |
    Analyze code changes and categorize by C4 level.

    EXISTING HIERARCHY: <from Step 1A>
    CHANGED FILES: <from Step 1B>

    GOALS:
    For each changed file:
    1. Determine C4 LEVEL: CONTEXT|CONTAINER|COMPONENT|CODE
    2. Determine CHANGE TYPE: ADDITION|DELETION|MODIFICATION|RENAME
    3. Identify CASCADE effects (parent/child impacts)

    OUTPUT:
    {
      "SYSTEM_ID": "...",
      "CHANGE_SUMMARY": {counts by level},
      "CHANGES": [<per c4-templates.md#change-detection-schema>],
      "STRUCTURAL_CHANGES": {
        "new_containers": [], "removed_containers": [],
        "new_components": [], "removed_components": [],
        "renamed_elements": []
      }
    }

WAIT for Phase 1 to complete.

---

Phase 2: Impact Analysis

Tool: Task
Parameters:
  subagent_type: "Explore"
  description: "Plan C4 updates"
  model: "haiku"
  prompt: |
    Create update execution plan.

    PHASE 1 OUTPUT: <insert>

    PLANNING RULES:
    1. DELETIONS (bottom-up): code -> component -> container -> context
    2. MODIFICATIONS: affected level + adjacent levels
    3. ADDITIONS (top-down): context -> container -> component -> code
    4. PARALLEL: Same-level operations can run in parallel

    OUTPUT:
    {
      "EXECUTION_PLAN": [
        {"step": N, "phase": "deletion|modification|addition", "depends_on": [], "tasks": [...]}
      ],
      "SUBAGENT_SPAWNS": {"sequential": [], "parallel_safe": []}
    }