Seperate Documents for Agreement Exhibits

[Robert-MacWha]

Overview
It can be challenging to share specific parts of the agreement (IE Exhibit B with DAOs) because GitHub doesn't provide per-page URLs for PDFs. By creating separate per-exhibit documents, it becomes easier to share agreement details and less overwhelming for parties responsible for specific parts of the agreement (IE the security team reviewing Exhibit C).

Recommendation

1. Create per-exhibit documents in the “safe-harbor/documents” directory.
2. Create markdown versions of the agreement & exhibit documents to simplify filling out the agreement or moving it to other platforms (IE in website ToS).

Cost
The downside of this recommendation is that there are now 2-3 copies of the same information. If that's considered a problem, we could use actions to generate the PDFs from Markdown automatically. We could also just discard the PDF altogether and switch to Markdown, my recommendation.

Won't implement this quite yet since I know there are a few incoming changes to the contents of the agreement. However, when the time comes, I could handle the translation of these documents.

[Robert-MacWha]

As a note --- if we don't want to host this breakdown in GitHub, I was planning on setting up per-exhibit pages on Skylock's website for easier access.