> ## Documentation Index > Fetch the complete documentation index at: https://docs.highailabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Notebooks & Stories Flow > The verified order and personal notebook flow, including partial recovery and gated companion artifacts. ## 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 ```mermaid theme={null} sequenceDiagram participant U as User participant App as High IQ participant DB as Convex participant Work as Generation worker participant Research as TIWIH research services U->>App: Choose an order or active stash items App->>DB: Submit frozen task input and source references DB->>Work: Start notebook generation Work->>Research: Resolve available strain facts and source URLs Research-->>Work: Research facts and citations Work->>Work: Generate and validate sections independently Work-->>DB: Persist section states and notebook payload DB-->>App: Show latest progress and completed sections Work->>DB: Install the validated companion plan in the artifact ledger DB-->>Work: Return blocked or disabled items; execution remains off ``` 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 ```mermaid theme={null} graph TD A[Start notebook] --> B{Source} B -->|Saved order| C[Freeze order task input and references] B -->|Active stash| D[Select items] D --> E[Freeze selected stash task input and references] C --> F[Confirm generation] E --> F ``` 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 ```mermaid theme={null} stateDiagram-v2 [*] --> Queued Queued --> Generating Generating --> Partial: Some sections ready Generating --> Completed: All required sections ready Generating --> Failed: No usable section Partial --> Completed: Retry failed sections Partial --> Partial: Retry remains incomplete Failed --> Queued: Retry ``` 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 ```mermaid theme={null} stateDiagram-v2 [*] --> Current Current --> UpdateAvailable: Newer reviewed research UpdateAvailable --> Updating: User requests update Updating --> UpdateFailed: Validation or research fails Updating --> UpdateCanceled: User cancels in time UpdateFailed --> Updating: Retry UpdateCanceled --> Updating: Retry Updating --> Promoted: Validated candidate published Promoted --> Current: New version is current Current --> ReadingHistory: Open prior publication ReadingHistory --> Current: Return to current ``` 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 ```mermaid theme={null} graph TD A[Readable notebook available] --> B[Artifact planner] B --> C{Profile and evidence gate} C -->|Future authorized path| D[Queued] C -->|Feature off| E[Disabled] C -->|Evidence or executor missing| F[Blocked] D --> G{Selected execution route?} G -->|No selected executor today| I[Blocked or unavailable] G -->|Future certified executor| H[Exact first-party task] ``` 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 | Format | Behavior | | -------------------- | ----------------------------------------------------------------------------------------- | | Share Card | Prototype until an exact deterministic renderer is selected and certified | | Story | Local/staging reading prototype; no selected executor | | Mindmap | First-party candidate only; blocked for legacy-unvalidated Report V1 and unselected | | Audio | First-party candidate chain only; blocked for legacy-unvalidated Report V1 and unselected | | Infographic | Prototype until its owned renderer is selected and approved | | Hero image and video | Off for launch pending quality, rights, privacy, and cost certification | | Daily Story | Availability-gated; not an automatic launch promise | ## Free and Pro ```mermaid theme={null} graph TD A[Open Notebooks] --> B{Pro access?} B -->|Yes| C[Account notebooks and generation actions] B -->|No| D[Read-only sample preview] D --> E[Upgrade action] ``` Sample data is labeled and kept behind a preview boundary. It is not submitted as an account generation request. ## Recovery cases | Scenario | Expected behavior | | ------------------------------------ | ---------------------------------------------------------------------- | | One or more sections fail | Keep completed sections and offer targeted retry | | No section is usable | Show a notebook-level failure and retry | | App closes during generation | Continue server-side and load persisted status on return | | Network is unavailable | Preserve server state and retry the client read when connected | | New research becomes available | Keep current readable and wait for an explicit update request | | Update fails or is canceled | Keep current readable; do not move the publication pointer | | Previous publication is invalid | Keep current visible and list the historical row as unavailable | | Feature profile disables a format | Do not execute it | | Evidence level is legacy-unvalidated | Block content-derived artifacts that require evidence-first Report V2 | | Notebook is legacy | Keep it identifiable and offer an explicit upgrade path when supported | ## 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. ## Related flows * [Notebooks Overview](/help/features/notebooks/overview) * [How notebook generation works](/help/features/notebooks/how-generation-works) * [Notebook Stories](/help/features/notebooks/stories) * [What's in Pro](/help/plans/whats-in-pro)