QConsul LLC — a certified Oregon Benefit Company. Portland, Oregon, USA.
Token Minimalism at Fleet Scale — knowing when not to compress
Case study of a July 2026 fleet-wide token-minimalism pass across five governed repositories. Fleet linting plus registry reconciliation, with every finding staged through Compress, Relocate, or Reorganize-only — never assumed in advance — under an append-only audit-trail policy and HITL logging.
Published July 24, 2026 · by Karen Michael, Founder, QConsul LLC.
Results by category
- Duplicated procedural boilerplate (11-file corpus): -48%.
- Oversized single-agent definition: -78%.
- Registry-to-filesystem drift: -62%.
- Duplicate-content audit hypothesis: validated as already clean upstream.
- Untracked binary weight: -100% (14.1 MB removed from version control).
- Legitimate audit trail (77 files): 0% reduction — reorganized into typed subfolders with an index, by design.
Frequently asked questions
What is fleet linting?
Fleet linting is automated detection of duplicated content, oversized artifacts, registry-to-filesystem drift, and untracked binary weight across a governed multi-repository agent fleet. QConsul's pass used 20-35 word block scans, paragraph-boundary splitting, and cross-referenced findings against the central skill/agent registry.
Why refuse to compress a 77-file archive?
Because it was a three-generation append-only audit trail required for governance lineage. Compression would have destroyed regulatory-relevant history. The correct staged decision was Reorganize-only: typed subfolders with an index, keeping the trail intact. Knowing when not to compress is the finding.