During Phase 6, as cross-domain bridge pages were being built, a reframing happened: psychology and behavioral-mechanics are not adjacent domains that touch the same phenomena from different angles. They are operationalization tiers of the same underlying mechanisms.
Psychology asks: "How does this work internally? What are the mechanisms?" Behavioral-mechanics asks: "How do I operate this externally? What's the performance form?"
But here's the sharp part: The same mechanism at different scales of deployment.
Example: Projection (psychology mechanism) becomes strategic misinformation through deflection (behavioral-mechanics tactic). Not two different things—one thing viewed at two different operational scopes. The psychological mechanism IS the substrate that makes the behavioral tactic possible.
This is different from "psychology informs behavioral-mechanics." It's more like: "Psychology is the mechanism. Behavioral-mechanics is the protocol for running that mechanism consciously."
First wire (obvious): Psychology explains what's happening inside. Behavioral-mechanics explains how to use it outside. Two complementary perspectives.
Second wire (deeper): If behavioral-mechanics is just psychology operationalized, then every behavioral tactic has a psychological prerequisite. You cannot reliably run a behavioral move without understanding the psychology underneath it. Conversely, psychological insight that doesn't translate into behavioral protocol isn't fully understood—you're missing the operational proof. The two domains aren't separate; they're verification tiers.
Third wire (uncomfortable): This means that a practitioner trying to deploy behavioral tactics without understanding the psychological mechanisms underneath is just fumbling with form. They can copy the shape of a move but can't adapt it in novel conditions because they don't understand the generative principle. Conversely, a psychologist who never translates insights into behavioral protocols hasn't actually tested whether their understanding is real or just useful-sounding. Psychology without operationalization is untested theory. Behavioral-mechanics without psychological substrate is mere performance that collapses under stress.
Essay seed: "The Performance Test: Why Every Psychological Insight Must Become a Behavioral Protocol." The piece is that understanding and deployment are not sequential steps—they're mutually verifying. You haven't truly understood a psychological mechanism until you can run it. You haven't truly mastered a behavioral protocol until you understand the psychological mechanism underneath.
Collision candidate (new): "Psychology as Explanation vs. Behavioral-Mechanics as Proof" — the tension is whether psychology requires external operationalization to be considered "understood" or whether understanding can be purely internal. Can a psychologist know something about human mechanisms without ever deploying that knowledge? Is psychology complete as a domain, or is it incomplete without behavioral operationalization?
Concept page candidate: "Operationalization as Verification" — a page explaining how deploying a mechanism tests the completeness of your understanding. If your psychological model breaks under deployment, the model was incomplete. If your behavioral deployment can't adapt when conditions change, you didn't understand the underlying mechanism.
Vault principle candidate: Should domain-index linking create bi-directional references between psychology and behavioral-mechanics pages? Or does that fragment the architecture? This spark suggests the answer is yes—the domains are operationalization tiers, not adjacent territories.