Working Principles

Rejected Media is a working creative system for building stories, tools, processes, software ideas, and experimental media with clarity and care. This document is not meant to be a manifesto carved in stone. It is a plain-English explanation of how I prefer to work, why certain boundaries exist, and how people can collaborate without confusion.

The heart of the work is simple: be honest, make the work better, respect people, and do not pretend something is something it is not.

Rejected Media is flexible with people and firm about the finished work. People should have room to think, learn, experiment, ask questions, and use the tools available to them. At the same time, the final output has to match the plan because my name, reputation, authorship, and responsibility are attached to it.

I care about finished work more than performance. I do not measure people by how many hours they sit with something, how busy they look, or whether they follow one exact personal method. I care whether the final product is clear, useful, honest, and aligned with the project.

I want people to use AI. I do not think AI is something to hide, fear, or be ashamed of. It can help people organize ideas, build structure, test language, create images, get feedback, learn faster, and move from a blank page into something real. That is a good thing.

The key is honesty. If AI helped make something, say that plainly. That does not erase the human idea. A person still deserves credit for the concept, direction, taste, revision, selection, arrangement, and final decisions they make.

When someone wants full artistic or copyright credit, the work needs meaningful human contribution. That usually means the person did more than ask for an output. They shaped it, moved it around, edited it, rewrote it, selected what mattered, rejected what did not, and made it serve a human purpose.

This is also a changing area. AI law, copyright standards, public expectations, and creative practice are moving quickly. This document is a working position, not legal advice. The practical standard is simple: use the tool, learn the process, transform the work, and be accurate about what happened.

I can help people learn how to use AI well. A good process might begin with a rough idea, use AI to create structure or options, then move through human revision, rearrangement, editing, research, feedback, and final judgment until the work no longer feels like raw AI output. The point is not to avoid AI. The point is to use it in a way that amplifies the creator instead of replacing them.

I do not want to micromanage people. When I hire someone to do a job, I expect them to do that job. I will give direction, context, tools, feedback, and support when needed, but I am not looking to take over someone else's role or manage every step of their process.

I care most about the finished work. I do not need to see every draft, every attempt, or every hour spent unless there is a real reason. If the final result is good, aligned, ethical, and usable, the method is mostly their business. If the work is not moving, if the result is not there, or if something starts to look dishonest, then I will step in.

I am willing to help people improve, clarify expectations, and give additional training when that makes sense. What I cannot do is carry a role for someone who is not doing the work. Trust works both ways: I give people room, and in return I expect honest effort, honest communication, and a finished product that reflects the assignment.

At the same time, honesty is not optional. I would rather hear the truth early than lose time to a cover story. Mistakes can usually be fixed. Confusion can usually be clarified. Skills can usually be trained. What damages trust is dishonesty, concealment, or trying to pass something off as something it is not.

The hard lines are about safety, respect, and basic trust. Sexual harassment, racism, lewd or hostile conduct, theft, dishonesty, and behavior that puts people or the project at risk are not training issues. Those are deal-breakers.

Good workflow should reduce confusion, not create more of it. I prefer direct communication, plain language, clear deliverables, and enough structure that people know what they are building. I do not want constant updates for the sake of updates, and I do not want to chase people for proof of effort. I do need important problems raised early, especially if the work is stuck, delayed, or drifting from the plan.

The plan matters because the finished work carries my name. That does not mean people cannot bring ideas or suggest a better route. It means changes should be discussed before the project drifts. Autonomy works best when everyone understands the destination.

Rejected Media should not be built on shame, pressure, or fake authority. People can like what they like, learn at their own pace, ask questions, and use tools without being treated like they are less creative. The goal is to make better work and help people understand the process honestly.

This is a living document. It should be updated as the work changes, as the law around AI and authorship changes, and as better language becomes available. It is not here to scare people. It is here to explain the standard clearly enough that people do not have to guess.