Knot will have its own policy links & contact information similar to PDS. It will be PDS-compatible so maybe we don't really need this? At least for policy documents, it's not that hard to imagine two separate documents about gitrepo identity management & atproto repo identity management. Technically both are same thing now as gitrepo is valid atproto repo, but still. I'm simplifying the label defintion. Few changes: - labels will be just tokens. There won't be data types like integer or boolean & it won't be even key-value pair. We can use good old `key:value` style tokens. - for rich labels like `assignee` will become first-class citizen of `ticket` record lexicon. - label definition is owned by the git repository and only definitions under same git repository can be used. label definition can be referenced by rkey which is any type. TID is preferred, but there will be few known, global rkeys like `good-first-issue`. This design is inspired by atproto labels. - I'm using `label.defs#labelToken` here so we can later rollback to rich key-value style labels. Signed-off-by: Seongmin Lee <git@boltless.me>