Sessions, logs and the flight deck

The machine runs like a small flight crew. A human captain sets the destination and approves money, sign-ins and anything legal. An AI operator is the pilot and flight engineer: it flies each working session and owns the wiring. A second AI is the co-pilot: it reviews every piece of work and can stop it. Scheduled jobs are the autopilot that holds altitude between sessions.

• Sessions are flights. Each one has a takeoff (read the log, check the board, load the standing orders) and a landing (write down what changed and what is still in the air). Nothing important lives only in a chat window.
• The log is the black box. Every action goes into a dated, plain-text log. The next session reads it first, so it never starts cold, and every miss can be traced.
• Checklists before takeoff. Live numbers checked, links opened, a phone-width look, the reviewer's pass. A failed check holds the work instead of shipping it.
• Written lanes. Each crew member has a written list of what it may do without asking; anything outside goes to the captain.

The point is not a smarter model. It's the habits that make flying boring and safe.