NotebookLM: when two service instructions disagree

Imagine finding two instructions for a stalled worker, the background process doing a service's jobs. The runbook says to restart it. A later incident review says restarting can destroy a diagnostic capture, the information being collected to understand the fault. Both documents look relevant. Following one could prevent you from doing what the other asks.

NotebookLM can help put those passages together: add sources, ask questions across them and follow citations back to the text. Google's current documentation calls the product Gemini Notebook; this guide retains NotebookLM for readers looking for the familiar name. For our hypothetical restart question, the useful result is a comparison that makes the exception clear. The documents alone cannot tell you whether the running worker is currently in that exceptional state.

Give the notebook both sides of the question

Start with the current runbook and the incident review that appears to disagree with it. Add ownership information, relevant notes about the services this worker depends on, the policy for service-level objectives, or SLOs, and a few pertinent reviews. Those objectives describe the service results the team aims to deliver; their policy helps explain the operating constraints. Keep each document's owner, version and effective date with it. An old procedure can explain why things changed, as long as it is clearly marked superseded.

These sources may contain more than the restart instructions. Before uploading them, confirm which account is approved for this material, who can see the notebook and what data-handling settings apply. Remove unnecessary customer information and credentials. A subscription to another Google product does not establish the controls for this workspace.

Then ask for a comparison of the restart procedure and the recovery actions in the selected reviews, with citations and unresolved conditions left visible. You want to find out why two sensible-looking passages point in different directions before asking for a recommendation. A smooth answer is much easier to agree with than a contradiction you can still see.

Read the sentence beside the restart instruction

A citation gives you a way back into the material. Google's chat documentation explains that selecting one opens the quoted passage in context. Follow it and check whether the passage supports the answer, whether it is complete and whether it is current for this service.

In our example, the general procedure addresses a stalled worker. The later review says to preserve the process while a diagnostic capture is pending. Put those passages beside their dates and service versions. Now the question for the service owner is much more specific: is this worker currently waiting for that capture?

Keep conflicting procedures visible

Read diagram description

Illustrative source comparison: two procedures disagree. A cited comparison helps find the disagreement; current service state determines which conditions apply. Diagram labels: Runbook A: Procedure and stated conditions; Runbook B: Different procedure or conditions; Notebook comparison: Citations, agreement and unresolved conflict; Human check: Open the sources; check current service state.

Ten old reports saying a restart helped do not settle the capture question. The exception matters when its condition holds. The comparison has done useful work by exposing that condition, without pretending the number of documents can decide whether it applies today.

Find out where the missing condition went

Suppose the notebook gives a restart answer with no mention of the capture. Open the runbook before rewriting the question. Perhaps the relevant condition was never written down. Perhaps it was there, but the answer missed the paragraph. Those problems look alike on screen and need different repairs.

When the source is incomplete, its owner needs to clarify the procedure. When the answer overlooks an existing condition, correct the summary against that passage. In either case, the service owner still decides which condition applies and whether the action is permitted. Put an agreed clarification in the maintained, authoritative procedure, not only in this notebook conversation. The next responder may never see the chat that solved your confusion.

The documents and the worker have different clocks

A document can be up to date about the procedure and still tell you nothing about what the worker is doing this minute. Imported material can also miss a recent edit. Refresh behavior depends on the source type and product workflow, so verify synchronization rather than assuming every source updates in the same way. During an incident, compare the advice with the maintained runbook and current system observations.

A historical case with a known outcome makes a useful first trial of this reading workflow. Can the notebook bring back the decisive exception and make missing or contradictory information apparent? The operator-prompting guide develops that approach. A fixed record is useful for reviewing what happened; deciding what to do now also requires fresh state and current permission.

You began with two instructions that seemed impossible to follow together. Now they sit beside their conditions, and the owner has a specific question to settle. Once that clarification reaches the maintained procedure, the next person looking at a stalled worker has less detective work to do.