{'fraction_non_alphanumeric': 0.030215827338129497, 'fraction_numerical': 0.0, 'mean_word_length': 5.327272727272727, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Patterns of self-management

Although each application of self-management techniques encounters problems and solutions unique to the application domain, there are several cross-cutting "patterns of self-management" that can be discerned. Much like programming patterns, these patterns can occur in a variety of different guises, but having a fundamental set of such patterns can be useful for designers beginning to design a self-managed system or to those adapting a system not previously capable of managing itself. Herein I sketch some of these patterns using an "architectural style" designed to express common element types used for self-management, such as probes, gauges, and "effectors."