# Count coordination edges before adding a component

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Count coordination edges before adding a component

ID: MHC-D-RESEARCH-9147 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/count-coordination-edges-before-adding-a-component

Every new node can create more interfaces to understand and maintain.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- When a proposed component, workflow or team boundary looks locally clean but adds many new interactions.

### Avoid when

- Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner.

### Explanation

Before adding a component, count required producers, consumers, approvals, observability paths and ownership handoffs. Compare coordination cost with the benefit of separation.

### Checklist

- List new inbound dependencies.
- List new outbound dependencies.
- List new ownership and support interfaces.
- Compare with keeping the capability inside an existing boundary.

### Example

A new microservice removes 200 lines of code but creates six operational interfaces and an on-call dependency; the trade-off is reconsidered.

### Check

The design decision includes coordination edges and lifecycle cost, not only local component size.

### Limits

- Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner.

### Evidence and sources

- contextualizes: Simon described complex systems as often hierarchical and near-decomposable, motivating analysis of relatively strong within-subsystem interactions and weaker cross-subsystem interactions. — RS-6F01EE9805D9E655. Near decomposability is a conceptual property, not evidence that any chosen boundary is correct. (Near-decomposability discussion)
- RS-6F01EE9805D9E655: The Architecture of Complexity — https://www.jstor.org/stable/985254

No review details supplied.
Related (useful_with): https://vedokrok.com/knowledge/test-whether-modularity-actually-localizes-change
