Start with the work you already have

Begin with what you already have

Relevant conversations, reports, plans, charts, and existing project work can provide a starting point in your own authorized Codex environment. E2C is intended to build on that investment, without asking you to reconstruct the full history or write a new formal specification just to begin.

Use ordinary language

The intended experience keeps the way you already talk to Codex: describe what you want to accomplish in ordinary language. You should not need special E2C commands, internal asset names, or another project-management system. Necessary clarification, suitable materials, and permissions still matter.

Read first, then ask what is missing

The first useful response should show an understanding of your existing work: what is available, how it relates to your goal, what remains uncertain, and what can happen next. The design calls for reading and comparing the materials before asking you to repeat them, then raising only the gaps, conflicts, or decisions that need your input.

Keep permission specific

Existing material helps explain the task; it does not prove every statement is correct or authorize every possible change. A request to understand the work is different from permission to modify or execute it. Make clear what may be read, proposed, changed, or used.

Starting is different from finishing

Exact starting steps and automatic handoffs still need to be verified for each product form.

Enough material for an initial review does not guarantee enough to complete the task. Keep project files and repositories in your own authorized working environment; website consultation is for brief text questions, not those materials.