diff --git a/README.md b/README.md
index 8f5825f..932a3fe 100644
--- a/README.md
+++ b/README.md
@@ -8,6 +8,7 @@ We can benefit from innovations that others may share with us! -- algorithms, da
 We have a potential audience for our contributions -- we may be heard and can receive feedback
 Networking can help us handle more demand for our services
 than we can provide with a single node, or even with all the nodes we can muster!
+Or similarly, to perform more computations in a given amount of time!
 
 How can we structure the application?
 ---
@@ -54,3 +55,27 @@ I think this base layer of rhizome nodes should integrate into the storage, comp
 Services can interface with the rhizome layer; the rhizome network may be used to support other functionality.
 The service may also perform some rhizome network function, perhaps indirectly supporting other services.
 
+# Algorithms
+
+Multi-party
+Informed by peer model
+
+JSON-Logic can encode condition expressions.
+It can also encode transformations, or other operations.
+
+Composable, functional units -- no side-effects (need to think about data structures for this)
+
+Algorithms encode rules for decisions. When executed, these decisions can lead to actions.
+
+Provenance is a fundamental consideration in this system.
+We don't need to require certainty. Instead, we can quantify our uncertainty.
+
+An example algorithm would be one for identity.
+An algorithm for performing a query.
+An algorithm for operating a service cluster; let's say a web service.
+
+Context roots, being UUIDs, are the initial point of coordination with regard to domain entities.
+But also, provenance is indeed a fundamental consideration, and as such,
+the context is marshalled by applying a filter to a set of deltas, which may filter based on creator and host.
+Decisions about such filtering depends on the node's view of its peers.
+