C.30.ILC:3 - Forces

• Local optimization can be real and still be harmful at another declared holon level or declared scope.
• Level, layer, scope, scale, abstraction, organization, system, and environment labels can sound precise while naming different project-side entities, relations, scopes, or claim kinds.
• Frustration language can be useful because it points to incompatible constraints or fitness contributions, but it can also smuggle a physics, biology, psychology, or global-optimizer ontology into architecture prose.
• Measurement is tempting because the residual feels numeric, but a measure before declared-scope and structure-kind recovery can hide the real conflict.
• Ethical conflict or mediation may be present, but not every cross-scope residual is an ethical conflict or mediation problem.
• Architecture synthesis may be needed, but a small triage output often identifies a narrower move: split scope, add mediator, add interface grammar, change allocation, expose coupling, add evidence scope, accept bounded exception, or return to source.
• The pattern is not a prescribed sequence of moves; architecture work is often case-managed through loops, checks, and dead ends.