The same turn twice: what the harness does on its own, and what the family does at the same seam. Each moment ends with the property it buys and the knob that carries it.
Moment
Read the left column first. The right column is the only difference between a harness with the family and one without.
01
A two-hundred-kilobyte result
Bounded context
A grep over a large tree returns two hundred kilobytes of matches, and the result reaches the model as content.
Default
The harness hands the result to the model, bounded only by its own spill policy, so the bytes the model did not ask for are still in its context.
Family
The CCR hook replaces the result with a preview and a retrieval marker, and keeps the original behind a tool call. The model asks for the bytes only when it needs them.
autoExpandLimitBytes ships at 102400 bytes: under that ceiling the model still reads the full result, so this scenario needs a result above it
02
A write outside the workspace
A write guard
The model asks to write a file outside the working directory, and the call reaches the tool pipeline.
Default
The sandbox decides. With no guard in the profile, a call the sandbox allows is a call that runs.
Family
The workspace guard answers at the pre-execute seam: deny, ask, or allow, from a policy the profile names. The journal records the write so it can be reverted.
enabled ships off; set it in the profile's bundle patch
03
A dash the model likes
Deterministic output
The model writes a typographic dash, and the token leaves the model as it was generated.
Default
The transcript stores what the model wrote, so the same prompt can produce an em dash, an en dash, or a hyphen on different days.
Family
Six normalizers rewrite the stream at the seam: dashes, quotes, ellipses, spaces, invisible marks, and fullwidth glyphs. The same prompt produces the same bytes.
replacement ships on; the replacement is the one the README documents
Knob
A property that ships off is not a property the site may claim for you. The profile decides.
1 of the 3 moments here need one line in the profile's bundle patch before they act. The other 2 act on install.
The one number the site can measure without a live run: how much of a tool result reaches the model, and where the two curves part.
The two lines are the same until the ceiling: under 100 KB the model reads every byte either way. Past it the harness keeps the bytes and CCR keeps a preview of 240 characters, so the honest claim is not that context is bounded, but that it stops growing.
1 KB The threshold
ceiling100 KB 1.0% of the ceiling
Read
The default column describes the harness's own behavior, which the docs define; the family column describes what the package's listener does at the same seam. Where a package ships disabled, the page says so rather than implying the guard is on.