.cursor/skills/evolution-cascade-validation/SKILL.md
Validates the evolution cascade executes atomically when personality changes. Use when modifying personality evolution, quantum state updates, knot calculations, or any service in the cascade chain. Ensures consistent state observations for the world model.
npx skillsauth add avra-cadavra/avrai evolution-cascade-validationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
When personality evolves, ALL downstream systems must update atomically before the next state snapshot is captured. A partially updated state vector is worse than a stale one -- it's internally inconsistent.
PersonalityChange
→ QuantumVibeEngine.recompile() // 24D quantum vibe state
→ PersonalityKnotService.recompute() // 5-10D knot invariants
→ KnotFabricService.updateInvariants() // 5-10D fabric invariants
→ WorldsheetEvolutionDynamics.step() // 5D worldsheet trajectory
→ KnotEvolutionStringService.updateRates() // 5D string evolution rates
→ DecoherenceTrackingService.updatePhase() // 5D decoherence features
→ WorldModelFeatureExtractor.captureFullSnapshot() // Full state vector
The world model's perception module must produce a single coherent state representation. If personality evolves but quantum vibe state, knot invariants, fabric metrics, worldsheet trajectory, string evolution rates, and decoherence phase don't cascade-update, the state encoder receives an internally inconsistent observation. The energy function and transition predictor would be trained on corrupted data.
/// UnifiedEvolutionOrchestrator handles the cascade
Future<void> _handlePersonalityEvolution(PersonalityDelta delta) async {
// ALL steps must complete before state snapshot
await _quantumVibeEngine.recompile(delta);
await _personalityKnotService.recompute(delta);
await _knotFabricService.updateInvariants(delta);
await _worldsheetDynamics.step(delta);
await _knotEvolutionString.updateRates(delta);
await _decoherenceTracking.updatePhase(delta);
// Only NOW capture state snapshot for episodic memory
final stateSnapshot = await _featureExtractor.captureFullSnapshot();
developer.log('Evolution cascade complete', name: 'EvolutionOrchestrator');
}
You MUST verify the cascade works when:
PersonalityLearning or ContinuousLearningSystemWorldModelFeatureExtractorUnifiedEvolutionOrchestrator cycleUnifiedEvolutionOrchestrator quantum coordination method is a placeholder (log-only)UnifiedEvolutionOrchestrator AI2AI learning coordination is a placeholderUnifiedEvolutionOrchestrator continuous learning coordination is a placeholderKnotEvolutionCoordinatorService)AtomicClockService timestamp on snapshotdocs/MASTER_PLAN.md Phase 7.1.2 (Evolution cascade fix)docs/MASTER_PLAN.md Phase 7.4 (Dependency chain management)lib/core/ai/unified_evolution_orchestrator.dart - Current implementationlib/core/ai/quantum/quantum_vibe_engine.dart - Quantum steppackages/avrai_knot/ - Knot, fabric, worldsheet, string stepsdevelopment
--- name: world-model-development description: Guides world model development patterns: state/action encoders, ONNX inference, feature extraction pipeline, latency budgets. Use when implementing world model components, state encoders, action encoders, feature extractors, or ONNX models. Core skill for Phases 3-6. --- # World Model Development Patterns ## Core Principle All world model components follow LeCun's autonomous machine intelligence framework. State observations flow through a percep
tools
Implements base workflow controller patterns for multi-step processes. Use when creating complex workflows that require orchestration of multiple steps with error handling and rollback.
testing
--- name: widget-test-patterns description: Guides widget test patterns: BLoC testing, user interactions, state changes, material app setup. Use when writing widget tests, testing UI components, or validating widget behavior. --- # Widget Test Patterns ## Core Pattern Widget tests verify UI behavior: user interactions, state changes, and visual display. ## Basic Widget Test Setup ```dart testWidgets('widget displays correctly', (WidgetTester tester) async { // Arrange: Create widget awa
testing
--- name: test-template-generation description: Generates test templates: unit, widget, integration, service tests following project patterns. Use when creating new tests or ensuring tests follow project standards. --- # Test Template Generation ## Available Templates Test templates are located in `test/templates/`: - `unit_test_template.dart` - `widget_test_template.dart` - `integration_test_template.dart` - `service_test_template.dart` ## Unit Test Template ```dart /// SPOTS Component Uni