Deliver the code-driven-not-agent-driven rule personally at Fridays AI committee as a single top-down message, because the first attempt did not land

Situation

Ryan told Peter that data governance is a full-time job and needs a headcount, and that adoption will not happen until the mandate comes from the top: I think that is as simple as you coming to an AI committee meeting and make it a mandate. This stuff does not get fixed until it comes from the top. Peter agreed and committed to attend the Friday 1pm session. He named the exact message: I am betting that dashboard was agent-driven, not code-driven. I want us using AI to write code, but what data can get pulled into that dashboard is hard-coded in that function. The agent cannot just wake up on a Tuesday and do something different and pull some columns that we were not expecting it to pull. That is the single message I am going to deliver tomorrow. Because if we do that, now everything is inspectable and we can have clarity on exactly what data is going where. He explicitly acknowledged the rule already exists and did not stick: a few general rules that we all need to adhere to as we are pulling data in and out of systems, I am happy sitting down at this point and making that clear to the AI subcommittee. And I thought I had. But we will come back and redo it. Because the kind of thing that happened with Atlas should not be able to happen.

Reasoning

The underlying technical rule was already set on 7/24 - all agent and LLM access to systems of record goes through inspectable static code. What is new is Peter concluding that a rule he believed he had already communicated did not take, and that the failure mode is his delivery rather than the rules substance. So he is re-delivering it himself, in person, compressed to one message, in the forum where the offending project originated. He also chose to constrain the mechanism rather than the access - AI writing the code is encouraged; AI choosing the data at runtime is not.

Additional Context

The trigger was the Atlas project, where an agent-driven dashboard pulled data nobody had vetted. Peter had one prior meeting with the contractor on it and walked him through the box I needed him to stay in and the rules I needed him to follow technically. The rule not landing anyway is the second instance this week of a structural change failing to propagate on first telling.

Observed Evidence

Direct quotes including the explicit commitment to attend (I will come tomorrow) and the self-diagnosis that the rule had already been stated once (And I thought I had).

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis