Investigate a payload found in unexpected diagnostics
Establish which data was copied, who could access it and which path created it. Contain further logging while preserving the evidence needed to assess the incident.
Read articleAI implementation, software architecture, cloud operations and Australian technology policy.
150 articles in AI engineering
Page 5 of 9
Establish which data was copied, who could access it and which path created it. Contain further logging while preserving the evidence needed to assess the incident.
Read articlePrevent new work, account for operations already accepted and preserve the useful result. Cancelling the conversation alone may leave costs and effects running in the background.
Read articleA handoff should carry the unanswered question and evidence already checked. Make the next owner clear without promising work the application has not actually submitted.
Read articleA search migration must preserve access rules as carefully as content. Use a parallel index and an explicit cutover check so incomplete permissions never become public results.
Read articleAn embedding change is an index migration. Keep query and document representations compatible, and preserve the exact-match path while comparing the new retrieval behaviour.
Read articleChanging passage boundaries should not make citations point to unrelated text. Separate source identity from the temporary shape of an index build.
Read articleUpdating the knowledge base should not silently change what an earlier answer claims to have used. Plan how source versions and saved answers move together.
Read articleA replacement index needs a source checkpoint, a catch-up plan and compatible answer caches. Switching a query alias is only one step.
Read articleA model that previously could only summarise may become much more consequential when it can send, update or retrieve additional data. Treat that capability change as a new security review.
Read articleMoving from suggestions to mutations changes the product's responsibility. Release one explicit operation with observable effects and a way to stop it.
Read articleA new review screen is ineffective if another endpoint can still execute the same mutation directly. Migrate the authority rule across every execution path.
Read articleA deployment can change tool schemas and state meaning while runs are waiting for approval. Plan compatibility for those saved records before switching new traffic.
Read articleChanging questions, sources or labels can change the score without changing the application. Keep dataset revisions explicit and preserve comparisons across the transition.
Read articleA small rollout is useful only if it exercises the behaviours you need to observe. Select the cohort by tasks and risk, not just by a random fraction of traffic.
Read articleBegin with a class whose fields and validation rules are understood. Expand using reviewed evidence rather than assuming every supplier format behaves the same way.
Read articleChanging the answer model's endpoint leaves ingestion, retrieval and diagnostics untouched unless the migration explicitly includes them. Review the entire dependency set.
Read articleA lower-cost model route should satisfy the task's existing quality and authority requirements. Evaluate routing errors and fallback work as part of the candidate.
Read articleChanging a threshold alters which questions receive answers. Review newly accepted and newly withheld cases before applying the change broadly.
Read article