Research Pipeline · deterministic workflow

Run one small study before changing the product.

This operator cockpit turns the NOUS OS North Star into a repeatable loop: preregister, run a bounded session, produce a review packet, update the evidence ledger, then make at most one product change through the gate.

North Star to evidence, in five moves.

01
Pre-registerName one prediction and one result that would change your mind.
02
Run sessionUse Student Sandbox, trading-agent review, or memory loop with explicit boundaries.
03
Review packetExport a de-identified packet with evidence, uncertainty, and observer notes.
04
LedgerUpdate the session index with N, outcome, and honest status.
05
GateShip only one focused product change when evidence justifies it.

Create a pre-registration packet.

This does not save private data. It generates a Markdown draft that can be stored under docs/research-line/preregistration/ or pasted into the operator's Obsidian review folder.

What kind of moment are you studying?
The friendly choice above is stored as the research sub-line metadata in the packet.
Generate first, then copy the Markdown packet.
Packet preview will appear here after you click Generate packet.

The pipeline is only complete when evidence changes the next run.

Before sessionPre-registration exists and includes one falsifiable prediction.required
During sessionHuman boundary is visible; AI assistance starts only when requested.required
After sessionReview packet is de-identified, exported, and linked from the session index.required
Before product changeResearch-to-product gate names evidence, claim, risk, test, and one next-run change.required