Public, sanitized mirror of an AI orchestration command center: agents, skills, MCP servers, slash-command workflows. All infrastructure identifiers, hostnames, mesh IPs/subnets, repo paths, maintainer identity, and hardware fleet specifics scrubbed to <placeholders>; session debug logs and host-specific memory removed. No live credentials. Verified clean by automated leak sweep. See SANITIZATION.md. churchofmalware.org . authorized research only
3.7 KiB
Voice Summary Template
For Orpheus TTS or similar expressive voice synthesis
Script: {{DECISION_TITLE}}
Opening (Set the stage)
So, here's the situation. {{CONTEXT_BRIEF}}
{{DECISION_QUESTION_SPOKEN}}
The Tension
{{KEY_TENSION_SPOKEN}}
It's not straightforward.
First Principles Reality Check
Let me be honest. {{FIRST_PRINCIPLES_ASSESSMENT}}
The Numbers
Here's what the analysis shows:
{{TIMING_SUMMARY}}
{{OPPORTUNITY_COST_SUMMARY}}
What Could Go Wrong
Now for the uncomfortable part.
{{SCENARIO_WORST_CASE}}
{{SCENARIO_PROBABILITY_SUMMARY}}
The Biases
And here's where I need to be really honest with myself.
{{BIAS_ACKNOWLEDGMENT}}
The Verdict
{{RECOMMENDATION_SPOKEN}}
{{BOUNDARY_STATEMENT}}
{{CLOSING_THOUGHT}}
Orpheus TTS Markup Reference
Emotional Tags
<sigh>— Expressing concern or resignation<chuckle>— Light humor or self-aware moment<whisper>— Emphasis through contrast<excited>— Enthusiasm
Pacing
<pause length="short"/>— Brief beat (0.5s)<pause length="medium"/>— Thinking pause (1s)<pause length="long"/>— Section break (2s)
Emphasis
<emphasis>word</emphasis>— Stress important terms<slow>phrase</slow>— Deliberate pacing for key points
Example Filled Script
Opening
So, here's the situation. Andrew called about joining Synthius, a mental health platform for builders.
Should I commit my time to this right now?
The Tension
The thing is, I'm launching Salience in February. Every hour I give Synthius is an hour not spent on my own launch.
It's not straightforward.
First Principles Reality Check
Let me be honest. I already have Claude Code, my own MCP servers, Obsidian. I can build agent memory myself. Synthius doesn't solve something I genuinely can't do.
The Numbers
Here's what the analysis shows:
If I give three hours a week for six weeks, that's eighteen hours. At my rate, that's about two thousand seven hundred euros worth of time.
That's roughly two Salience course modules I won't be building.
What Could Go Wrong
Now for the uncomfortable part.
In September, Andrew had six to eleven potential co-founders. Now it's just him and Artem. Eighty percent attrition in four months.
The analysis suggests a seventy-five percent probability of zero or negative return.
The Biases
And here's where I need to be really honest with myself.
I'm feeling FOMO. I'm feeling sunk cost from those previous meetings. I'm influenced by the "tier zero point three investors" mention. Classic authority bias.
The Verdict
My recommendation? Observe only.
Take the Monday call. Maximum three hours per week. No builder commitment until Salience launches.
"I'm launching Salience in February. Until then, I can offer maximum three hours per week for observation. If that doesn't work, let's reconnect in March."
Sometimes the best decision is no decision. Yet.
Usage Notes
- Customize placeholders: Replace {{VARIABLE}} with decision-specific content
- Match emotional beats: Place
<sigh>at genuine concern points,<chuckle>for self-awareness - Use pauses strategically: Before key revelations, after heavy information
- Keep it conversational: Write for the ear, not the eye
- Duration target: 2-3 minutes spoken (roughly 350-500 words)