
The Bio Rust Studio and Editors
Every tutorial on Bio Rust is signed by the Bio Rust studio rather than by one name. That is deliberate. The library is written and reviewed by a small group of working artists, and a method only goes out once it has been drawn through at the canvas by someone other than the person who wrote it. The byline stands for that shared check, not for a single personality.
What the studio does
The studio writes each technique as an ordered method, tests it by following the written steps alone, and rewrites any step that needs extra explanation. It keeps the library tool agnostic where it can, names a specific app only when a step truly depends on it, and dates every page so readers can see when it last changed. Since fix pass two of the relaunch, every article also closes with its sources: museum glossaries, software manuals, standards bodies, and published studies, so the facts and definitions can be checked independently.
How a tutorial is reviewed
A tutorial passes through four stages in a fixed order, and none is skipped.
- Written. One artist writes the method as an ordered set of decisions: what to do, in what order, and why that order. The draft includes the direct answer, the numbered steps, the table, the FAQ and the sources, so the reviewer sees the whole page.
- Drawn through by a second artist. A different member of the studio works the method at the canvas from the written steps alone, without talking to the writer. Every place the second artist has to stop, guess or ask is marked, and each marked step is rewritten until it can be followed cold.
- Sources checked. Each factual claim and each definition is traced to a source in the list at the foot of the page. A claim that cannot be traced is cut, or reworded as the studio's own practice and labelled as such.
- Dated. The page carries the month it was last changed. The date moves whenever the text changes in a way that affects what a reader would do, and stays put for spelling and link repairs.
Sources the studio accepts and rejects
| Source type | Verdict | Reason |
|---|---|---|
| Museum and gallery glossaries | Accepted | Definitions of value, edge and glaze, written by people who look after the originals |
| Software manuals and official documentation | Accepted | The authority on what a setting actually does in a given app |
| Standards bodies and published specifications | Accepted | The only reliable account of what a provenance standard or a metadata field records |
| Peer reviewed studies | Accepted, with limits stated | Used for detector accuracy and perception claims, quoted with the sample size and the caveats |
| Reported journalism from named publications | Accepted for events and dates | Establishes that something happened; never used as a source for technique |
| Forum posts and comment threads | Rejected | No way to check who wrote them or whether the method was ever tested |
| Unsourced blogs and video descriptions | Rejected | They tend to repeat one another; a claim with no origin is not a source |
| Anything owned by a vendor selling a detector | Rejected | The vendor has a commercial interest in how accurate detection appears to be |
What the studio will not do
- Publish a method that has not been worked through at the canvas.
- Sell courses, collect emails, or place advertising inside the tutorials.
- Present a generated image as an example of technique. Header still lifes are illustrative and disclosed on the methodology page.
- Claim certainty it does not have. Where a question, such as whether an image was generated, cannot be settled by looking, the library says so.
Generated images and detector questions
Two subjects come up in reader mail more than any other. First, the header still lifes that open each section are produced with an image generation tool, art directed by the studio, and disclosed on the methodology page. They are decorative. No generated image appears anywhere on the site as an example of technique, as a step, or as a reader's work.
Second, the studio cannot act as a verification service. Readers ask whether a particular image was generated, whether a detector result is right, or whether the studio will vouch for a piece. Nobody can settle those questions by looking, and the studio will not pretend otherwise. What it can do is teach the method: how to check where an image came from, what Content Credentials and C2PA do and do not prove, and why AI image detectors flag real art. The reader applies the method to their own case.
What the studio has written
The library spans character and anime construction, painting fundamentals, free resources, and process and provenance. A few places to start:
- How to Draw Anime Eyes: A Complete Method
- Anime Face Proportions: Head Construction From Any Angle
- How to Draw Anime Hair as Blocks, Not Strands
- Layer Blend Modes for Shading, Explained
- Blend Modes Cheat Sheet for Digital Painting
- Values in Painting: Why Your Color Looks Off
The full list lives in the tutorials archive, and the thinking behind the library is on the about page and manifesto. New pieces are chosen from reader requests and from the questions working artists bring to the studio most often, which lately means as many questions about proving authorship as about drawing eyes and hands.
How a correction changes a page
When a reader reports an error, the report is first checked at the canvas by an artist who did not write the piece. If the method fails as described, the step is rewritten, the page date changes, and the change is noted in the studio's working log. If the method holds and the reader's result still differs, the studio looks for the missing condition, usually a setting, a brush or an app difference, and adds it to the text. Wrong facts are corrected in place, with the source that settles them added to the list. Nothing is changed silently: a date that moved is the signal that something did.
Where reader requests come from
New pieces come from three places. Reader email is the largest: questions about a method, requests for a technique not yet covered, and reports that a page stopped matching an app after an update. The second is the studio's own work, where a problem solved at the canvas becomes a method worth writing down. The third is the archive itself: old addresses that other sites still link to, which show which of the original pages readers still want. A request that several readers make in the same month moves to the front.
How to reach the editors
Corrections, questions about a method, and requests for new techniques go to the studio by email at hello@biorust.com, also listed on the contact page. Reported errors are checked against the canvas, corrected in place, and the page date changes. The process record habits the studio uses on its own work are the same ones taught in how to document your art process.
Related reading
- How Bio Rust tutorials are madeHow techniques are written, tested, corrected, and illustrated.
- About Bio Rust and the made by hand manifestoWhy the library exists and what it stands for.
- Contact the studioCorrections, licensing questions, and requests.
- Accused of Using AI Art? How to RespondA calm, evidence first playbook for artists accused of posting generated work: what to share, what to keep private, how to appeal, and how to stop it happening again.