feat: do cleanup

Signed-off-by: kjuulh <contact@kjuulh.io>

README.md

@@ -34,4 +34,17 @@ Data enteres nodata
 3. Data is sent to a topic
 4. A broadcast is sent that said topic was updated with a given offset
 5. A client can consume from said topic, given a topic and id
+// 6. We need a partition in here to separate handling between partitions and consumer groups
 6. A queue is running consuming each broadcast message, assigning jobs for each consumer group to delegate messages
+
+## Components
+
+A component is a consumer on a set topic, it will either act as a source, sink or a tranformation between topics. It can declare topics, use topics, transform data and much more.
+
+A topic at its most basic is a computational unit implementing a certain interface, source, sink, transformation. 
+
+The most simple is a source and sink, where we respectively push or pull data from the topics.
+
+### What does it look like
+
+As part of nodata, you'll be given nodata the cli. The cli can bootstrap a variety of components,