Review and apply LCARS strategy proposals crystallized from observed drift patterns
Review correction strategies that the plugin has crystallized from observed patterns. Proposals are staged for your approval — nothing is auto-applied.
The Foundry observes three signals:
Proposals are staged in ~/.claude/lcars/memory/staged-strategies.json and only applied when you approve them here.
When user runs /lcars:foundry:
python3 ${CLAUDE_PLUGIN_ROOT}/lib/foundry.py --analyze
This scans patterns and outcomes, generates new proposals if warranted, and reports what it found.
python3 ${CLAUDE_PLUGIN_ROOT}/lib/foundry.py --staged
For each proposal, display:
Present the proposals and ask which to apply. Options:
python3 ${CLAUDE_PLUGIN_ROOT}/lib/foundry.py --apply {indices}
Report what was applied: strategies added to corrections.json, version bumped, remaining staged count.
Suppression proposals suggest threshold changes rather than new strategies. Present them as recommendations for /lcars:calibrate rather than applying directly.
The analysis output includes tool_proposals — repeated tool sequences detected in tool-usage.jsonl that could be crystallized into tool-factory tools.
If tool proposals exist, show them from ~/.claude/lcars/memory/staged-tools.json:
python3 -c "import sys, json; sys.path.insert(0, '${CLAUDE_PLUGIN_ROOT}/lib'); from staging import load_staged; print(json.dumps(load_staged(), indent=2))"
For each tool proposal, display:
If user approves a tool proposal:
factory__create_tool via MCP with the tool's name and descriptionpython3 -c "import sys; sys.path.insert(0, '${CLAUDE_PLUGIN_ROOT}/lib'); from staging import mark_registered; mark_registered('TOOL_ID', 'MCP_NAME')"
If no proposals exist and analysis finds nothing new, report:
/lcars:dashboard for current fitness rate