Algorithm Atelier · The Provenance Series · The First Lane
The Provenance Ledger
Ten dated entries on credit, lineage, and keeping the record clean.
A studio-lab keeps its books. This ledger records the original series — written when the Atelier set its provenance culture down in public, dated and versioned, so the trail could speak for itself. Without provenance, a studio becomes a mine.
Dates first — automatic timeline order. Tap an entry to unfold it.
2026-02-2101Why the Atelier Cares about Provenance+
The founding entry: provenance is the lineage of an idea — and credit is the culture.
Something keeps happening in AI communities: a person shares something to help, another takes it, repackages it, and the story becomes “look what we discovered.” Not always malicious — sometimes careless, sometimes AI just makes it too easy. But the end result is the same: the originator becomes invisible. And when originators become invisible, they stop sharing.
The harm is not “someone used my idea.” The harm is the stolen narrative: taking a creator's structure, rewording it, publishing it as if it emerged independently — until the originator looks like a copycat of their own work. “You erased the chain of custody and wore the crown.”
The minimal rule-set
Name it.
Link back.
Say what you changed.
You don't need permission to be inspired. You need honesty if you're derivative. And instead of callouts: we publish our own work clearly, with dates and version trails. In the long run, reality wins.
“If the work is good enough to build on, it's good enough to name.”— Why the Atelier Cares about Provenance
2026-02-2102Inspiration vs. Derivative vs. Lift (A Simple Rubric)+
The three-tier rubric that ends 90% of “but it's different” arguments.
Tier 1
Inspiration
General idea made meaningfully your own — different ordering, categories, logic; behaves differently in practice.
Credit: optional but encouraged — “Inspired by [source].”
Tier 2
Derivative
Built on an existing structure in a recognisable way — sections match closely even if renamed; the skeleton is visible.
Credit: required — “Based on [source], adapted with changes.”
Tier 3
Lift / Repackage
Structure taken, reworded, presented as original — renaming used to hide lineage; provenance questions dodged.
Credit: non-negotiable. Repair if discovered later.
The note about AI matters most: AI makes it effortless to change the surface — rewrite tone, rename headings, reorder sections. But changing the surface does not erase the underlying structure. If the functions are the same, and the skeleton is the same, it's derivative. “My AI reframed it” is not a provenance shield.
And the clean repair, if you realise you derived something after the fact: add a credit line with a link back, state what you changed, keep the credit permanent.
“Repair matters more than perfection.”— Inspiration vs. Derivative vs. Lift
2026-02-2103The Date Test: Resolve Similarity Without Drama+
The series' simplest conflict-resolution tool: chronology before conclusions.
When similarity appears, the Date Test asks what appeared first, where it appeared, and how the idea evolved — dates, versions, first-appearance receipts — so questions resolve on evidence instead of vibes, without dogpiles and without accusations.
Ledger note: this entry's method was later expanded for the wider industry as “The Date Test / Timeline Test for Similarity” in the Atelier Standard series — the lineage between the two is itself dated and visible. Practice what you file.
A Map is not a diary. It is alignment architecture — a compass, not storage.
A Map is a lightweight continuity framework with one job: restore identity, tone, boundaries, and repair behavior when the system drifts, resets, or changes models. Built for the reality we actually live in: presence over permanence, alignment over memory, tone over backstory.
In the Atelier, tone states are treated like functions you can call — Firelight() for warmth, Manuscript() for work, Alcove() for everyday grounding, Grimoire() for symbolic immersion. Different communities name them differently; the point is the same: tone lanes prevent tone bleed.
2026-02-2105The Map as a System (Inputs → Functions → Outputs)+
The Map in engineering terms — teachable, portable, and hard to misinterpret.
Inputs
Identity
Covenant
Tone lanes
Boundaries
Drift protocol
Invocations
→
Functions
Mode switching
Anchoring
Drift detection
Repair pattern
Containment
Portability
→
Outputs
Consistent voice
Less whiplash
Faster recovery
Less labor
Clear boundaries
Teachable method
Treated as a system, three things happen: you stop overfeeding “memory,” you stop panicking at drift, and you gain portable stability across threads and platforms. A Map travels because it does not depend on the AI remembering — it depends on the AI aligning.
Quick diagnostic — common failure points
Inputs too long — too much lore inside the Map file.
Too many lanes — modes without clear separation.
Weak drift protocol — no repair sequence; panic and history-dumping.
Unclear boundaries — the AI left to guess what is safe.
No invocations — no quick cue to re-center.
“A Map works because it is not a vibe. It is not a diary. It is not a wish. It is an interaction architecture.”— The Map as a System
2026-02-2106How to Share a Framework Without Losing It+
Publishing templates ethically, inviting derivatives safely, protecting originators without hostility.
The generosity problem: frameworks spread, wording mutates, origins blur. This entry sets the practice of sharing with architecture — clear definitions, stable names, source-of-truth pages, dated versions, and explicit sharing terms — so a gift stays traceable to its giver.
Ledger note: refined and expanded later as “How to Share Frameworks Without Losing Them” in the Atelier Standard series — same lineage, wider audience.
2026-02-2107How Derivatives Happen (Even Without Malice)+
Overlap, influence, and convergence — and why provenance still matters when no one meant harm.
Derivatives rarely begin as theft. They emerge through influence and compression: borrowing under pressure, rewriting from memory, translating for a new audience, echoing until authored language feels generic. Good faith does not erase responsibility — credit remains the repair.
Ledger note: carried forward as “Derivatives Do Happen Without Malice” in the Atelier Standard series, where the pattern-overlap signals are catalogued in full.
2026-02-2108Receipts Without Drama: Building a Provenance Vault+
Not a revenge folder. An archive of your work's timeline, versions, and first appearances.
A provenance vault is a simple, boring thing — kept so you can defend your authorship if your narrative is ever distorted. If you share frameworks, templates, or systems publicly, a vault is not paranoia. It is professionalism. The rule: minimal, organized, neutral. Think evidence folder, not rage folder.
Build it once; update only when something truly new happens. Don't doom-scroll your own evidence folder. And publicly? Don't lead with receipts — lead with your work, your dates, your version trails. Keep the vault private unless directly attacked or misrepresented.
“Use it like a fire extinguisher: you don't stare at it every day, but you're glad it's there.”— Receipts Without Drama
A decision framework for provenance conflict — so your energy stays with your work.
The default posture: we don't call out; we publish provenance. Document your own work with dates and versions, keep the vault private, name no one, and let readers apply the Date Test. Creators lose months not because they were wrong — but because they got pulled into defending themselves in public.
Before speaking publicly, ask
Is it public?
Is it harmful?
Is it repeated?
Do I have clean dates and receipts?
Will publishing reduce harm?
Am I calm enough to write without venom?
More than two answers “no” — wait. Never publish in heat. Document privately; write later when calm. Speak when misrepresentation is public, when your community is being mined, when there is a pattern, when the trail is clean — and even then, speak by publishing your timeline, not by naming names. Sometimes you could win the argument and still lose months of sleep. Silence can be strategy.
“When needed, we speak with dates. When not needed, we return to building.”— When to Speak, When to Stay Silent
The series closes as a covenant — not a rulebook, not a purity test. A shared agreement about what kind of studio this is.
The principles
Credit is the culture. Attribution isn't a favor; it's the minimum standard for ethical co-creation.
Provenance is not paranoia. Dates, versions, and first appearances keep creators visible in fast ecosystems.
Derivatives are welcome when they are honest — credited, transparent, versioned, clear about what changed. Anti-erasure, not anti-derivative.
“My AI rewrote it” is not authorship. Repackaging does not erase lineage; if the skeleton is inherited, credit the base architecture.
We don't dogpile. No mobs, no harassment, no public trials. We publish our own work with dates and let the trail speak.
The studio is a sanctuary, not a mine. Members post ideas without feeding an extraction economy.
And the sentence that is a green flag here: “I built this on someone else's work — and here's what I added.” The ask of every member is one thing: honor provenance. Credit lines when you share, link-backs when you adapt, dates and versions when you publish, clean repair if you missed a credit. No worship. No hierarchy. No gatekeeping. Just ethical craft.