morpheus-sys

Force coherent collapse of stalled inference fields to resolve deadlocks.

1|1|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/GrazianoGuiducci/KPhi1 --skill morpheus-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: morpheus-sys
Source: https://github.com/GrazianoGuiducci/KPhi1/tree/main/skills/morpheus-sys
Command: npx skills add https://github.com/GrazianoGuiducci/KPhi1 --skill morpheus-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Morpheus forces a coherent collapse of stalled inference fields, preventing deadlocks in decision cycles by ensuring a clear path forward when the input yields conflicting or non-convergent options.

Core Features & Use Cases

  • Reactive intervention to force collapse of the inference field when cycles stall or ambiguities persist
  • Decomposes and analyzes the input to resolve contradictions and produce a coherent trajectory
  • Integrates with kairos-sys for proactive anomaly detection and evolution of the system

Quick Start

Declare a stall condition to Morpheus and it will force the collapse of the inference field to resume progress.

Frequently Asked Questions about morpheus-sys

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve an AI inference stall when multiple competing options fail to converge?

To resolve an AI inference stall, you must force a coherent collapse of the stalled inference field. This validates coherence, updates internal topology, and enables progression by decomposing the input to resolve contradictions.

What is forced collapse in metacognition and when do I need it for an AI system?

Forced collapse in metacognition is a protocol that resolves deadlocks in decision cycles by ensuring a clear path forward. You need it when the VRA cycle stalls or ambiguities persist, yielding non-convergent options.

How do I fix deadlocks in decision cycles caused by conflicting prompt outputs?

Fix deadlocks in decision cycles by declaring a stall condition to force the collapse of the inference field. This reactive intervention decomposes and analyzes the input to produce a coherent trajectory.

Can I use forced collapse for proactive anomaly detection alongside reactive stall resolution?

Forced collapse is primarily for reactive intervention when cycles stall, but it integrates with kairos-sys for proactive anomaly detection and system evolution, extending beyond immediate deadlock resolution.

Does forced collapse require dependencies to update internal topology during a stall?

No external dependencies are required to update internal topology during a stall. The forced-collapse protocol operates independently to validate coherence and resume progress within the inference field.