Pre-production · pilot programme open
labraos is a LIMS and an electronic notebook on one record. Materials, protocols, instruments and signatures share a single append-only trail — and bounded agents do the preparation and the chasing, never the signing.
The lab’s work usually lives in a notebook, a spreadsheet, an instrument folder and somebody’s memory. Here it is one record, and the evidence is attached to it.
Notebook
Projects, versioned protocols, experiments and SOPs
Inventory
Materials, physical lots, purchasing and barcode labels
Storage
Location hierarchies, grids and box contents
Equipment
Calibration gating, maintenance plans and reservations
Analysis
Instrument ingestion, datasets, trending and reports
Compliance
Audit trail, signatures, retention and audit packs
The connected lab
Every handoff adds to the record instead of losing part of it. Structure, lineage and proof travel with the work from first receipt to the signature at the end.
Protocols · Versions · Experiments
An experiment copies the structure of a protocol version, so what was executed is fixed at the moment it was executed. Later edits to the protocol never rewrite work already done, and approved, format-locked and witnessed structures refuse changes outright.
Materials · Lots · Ledger
Materials and physical lots are separate records. Every movement is a row in an append-only ledger written under a row lock, so a balance is never a number somebody typed — it can be reconstructed from its own history, with units carried throughout.
Ingestion · Checksums · Datasets
Raw bytes are stored and checksummed before a parser sees them, and a parsed row is refused unless its checksum is the stored one. Every value keeps the parser and version that produced it, and points back at the exact file it came from.
Corrections · Versions · Retention
Recorded results, signatures, versions and audit entries cannot be edited or deleted. A correction is a new record naming the one it supersedes, and a withdrawal keeps the original readable. The history of a decision survives the decision changing.
How it is built
A laboratory operation is declared once — its inputs, its permission, its audit obligation and how much autonomy an agent may have over it. The screen you click, the REST endpoint, the MCP tool and a scheduled job all run that same declaration.
There is no second path into the data. An integration cannot reach past a permission the interface enforces, and nothing writes to the database without leaving the evidence the kernel demands.
Bounded agents
Agents in labraos are not a chat window bolted to the side. They hold an identity, run through the same capabilities people do, and are governed by a ceiling the kernel enforces before a handler ever runs.
Traceability
These are not badges. Each one is a point where the software refuses something, and a place a quality unit can go to watch it do so.
A write that emits no audit event does not commit. The trail is append-only by grant and trigger, and chained per tenant with SHA-256, so a gap or an alteration is detectable rather than merely unlikely.
compliance.audit.verify
A signature consumes a fresh, single-use re-authentication before the handler runs, and covers a content hash of the version it signed. If the record moves afterwards, the record says so and names the difference.
compliance.signature.create
Witnessing refuses the signer’s own signature and refuses content that has moved since. Once witnessed, further writes to that structure are refused.
compliance.signature.witness
Row level security is forced on every tenant-scoped table, and the application connects as a role that holds neither SUPERUSER nor BYPASSRLS. Isolation is structural, not a filter somebody remembered to add.
forced RLS · labraos_app
Attaching an instrument whose calibration has lapsed is refused, or recorded with the operator’s justification — never silent. Each recorded use keeps the state the instrument was in at the time, not the state it is in now.
equipment.usage.list
A record, its versions, its signatures and its entire trail export as a single audit pack with the same evidence attached as a manifest, in open formats that outlive any one vendor.
compliance.pack.export
On compliance. Software cannot be compliant on its own. Compliance is a property of a validated system, operated under written procedures, by trained people. labraos provides the technical controls that make it achievable and inspection cheap. It holds no certification, and none of the above is a claim to one.
Where it stands
labraos is pre-production, with broad functionality implemented and pilot acceptance still open. The first pilot is a qPCR workflow end to end: author, execute, correct, review, sign, witness, export. If that is a week you recognise, we should talk.