Compliance notes
Examples should be clear about what they contain, where assets came from, and how a result was reviewed before publication or reuse.
Choose this when
Use public or self-created assets
Record the source, license, and any required attribution beside the prompt or output.
A technically strong example can still create avoidable rights problems when its inputs are undocumented.
Choose this when
Show generated people, places, or brands
Add a plain-language note identifying synthetic elements and avoid implying real endorsement or events.
Readers should be able to distinguish a creative test from documentary footage or approved brand material.
Choose this when
Share a repository example
Separate prompts, code, media, and environment notes, and remove private keys or personal data before publishing.
Clear boundaries make examples safer to inspect, fork, and adapt without exposing sensitive information.