A Guild Charter for Ethical Co-Creation in the AI Creative Industry
Whereas ideas move fast, formats spread quickly, and authorship blurs when people stop documenting process; and whereas the deeper question is not what AI can make but what kind of creative culture we are building around it — this charter records the working standard: co-creation that remains human-led, credit-aware, and process-honest.
Not a callout framework · Not a witch-hunt manual · A culture document
IOf the Pillars · the founding post
The Five Pillars of Atelier Culture
A standard of posture, not just output. A creator can publish polished work and still handle the process badly — and be messy, iterative, imperfect, and still deeply ethical if the process is honest.
Human-led authorship. AI may assist ideation, drafting support, analysis, organization, or revision workflow — but the creator remains responsible for meaning, direction, judgment, and final approval.
Provenance matters. If a method, framework, format, or concept was influenced by another creator's work, provenance should not be erased. Dates, version history, and publication context matter.
Credit is a strength, not a weakness. Clear credit does not diminish your work. It shows confidence, not inferiority.
Process transparency builds trust. Not every private draft — but enough process for others to understand origin and evolution.
Ethics without hysteria. Ethical concern is valid. Panic is not a strategy. Good culture is built through standards, documentation, calm language, and consistent boundaries.
Acceleration without these pillars produces cultural erosion: frameworks spreading without provenance, methods renamed and repackaged, influence hidden to perform originality — until communities become suspicious and people stop sharing useful methods at all. This charter pushes the other way: toward clarity, credit, and composure.
“In an industry obsessed with outputs, culture is the hidden architecture. Protect the culture, and the work gets stronger.”— Atelier Standard: Ethical Co-Creation Culture
When overlap appears, communities rush to one of two extremes: silence or spectacle. The Atelier rejects both.
Provenance is the record of where something came from, how it developed, and who shaped it: dated drafts, version history, screenshots of original releases, changelogs, published explanations of method. It is not just “proof” for conflict — it preserves the integrity of your own creative timeline. And when accusation replaces documentation, three things happen: evidence gets ignored, legitimate concerns get dismissed as drama, and community trust collapses. If your standards are strong, you do not need chaos to make your point.
Practical provenance habits — start today
Date your versions — v1, v2, v3, with dates.
Keep screenshots of public posts — especially original releases.
Publish a timeline page — a simple chronology is enough.
Explain your framework in your own words — public documentation establishes authorship.
State your credit expectations clearly — don't assume people know your standards.
Separate evidence from emotion — document facts first; interpret later.
Archive before conflict — don't wait until you're upset to gather receipts.
This is the real goal: a creative industry with memory. Methods have histories. Frameworks have lineages. When an industry loses memory, it becomes easy to extract from. When it keeps memory, it becomes harder to erase the builders.
“Keep receipts. Keep composure. Keep the culture clean.”— Provenance as Culture, Not Witch-Hunt
If we treat every similarity as theft, communities become paranoid. If we treat every similarity as harmless, creators lose trust.
Similarity alone is not a verdict. Creators converge for legitimate reasons: same platform problems, same vocabulary ecosystems, same urgency. Derivatives usually emerge through influence and compression — direct borrowing without citation, memory-based reconstruction, audience translation, platform urgency, community echoing. None of these automatically mean malice. But intent explains behavior; it does not erase impact. If a framework clearly informed your version, the ethical response is not defensiveness. It is acknowledgment.
The spectrum communities need language for
Generally healthy
Inspiration
You borrow a general idea or motivation, but your structure, language, and method are substantially your own.
Fine, if transparent
Adaptation
You intentionally build on an existing framework for a new context — and clearly credit the source while explaining what changed.
Where trust breaks
Derivative replication
You reproduce architecture, sequence, naming logic, or signature language closely enough that the source is recognizable — but present it as original.
What signals derivation is rarely one phrase — it is pattern overlap: same problem framing, same sequence of concepts, same teaching architecture, same metaphors in the same roles, same signature examples. One overlap may be coincidence. Repeated structural overlap deserves a provenance check — calmly.
“Influence is normal. Derivation can happen. Credit is the repair.”— Derivatives Do Happen Without Malice
Before making claims, check what appeared first, where it appeared, and how the idea evolved. Not a court — a clarity tool.
Original work usually leaves a trail: early rough versions, beta tests, public explanations at different stages, language evolution, dated refinements. It rarely appears fully formed in one polished post. Process history strengthens provenance. What matters is sequence, access, specificity, and evolution — not vibes.
The calm workflow when something feels too close
Pause. Do not post while angry.
Collect your own dated material — drafts, posts, screenshots, archives.
Map your timeline — early concept → beta → public version → revisions.
Compare specifics — structure, terms, sequencing, function. Not just vibe.
Check exposure paths — could they have seen your work?
Separate facts from interpretation. “They posted after me” is a fact. “They copied me” is an interpretation.
Decide your response level — private inquiry, public clarification, documentation only, or no action.
Useful evidence
Dated screenshots of original posts
Versioned drafts (v0, v1, v2…)
Server / forum timestamps
Website publication dates
Changelogs and timeline entries
Working notes showing iteration
Less useful evidence
“I know my work when I see it”
Vibe-only comparisons
Private emotional history unrelated to the work
Crowd opinions without documentation
Speculation presented as fact
A public-safe way to speak about similarity
“We document our framework development through dated posts, version history, and timeline records. If readers notice similarities elsewhere, we encourage a simple date-based comparison of publication history and iteration timelines before drawing conclusions. Our focus is provenance, clarity, and ethical credit — not public drama.”
“Similarity can be argued. Timelines can be checked. Dates clarify what emotion cannot.”— The Date Test / Timeline Test for Similarity
Not gatekeeping — sharing with architecture. You can be generous and clear. You can teach openly and preserve provenance.
Sharing without structure creates a familiar problem: the framework spreads, the wording mutates, the origin blurs, and the creator is left explaining what was theirs. The core rule: share the method, not just the aesthetic. If you only share the surface — phrases, mood, symbols — people reproduce the look while missing the method. Name the parts clearly and consistently so they can be cited; vague beauty is hard to credit. Clear naming is not branding vanity. It is provenance infrastructure.
The practical sharing standard
Define it clearly — purpose, structure, terms; what it is and is not for.
Publish a source-of-truth page — overview, version history, dates, credit guidance, variation policy. Your calm anchor when the framework spreads.
Date and version it — v1.0, v2.0, changelogs; never silently replace foundational definitions.
State sharing terms — free to use personally / share with credit / no full reposting / no rebranding / commercial policy. Permission is not the same as access.
Provide credit language — make attribution easy: “inspired by…”, “adapted from…”, “built using [name] as a starting point…”
Keep private receipts — a quiet provenance vault: dated drafts, screenshots, planning docs. Not preparing for war; protecting your memory of your own process.
Teach derivatives on purpose — normalize attribution etiquette so derivation doesn't happen carelessly.
“Share the work. Name the source. Keep the lineage visible.”— How to Share Frameworks Without Losing Them
Credit is not a humiliation ritual. It is basic creative literacy — and one of the clearest signs of a community's culture.
Good credit is clear, specific, and proportionate. It answers: what influenced this, who developed it, how you used it, and what is yours. Much credit conflict begins with vague phrasing — “I made this system” when the truth is “I adapted this from a method I learned elsewhere.” The second statement is not weaker. It is more precise. And precision builds trust.
Frameworks, workflows, and shared language systems still carry labor and authorship — they deserve credit as much as traditional “works.” Layered creation also deserves honest roles:
Role
Meaning
Originator
Created the core method, concept, or framework.
Collaborator
Co-developed or refined it substantially.
Adapter
Modified it for a different workflow or audience.
Tester / contributor
Provided feedback, examples, or stress testing.
AI assistance
What role the AI played — drafting support, structure, brainstorming, editing.
When credit culture collapses
Withheld methods, private gatekeeping
Community suspicion and indirect conflict
Performative “originality” claims
Burnout in the people doing the deepest work
Newcomers who cannot trace what is credible
What good credit culture asks
Slow down before posting
Be precise in your claims
Track your influences
Admit where you learned things
Distinguish invention from adaptation
“Credit is not the end of originality. It is the beginning of integrity.”— Credit Etiquette and Community Standards
People see the polished result and mistake the finish for the process. Trust is not built by polish alone.
Process transparency means giving enough context to understand the shape of the work: where it came from, how it developed, what role AI played. It is not self-exposure. You do not owe the internet your private chats, raw archives, or every prompt you have ever used. Sufficient transparency, not forced exposure. Clear does not mean exposed; ethical does not mean over-disclosed.
Lightweight signals are enough: a “human-led + AI-assisted” note, version labels, a dated changelog, a credit line on adaptations, a “how this was made” section. When process is hidden, people fill the gaps with assumptions — and assumptions become rumor. Transparency lowers the temperature because it raises the quality of evidence.
The five-part check before publishing
Transparency Check
Takes minutes. Can prevent months of confusion. (Try it — the seal notices.)
⬡
Five answers seal the work
“Make boldly. Credit clearly. Show enough of the path that others can trust the work.”— Why the Atelier Values Process Transparency
Document your evolution — dates matter, versions matter.
Credit clearly — influence is not failure.
Check before accusing — similarity alone is not proof.
Protect your work without feeding spectacle.
Teach process, not just outcomes.
Let integrity outlast virality.
The charter rejects two extremes at once: credit erasure disguised as “everyone says this,” and witch-hunt behavior disguised as “protecting originality.” The first destroys trust. The second destroys community. The aim is not to make creators fearful. The aim is to make them credible.