Skip to main content

​
Overview

Notebooks turn a saved order or up to 32 items from your active stash into a personal learning record. The readable notebook is the center of the experience: a visual saved-lineup gallery, nine evidence-aware lessons, and a private journal you can revisit as your preferences become clearer. High IQ is still validating readable notebook generation before launch. Companion formats such as Stories, Daily Stories, mindmaps, audio, infographics, images, and video are separate artifacts with durable planning state, but no companion executor is selected. They are unavailable outside clearly labeled local or staging prototypes. A notebook does not need those formats to be useful or complete.
Notebooks are a Pro feature. If you do not have Pro, the app may show a clearly labeled sample preview. Sample content is local preview data and is not a generated notebook for your account.

​
Notebook sources

Each generation task freezes its input and source references for that run. The evidence-first Report V2 implementation also persists a minimized immutable source snapshot and publishes validated notebook revisions without rewriting earlier ones. Report V2 writes and customer update requests remain disabled while launch policy is reviewed, so current customer builds do not promise automatic regeneration when an order, stash, or research record changes.

​
Generate a personal notebook

1

Open Notebooks

Tap Notebooks in the app. Your library also includes shortcuts to Order History and Scan a Label, so the purchase record, captured product details, and learning record stay connected.
2

Start a notebook

Tap the add action, then choose the active stash items you want included.
3

Confirm the selection

Review up to 32 selected items and start generation. Select all safely stops at the supported limit, and the app reports real pipeline states rather than inventing a percentage or finish time.
4

Open completed sections

Completed sections remain readable even if another section needs attention. If a section fails, retry that failed section without replacing work that already completed.
Order notebooks are generated from the matching saved order flow and retain the task’s order source references. When that saved order is available, View Source Order opens it directly from the notebook. The stronger persisted-source and immutable-publication guarantees apply only to validated Report V2 publications; Report V1 remains legacy-unvalidated.

​
What a notebook contains

Evidence-first notebooks are organized as nine short lessons:
  • Snapshot and orientation — what the notebook contains and how to read it.
  • Saved lineup and research context — the strains or products frozen for this run, with available images and direct strain-profile access.
  • Cannabinoids and terpenes — sourced chemistry facts when research supports them.
  • Patterns and reflection — transparent comparisons plus prompts for your own observations.
  • Harm minimization — stable safety guidance that remains separate from personalized medical advice.
Open a supported claim’s Evidence action to see the source and whether it supports, contradicts, or only provides context. If the source data does not support a lesson, the notebook says it is unavailable instead of filling the gap with a guess. Use the top Notebook / Journal switch to move between the educational reader and your own notes. Content can vary with the source data, feature profile, and validation state. Empty or unavailable sections should not be treated as generated facts. Current Report V1 is legacy-unvalidated. It can synthesize fallback/default content and does not consistently preserve absence, so it is not evidence that missing values will always render as unavailable. Absence-preserving generation and validation belong to Report V2.

​
Sources and evidence

Notebook content is assembled from three fact classes:
  • Your data — the order or stash inputs and source references frozen for the generation task.
  • Research facts — strain information and source URLs collected by TIWIH.
  • Model synthesis — explanatory text derived from the first two groups.
Legacy Report V1 can show provenance at the notebook or strain-source group level. Evidence-first Report V2 implements claim-level evidence, explicit unavailable states, immutable source snapshots, and safe publication history in the staging code path. Those guarantees do not apply retroactively to legacy content, and the Report V2 write gate remains off pending launch review.

​
Research updates and version history

The Report V2 reader can keep the current publication readable while another candidate is being prepared, compare a validated earlier publication with current, and open immutable history without changing the notebook. Corrupt or incomplete historical content fails closed and is shown only as unavailable. The intended update journey is explicit: reviewed research can make an update available; the user chooses whether to generate it; failure or cancellation preserves the current publication; and only a fully validated candidate becomes current. The deterministic journey is available in the internal Notebook Studio today. Automatic freshness detection and the customer update action are not enabled yet. Read How notebook generation works for the complete lifecycle.

​
Companion formats

Each companion is planned independently in a durable artifact ledger. The ledger records safe plan and lifecycle state, but it is not an execution switch: its registry has zero selected executors and the execution gate is off. Current customer builds therefore do not generate new companion formats. A missing card does not mean the readable notebook failed. Disabled and blocked artifacts stay out of the production route.

​
Artifact ledger states

The durable artifact contract defines disabled, blocked, queued, generating, reviewing, ready, failed, outdated, and canceled item states. Generations can be planned, active, settled, canceled, or superseded; scheduling can fail closed as unresolved. These persisted control-plane states should not be read as a promise that a companion executor is available.

​
Retry and recovery

Notebook sections are independently recoverable:
  • A failed section can be retried while completed sections are preserved.
  • If no usable section completes, the app presents a notebook-level retry state.
  • Closing the app does not require the work to stay on screen; refresh the notebook list to see its latest server state.

​
Existing notebooks

Older notebook records remain visible. Legacy entries can be identified and upgraded into the current format through the app when that path is available. Legacy or prototype media does not become a launch-approved artifact merely because it already exists.