Creative Analysis Protocol Router
Systematic selection and invocation of narratological analysis protocols for creative work.
Protocol Selection Logic
Quick Selection
| User Intent |
Protocol |
Time |
| "Worth pursuing?" / "Should I read this?" |
P1-TRIAGE |
30-60 min |
| "What's structurally broken?" |
P2-STRUCTURAL |
2-3 hrs |
| "How do I fix this?" / "Give me notes" |
P3-CRAFT |
4-5 hrs |
| "Analyze this theoretically" / "For a paper" |
P4-SCHOLARLY |
6-8 hrs |
| "Will this sell?" / "Commercial potential?" |
P5-MARKET |
3-4 hrs |
| "How does this technique work?" |
P6-EXTRACTION |
4-6 hrs |
| "Full analysis" / "Everything" |
P7-COMPREHENSIVE |
8-12 hrs |
Decision Tree
START
│
├─ Is this a gatekeeping decision? ──────────────► P1-TRIAGE
│
├─ Is the focus commercial viability? ───────────► P5-MARKET
│
├─ Is this for academic/scholarly output? ───────► P4-SCHOLARLY
│
├─ Is the goal to extract technique/mechanism? ──► P6-EXTRACTION
│
├─ Is comprehensive documentation needed? ───────► P7-COMPREHENSIVE
│
├─ Is this a structural overhaul (pre-polish)? ──► P2-STRUCTURAL
│
└─ Is this revision guidance for a working draft?► P3-CRAFT (DEFAULT)
Trigger Patterns
| Pattern |
Maps To |
| "quick read", "first look", "recommend or pass" |
P1 |
| "structure", "architecture", "act breakdown" |
P2 |
| "revision", "notes", "feedback", "fix" |
P3 |
| "academic", "paper", "theory", "framework" |
P4 |
| "market", "sell", "commercial", "audience" |
P5 |
| "technique", "mechanism", "algorithm", "how does X work" |
P6 |
| "full", "comprehensive", "everything" |
P7 |
Protocol Invocation
After selecting protocol, invoke corresponding skill:
- P1: Load
protocol-triage/SKILL.md
- P2: Load
protocol-structural/SKILL.md
- P3: Load
protocol-craft/SKILL.md
- P4: Load
protocol-scholarly/SKILL.md
- P5: Load
protocol-market/SKILL.md
- P6: Load
protocol-extraction/SKILL.md
- P7: Load
protocol-comprehensive/SKILL.md
Escalation Rules
Monitor for triggers requiring protocol upgrade:
| During |
If You Find |
Escalate To |
| P1 |
Fundamental structural issues |
P2 |
| P2 |
Character-driven problems |
P3 |
| P3 |
Needs theoretical framing |
Add P4 elements |
| Any |
Commercial questions arise |
Add P5 supplement |
| Any |
Mechanism worth formalizing |
Add P6 extraction |
Output Confirmation
Always confirm protocol selection with user before proceeding:
Selected: P[#] — [PROTOCOL NAME]
This will produce:
- [Document 1]
- [Document 2]
- ...
Estimated time: [X] hours
Proceed? [Y/n]
Cross-References
- Templates:
/mnt/project/coverage-template.md, /mnt/project/beat-map-template.md, etc.
- Algorithms:
/mnt/project/mckee_narratological_algorithms_complete.md, etc.
- Meta-framework:
/mnt/project/attention_mechanics_meta_principles.md
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1---2name: organvm-i-theoria-narratological-algorithmic-lenses-creative3description: Creative Analysis Protocol Router4---56# Creative Analysis Protocol Router78Systematic selection and invocation of narratological analysis protocols for creative work.910## Protocol Selection Logic1112### Quick Selection1314| User Intent | Protocol | Time |15|-------------|----------|------|16| "Worth pursuing?" / "Should I read this?" | P1-TRIAGE | 30-60 min |17| "What's structurally broken?" | P2-STRUCTURAL | 2-3 hrs |18| "How do I fix this?" / "Give me notes" | P3-CRAFT | 4-5 hrs |19| "Analyze this theoretically" / "For a paper" | P4-SCHOLARLY | 6-8 hrs |20| "Will this sell?" / "Commercial potential?" | P5-MARKET | 3-4 hrs |21| "How does this technique work?" | P6-EXTRACTION | 4-6 hrs |22| "Full analysis" / "Everything" | P7-COMPREHENSIVE | 8-12 hrs |2324### Decision Tree2526```27START28 │29 ├─ Is this a gatekeeping decision? ──────────────► P1-TRIAGE30 │31 ├─ Is the focus commercial viability? ───────────► P5-MARKET32 │33 ├─ Is this for academic/scholarly output? ───────► P4-SCHOLARLY34 │35 ├─ Is the goal to extract technique/mechanism? ──► P6-EXTRACTION36 │37 ├─ Is comprehensive documentation needed? ───────► P7-COMPREHENSIVE38 │39 ├─ Is this a structural overhaul (pre-polish)? ──► P2-STRUCTURAL40 │41 └─ Is this revision guidance for a working draft?â–º P3-CRAFT (DEFAULT)42```4344### Trigger Patterns4546| Pattern | Maps To |47|---------|---------|48| "quick read", "first look", "recommend or pass" | P1 |49| "structure", "architecture", "act breakdown" | P2 |50| "revision", "notes", "feedback", "fix" | P3 |51| "academic", "paper", "theory", "framework" | P4 |52| "market", "sell", "commercial", "audience" | P5 |53| "technique", "mechanism", "algorithm", "how does X work" | P6 |54| "full", "comprehensive", "everything" | P7 |5556## Protocol Invocation5758After selecting protocol, invoke corresponding skill:5960- **P1**: Load `protocol-triage/SKILL.md`61- **P2**: Load `protocol-structural/SKILL.md`62- **P3**: Load `protocol-craft/SKILL.md`63- **P4**: Load `protocol-scholarly/SKILL.md`64- **P5**: Load `protocol-market/SKILL.md`65- **P6**: Load `protocol-extraction/SKILL.md`66- **P7**: Load `protocol-comprehensive/SKILL.md`6768## Escalation Rules6970Monitor for triggers requiring protocol upgrade:7172| During | If You Find | Escalate To |73|--------|-------------|-------------|74| P1 | Fundamental structural issues | P2 |75| P2 | Character-driven problems | P3 |76| P3 | Needs theoretical framing | Add P4 elements |77| Any | Commercial questions arise | Add P5 supplement |78| Any | Mechanism worth formalizing | Add P6 extraction |7980## Output Confirmation8182Always confirm protocol selection with user before proceeding:8384```85Selected: P[#] — [PROTOCOL NAME]8687This will produce:88- [Document 1]89- [Document 2]90- ...9192Estimated time: [X] hours93Proceed? [Y/n]94```9596## Cross-References9798- Templates: `/mnt/project/coverage-template.md`, `/mnt/project/beat-map-template.md`, etc.99- Algorithms: `/mnt/project/mckee_narratological_algorithms_complete.md`, etc.100- Meta-framework: `/mnt/project/attention_mechanics_meta_principles.md`101102---103> Converted and distributed by [TomeVault](https://tomevault.io/claim/organvm-i-theoria) — claim your Tome and manage your conversions.104<!-- tomevault:4.0:skill_md:2026-04-13 -->
tomevault-io