SPACETRC / SCIENTIFIC NOTEBOOKS
Make the question explicit.
Rerun every step.
From a single code recipe to a multi-cell research notebook with traceable source data and dependencies. Real observations, explicit assumptions, portable work.
01 / SOURCE AND QUESTION
No dataset or Python runtime downloads when the page opens. Open a data selection first, then explicitly start execution.
02 / MULTI-CELL WORKSPACE
Notes, methods, calculation and output.
Each code cell replays earlier code cells in a clean scope. Cell order matters; there is no hidden persistent Python state. Imported code never runs automatically.
Up to 10 cells; 12,000 code characters total; 262 KB data. Runtime loading is limited to 60 seconds and each code step to 20 seconds. Imports beyond math, statistics, csv, io, json; file/network access and package installation are disabled.
03 / REPRODUCTION FILE
Carry the notebook with its sources and versions.
JSON carries text, data, methods, results and SHA256 records. The .ipynb defines the same public data in its first cell; environment and licence notes are retained in metadata. Imported results are not considered executed in this session.
04 / COMPLETION FOR A REAL PROGRAMME
Ready software does not mean a completed pilot.
This checklist is your operational declaration. It creates no learners, scientists, observatory access or independent approval. Actual protocols/cohorts and distinct-account feedback are managed in the existing programme workspace.
This multi-cell notebook is not the fixed 5.x research-object schema. General code output is not automatically converted into a verified research object or open-archive publication.
