edit and accept arch-v1.0.0

3 files changed, 7 insertions, 1 deletions

diff --git a/requirements/architecture/arch-v1.drawio b/requirements/architecture/arch-v1.0.0.drawio
index 5e2d9b8..5e2d9b8 100644
--- a/requirements/architecture/arch-v1.drawio
+++ b/requirements/architecture/arch-v1.0.0.drawio
diff --git a/requirements/architecture/arch-v1.md b/requirements/architecture/arch-v1.0.0.md
index 41fadca..014cd59 100644
--- a/requirements/architecture/arch-v1.md
+++ b/requirements/architecture/arch-v1.0.0.md
@@ -1,6 +1,6 @@
 # Architecture
 
-Status: draft
+Status: accepted
 
 ## Problems
 
@@ -53,5 +53,11 @@ Status: draft
   (req-062)
 - Schist must not allow anybody other than the user to access its data in motion
   (req-063)
+- Right now we're assuming that Schist should have a Web GUI (ass-018). Can we
+  trace this assumption back to user needs?
 - Do we need or want any virtualisation or containerisation on the CRDT sync
   server?
+- Are there expensive lookups or aggregations we should be caching? If so, how
+  and where should we implement caching?
+- Do we want or need any monitoring or logging?
+- What patterns or frameworks should we use -- or avoid -- in the Web GUI?
diff --git a/requirements/architecture/arch-v1.png b/requirements/architecture/arch-v1.0.0.png
index 6f08be2..6f08be2 100644
--- a/requirements/architecture/arch-v1.png
+++ b/requirements/architecture/arch-v1.0.0.png