Why Do We Require You to Have Codex or Claude?

When we tell a client they need at least basic access to Codex or Claude, we are not trying to sell them software. We do not receive a kickback, referral fee or commission from either company.

It is simply a tool requirement.

Our development process assumes the client has an AI workspace they can actually use. That gives us a place to hand off instructions, review ideas, test prompts, create structured project context and let the client participate in the same kind of workflow our team is using.

Your personal AI account does not magically become EAS. We create what we call an Ai.Id for the project relationship. That identity is how your case, your instructions, your project goals and your decisions are recognized inside our own process.

Once your case is identified, our internal system can route the idea through different agents, actuals, oracles, engineering tools and specialized datasets. Some challenge the idea. Some refine it. Some look for technical problems. Some look for better ways to build it. Others may be instructed specifically not to filter the idea because the point is to preserve the original concept.

You do not need to learn our entire pipeline. You do not need fifty agents on your laptop. You do not need to understand every model we use.

You need enough access to participate when the project requires it.

If your EAS project requires AI access, we will tell you exactly what minimum tool is required. If we do not instruct you to obtain something, you are not required to have it.

That is the whole policy. We are building with modern tools, so the people on the job need access to the tools the job requires.

One rule, five angles. This is one of five Gazette pieces explaining the same EAS AI-access policy for different readers.

• For the Skeptic
• For the Non-Technical Reader
• For Developers and Engineers
• For Designers, Creators and Idea People