pxpipe/docs/MODEL_RENDER_PROFILES.md

Model render profiles

The endpoint is a wire protocol, not a rendering profile. Claude, GPT, and Grok can all arrive on /v1/responses; pxpipe resolves geometry and vision billing from the model id.

model rule	default	cell	columns	max height	evidence
claude-fable-5*	yes	Spleen 5×8	312	728 px	established Claude suites
gpt-5.6-sol*	opt-in	Spleen 5×8	152	1932 px	98/100 production arithmetic; 83/98 gist
grok-*	opt-in	Spleen 5×8	152	512 px	82/100 arithmetic; 83/98 gist
other GPT/o-series	opt-in	Spleen 5×8	152	1932 px	conservative fallback

Every production path adds IDS rows to the image and an adjacent text factsheet for precision-critical strings. Recent and open protocol state remains native. Those guards reduce exact-string risk; they do not make image reading byte-safe.

Sol and Grok remain opt-in because their broader image-reading results do not match Fable. Enable them explicitly with PXPIPE_MODELS, for example:

PXPIPE_MODELS=claude-fable-5,gpt-5.6-sol

gpt-5.6-terra and other siblings do not inherit the Sol profile or allowlist.

Evidence: Sol results, Grok results.

Overrides

PXPIPE_GPT_PROFILES is a JSON map from model-id prefix to a partial profile. The longest prefix wins. Supported render fields are font, cellWBonus, cellHBonus, aa, grid, gridCols, colorCycle, markerScale, and markerRed; geometry fields are stripCols and maxHeightPx.

PXPIPE_GPT_PROFILES='{"gpt-5.6-sol":{"stripCols":120}}'

The profitability gate uses the same resolved profile as the renderer, so a style or geometry override cannot leave cost prediction on stale dimensions.