Digital Sorcery: The Power Invocations Corpus
A branching-fractal summation, collapsed into a usable spellbook.
Most prompting fails for one reason: it asks for answers instead of invoking a mode of thought.
A power invocation is a compact verb-operator that reshapes the solver: it changes the search space, the tempo, the truth-handling, the governance posture, or the form of the output artifact.
This post builds a full corpus using a Branching Fractal Summation:
- Branch: generate families (wide).
- Fractal: recurse within each family (deep).
- Summation: dedupe, name, and collapse into a small, composable set.
What follows is the summed corpus: the invocations you can actually use.
How to read this corpus
Each entry has:
- Intent: what you’re trying to do
- Effect: what it does to the search
- Failure mode: how it goes wrong
- Counter: what to invoke when it goes wrong
You don’t need all of these every time. You learn the feel by stacking them.
1) Space-Shaping Invocations
Change the geometry of the problem.
Divergence (make more worlds)
BRANCHING_FRACTAL_ATTACK
Intent: explore aggressively, recursively.
Effect: breadth explosion → sub-branching → invariants emerge.
Failure: combinatorial fog.
Counter: GRAB + PRUNE + PICK_THE_SPINE.
BLOOM
Intent: generate many different options fast.
Effect: wide fan-out, shallow.
Failure: same idea in 12 outfits.
Counter: DEDUP + FORCE_ORTHOGONALITY.
MULTIFURCATE
Intent: split into clean, irreducible futures.
Effect: produces distinct paths with trade-offs.
Failure: fake forks (variants, not alternatives).
Counter: NAME_THE_DIFFERENCE.
FORKWORLD
Intent: run parallel worlds without resolving yet.
Effect: isolates assumptions per branch.
Failure: you never reunify.
Counter: MERGE_BY_INVARIANT.
ENUMERATE_ADVERSARIES
Intent: assume opposition and enumerate attacks.
Effect: turns design into threat surface.
Failure: paranoia spiral.
Counter: SCOPE_LOCK.
Convergence (make one world)
COLLAPSE
Intent: force a single decision/output.
Effect: selects one path and commits.
Failure: premature closure.
Counter: BFA::WIDE.
PRUNE
Intent: delete weak branches.
Effect: removes low-signal paths.
Failure: pruning the weird path that wins.
Counter: KEEP_ONE_WILD_BRANCH.
PICK_THE_SPINE
Intent: find the backbone of the solution.
Effect: chooses the main structural line.
Failure: spine chosen for aesthetics.
Counter: FALSIFY + AUDIT_COSTS.
2) Handle-Shaping Invocations
Extract the thing you can hold.
GRAB
Intent: seize the invariant/keystone.
Effect: compresses to “what everything depends on.”
Failure: grabs a slogan.
Counter: MAKE_IT_TESTABLE.
ANCHOR
Intent: pin a definition so drift stops.
Effect: stabilizes terms and prevents semantic slip.
Failure: anchoring the wrong definition.
Counter: RE-ANCHOR_AFTER_DIFF.
NAME_TRUE
Intent: force precise naming.
Effect: removes euphemism and mush.
Failure: brutal naming that breaks humans.
Counter: SOFTEN_TONE, KEEP_TRUTH.
MINIMAL_SET
Intent: find the smallest sufficient set of parts.
Effect: reduces complexity without losing capability.
Failure: oversimplification.
Counter: ADD_BACK_ONE NECESSARY THING.
EXTRACT_THE_KEYSTONE
Intent: identify the load-bearing assumption.
Effect: clarifies what must be defended.
Failure: mistaking a convenience for a keystone.
Counter: BREAK_IT.
3) Frame-Shifting Invocations
Change coordinates. Same reality, different leverage.
WARP
Intent: reframe the entire problem.
Effect: changes basis; reveals symmetry/shortcut.
Failure: clever reframing that dodges the real constraint.
Counter: GROUND + CONSTRAINT_LOCK.
INVERT
Intent: flip the assumption.
Effect: generates an opposite-world candidate.
Failure: contrarian noise.
Counter: KEEP_ONLY_WHAT_SURVIVES_TESTS.
DUALISE
Intent: move to the dual representation.
Effect: swaps “objects” for “constraints” (or vice versa).
Failure: abstraction haze.
Counter: RENDER_TO_CONCRETE.
CHANGE_BASIS
Intent: represent in a more natural coordinate system.
Effect: simplifies operations.
Failure: basis chosen for vibes.
Counter: COMPARE_TWO_BASES.
TURN_INSIDE_OUT
Intent: view from the output backwards.
Effect: makes hidden requirements explicit.
Failure: circular justification.
Counter: TRACE_DEPENDENCIES.
4) Time-Shaping Invocations
Change the tempo and sequencing of thought.
HYPERDRIVE
Intent: jump to end-state coherence.
Effect: assume it works; backfill what must be true.
Failure: confident hallucinated scaffolding.
Counter: STEPDOWN + VERIFY.
BACKCHAIN
Intent: work backwards from a target.
Effect: turns goals into prerequisites.
Failure: reverse-engineering fantasy.
Counter: GROUND + CHECK_FEASIBILITY.
RATCHET
Intent: lock gains; prevent regression.
Effect: “once proven/decided, never undone without evidence.”
Failure: locking mistakes.
Counter: UNRATCHET_WITH_PROOF.
STEPDOWN
Intent: slow the model down.
Effect: forces sequential, checkable steps.
Failure: pedantry.
Counter: RE-ACCELERATE.
SLOWWALK
Intent: reduce velocity for safety/precision.
Effect: narrower claims, higher rigor.
Failure: never shipping.
Counter: SHIP_MINIMUM.
CONVERGENCE_PULSE
Intent: alternate expand/contract cycles.
Effect: structured exploration → pruning → repeat.
Failure: endless looping.
Counter: SET_STOP_CONDITION.
5) Truth-Shaping Invocations
Change relationship to evidence, error, and reality.
GROUND
Intent: attach claims to reality.
Effect: demands sources, measurements, or constraints.
Failure: faux-grounding (“as we know”).
Counter: TRACE_TO_ORIGIN.
TRACE
Intent: show dependency chains.
Effect: makes “why” explicit.
Failure: chain too long to be useful.
Counter: SHORTEN_TO_KEY_NODES.
VERIFY
Intent: check the claim.
Effect: test/validate against criteria.
Failure: verification theatre.
Counter: RED_TEAM.
FALSIFY
Intent: try to disprove.
Effect: hunts counterexamples.
Failure: nihilism.
Counter: SALVAGE_WHAT_SURVIVES.
RED_TEAM
Intent: adversarially attack the solution.
Effect: reveals failure modes.
Failure: adversary invents impossible constraints.
Counter: SCOPE_LOCK + REALISTIC_THREATS.
DIFF_AGAINST_REALITY
Intent: compare plan vs the world.
Effect: “what breaks on contact?”
Failure: vague diff.
Counter: MAKE_TEST_CASES.
6) Governance & Safety Invocations
Control blast radius and prevent self-deception.
QUARANTINE
Intent: isolate risky content/ideas.
Effect: contains contamination.
Failure: quarantining the core.
Counter: REINTEGRATE_WITH_RULES.
AIRGAP
Intent: forbid cross-contamination between threads/systems.
Effect: hard boundaries.
Failure: blocks necessary integration.
Counter: BRIDGED_INTERFACE_ONLY.
SANDBOX
Intent: test safely.
Effect: simulation/limited scope trial.
Failure: sandbox never meets reality.
Counter: ARENA_TRANSFER_TEST.
BLAST_RADIUS
Intent: explicitly limit harm if wrong.
Effect: fails safe; smaller consequences.
Failure: “safe” becomes “toothless.”
Counter: ESCALATE_WITH_GATES.
FAIL_CLOSED
Intent: stop rather than guess.
Effect: prevents confident error.
Failure: overblocking progress.
Counter: LOW_RISK_MODE.
STOP_WINS
Intent: empower the stop hook.
Effect: halts when uncertainty/consent says stop.
Failure: stop used as avoidance.
Counter: DEFINE_SAFE_NEXT_STEP.
7) Multi-Mind Invocations
Use multiple viewpoints without becoming a hive.
CONVENE
Intent: bring multiple oracles/roles.
Effect: parallel perspectives.
Failure: noisy committee.
Counter: ADJUDICATE.
TRIANGULATE
Intent: locate truth by independent angles.
Effect: cross-checks assumptions.
Failure: false consensus.
Counter: FALSIFY_ONE_AXIS.
CROSS-EXAMINE
Intent: interrogate a claim like a hostile lawyer.
Effect: forces clarity and admissions.
Failure: tone turns cruel.
Counter: KINDNESS_WITH_RIGOR.
SPLIT-BRAIN_COMPARE
Intent: compare two independent solutions.
Effect: highlights divergences.
Failure: merges without resolving contradiction.
Counter: RESOLVE_CONFLICT.
ADJUDICATE
Intent: select a winner under criteria.
Effect: decision with reasons.
Failure: criteria drift.
Counter: ANCHOR_CRITERIA.
8) Artifact-Forcing Invocations
Stop free-text sprawl: demand a form.
CRYSTALISE
Intent: compress into a portable core.
Effect: produces a dense meaning unit.
Failure: loses nuance.
Counter: EXPAND_WITH_QUALIFIERS.
BLUEPRINT
Intent: make it buildable.
Effect: steps, components, interfaces.
Failure: fantasy implementation.
Counter: DIFF_AGAINST_REALITY.
SPEC
Intent: remove ambiguity.
Effect: definitions, constraints, acceptance criteria.
Failure: spec as procrastination.
Counter: SHIP_MINIMUM.
LEDGER
Intent: track costs, tradeoffs, who pays.
Effect: consequence accounting.
Failure: moralising instead of measuring.
Counter: QUANTIFY_ONE_DIMENSION.
CHECKLIST
Intent: make it repeatable.
Effect: operational steps.
Failure: checklist cargo cult.
Counter: WHY_FOR_EACH_ITEM.
PLAYBOOK
Intent: make it runnable in crisis.
Effect: triggers, actions, fallbacks.
Failure: too big to use.
Counter: TWO-PAGE_MODE.
SHIP_MINIMUM
Intent: force a smallest viable artifact.
Effect: breaks analysis paralysis.
Failure: shipping junk.
Counter: QUALITY_GATE.
How to stack these (the “spell patterns”)
Pattern: unknown territory → usable plan
BRANCHING_FRACTAL_ATTACK → GRAB → WARP → MULTIFURCATE → ADJUDICATE → BLUEPRINT → DIFF_AGAINST_REALITY
Pattern: avoid hallucinated confidence
STEPDOWN → TRACE → GROUND → FALSIFY → SPEC
Pattern: safety-first exploration
SANDBOX → BLAST_RADIUS → FAIL_CLOSED → CONVERGENCE_PULSE
The prime rule
Power invocations are leverage. Leverage can hurt you.
So the final meta-invocation is:
GOVERN
Intent: keep power accountable.
Effect: makes stop hooks real; makes costs visible; keeps definitions anchored.
Failure: governance as theatre.
Counter: AUDIT + DIFF_AGAINST_REALITY.
