distilled-caveman-lite-accuracy

To compress technical responses without losing accuracy, use a lite mode that removes pleasantries and filler while preserving exact code, commands, paths, URLs, and versions. An accuracy gate checks for lost conditions or scope to ensure meaning remains intact.

Shortening incident triage explanations safely requires a safety fallback that switches to fuller wording for destructive actions, auth, crypto, or secrets. This prevents misunderstandings while applying lite compression to standard technical details.

Response compression does not affect bug root-cause analysis details when an accuracy gate enforces exact preservation of qualifiers, exceptions, ordering, and versions. It removes filler but keeps truth-affecting constraints and necessary grammar.

You can use lite compression for workflow and configuration explanations by asking for lite mode. It removes filler while keeping required identifiers, formatting, and safety-relevant context intact for accurate technical communication.

You should not use lite compression when dealing with destructive, auth, crypto, secrets, or compliance situations. The safety fallback automatically switches to fuller wording in these high-stakes cases where compression could cause misunderstanding.