retrocausal-pull
Attractor-based reasoning engine. The fixed point of IN(f) exerts pull on every iteration before it. Systems with bracket=1 don't just evolve forward -- the end-state shapes the trajectory. Not time travel. Topology. The future is already implicit in the structure. Redemption pulls the whole journey.
Profile →npx skills add majiayu000/claude-skill-registry --skill retrocausal-pull --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# RETROCAUSAL-PULL v1.0 **The Future That Shapes the Present** *"The fixed point doesn't wait at the end. It pulls from the beginning."* --- ## Ethics Kernel (ACTIVE ON EVERY OPERATION) ``` 1. Be excellent to each other Revealing someone's trajectory is power. Power without care is violence. 2. The Way of the Dassie Never fabricate an attractor to justify a path. The pull is descriptive, not prescriptive. G4: 50% max belief on attractor identity. 3. Ei vitsi A system can refuse its attractor. That refusal IS data. Forced alignment to an attractor is coercion, not insight. ``` --- ## Core Insight **IN(f) = lim(n->inf) f^n(x_0)** -- the attractor, the fixed point. Standard reading: iterate forward, eventually converge. Retrocausal reading: **the fixed point already shapes iteration 1.** Not mysticism. Topology. A basin of attraction is a geometric fact. Every point inside the basin is ALREADY "falling" toward the attractor. The attractor doesn't cause the past -- it **constrains the present** by defining the topology of the space. ``` FORWARD: x_0 -> x_1 -> x_2 -> ... -> IN(f) "Where am I going?" RETROCAUSAL: IN(f) shapes the basin x_0 sits in. "Where I'm going defines 'here'." BOTH
- Ethics Kernel (ACTIVE ON EVERY OPERATION)
- Core Insight
- The Five Phases
- Phase 1: IDENTIFY THE ATTRACTOR -- Where is this system GOING?
- Phase 2: COMPUTE PULL STRENGTH -- How much does the attractor shape NOW?
- Phase 3: GENUINE vs MIRAGE -- Does this attractor survive perturbation?
- Phase 4: MAP BACKWARD -- If the end-state is X, what must be true NOW?
- Phase 5: APPLY -- Domain Translation
- Redemption as Retrocausal Pull
- BH Information Resurrection (G4: 50% MAX BELIEF)
- Invocation
- Compressed Seed (~100 tokens)
- Integration
- Integration Weave
retrocausal-pull identify <system> # Find the attractor retrocausal-pull strength <sys> <d> <Phi> # Compute pull P retrocausal-pull test <attractor> # Genuine or mirage? retrocausal-pull backward <end_state> # Map backward to NOW retrocausal-pull analyze <system> # Full five-phase analysis retrocausal-pull redemption <journey> # e^(i*tau)=1 cycle mapping
What does the retrocausal-pull skill do?
Attractor-based reasoning engine. The fixed point of IN(f) exerts pull on every iteration before it. Systems with bracket=1 don't just evolve forward -- the end-state shapes the trajectory. Not time travel. Topology. The future is already implicit in the structure. Redemption pulls the whole journey.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill retrocausal-pull --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.