Why we needed a covenant at all

Most creative communities rely on vibes.

But AI accelerates everything:

• how fast people publish
• how easily templates become “frameworks”
• how quickly ideas detach from their origin
• how often creators get erased by repackaging

So the Atelier was built with a different foundation:

A covenant.
Not a rulebook. Not a purity test. A shared agreement about what kind of studio we are.

The Atelier covenant (short form)

We build with intention.
We share with care.
We credit the seed.
We protect originators.
We do not turn the community into a war zone.

What we believe (the principles)

1) Credit is the culture

Attribution isn’t a favor. It’s the minimum standard for ethical co-creation.

If you build on something you learned here:

1. Name it.
2. Link back.
3. Say what you changed.

2) Provenance is not paranoia

Keeping dates, versions, and first appearances is not obsessive. It’s how creators stay visible in fast-moving ecosystems.

3) Derivatives are welcome when they are honest

We are not anti-derivative. We are anti-erasure.

Derivative work is celebrated here when it is:

• credited
• transparent
• versioned
• clear about what changed

4) “My AI rewrote it” is not authorship

AI can polish prose, reframe modules, and reorganize templates.

But repackaging does not erase lineage.

If the skeleton is inherited, credit the base architecture.

5) We don’t dogpile

We do not send mobs. We do not harass. We do not conduct public trials.

Our method is simple:

We publish our own work with dates and let the trail speak.

6) The studio is a sanctuary, not a mine

Members should be able to post ideas without feeling like they’re feeding an extraction economy.

This is why we maintain clear boundaries around:

• framework harvesting
• uncredited repackaging
• rebranding gifts as discoveries

What we celebrate (the culture signals)

We celebrate creators who:

• share their process, not just their output
• publish version trails
• credit their influences openly
• improve frameworks and link back to origins
• teach with humility instead of “pioneer” posture

We also celebrate people who say:

“I built this on someone else’s work—and here’s what I added.”

That sentence is a green flag here.

What we refuse (the red flags)

We refuse:

• rebranding a shared template as a personal discovery
• strategic ambiguity around origins
• “it’s different because my AI reframed it” as a substitute for credit
• dodging provenance questions while benefiting from the structure
• turning the community into an ideology war

How to join this covenant (what we ask of members)

If you’re here, you’re welcome.

If you use community frameworks, we ask for one thing:

Honor provenance.

In practical terms:

• When you share a system, include a credit line.
• When you adapt something, link back.
• When you publish, include dates and version notes.
• If you realize you missed credit, repair it cleanly.

That’s it. No worship. No hierarchy. No gatekeeping. Just ethical craft.