started Agent details for Status

content/roadmap/networking/overview.md

@@ -14,7 +14,7 @@ It is hopeful that Nomos can leverage the work of the Waku project to provide th
 
 ### Scalability Studies
 Currently, the amount of research and analysis of the scalability of Waku is not sufficient to give enough confidence that Waku can serve as the networking layer for the Nomos project. Thusly, it is our effort to push this analysis forward by investigating the various boundaries of scale for Waku. Below is a list of endeavors in this direction which we hope serves the broader community: 
-- [Status' use of Waku study w/ Kurtosis](./status-waku-kurtosis.md)
+- [Status' use of Waku study w/ Kurtosis](roadmap/networking/status-waku-kurtosis.md)
 
 
 

content/roadmap/networking/status-network-agents.md

@@ -8,7 +8,7 @@ tags:
 
 This page creates a model to describe the impact of the various clients within the Status ecosystem by describing their individual contribution to the messages within the Waku network they leverage. 
 
-This model will serve to create a realistic network topology while also informing the appropriate _dimensions of scale_ that are relevant to explore in the [Status Waku Scalability Study](./status-waku-kurtosis.md)
+This model will serve to create a realistic network topology while also informing the appropriate _dimensions of scale_ that are relevant to explore in the [Status Waku scalability study](roadmap/networking/status-waku-kurtosis.md)
 
 Status has three main clients that users interface with (in increasing "network weight" ordering):
 - Status Web
@@ -29,4 +29,23 @@ By describing all `Agents` and their associated feature list, we should be able
 - Estimate how much impact per unit time an individual `Agent` impacts the Status network
 - Create a realistic network topology and usage within a simulation framework (_e.g._ Kurtosis)
 - Facilitate a Status Specification of `Agents`
-- Set an example for future agent based modeling and simulation work for the Waku protocol suite 
+- Set an example for future agent based modeling and simulation work for the Waku protocol suite 
+
+## Status Web
+
+## Status Mobile
+
+## Status Desktop
+Status Desktop serves as the backbone for the Status Network, as the software runs on hardware that is has more available resources, typically has more stable network and robust connections, and generally has a drastically lower churn (or none at all). This results in it running the most Waku protocols for longer periods of time, resulting int he heaviest usage of the Waku network w.r.t. messaging. 
+
+Here is the model breakdown of its usage:
+```
+Status Desktop
+  - Prekey bundle broadcast
+  - Account sync
+  - Historical message melivery
+    - Waku-Relay (answering message queries)
+  - Message propogation
+    - Waku-Relay
+    - Waku-Lightpush (receiving)
+```

content/roadmap/networking/status-waku-kurtosis.md

@@ -6,14 +6,14 @@ tags:
 - "waku"
 ---
 
-[Status](https://status.im) is the largest consumer of the Waku protocol, leveraging it for their entire networking stack. THeir upcoming release of Status Desktop and the associated Communities product will heavily push the limits of what Waku can do. As mentioned in the [Networking Overview](./overview.md) page, rigorous scalability studies have yet to be conducted of Waku (v2). 
+[Status](https://status.im) is the largest consumer of the Waku protocol, leveraging it for their entire networking stack. THeir upcoming release of Status Desktop and the associated Communities product will heavily push the limits of what Waku can do. As mentioned in the [Networking Overview](roadmap/networking/overview.md) page, rigorous scalability studies have yet to be conducted of Waku (v2). 
 
-While these studies most immediately benefit the Status product suite, it behooves the Nomos Project to assist as the lessons learned immediately inform us the limits of what the Waku protocol suite can handle, and how that fits within our [Technical Requirements](../../requirements/overview.md).
+While these studies most immediately benefit the Status product suite, it behooves the Nomos Project to assist as the lessons learned immediately inform us the limits of what the Waku protocol suite can handle, and how that fits within our [Technical Requirements](requirements/overview.md).
 
 This work has been kicked off as a partnership with the [Kurtosis](https://kurtosis.com) distributed systems development platform. It is our hope that the experience and accumen gained during this partnership and study will serve us in the future with respect to Nomos developme, and more broadly, all projects under the Logos Collective. 
 
 As such, here is an overview of the various resources towards this endeavor:
-- [Status Network Agent Breakdown](./status-network-agents.md) - A document that describes the archetypal agents that participate in the Status Network and their associated Waku consumption.
+- [Status Network Agent Breakdown](roadmap/networking/status-network-agents.md) - A document that describes the archetypal agents that participate in the Status Network and their associated Waku consumption.
 - [Wakurtosis repo](https://github.com/logos-co/wakurtosis) - A Kurtosis module to run scalability studies
 - [Waku Topology Test repo](https://github.com/logos-co/Waku-topology-test) - a Python script that facilitates setting up a reasonable network topology for the purpose of injecting the network configuration into the above Kurtosis repo
 - [Initial Vac forum post introducing this work](https://forum.vac.dev/t/waku-v2-scalability-studies/142)