diff --git a/README.md b/README.md
index 646cd2b..0f2c137 100644
--- a/README.md
+++ b/README.md
@@ -10,4 +10,20 @@ If you can serialize a board game, you can do cool stuff:
 
 This tries not to introduce players into the state itself, instead use markers to keep track of where everything is. Built using Cap'n Proto. The game rules themselves are not part of this, and game validations are optional.
 
-For eg, having a chess serialization that allows for 2 kings is _okay_, since the game's logic would never allow it to reach such a state.
\ No newline at end of file
+For eg, having a chess serialization that allows for 2 kings is _okay_, since the game's logic would never allow it to reach such a state.
+
+# Status
+
+|Game|State|Partial State|Transform|RPC|Game Engine|
+|---|---|---|---|---|---|
+|Sushi Go|:white_check_mark:|||||
+
+Meanings:
+
+**State**: Support to serialize the current state of any game. Just the state specification.
+**Partial State**: State specification for partial state (if any). Just the partially observable state that the players would get.
+**Transform**: Code to transform the state -> partial state given other parameters.
+**RPC**: Code to send state transforms over the wire. Or moves
+**Game Engine**: Code for the server
+
+Only the first 2 are covered in the project.
\ No newline at end of file
diff --git a/sushigo/README.md b/sushigo/README.md
new file mode 100644
index 0000000..baae3d7
--- /dev/null
+++ b/sushigo/README.md
@@ -0,0 +1,6 @@
+# sushigo
+
+- See https://github.com/captn3m0/sushigo/ for my first attempt in Ruby
+- Rules: http://www.gamewright.com/gamewright/pdfs/Rules/SushiGoTM-RULES.pdf
+
+