create table showing the teams

doc/src/architecture/architecture.md

@@ -3,3 +3,25 @@ Architecture design
 
 This section of the book shows the software architecture of DarkFi and
 the network implementations.
+
+For this phase of development we organize into teams lead by a single
+surgeon. The role of the team is to give full support to the surgeon
+and make his work effortless and smooth.
+
+| Component   | Description                                                            | Surgeon | Copilot | Assistant | Status   |
+|-------------|------------------------------------------------------------------------|---------|---------|-----------|----------|
+| consensus   | Algorithm for blockchain consensus                                     | err     | agg     |           | Progress |
+| zk / crypto | ZK compiler and crypto algos                                           | par     | nar     |           | Mature   |
+| wasm        | WASM smart contract system                                             | par     | nar     | das       | Progress |
+| net         | p2p network protocol code                                              | agg     | xsan    | nar       | Mature   |
+| blockchain  | consensus + net + db                                                   | err     | das     |           | Easy     |
+| bridge      | Develop robust & secure multi-chain bridge architecture                | par     | xsan    |           | None     |
+| tokenomics  | Research and define DRK tokenomics                                     | xeno    | err     | nar       | Starting |
+| util        | Various utilities and tooling                                          | nar     | xsan    | das       | Progress |
+| integration | Responsible for overseeing integration and liaising with team copilots | nar     |         |           | Progress |
+
+Priorities:
+
+1. consensus
+2. wasm
+3. util

doc/src/misc/hashchain/network_protocol.md

@@ -21,6 +21,9 @@ Inventory vectors are used for notifying other nodes about objects they have or
 
 ### Receiving an `Inv` message
 
+Allows a node to advertise its knowledge of one or more objects. It can be received unsolicited,
+or in reply to `getevents`. 
+
 An `Inv` message is a confirmation from a node in the network that the `Event`
 has been read.