pub struct TranscriptSettings {
pub max_view_bytes: usize,
pub step_bytes: usize,
pub max_section_messages: usize,
pub max_block_bytes: usize,
}Expand description
The view’s settings.
Fields§
§max_view_bytes: usizeThe byte budget a request’s messages aim for. The transcript engages only past it — below, requests pass through byte-identical — and the current turn may exceed it: the tail is never cut.
step_bytes: usizeThe bytes one section’s messages aim for: the summarizer worker’s input bound, and the granularity compaction works at. A section carries at least one message whatever this says.
max_section_messages: usizeThe messages one section covers at most. Bounds the extractive stand-in’s lossiness: each section’s digest is a few hundred bytes, so this caps how much history one line may paper over when no model fill is configured.
max_block_bytes: usizeThe bytes the committed block may reach before the oldest sections consolidate into one. Consolidation rewrites the block — a full cache break — so it fires only past this cap, and merges down to half of it before stopping.