I wanted AI conversations to change real files and screens. Select a piece of code or a page, discuss it, inspect the change and refine it.

Repeated work exposed a handover problem: knowledge left only in a conversation makes the next person start over. This site records editing locations, build commands and the boundary between verified and unverified results. The journal extends that approach.

A relationship that does not depend on every small edit

I want an owner to have enough knowledge for independent changes. We can work together when a business-specific decision or a new design is needed. Useful public information and a professional relationship fit together.

Five things the next agent needs

  1. The audience and purpose of the site.
  2. Where copy, design and behavior are edited.
  3. The brand and functions that must remain unchanged.
  4. The observable result required for completion.
  5. Where facts, open questions and changes are recorded.

Check actual access, not just the model name

Codex, Claude, Gemini and Grok should not be described as having identical operational access. A tool with project-file access works differently from a general chat receiving attached files.

The goal is a structure the owner can maintain with a chosen tool: bounded edits, review and a documented workflow. No model automatically acquires every permission.

A reusable work request

Also connect editable source to the public deployment and its recovery target. A restoration procedure belongs in the handover.

Explore the implementation

Adapt this request to your own project

Goal: update the service introduction.
Scope: the primary copy file and related HTML.
Preserve: brand, contact address, navigation and functions.
Completion: build succeeds; desktop/mobile copy,
            links and related behavior are checked.
Record: changed files, performed checks, open questions,
        recovery version and the next starting point.

Why publish the method

If a reader solves the problem independently, the journal has done its job. Readers who need an implementation fitted to their business can still get in touch.

The valuable part explains why a choice was made, when it should change and how its result can be established—not simply which button to press.