Jason Rodriguez evaluation - clear deliverables, no guardrails

Situation

Rather than building guardrails around Jasons working style (works alone, doesnt communicate, delivers code that doesnt integrate), set clear deliverables with acceptance criteria and evaluate on results. If he cant deliver, move on. Do not coach around his limitations.

Reasoning

Building guardrails for individuals doesnt scale and masks whether someone can actually perform in the environment we need. Setting clear targets and evaluating on results reveals capability. If Jason doesnt make it, explaining why to the team teaches everyone the standard. Max believes Jason wont make it.

Additional Context

Jason submitted 5 PRs to NARF - 4 were rejected outright, 1 had a kernel of value but needed complete rework. Pattern of delivering things that dont integrate with existing codebase. 25000 lines of code that dont fit on existing train tracks.

Observed Evidence

Max: "Cards on the table, I dont think Jason makes it" and Peter: "Set a clear deliverable, dont provide the guardrails... I dont want this to be voting people off the island, but I dont want to take that off the table" and "If Jason doesnt work out, we owe it to everybody here to explain why that didnt work out"

Confidence Breakdown