Workflow
A developer requests a change; assistance proposes code, tests and an explanation. The established repository review, build and release process determines what is accepted.
Platform requirements
Repository access boundaries, isolated execution, secret handling, dependency provenance and a traceable change record. Tool access should be no broader than the particular task requires.
Pilot evidence
Measure reviewed changes accepted, defects introduced, tests that actually catch failures and review time. More generated lines are not a useful outcome measure by themselves.
Keep the commercial boundary clear
This is an illustrative workflow for discussion. No customer results, integrations, regulatory approval or automated service are claimed. The organisation operating a future implementation must establish permissions, safety, quality and support.