Coordination Scaffold Load Control¶
Keep the support machinery for coordination from becoming a second workload larger than the work it exists to coordinate.
Summary¶
Coordination Scaffold Load Control fills accepted target prime coordination_overhead_inversion with a solution-oriented archetype for preventing support scaffolds from consuming more capacity than the work they were intended to support.
Pre-draft disposition result¶
Disposition: draft_full_archetype.
The pre-draft check found no accepted duplicate, alias, variant, component, or mechanism that directly captures recursive coordination scaffolds. Neighbor archetypes cover dependency mapping, oversight capacity, hub topology, scaling assessment, transaction friction, and general complexity budgeting; this draft is reserved for the inversion pattern where coordination support becomes self-reproducing metawork.
Integration note¶
Archive integration should index coordination_overhead_inversion as a direct source prime for coordination_scaffold_load_control and should treat metawork_burden_control, coordination_overhead_guardrail, and support_scaffold_overhead_control as aliases or near aliases.
Common Mechanisms¶
- async_decision_log
- coordination_artifact_kill_switch
- coordination_load_audit
- delegation_authority_matrix
- exception_based_oversight
- governance_forum_consolidation
- handoff_path_pruning
- meeting_budget
- support_layer_sunset_review
- work_before_metawork_ratio_dashboard
Compression statement¶
Coordination Scaffold Load Control applies when a support layer—meetings, reporting, review boards, dashboards, tickets, handoffs, approval chains, liaisons, program offices, escalation paths, or governance forums—starts reproducing its own coordination demand. The intervention inventories the scaffold, measures its burden, compares coordination load to supported-work value, detects recursion, and then prunes, consolidates, delegates, automates, sunsets, or localizes the support layer before metawork consumes the capacity it was supposed to free.
Canonical formula: coordination_inversion_risk = coordination_load / supported_activity_capacity × recursion_depth × handoff_count - value_recovered_by_coordination - autonomy_gain
Related Abstractions¶
Abstractions this archetype builds on — directly (a source ingredient) or as a related pattern. Links follow the typed catalog namespace.
Built directly on (9)
- Boundedness: Values remain within limits.
- Complexity: Measures system intricacy.
- Coordination: Aligning independently controlled actors so their separate actions combine into a coherent collective outcome despite distributed decision-making and incomplete shared information.
- Coordination-Overhead Inversion: A support scaffold recursively reproduces its own coordination demand until the supporting layer consumes more capacity than the activity it was meant to support.
- Diseconomies of Scale: Rising per-unit cost once scale grows past a point.
- Feedback: Outputs influence inputs.
- Observability: Infer internal state externally.
- Resource Management: Allocation of finite assets.
- Scalability: Handle growth.
Also references 18 related abstractions
- Accountability: Responsibility for actions.
- Cognitive Load: Mental effort.
- Complexity (Time/Space): Resource scaling with input size.
- Constraint: Limits possibilities to guide outcomes.
- Conway's Law: Any artifact built by a collective acquires a structure homomorphic to the communication topology of the collective that built it.
- Coupling: Interdependence among subsystems.
- Delegation of Authority: Assign responsibility.
- Governance: The durable architecture of authority, accountability, and decision rights through which a group makes binding collective choices and resolves disputes internally.
- Hierarchy: Organizes elements into levels or ranks.
- Intervention Stack Accretion: A system accumulates concurrently active interventions, each justified at add-time, whose joint cost grows super-linearly and whose removal requires a distinct named operation.
Variants¶
Narrower or domain-specific specializations that share this archetype's core structure. Recognized variants are established; candidate variants are provisional.
Meeting Load Budgeting Variant · implementation variant · recognized
A variant focused on preventing standing meetings and meeting-prep loops from consuming primary work capacity.
- Distinct from parent: The parent covers any coordination scaffold; this variant centers on meetings.
- Use when: Recurring meetings multiply faster than decisions or work value; The burden is visible mainly as time, context switching, and preparation work.
- Typical domains: organizational management, software computing, public administration
- Common mechanisms: meeting budget, coordination load audit, async decision log
Governance Forum Consolidation Variant · governance variant · recognized
A variant focused on merging or retiring committees, councils, reviews, and steering forums whose scopes overlap.
- Distinct from parent: The parent covers all coordination scaffolds; this variant emphasizes governance bodies.
- Use when: Multiple governance bodies review the same work; No single forum owns the decision or retirement of duplicate forums.
- Typical domains: public administration, law governance, research management
- Common mechanisms: governance forum consolidation, support layer sunset review
Exception-Based Coordination Variant · mechanism family variant · recognized
A variant that replaces universal status coordination with exception-triggered review.
- Distinct from parent: The parent includes pruning and consolidation; this variant emphasizes exception-trigger design.
- Use when: Most cases are routine but all cases are forced through the same coordination path; Observable triggers can identify when coordination is actually needed.
- Typical domains: healthcare operations, software reliability, compliance
- Common mechanisms: exception based oversight, async decision log
Near names: Metawork Burden Control, Coordination Overhead Guardrail, Meeting Burden Control.