self-evolving-is-model-discipline-not-hook-enforced
Claims of ‘self-evolving/self-healing setup’ are aspirational, not mechanically guaranteed. No hook currently forces setup-curator invocation before writing to setup files. A session can bypass the skill entirely and write directly to MEMORY.md or CLAUDE.md without routing checks. The system is skill-aware (via auto-discovery) but not skill-enforced — reliability depends on model discipline and the Stop hook verification gate.
Related
- enterprise-capability-expansion-5-pillars-from-digital-employee-analysis
- stop-hook-forces-pristine-sweep-before-exit
- 2026-04-04-oracle-001-self-architecture-analysis
- stop-hook-blocks-proposals-awaiting-permission
- clawteam-openclaw-multi-agent-swarm-evaluation
- setup-curator-skill-is-the-permanent-routing-guardian
- setup-curator-three-layer-self-maintenance-architecture
- guard-hook-unknown-session-id-cross-session-bypass
- setup-curator-three-layer-enforcement-architecture
- setup-enforcement-triad-three-layer-automation-pattern
- setup-curator-cascade-required-for-new-artifact-categories
- setup-curator-cascade-for-new-memory-category
- stop-hook-blocks-until-brainstorming-workflow-terminal-state
- brainstorming-skill-hard-gate-blocks-stop-without-user-appro
- brainstorming-skill-stop-hook-blocks-incomplete-workflows