010-notebook · The notebook
A specification and the implementation: make OpenGenie's notebook the thing Databricks documented on 27 October 2026 — a document you select, run in ranges, skip on purpose, and read from a map — without inventing a cluster, a debugger, or a share button the app cannot honour.
Status: implemented and inspected, 9 November 2026. Why this is 010: 008 is the public site and 009 is attachments. This folder is the notebook. Sources: Navigate the notebook editor (updated 27 Oct 2026), Run notebooks, Notebook outputs. Builds on: 003 (cells), 006 (run, output, fix), 007 (keys and scroll).
The one sentence
Press Esc and the cell is a thing you can move, run, and skip; press Run all and the notebook stops at the first failure, names what it left out, and shows you where that failure is.
Read in this order
| # | Document | Answers |
|---|---|---|
| 01 | Five whys and first principles | Why a notebook is not a list of editors |
| 02 | Grounding | What the code already did, and what the Oct 2026 docs add |
| 03 | Requirements | NB-*, each with its test |
| 04 | Wireframes | The bar, the cell, the map, the result |
| 05 | Diagrams | Sequence, state, ER |
| 06 | Lenses | Eight owners, and the one thing each vetoes |
| 07 | Architecture | [D1..D8], DRY and SOLID |
| 08 | Implementation plan | The order the code was written in |
| 09 | Edge cases | What was envisioned, and the two limits we will not fake |
| 10 | E2E plan | Scenes, and the inspection loop |
| 11 | Outcome | What the screenshots changed |
A requirement is [NB-3], a decision [D4], an edge [E-7], a scene [S2], a principle [P2], a veto [V5]. Each id is defined once.
What this is
The editor already had cells, command mode for a handful of keys, Run all for SQL, outputs, and Fix with agent (006). What it did not have is the document Databricks describes: a map of execution, a run that means "above" or "below", a cell the author marked %skip, and a result you can filter without leaving the cell.
What this is not
A cluster picker, a debugger, widgets, comments, schedule, and share. Each of those needs a capability this app does not have. Drawing the control would be the inert-button bug 006 already forbids. They are listed in 09 so they are not rediscovered as bugs.