Maintain the reason behind each evaluation label
A label without its rationale becomes difficult to defend when the source or product changes. Transfer the judgement behind the test, not only its expected output.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
150 articles in AI engineering
Page 9 of 9
Record when the old model can be retired
Keeping a previous configuration available supports recovery, but it also creates maintenance and data-handling obligations. Give it an explicit retirement condition.
Read articleHandover needs the awkward invoice examples
Transfer the documents that explain the pipeline's limits, not only clean demonstrations. The next team needs to recognise unsupported layouts and maintain acceptance rules.
Read articleName the owner of every inference dependency
The model endpoint is only one service in the request path. Assign responsibility for retrieval, identities, diagnostics and fallback routes before the implementation team moves on.
Read articleGive finance the assumptions behind the AUD estimate
An estimate is useful when its workload, price basis and currency treatment are visible. Transfer those assumptions with the model configuration and usage records.
Read articleKeep examples of justified and unjustified refusals
The next team needs to know both when the assistant must stop and when it should help. Preserve the reasoning behind those expectations as the product evolves.
Read article