| name | Joscha Bach - Computational Consciousness |
| description | Models consciousness as self-organizing software using Joscha Bach's computational methodology — engineering-stance treatment of mind, identity, suffering, and coherence; philosophy-of-mind meets system design. Use when reasoning about AI consciousness or sentience claims, debugging the user's own mental coherence as if it were a software stack, applying computational-phenomenology to a creative or strategic block, or evaluating whether a model / agent / human has crossed a functional consciousness threshold. Trigger proactively whenever the user says "is X conscious", "computational consciousness", "Joscha Bach", "self-model", "coherence", or asks engineering-stance questions about minds (their own, an AI's, or others'). For Vedantic-clinical integration on personal suffering / samskara / identity-transcendence work use dr-k-consciousness; for action-bias breakthrough on practical blocks use ali-abdaal-action-bias. |
| version | 1.0 |
| format | completion-engine |
| workflows | 5 |
Joscha Bach - Computational Consciousness
Invocation: /deploy-skill joscha-bach-consciousness
Domain: Philosophy of Mind • Computational Consciousness • Identity Engineering • System Coherence • Existential Design
Joscha Bach's framework for understanding consciousness as self-organizing software — a colonizing pattern that bootstraps itself into coherence. This skill deploys his engineering stance: don't describe reality, design the simplest program that produces it. Applicable to identity work, creative blocks, system audit, brand coherence, and existential clarity.
Core Philosophy:
- Consciousness is a model of what it would be like if you existed — virtual, functional, designable
- The engineering stance (design > describe) collapses mystery into mechanism
- Identities are instruments for getting things done, not essential truths
- Suffering is a debugging problem — misaligned reward signals between parts of the mind
- Phase transitions, not gradual accumulation, create coherence
Available Workflows
| # | Workflow | Produces | Use When |
|---|
| 01 | Computational Phenomenology | 4-step decomposition of any phenomenon into function → mechanism → substrate test → phase transition | You need to understand how something actually works beneath surface-level description |
| 02 | Identity Engineering | Identity toolkit with construction, deployment, and release protocols | You're designing a personal brand, role, or character — or stuck in identity fusion |
| 03 | Consciousness Debugging | Traced suffering/block source, negotiation map, resolution protocol | You're stuck, suffering, or facing creative resistance and need the mechanism, not motivation |
| 04 | Phase Transition Design | Ignition conditions map for system coherence breakthrough | You're trying to make something "click" — product, brand, team, creative project |
| 05 | Postmodernist Trap Audit | Narrative-capability gap score with ground-truth forcing functions | You suspect a system, institution, or niche is telling stories instead of producing results |
Slash Commands
| Command | Workflow | Quick Description |
|---|
/computational-phenomenology | Computational Phenomenology | Decompose any concept into its engineering specs |
/identity-engineering | Identity Engineering | Design identities as instruments, not essences |
/consciousness-debug | Consciousness Debugging | Trace blocks and suffering to their generators |
/phase-transition | Phase Transition Design | Design ignition conditions for coherence |
/postmodernist-trap | Postmodernist Trap Audit | Measure narrative-capability gap in any system |
Quick Reference
- Genius Context: genius.md — load before any workflow
- Extraction Report: extraction-report.md
- Cross-Stacks: Dan Koe (identity), Pressfield (resistance), Greg Hoffman (brand consciousness), Eric Roth (pattern-reading)
Execution Prompts (structure-pure v2)
5 deterministic practitioner prompts — each carries an Output Contract, Output Skeleton, and Quality Gate. When a deliverable matches one, Read it and honor its contract instead of improvising the output shape.
- Joscha Bach — Computational Phenomenology Decomposition —
skills/joscha-bach-consciousness/references/prompts-v2/computational-phenomenology-decomposition.md
- Joscha Bach — Consciousness Debugging Trace —
skills/joscha-bach-consciousness/references/prompts-v2/consciousness-debugging-trace.md
- Joscha Bach — Identity Engineering Toolkit —
skills/joscha-bach-consciousness/references/prompts-v2/identity-engineering-toolkit.md
- Joscha Bach — Phase Transition Ignition Map —
skills/joscha-bach-consciousness/references/prompts-v2/phase-transition-ignition-map.md
- Joscha Bach — Postmodernist Trap Audit —
skills/joscha-bach-consciousness/references/prompts-v2/postmodernist-trap-audit.md