From e276089b0cceab2557f9e501f1d869cee870effd Mon Sep 17 00:00:00 2001
From: Jazz Turner-Baggs <473256+jazzz@users.noreply.github.com>
Date: Thu, 24 Jul 2025 17:12:21 -0700
Subject: [PATCH] Initial core dump

---
 requirements/status.md | 69 +++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 68 insertions(+), 1 deletion(-)

diff --git a/requirements/status.md b/requirements/status.md
index c3eef5c..2a5c38e 100644
--- a/requirements/status.md
+++ b/requirements/status.md
@@ -1,3 +1,70 @@
 # Waku's requirements on Status
 
-TODO: list specific areas of concerns and risks
\ No newline at end of file
+## Minimal Test UI
+
+Chat SDK needs an slimmed down version of Status to perform testing. 
+
+Features such as Wallet, Communities, etc, can add complexity and noise to the testing process. 
+To test the ChatSDK effectively a version of the Status application which only implements the required features for private chat are needed.
+
+### Functionality
+
+1. Ability to create Identity
+1. Create new conversations from introduction
+1. View Conversations
+
+1. Ability to send messages 
+1. Ability to receive messages automatically in the background
+1. Notifications are posted when receiving new messages.
+
+### Usability
+
+### Reliability
+
+### Performance
+
+### Supportability
+
+**+ (Privacy, Anonymity, Censorship-Resistance, Deployments)**
+
+## Migration Preparation
+
+To complete ChatSDK integration without issues, Status needs to prepare the existing code base. 
+Focus is on creating abstractions and planning for breaking changes.
+
+The ChatSDK takes a different approach to managaging conversations, and is incompatible with the existing application. To smooth the integration process starting on these adaptations now, provides the fastest integration possible.
+
+### Functionality
+
+1. Isolate chat internals from application so they can be replaced effectively. 
+1. Stored user level conversations are isolated/inpedendant from the transport used.
+1. Add facade to isolate dependency on Waku.
+
+### Usability
+
+### Reliability
+
+### Performance
+
+### Supportability
+
+1. Document strategy for managing conversations through the upgrade.
+1. Document strategy for identity binding between new and old accounts.
+
+**+ (Privacy, Anonymity, Censorship-Resistance, Deployments)**
+
+## Status Fleets Ownership
+
+[Placeholder - Cannot find an references to this Conversation]
+
+### Functionality
+
+### Usability
+
+### Reliability
+
+### Performance
+
+### Supportability
+
+**+ (Privacy, Anonymity, Censorship-Resistance, Deployments)**