NORTHN BENCH · FOR LABS, CROs, AND SPONSORS
A lab notebook that can't be edited. Only extended.
Run sheets sealed as they happen. Instruments write straight to the record. A sponsor reads it between monitoring visits, not weeks after.
- Sealed as it happens
- Instrument writes the sheet
- CRO oversight between visits
- Verifies offline
- Record only — moves no money
RUN SHEET · STUDY HX-204
northn bench · 5 entries · head 75ec…6b0f
Criteria locked — 6 lines
001 · abdcbefore any capture
Run 1 start — 07:41
002 · ca10window 07:30–08:15 · met
Standard curve R² 0.9964
003 · 6415posted by the plate reader
Late capture
004 · e836capture-window-missed
Sponsor QA sign-off
005 · 3742against the record
Every hash recomputes in the reader's browser.
anchored · 7fb7WHO IT'S FOR
Two doors into the same record
One chain. Each seat reads only what it was granted.
SPONSORS OVERSEEING A CRO
See the record as it's written
Today you see what arrives weeks after the visit, written by the party being paid. Here your QA seat reads the live record between visits.
SPONSOR QA SEAT
WHAT THIS SEAT SEES
- Live run sheet, read as it's written
- Evidence and chain — never the raw files
- Refusals surface the day they happen
- Your access log is part of the record
LABS AND PIs
Reproducibility as a record, not a policy
Any figure can be faked convincingly now. A sealed run sheet with instrument-posted readings is something a reviewer can check without a phone call.
LAB SEAT
WHAT THIS SEAT SEES
- Instruments post readings straight to the sheet
- Every figure traces back to the plate
- See who looked at the record, and when
- A journal sees attestations only
WHAT THE RECORD PROVES
Six things a notebook claims and a record shows
Each is enforced by the chain, not by policy. When the engine can't establish something, it refuses with a named code.
How the record is built →01Criteria fixed before evidenceseq 1–6 sealed first
Protocol steps, acceptance floors, and capture windows are the first sealed entries. Sequence numbers show the window was set before the shot.
seq 1–6 sealed first
02Capture windows for perishable observationscapture-window-missed
A gel before it fades, a reading before the sample is gone. A late capture is refused as capture-window-missed — two timestamps, never a model's opinion.
capture-window-missed
03The instrument is the producerinstrument serial on record
A plate reader, serial and calibration on record, posts its curve straight to the sheet. No analyst transcription.
instrument serial on record
04Figure lineage, sealedfigure → run → plate
Every figure traces to the sealed runs and the script that made it. Walk backwards from the plot to the plate.
figure → run → plate
05Refusals from a versioned registernamed refusal codes
A missed window, a capture naming the wrong step, evidence that can't reach a criterion — logged with a code. Never quietly accepted.
named refusal codes
06Verifier seats with a sealed audit trailevery read sealed
Sponsor QA sees evidence and chain. A journal sees attestations only. The lab sees who looked, and when — an audit trail that is itself part of the record.
every read sealed
PRIVACY BY CONSTRUCTION
What leaves the building
Hashes and metadata travel. Bytes stay on the bench.
Stays
- raw data
- images
- run-sheet PDFs
- anything with content
Travels
- hashes
- timestamps
- criterion references
- instrument serials
- refusal codes
VERIFY WITHOUT TRUSTING US
One click. One ALCOA+ bundle.
Carries hashes, never files. Verifies in a browser with no server, no account, and no Northn.
- A
Attributable
Every entry names its producer and the device that sealed it.
- L
Legible
Plain-language titles beside every hash.
- C
Contemporaneous
Device-sealed times and capture windows, enforced rather than asserted.
- O
Original
Instrument-posted readings, fixed at capture. Extended, never edited.
- A
Accurate
Readings checked against their floors on the record. A curve below R² 0.99 can't pass silently.
- Open the export in any browser — the chain recomputes from entry one
- Check the head against its public anchor
- Hand it to a journal or a skeptic
WHERE IT STANDS
What is built. What is roadmap.
BUILT
6- ALCOA+ export bundle
- Capture windows and the capture-window-missed refusal
- Instrument-posted readings
- Figure-to-data lineage seals
- Verifier seats with sealed access logs
- Public anchoring of the chain head
ROADMAP — NOT CLAIMED TODAY
3- 21 CFR Part 11 validation dossier
- Remote source-data verification for clinical monitoring
- GLP/GMP batch records
Research oversight is the stepping stone to clinical monitoring. Sponsors piloting now shape the clinical version.
ALSO FITS
Same record, not yet packaged:
- CDMO oversight
- Compounding pharmacy logs
- Specimen chain of custody
- IACUC protocol evidence
- Grant effort reporting
STRAIGHT ANSWERS
What QA leads and PIs ask first
Does this replace our LIMS or ELN?
No. It's a desktop app plus a camera that sits beside what you already run. No integration project before the first sealed run.
Does this satisfy 21 CFR Part 11?
We don't claim that. The record is built; the Part 11 validation dossier is roadmap. If Part 11 is your requirement, we'll show you the gap before a pilot starts.
Do our data leave the building?
Hashes and metadata travel; bytes stay. A sponsor sees only what its seat grants.
RUN A PILOT
Run one protocol on the record.
Keep every seal.
One protocol, one bench, or one CRO workstream — desktop app plus camera on the bench side, a QA seat on yours. No LIMS integration. Scope and terms on a call.
No money moves. The sealed record is the deliverable.