Reuse policy

grimoire explains techniques by showing them running. Some of that code is written here from a described algorithm. Some of it started life as someone else's.

What we do

• Every implementation records where it came from. The chip under each embed states whether it is clean-room, adapted, reproduced, or embedded from the original — plus the author, the source URL and the licence. That text is generated from the record, not typed by hand, and an automated check corrects it when the code and the claim disagree.
• The original is always linked. A source URL is mandatory on every reuse.
• Restrictive licences are never copied. NonCommercial, ShareAlike, GPL and AGPL work is embedded from the original host, not reproduced here. A build check enforces it.
• Images of artworks are linked or embedded from their source, never rehosted.
• No runnable is presented as a reproduction of a living artist's named work. Pages demonstrate techniques; they do not recreate pieces.
• Every reuse is listed in one place: the attribution index.

If you'd rather we didn't

Email nicoarbogast@pm.me and it comes down. You do not need to give a reason, cite a licence, or argue the point.

Removal is one field in a record. The embed is replaced by a link to your original and the surrounding page keeps working — so taking something down costs you one email and costs this site nothing. That is deliberate: a takedown process that is expensive to honour is one that quietly does not get honoured.

This applies to whole pages too, not just code. If you would rather there were no page about you or your work here, say so and it goes.

Mistakes

Getting an attribution or a date wrong is a bigger problem than a licence question, and it is the one we most want to hear about. See corrections.