Codex Product Context

Codex can move quickly through implementation. Notiky makes sure the task carries the product memory behind it, so the run optimizes for the product decision instead of only the local code change.

Notiky supplies the shared goal, accepted decisions, customer evidence, and constraints around a task. Codex uses the repository and its own execution environment to implement the work. Keep these responsibilities explicit so a successful code change can be reviewed against the intended product outcome.

Before starting, make sure you can access the Notiky workspace and the repository for the task. Follow the supported connection guidance in Notiky Settings for your Codex environment. Verify the resolved project and ask the agent to summarize the relevant knowledge before it makes changes.

For a permissions change, the brief should explain who may perform each action, why the restriction exists, and which user journeys must continue to work. Codex can inspect the code, identify the affected paths, and implement the task with those constraints in view.

Ask for evidence after implementation: the checks that ran, their results, and any limitations in the test environment. A result that passed a focused test may still require a human review of the complete journey. Keep the acceptance criteria attached to the work throughout that review.

When an implementation reveals an incorrect assumption, update the shared knowledge through the team review process. Avoid leaving the only explanation inside an individual Codex session. Future work in Codex, Cursor, or another supported agent should be able to retrieve the same current decision and understand what changed.