Hand over the rules for stale approvals
The receiving team needs to know when an approved proposal can still run, when it needs review again and how to explain the difference to users.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 27 of 29
Let the receiving team recover a paused run
Recovery documentation is ready when another team can use it to restore a task and explain its final business state. Make that exercise part of the handover.
Read articleMaintain 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 articleRecord 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 articleTransfer ownership of the capability, not a folder
A module owner needs responsibility for its rules, public contract, data and operational behaviour. Source-code location is only one part of that responsibility.
Read articleGive operators an event trail they can follow
Support needs to trace a committed business change through publication and consumption. Transfer identifiers, recovery rules and ownership for every stage.
Read articleDocument what makes a command the same command
Transfer the identity, payload-equivalence and retention rules with the endpoint. Callers and operators need the same understanding of a retry.
Read articleHand over the evidence required for deprecation
The next team needs to know who still uses the old contract, what those callers depend on and which conditions allow it to be retired.
Read articleGive maintainers a map of partially completed states
Operators need to know which effects exist, which remain uncertain and who can resolve them. Transfer that map with the coordinator code.
Read articleGive support a tenant-safe diagnostic path
Operators should be able to locate a failure without gaining unnecessary access to every customer's data. Transfer scoped tools and escalation rules with the application.
Read articleName the owner of an event's meaning
The platform team can run the broker, but domain teams must resolve what published facts mean. Make that responsibility visible before a disputed change reaches production.
Read articleDocument how to bypass the cache safely
The receiving team needs a way to inspect authoritative data and recover stale entries without turning a diagnostic action into a production outage.
Read articleHand over the migration's unfinished state explicitly
A paused backfill or retained old column is part of the running system. Give the next team the evidence and authority to finish it safely.
Read articleExplain the invariant before the locking code
A maintainer can preserve the wrong lock and still break the system. Hand over the business rule, every writer that protects it and the evidence that it holds.
Read article