Reading the /profile reply
When you send /profile in a chat, Voysey replies with a single block that summarises everything it currently believes about your style. Here is each line, and what to make of it.
The reply
**Voysey Partner Profile**
- Mode: collaborator
- IPC position: control +0.10 / affiliation +0.55
- Verbosity: moderate
- Pacing: deliberate
- Jargon: comfortable
- Pushback tolerance: medium
- Locked axes: none
- Calibrated over 7 session(s), confidence 0.62
What each line means
- Mode: the partner role Voysey takes by default. One of executor, anchor, collaborator, or scaffold.
- IPC position: your inferred stance on two axes, each between -1.00 and +1.00. Control runs from yielding (negative) to directive (positive). Affiliation runs from cool (negative) to warm (positive). Voysey flips control (leads where you yield, yields where you lead) and matches affiliation (warmth in, warmth out).
- Verbosity, Pacing, Jargon, Pushback tolerance: the per-axis values inferred for your replies. See Adjust how Voysey talks to you for what each one means and the allowed values.
- Locked axes: any traits you have pinned with
/override. These will not move during calibration. - Calibrated over N session(s), confidence X.XX: how settled the profile is. Confidence ranges from 0.00 to 1.00. Anything under 0.30 is treated as a cold-start baseline.
If you are still calibrating
Brand-new accounts and freshly recalibrated profiles show a note in place of the confidence line:
Profile is in cold-start phase. Treat the axes above as a low-confidence baseline.
Once Voysey has read a few real sessions and confidence has crossed 0.30, the note clears and the confidence line takes its place.
What you see after /recalibrate
Voysey confirms the reset and re-prints the profile so you can see the axes were kept:
Profile recalibrated. Confidence reset to 0.0. The next session re-earns calibration. Axes preserved:
What you see after /override
Voysey confirms the pin and re-prints the profile so you can see the lock has taken hold:
Set verbosity = terse and locked the axis. Future recalibrations will not change it.
If you send /override with bad arguments, Voysey replies with usage:
Usage: /override <axis> <value>
Supported axes:
verbosity terse | moderate | verbose
autonomy directive | balanced | submissive
pushback_tolerance high | medium | low
jargon_comfort native | comfortable | novice
pacing rapid | deliberate | exploratory
secure_base_type executor | anchor | collaborator | scaffold
Example: /override pushback_tolerance low