Introduce the concept of trust.

documentation/trust

@@ -35,10 +35,15 @@ The opposite is true too, a known company can have identified itself as the
 owner and that we can advertise the trust to be higher.
 
 
-In hour generated metadata this is reflected by the (token) category itself
+In our generated metadata this is reflected by the (token) category itself
 having a trust, and each metadata file linked having it's own specific
 trust.
 
+As a suggestion of policy, if a publisher of metadata has inconsistent data,
+for instance they failed to have 18+ tags in their metadata file while this
+would be appropriate, then what we suggest is to simply not include this
+teams data in the registry until such a time that this omission has been fixed.
+
 # Config format
 
 In the trust subdir of the input directory you can place many text files
@@ -49,6 +54,13 @@ Fields are read from top to bottom, you can mention the same field various
 times such that the item is processed in order.
 
 * trust=ultimate
-  The trust level is given. none, marginal, good, ultimate
+  The trust level is given. none, marginal, good, high, ultimate
 * domain=bitcoincash.org  
-  Provides the source of the 
+  Provides the source of the metadata in dns form.
+* category=deadbeef0124
+  A 64 character, hex-encoded token category. Which will then inherit
+  the most recently set trust.
+* authbase=deadbeef0124
+  A 64 character, hex-encoded authbase (txid). Which will then inherit
+  the most recently set trust. Allowing for all metadata files indicated
+  by it to likewise inherit this trust.