Skip to main content

​
Overview

Notebook tasks freeze the order or active-stash input and source references they receive for a run. Evidence-first Report V2 persists a minimized immutable source snapshot and validated immutable publications; Report V1 does not provide that guarantee. The Report V2 write and customer-update gates remain disabled while the readable notebook is validated before launch. Companion formats have a durable, fail-closed planning ledger, but the executor registry has zero selected entries, so those formats are currently unavailable outside labeled local prototypes.

​
Generation flow

The server continues durable work independently of the screen. The UI reads persisted state instead of relying on a single open connection.

​
Choose a source

An order or personal notebook keeps the output generated for its original task inputs; it does not automatically regenerate after later source edits. Report V2 now provides persisted minimized snapshots and evidence-first provenance behind its hard-disabled write gate. Automatic freshness detection and customer update requests still require an approved research watermark and refresh policy.

​
Notebook states

Section states are persisted independently. Retrying failed sections preserves completed work and does not require replacing the whole notebook.

​
Detail view

The notebook detail experience can present the available Overview, Strains, Terpenes, Plan, and Insights content. A section can be omitted or shown as unavailable when its source data or validated output does not exist. The source area distinguishes:
  • User facts from the order or stash task input.
  • Research facts and collected source URLs.
  • Model synthesis derived from those inputs.
Report V1 provenance is at notebook or strain-source group level and must not be treated as claim-level citation. Report V2 provides claim-level evidence and explicit unavailable states in the staging implementation, but its write path remains gated.

​
Publication update flow

Current remains readable throughout update available, updating, failed, and canceled states. Promotion creates a new immutable publication; it does not rewrite the earlier one. History content must pass the safe Report V2 parser before the app labels it as a previous version. This complete journey is testable with synthetic data in Notebook Studio; freshness detection and the customer request action are not enabled in production.

​
Companion artifact planning

The current planner validates and atomically installs a bounded manifest as one generation plus its artifact items. Installation creates no attempt; an attempt would be created only after a future eligible claim succeeds. The ledger can preserve attempt, retry, reconciliation, cancellation-event, supersession, and outdated state once those transitions occur. It does not authorize execution: the shared registry is candidate-only with zero selected executors, and the execution gate is hard false. There is no production claim/dispatch/reconciliation worker, safe owner artifact-cancel route, or Trigger run-cancel handshake. Historical provider environment values cannot create or reroute a selection, and the production manifest has no NotebookLM provider or executor identity.

​
Format posture

​
Free and Pro

Sample data is labeled and kept behind a preview boundary. It is not submitted as an account generation request.

​
Recovery cases

​
Stories and Daily Stories

Story designs are exercised in staging and the Experience Lab. The durable ledger can represent Story freshness, failure, and retry state, but no Story executor is selected, so those states are not a promise of live account generation. Daily Stories remain a development preview. Their scheduler and generation task are inert. A local or staging fixture can exercise the design, but documentation and UI must not claim that an account receives an automatically generated story each morning.