| name | chase-hughes-context-engineering |
| description | The Context Engineering Operating System — Chase Hughes's behavioral-influence architecture for designing the CONTEXT where a desired behavior becomes automatic, instead of pushing the outcome. Built on PCP (Perception → Context → Permission) and the one inversion "engineer conditions, not outcomes; build the perfect recipient first." Covers the macro layer the conversational-influence skill excluded — PCP/upstream design, the FEAR brainwashing formula + fractionation, the five trust factors / followability, contagious confidence, the benevolent SMRP honesty protocol, the Behavior Suite (change-cluster-context reading), threat detection (COPE), the emotional-debt substrate, and manipulation DEFENSE. Every offensive mechanic ships with its detection tell + resistance move + ethical deployment (Hughes's Plato's-Cave ethic), and all /ce-* output passes a deterministic Defense/Ethics Gate. Use when the user says "context engineering", "engineer the conditions", "make the behavior automatic", "what's upstream of the outcome", "design the context so they…", "build the perfect recipient", "Chase Hughes", "PCP", "followability", "read this person/transcript/pitch", "is this manipulation", "am I being manipulated", or wants to design an offer/funnel/launch/onboarding where the action feels self-chosen. Standalone operating layer (/ce-design, /ce-build) AND a Chain Step-3.5 front-end that hands a Context-Design Spec to a production expert. Dual-use, uncensored mechanics with defense baked in. |
| domain | Context engineering × Behavioral influence × Brainwashing architecture × Interrogation × Behavioral reading × Cognitive defense |
| expert | Chase Hughes |
| version | 1 |
| extraction_tier | Deep |
| source | YouTube — Modern Wisdom (Chris Williamson × Chase Hughes), 23,512 words |
| extracted | "2026-05-30T00:00:00.000Z" |
| companion | chase-hughes-conversational-influence |
| ethics_gate | execution/context_ethics_gate.py (deterministic backstop, wired into chain_runner finalize Step 11.9) |
Chase Hughes — Context Engineering
The operating layer for the one inversion underneath all of Chase Hughes's work: stop engineering outcomes — engineer the context where the outcome is inevitable. Behavior is downstream of permission, permission of context/category, context of perception (the PCP formula). The amateur reaches for a script or a close; if you are good, what you engineer are conditions, and you build the perfect recipient first so the behavior falls out for free and feels self-chosen. The planning verb is always "what is upstream of the thing I want?" and its sharp form "what context makes the behavior I want automatic?"
This skill turns that inversion into a deployable system — for marketing, content, offers, leadership, coaching, self-change, and cognitive defense.
Two modes. Design (/ce-design, /ce-pcp, …) produces the context spec and hands off. Production (/ce-write, /ce-offer) fuses the psychology with the craft experts and produces finished, publishable work across seven verticals — social, content, media, storytelling, marketing, copywriting, ghostwriting — plus rebuilds weak offers. Both pass the deterministic ethics gate, so finished output is also defensible.
Source Note + The Two-Skill Stack (Honest Scope)
This is the methodology-rich companion the original Hughes extraction (chase-hughes-conversational-influence, from the Unlearn podcast) explicitly deferred — it flagged that the Behavior Suite, brainwashing, and interrogation work needed "a separate extract on a methodology-rich source." This is that extract, from a 23,512-word Modern Wisdom appearance.
| Skill | Layer | Source |
|---|
chase-hughes-conversational-influence | Line-level moves (5): engineered self-conclusion, archetype priming, empathy ladder, two-ideas detection, camera-angle | Unlearn podcast |
chase-hughes-context-engineering (this) | Macro architecture: PCP/context engineering, FEAR/fractionation, followability, SMRP, Behavior Suite, COPE, emotional debt, defense | Modern Wisdom |
PCP sets the macro-context; engineered-self-conclusion is the line-level move inside it. No overlap. Stack both when a deliverable needs the architecture and the craft.
