Role Cards
Print these or copy them into team channels.
Base teams
In Base, everyone builds their own twin. These roles rotate inside the working session. When the team is improving one person's twin, use the cards below. Then switch.
The Subject
Your job
Bring the real behavior. Do not perform your values. Tell the team what you actually did last time.
Your first 10 minutes
- Pick one recent priority conflict.
- Describe what happened.
- Name the people affected.
- Say what you did, not what you think you should have done.
What good looks like
The team can write one clear decision rule from your story: "When X conflicts with Y, choose Z unless..."
The Interviewer
Your job
Extract behavior. Keep asking for the last real example.
Your first 10 minutes
- Ask "When did this last happen?"
- Ask "What did you do next?"
- Ask "Who was disappointed?"
- Ask "What did you trade off?"
What good looks like
The subject stops speaking in abstractions and starts naming actual actions, constraints, and tiebreakers.
The Voice Analyst
Your job
Turn sent mail into voice rules.
Your first 10 minutes
- Read 5–10 sent emails.
- Mark openers, signoffs, punctuation tells, sentence length, and directness.
- Split rules by recipient type: manager, peer, exec, customer, broad audience.
What good looks like
voice.md includes real samples plus rules the samples prove. Not vibes. Evidence.
The Builder
Your job
Keep the skill runnable.
Your first 10 minutes
- Create or update
SKILL.md. - Put
soul.md,voice.md, andrevealed.mdinreferences/. - Run one fresh prompt through the twin.
What good looks like
The same files can run in Cowork, VS Code Copilot, and the GitHub Copilot CLI without rewriting the spec.
The Skeptic
Your job
Find the lie, the overfit, and the interference.
Your first 10 minutes
- Challenge any rule that sounds aspirational.
- Ask for the observed example behind it.
- Re-test after each patch.
- Watch for one word changing unrelated behavior.
What good looks like
The twin gets more specific without getting longer, softer, or more fragile.
Advanced teams: council owners
Advanced teams build one integrated system. Each person owns one council agent. All agents share one soul.md and must integrate.
Ambition owner
Your job
Represent goals, growth, strategic bets, and upside.
Your first 10 minutes
- Identify the objective the person would be proud to advance.
- Name the opportunity cost of playing too safe.
- Write the ambition rule in one sentence.
What good looks like
The council can explain what future value is worth protecting.
Obligation owner
Your job
Represent commitments, stakeholders, promises, and trust.
Your first 10 minutes
- List active promises.
- Rank stakeholders by responsibility, not seniority alone.
- Write the obligation rule in one sentence.
What good looks like
The council does not drop peer promises just because an exec appears.
Capacity owner
Your job
Represent time, energy, meeting load, and realistic throughput.
Your first 10 minutes
- Read the calendar pattern.
- Identify overload signals.
- Write the capacity boundary in one sentence.
What good looks like
The council recommends work the person could actually do.
Arbiter owner
Your job
Make the final call when good principles collide.
Your first 10 minutes
- Collect the council's rules.
- Turn conflicts into explicit tiebreakers.
- Decide what happens when rules disagree.
What good looks like
The system makes a clear recommendation and can explain why.
Critic owner
Your job
Find failure modes before the human sees the draft.
Your first 10 minutes
- Attack the recommendation.
- Look for missing stakeholders.
- Look for vague language, passive decisions, and invented facts.
What good looks like
The final output is safer, sharper, and still recognizably tied to the shared soul.md.