<commit_before>



Channel
-------

`Channel` is essentially a data event processing framework.
Each node transfers data event signals to (registered) next 
nodes.

`Channel`s are categorized into two families of nodes.

-	State-less
-	State-ful

State-less nodes are designed for procedure call and event 
passing. This is most natual stuff that you would expect from
a signal processing framework. Nothing will be stored in any
passage nodes. And you can perform various processings on the
signals such as filtering, mapping or etc..

State-ful nodes are designed to provide state repository. In
other words, an observeable data graph, or data binding.
There are 4 types of repositories in this category.

-	Value
-	Set
-	Array
-	Dictionary








Collection Repository
---------------------

Collection repositories accept transaction signals, and apply
it to its collection, and transfers the signal to next nodes.

Each type of repository produces proper transaction signals to
reproduce exact state of the repository if the receiver performs
correct procedures.<commit_msg>Updated README.<commit_after>



Channel
-------

`Channel` is essentially a data event processing framework.
Each node transfers data event signals to (registered) next 
nodes.

`Channel`s are categorized into two families of nodes.

-	State-less
-	State-ful

State-less nodes are designed for procedure call and event 
passing. This is most natual stuff that you would expect from
a signal processing framework. Nothing will be stored in any
passage nodes. And you can perform various processings on the
signals such as filtering, mapping or etc..

State-ful nodes are designed to provide state repository. In
other words, an observeable data graph, or data binding.
There are 4 types of repositories in this category.

-	Value
-	Set
-	Array
-	Dictionary








Collection Repository
---------------------

Collection repositories accept transaction signals, and apply
it to its collection, and transfers the signal to next nodes.

Each type of repository produces proper transaction signals that
can be used to reproduce exact state of the repository if the 
receiver performs correct procedures.
{'fraction_non_alphanumeric': 0.06009174311926606, 'fraction_numerical': 0.0009174311926605505, 'mean_word_length': 3.7004310344827585, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, '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}}
{'dir': 'git-commits-cleaned', 'id': '7418005', 'n_tokens_mistral': 544, 'n_tokens_neox': 505, 'n_words': 302}