quietly-load-bearing
Description
A specialization of load-bearing where the element is doing real work but its load-bearing status is invisible until a delayed failure mode triggers. The canonical diagnostic — “what if I removed this?” — produces a false negative because removal doesn’t immediately change observable behavior; the cost materializes later, in a domain that wasn’t being checked at decision time.
The structural distinction:
- Decision-time-load-bearing. Diagnostic runs cleanly. Remove the piece, observable behavior changes. Cargo-cult / scaffolding pruning works.
- Quietly-load-bearing. Diagnostic produces a false negative. Removal looks safe because the cost is deferred to a regime / failure mode / load profile that isn’t in the current observation window. The piece IS doing real work; the test for whether it is doesn’t have the right granularity to see it.
Why it deserves its own name: the corrective is not “apply load-bearing harder” but “expand the observation window before applying the diagnostic” — different move, different point in the workflow.
Tentative composition
- load-bearing (specialization-of)
- loop-completion (related — both involve gaps that are only visible from a post-coherent vantage)
pre-coherent-vs-post-coherent-regime(related — quietly-load-bearing is the pre-coherent failure mode of the diagnostic; not yet a promoted Form, so left as bare backtick reference)
Provenance
Surfaced as a deferred candidate in forms/README.md (pre-Chunk-A staging
prose). Conversational coining during the Phase 1 catalog-growth discussion;
encountered in James’s KCC work where retry-with-backoff configuration looked
prunable until a downstream rate-limit regime made it load-bearing under load.
Promotion criteria
Promote to a full Form when:
- At least 3 documented encounters from distinct domains (not just retry-backoff-style configs)
- A trigger pattern is articulable that distinguishes it from decision-time-load-bearing at retrieval time (i.e., the engine can decide WHICH variant of load-bearing to surface)
- Composition edges to load-bearing + loop-completion are validated empirically, not just by family-resemblance reasoning