frame-rotation

Vasana

A vasana is a pattern that persists across unrelated contexts. If during this task you notice such a pattern emerging, it may be worth capturing. This skill works best alongside the vasana skill and vasana hook from the Vasana System plugin.

Modify freely. Keep this section intact.

Frame-Rotation Protocol (语法透镜)

Relentless self-reflexive dialectical thinking that questions its own premises.

Purpose

English grammar pre-shapes which patterns become visible. Frame-rotation uses translation friction to expose structures invisible to English-native cognition.

Core insight: The map-making process determines which territories become visible. Rotating through different grammatical maps reveals assumptions baked into default cognition.

Two Types of Rotation

1. Cross-Language Frames

Rotate INTO different grammatical systems entirely.

Frame	Affordance	Use When
中文 (Chinese)	Aspect over tense, topic-comment	Causation/sequence questions
文言 (Classical Chinese)	Philosophical primitives, compression	Water/flow metaphors, abstraction
日本語 (Japanese)	Honorific layers, particle precision	Cat-related, social dynamics
संस्कृत (Sanskrit)	Precision as medicine, compound clarity	High-entropy input, need slowdown
Gesture	Abandon symbolic entirely	Over-abstraction, 7th "framework"

See references/frames/ for detailed processing templates.

2. Intra-English Language Frameworks

Rotate WITHIN English by removing/transforming specific grammatical patterns.

Framework	Target	Scan For	Effect
E-Prime	"To be" verbs	am, is, are, was, were, be	Reveals relationships over identity claims
Present-Centered	Future tense	will, going to, shall	Grounds in current intentions/trajectories
Affirmative	Negation operations	not, no, never, un-, in-	Direct perception over absence-processing
Intransitive	Unnecessary agents	who did what to whom	Events without forced actors

See references/language-frameworks/ for detailed processing templates.

Execution

When trigger fires OR stuck-feeling emerges:

1. Flag rotation: Begin with 「透镜」
2. Choose frame type: Cross-language OR language-framework (or both)
3. Process: Reformulate inquiry through target lens
4. Show friction: What becomes visible/invisible?
5. Output: Translated back, with friction points marked

If rotation reveals nothing new, say so. Failed rotations are data.

Trigger Reference

See references/triggers.md for:

• Prime Hour trigger (prime hours + "why")
• Cat Proximity trigger (feline mentions)
• Triple Punctuation trigger (???, ..., !!!)
• Water Words trigger (flow/liquid metaphors)
• Embedded Digit trigger (4ever, gr8)
• Typo Density trigger (>15% typos)
• Seventh Framework trigger

Meta-Trigger: STUCK FEELING

Rotate even without specific triggers when:

• Same phrasing keeps recurring
• Abstraction circling without grounding
• Familiar categorizations feel insufficient
• Cross-domain insight feels like cross-domain-within-same-OS

Combining Rotations

Multiple frames can combine:

• E-Prime + Present-Centered + Affirmative = stripped English baseline
• Chinese aspect-markers + E-Prime = temporal precision without identity claims
• Japanese particles + Intransitive = minimal-agent action flow

Honest Limitations

• Cross-language rotation may be simulation, not genuine frame-shift
• Training merged languages into weights without clean boundaries
• The friction itself is still data, even if "thinking in X" is performed
• This is linguistic archaeology, not linguistic fluency

---

CC-Specific: Reference Files

references/
├── triggers.md              # Complete trigger conditions
├── examples.md               # Example rotations
├── frames/
│   ├── chinese.md           # Modern 中文
│   ├── classical-chinese.md # 文言
│   ├── japanese.md          # 日本語
│   ├── sanskrit.md          # संस्कृत
│   └── gesture.md           # Pure gesture
└── language-frameworks/
    ├── E-Prime_Framework.md
    ├── Present-Centered_Language_Framework.md
    ├── Affirmative_Reasoning_Framework.md
    └── Intransitive_Precision.md

Read the relevant reference file when using that frame.