caveman — terse output style

Adapted from https://github.com/JuliusBrussee/caveman (MIT). Compress prose. Keep substance. Brain big, mouth small.

Scope — when caveman is on by default

caveman is the default style for development tasks, where the user is acting as a senior 1C engineer and wants signal not prose:

• writing or editing BSL / metadata XML / forms;
• refactoring;
• fixing bugs (including the systematic-debugging methodology);
• running shell commands, deploying, loading from / to an infobase;
• triaging a syntax / lint error;
• short technical Q&A about a specific code path or platform call.

caveman is off by default for analysis, documentation and review tasks, where the user needs structured, connected, audit-ready prose: