{'fraction_non_alphanumeric': 0.03471295060080107, 'fraction_numerical': 0.0, 'mean_word_length': 4.813953488372093, '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}}
Software architecture of the challenge propagation model

I focus on two special requirements for the simulation model: Ability to observe global and local behaviour (“micro/macro-scope”). This means that we should be able to observe in real time (i.e. during the simulation) or subsequently analyze every chosen component of the network. A component of the network could be a challenge, a situation, an agent, a link, or a combination of these. From the software architecture point of view this implies that we should have the ability to access each component of the model as a separate object. Ability to observe and analyze the dynamics of the network development (“life-logging”). Running the simulation with certain parameters for the predeter-