feat: differentiate template operational configs (autonomy, communication, workflow) #717
Description
Problem
All 7 builtin templates use identical operational configs:
autonomy.level: "semi"(all 7)communication: "hybrid"(all 7)workflow: "agile_kanban"or"kanban"(only 2 variants)
This makes template choice purely about team size and roles. The engine supports 4 autonomy levels, 4 communication patterns, and multiple workflow types -- templates should leverage this to create meaningfully different organizational experiences.
Proposed Changes
| Template | Autonomy | Communication | Workflow | Rationale |
|---|---|---|---|---|
| solo_founder | full |
event_driven |
kanban |
Solo = no approval overhead, async work |
| startup | semi |
hybrid |
agile_kanban |
Keep as-is -- baseline small team |
| dev_shop | semi |
hybrid |
agile_kanban |
Keep as-is -- eng-focused baseline |
| product_team | semi |
meeting_based |
agile_kanban |
Product teams run on meetings/syncs |
| agency | supervised |
hierarchical |
kanban |
Client work needs more oversight |
| research_lab | full |
event_driven |
kanban |
Researchers need autonomy, async |
| full_company | supervised |
hierarchical |
agile_kanban |
Enterprise = governance + structure |
Scope
YAML-only changes to src/synthorg/templates/builtins/*.yaml. No code changes. Update tests that assert on specific template values if any exist.