monthlies final (almost)

content/codex/monthly-reports/2023-sept.md

@@ -1,6 +1,6 @@
 ---
 title: 2023 September Codex Monthly Report
-draft: true
+draft: false
 lastmod: 2023-09-18
 ---
 

content/nomos/monthly-reports/2023-sept.md

@@ -1,10 +1,15 @@
 ---
 title: 2023 September Nomos Monthly Report
-draft: true
+draft: false
 lastmod: 2023-09-27
 ---
 
 ## Executive Summary
+The Nomos team continues to stay focused on research related to the fine-grained details of the Base Layer specification and implementation. The addition of a Project Manager is expected to not only expedite the research by allowing the lead to dive deeper into the issues involved but also make that work and progress more transparent. 
+
+Mehmet joins the team next month to fulfill a long needed dedicated role in research privacy and zero-knowledge technology as it pertains to the Nomos requirements. 
+
+The whitepapers plan to be polished and published by early next month which not only details the current specifications but also known problems that need to be solved. 
 
 ## Key Updates
 
@@ -48,8 +53,6 @@ A PoC/Draft Testnet was created and merged via Docker-Compose, then general expl
 
 Simulations of the branch overlay with 1 committee was conducted. Initial results discovered a bug  in reproducibility that was fixed. Additional simulations resulted in discovery of inter-module errors with the leader selection. This is currently being explored along with integration of mixnet developments. 
 
-NEED ESTIMATION OF TIMING HERE
-
 #### Private PoS
 Research was conducted in a variety of areas around a Private Proof of Stake spec relevant to the architecture of Nomos. All details can be found in the Whitepaper descriptions. 
 
@@ -89,5 +92,6 @@ Next month focuses on finalizing and publishing:
 
 Weekly updates referenced
 - [[nomos/updates/2023-09-04|2023-09-04]]
+- [[nomos/updates/2023-09-11|2023-09-11]]
 - [[nomos/updates/2023-09-19|2023-09-19]]
 - [[nomos/updates/2023-09-26|2023-09-26]]

content/waku/monthly-reports/2023-sept.md

@@ -2,8 +2,6 @@
 title: 2023 - September Monthly Waku Report
 draft: true
 ---
->[!note] This is the inaugural monthly report for Waku, and as such is just a start to a much more detailed and larger report in the future. We are still in the process of honing in on the reporting and subsequent insight process that stems from project planning and development
-
 ## Executive Summary
 
 
@@ -15,7 +13,11 @@ draft: true
 	- 
 
 ### Milestones
-A lot of work has been put into coalescing and finalizing the development tracking process that is in line with the Insight Reporting requirements, and Aaron's addition to the team this month as pushed it over the edge to completion. Much of this has gone into automating the weekly reporting process via Github labels and comments on issues. It is expected that next month it will be finalized and ready for review by other teams to see if they'd like to adopt it. 
+A lot of work has been put into coalescing and finalizing the development tracking process that is in line with the Insight Reporting requirements, and Aaron's addition to the team this month as pushed it over the edge to completion. Much of this has gone into automating the weekly reporting process via Github labels and comments on issues. 
+
+For tracking Waku maintains these Milestones in the `waku-org/pm` repo. Within each milestone description, you'll find the corresponding Epics. Every Epic is distinctly labeled, and this label is affixed to each issue associated with that particular Epic. The labels are managed by the `labels.yaml` file located in the `waku-org/pm` repo. 
+
+Given the expansive nature of Waku and its various repositories working towards the milestones, the labels established in the `labels.yaml` file are replicated across each respective `waku-org/pm` repo. This structure allows for seamless navigation, starting from top-level milestones down to the most granular issues.
 
 Waku is broken out into the following four Milestones, with Epics associated with them:
 - `Waku Network Gen0`
@@ -64,16 +66,21 @@ Much of the work this month was fleshing out the available REST APIs of `nwaku`.
 
 ## Perceived Changes in Project Risk
 - Richard doing most integration of waku into status-go
-	- C-bindings in Nim is a lot of effort and has large unknowns
-		- this effort doesn't progress on the rest of the roadmap
-- waku network mvp target being tracked well
+- There effort to convert `nwaku` to the main native integration client requires a large effort in the implementations of C-bindings in Nim and has some unknowns associated with it. Furthermore this additional effort and uncertainty doesn't directly contribute to the current critical path of development. 
+- The first main application of the milestone reorganization within the project has made the milestones associated with it clear, thus allowing the Waku Network MVP target setup to be tracked well
 - status remaining items
 	- postgres integration (should have been finished)
 	- fleet setup (lack of infra resources, not entirely on them though)
 	- 10k node simulations by DST 
 
 ## Future Improvement Plans
+### Insight
+The insight team plans to further evaluate the value the reporting process implemented by Waku as it pertains to use within the other projects under Logos. It is expected that next month it will be finalized and ready for review by other teams to see if they'd like to adopt it. 
 
+One side effect of the automated reporting process is that the associate issue labels are already compatible with our data lake ingestion that was initiated by the Status project. This will allow us to create more useful dashboards and monitoring that take into account accurate development activity. 
+
+### Project
+As the milestones continue to be fleshed out and detailed, the ability to show progress over time will improve. 
 
 ## Sources and Useful Links
 Weekly Reports