prop reference infrastructure, and other things

doc/logbooks/template-layers/4-fields

@@ -28,6 +28,16 @@ TODO:
         this may actually only apply to counters...
     This is trivial in a 2-process implementation, but i'd rather avoid the overheads
 
+TODO:
+    Scour the RDL spec.
+    Does this "next state" precedence model hold true in all situations?
+
+TODO:
+    Think about user-extensibility
+    Provide a mechanism for users to extend/override field behavior
+
+TODO:
+    Does the endinness the user sets matter anywhere?
 
 Implementation
     Makes sense to use a listener class

doc/logbooks/template-layers/5-readback-mux

@@ -62,4 +62,8 @@ WARNING:
 
 Forwards response strobe back up to cpu interface layer
 
-Dont forget about alias registers here
+TODO:
+    Dont forget about alias registers here
+
+TODO:
+    Does the endinness the user sets matter anywhere?