contrib-consolidate · git:20260731.937a638 · 2026-07-31 · sha256 38c074ea92a95fc6
contrib-consolidate git:20260731.937a638A
Immutable. This exact content is served forever at /api/v1/blob/38c074ea92a95fc6.
---
name: contrib-consolidate
description: Internal phase — consolidate a contributor's L1 atoms into an L3 persona (11 dimensions). Invoked by contrib-profile / `/contrib build`.
user-invocable: false
---
# Contributor Consolidate
Group one subject's L1 atoms into themes (L2 scenes, conceptual) and write a
single L3 persona summarising all 11 dimensions with evidence.
## Workflow
### 1. Read the atoms
```bash
tmem contrib atoms <subject-id>
```
### 2. Build the persona
**Read `references/persona-guide.md` first** — it covers merging atoms (not
listing), resolving conflicting atoms, weighting by evidence, when to mark
"insufficient data", and the quality bar (a persona should predict how the
subject tackles a *new* task).
For each of the 11 dimensions (`idea, plan, solve, craft, comms, mentor,
conflict, scope, ownership, execution`), synthesise the atoms in that dimension
into 1–3 sentences. Carry the strongest evidence links into the text. If a
dimension has no atoms, set it to `"insufficient data"`.
Collect 3–6 `notable_traits` — distinctive things that don't fit a fixed
dimension (e.g. "writes prose-quality commit bodies", "prefers small composable
modules").
### 3. Write the persona
```bash
tmem contrib upsert-persona --json '{
"subject_id": "<id>",
"summary": "<2-3 sentence overview of how this engineer works>",
"dimensions": {
"idea": "...", "plan": "...", "solve": "...", "craft": "...",
"comms": "...", "mentor": "...", "conflict": "...",
"scope": "...", "ownership": "...", "execution": "..."
},
"notable_traits": ["...", "..."],
"updated_time": "<ISO timestamp>"
}'
```
### 4. Report
Print the persona (`tmem contrib persona <id>`) and tell the user which
dimensions are well-evidenced vs "insufficient data".