Diagnose a missing search result before boosting its title
Check eligibility, ingestion and query interpretation before changing ranking. A score adjustment cannot retrieve a document that never entered the candidate set.
Read articleCobnex blogs / Australia
Cobnex blog
AI implementation, software architecture, cloud operations and Australian technology policy.
512 articles
Page 15 of 29
Find every artifact that contains the reported package
A dependency incident starts with exposure mapping. Determine where the code ran and which credentials or data were available before choosing the recovery action.
Read articleDiagnose Access denied before attaching an administrator policy
Identify the actual principal, action and target. A narrow correction is possible only after the failed operation is understood.
Read articleTake over an incident by confirming four things first
Establish impact, active changes, unresolved outcomes and ownership before starting another intervention. A brief read-back can prevent a costly assumption.
Read articleInvestigate a record that reappears after recovery
Find the source that recreated the data before deleting it again. Otherwise the next reindex or restore can repeat the same failure.
Read articleReindex protected documents without opening a gap
A 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 articleChange the embedding model without losing identifier search
An 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 articleRechunk a corpus with stable source references
Changing passage boundaries should not make citations point to unrelated text. Separate source identity from the temporary shape of an index build.
Read articleKeep older answers inspectable after a source revision
Updating 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 articleRun old and new indexes with a clear activation point
A replacement index needs a source checkpoint, a catch-up plan and compatible answer caches. Switching a query alias is only one step.
Read articleRetest boundaries whenever a new tool is added
A 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 articleIntroduce a write tool behind a bounded cohort
Moving from suggestions to mutations changes the product's responsibility. Release one explicit operation with observable effects and a way to stop it.
Read articleAdd approval without leaving an older bypass open
A new review screen is ineffective if another endpoint can still execute the same mutation directly. Migrate the authority rule across every execution path.
Read articleUpgrade the agent while old workflows are paused
A 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 articleVersion the evaluation set alongside the release
Changing questions, sources or labels can change the score without changing the application. Keep dataset revisions explicit and preserve comparisons across the transition.
Read articleChoose a release cohort that includes difficult work
A 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 articleIntroduce automatic acceptance one document class at a time
Begin 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 articleMove inference without overlooking the embedding store
Changing the answer model's endpoint leaves ingestion, retrieval and diagnostics untouched unless the migration explicitly includes them. Review the entire dependency set.
Read article