Merge pull request #326 from waku-org/requirements

Introduce Inbound/Outbound Requirements

2025H2-SUMMARY.md

@@ -37,7 +37,7 @@ Strategy changes:
 | [BD - Acquire first 10 customers](draft-roadmap/acquire_first_10_customers.md)                        | Logos Movement Community Enabling: Growth               | 2.1       | 7                   | N/A    |
 
 ✱ Capacity: How many people assigned in a 6 months window.
-- 3.5 are applied across all milestones (Franck, Aaron, 1/2 Hanno, Tanya), 1 core research cc is awol.
+- 3.5 are applied across all milestones (Franck, Aaron, 1/2 Hanno, Tanya), 1 core research cc was awol for 5 weeks.
 
 ## 🧩 Strategic Benefits Realisable from coming Half-Year (Top 5)
 

FURPS/TEMPLATE.md

@@ -20,6 +20,6 @@
 
 1. ...
 
-## + (Privacy, Anonymity, Deployments)
+## + (Privacy, Anonymity, Censorship-Resistance, Deployments)
 
 1. ...

README.md

@@ -2,6 +2,21 @@
 
 *For tracking and project management processes please see* [PROCESS.md](./PROCESS.md)
 
+## Roadmap & Milestones
+
+High Overview of approved milestones and roadmap can be found in https://roadmap.logos.co/waku/waku-milestones.
+Milestones and deliverables can be found in GitHub: https://github.com/waku-org/pm/milestones
+
+More detailed explanation of proposed roadmap can be found in [draft-roadmap](./draft-roadmap/README.md)
+
+- Report for 2025H1 in [2025H1-SUMMARY.md](./2025H1-SUMMARY.md)
+- Milestone proposal for 2025H2 in [2025H2-SUMMARY.md](./2025H2-SUMMARY.md)
+
+Outbound requirements, inbound requirements and Waku's response can be found in [REQUIREMENTS.md](requirements/README.md)
+
+We use the FURPS+ framework to specify software and some non-software requirements.
+Due to the desired properties of our software, `+` is used to express _privacy_, _anonymity_, _censorship-resistance_ and _deployments_ requirements.
+
 ## Weekly Reporting
 
 Weekly reporting provides an insight on the progress by Milestones. Updates are published to https://roadmap.logos.co/tags/waku-updates.

requirements/README.md

@@ -0,0 +1,37 @@
+# Inbound and Outbound Requirements
+
+## Flow
+
+The expected flow (feedback welcome to refine it) is:
+
+1. Project A writes requirements to B (outbound for A, inbound for B) in FURPS+ format.
+2. Project B responds to A's requirements with their own FURPS+ commitments and roadmap,
+   including an overview of which milestones in B's roadmap cover which requirements of A.
+
+Note:
+
+Requirements are negotiable and are stated explicitly to enable said negotiation.
+
+B may not be able to deliver all requirements within a half-year,
+a light justification is needed to explain how do we work towards a requirement.
+For example: "Building block x, y, z are necessary, and they are being worked on with milestones 1, 2, 3.
+
+Some requirements may be "rejected" as not considered in scope of B's work, ensuring that further discussion happen
+and requirements are adjusted.
+
+Finally, B may challenge some requirements, to ensure their are founded, and have been validated by A, through users and community work.
+
+## Inbound to Waku
+
+### Status
+
+TODO: Add link here once Status product document
+
+#### Waku's Response
+
+TODO: Justify here how Status' requirements are being worked towards to with current roadmap.
+
+## Outbound from Waku
+
+- [Status](./status.md)
+- [Codex](./codex.md)

requirements/codex.md

@@ -0,0 +1,3 @@
+# Waku's requirements on Codex
+
+TODO

requirements/status.md

@@ -0,0 +1,3 @@
+# Waku's requirements on Status
+
+TODO: list specific areas of concerns and risks