What goes into a data sample of SOPs, documents or code?
A good data sample shows the structure and quality of the full set without giving away its value: a handful of procedures from different teams, a slice of knowledge-base articles, or one module of a repository with its commit and review history, prepared the same way the full delivery would be. It should match the written description the deal will rely on. micro1's master terms define a "Data Manifest" that covers "sources, types, volumes and specifications" (micro1, s. 1.1), and give the buyer 60 days after acceptance to claim "a material non-conformity" with it (micro1, s. 1.3).
How do you protect a data sample?
Share it under a non-disclosure agreement, keep it small, and record what you sent and to whom. In the US, business information such as "methods, techniques, processes, procedures, programs, or codes" can be a trade secret only if its owner "has taken reasonable measures to keep such information secret" (18 U.S.C. § 1839(3)), so handing out unprotected samples could weaken that position; take advice on your own case. A buyer's license terms may treat non-public information shared "in connection with" the agreement as confidential (micro1, s. 2.3), but a sample shared before signing may fall outside them.
Does a sample change what you are paid?
Indirectly, yes: the sample sets the expectations that delivery is later measured against, and under micro1's terms the buyer has no obligation to pay for data it validly rejects (micro1, s. 1.3). A sample that shows the data as it really is protects the payment. fearofgod.ai de-identifies the data before it goes to buyers. Your company's name stays confidential until the agreement is fully signed, and a completely anonymous partnership is also possible.
General information, not legal advice.