Experimental Laboratory Notebook Protocol

Template Overview

Scientific reproducibility depends entirely on the rigor of laboratory record-keeping. When researchers rely on hurried scribbles in paper notebooks or fragmented spreadsheets, critical protocol details—such as centrifuge speeds, reagent lot numbers, and ambient humidity—are lost, making reproduction impossible.

An electronic laboratory notebook entry must serve as an auditable scientific discovery artifact: detailing the experimental hypothesis, material reagents, step-by-step execution protocol, deviations, raw observations, and conclusions.

This template provides an academic-grade Laboratory Protocol format: hypothesis framing, materials and reagents, step-by-step procedure, deviation logs, empirical results, and analytical conclusions.

Markdown Template Structure

Copy the block below or click Download .md File to add this template directly to your personal vault:

---
title: "Lab Protocol: [Experiment ID / Topic]"
date: [YYYY-MM-DD]
experiment_id: "EXP-2026-104"
researcher: "[[Lead Scientist Name]]"
principal_investigator: "[[Prof. Elena Rostova]]"
project_name: "Benchmarking Low-Latency Audio Kernel Ingestion on Apple Silicon"
experiment_status: [Completed & Verified | Failed / Inconclusive | In Progress]
tags: [lab-notebook, protocol, science, experiment, data, engineering]
---

# Lab Protocol: [Experiment ID / Topic] — [YYYY-MM-DD]

## 1. Experimental Hypothesis & Scientific Objective
- **Hypothesis:** Expanding the CoreAudio ring buffer from 256 samples to 1024 samples with dynamic backpressure will reduce audio frame drop rates to exactly 0.00% under sustained 100% CPU stress on baseline M1 hardware.
- **Independent Variable:** Ring buffer allocation size (256 vs 512 vs 1024 samples).
- **Dependent Variable:** Total audio frame drop count and P99 audio callback latency over 2 hours of continuous recording.

## 2. Materials, Reagents & Hardware Apparatus
- **Test Machine 1:** Apple M1 Mac Mini (8GB Unified Memory, macOS Sonoma 14.6).
- **Test Machine 2:** Apple M3 Max MacBook Pro (36GB Unified Memory, macOS Sequoia 15.0).
- **Stress Generator Tool:** `stress-ng --cpu 8 --io 4 --vm 2 --vm-bytes 2G`.
- **Audio Test Source:** High-fidelity 48kHz 24-bit stereo test tone generator fed through loopback audio bus.

## 3. Step-by-Step Execution Protocol
1. Boot test machine into clean operational state; close all non-essential user daemons.
2. Launch automated audio capture daemon configured with target buffer size allocation.
3. Initiate continuous 48kHz audio loopback recording.
4. Concurrently trigger `stress-ng` artificial system load after exactly 60 seconds of baseline recording.
5. Maintain sustained load for 120 minutes.
6. Terminate load generator; extract SQLite WAL database buffer and inspect frame counters.

## 4. Empirical Observations & Quantitative Results
| Test Run # | Buffer Size (Samples) | Hardware | Duration | Dropped Frames Count | P99 Callback Latency | Verdict |
| :--- | :--- | :--- | :--- | :--- | :--- | :--- |
| **Run 01** | 256 Samples | M1 Mac Mini | 120 mins | 48 Frames dropped | 14.2ms | 🔴 Failed SLA |
| **Run 02** | 512 Samples | M1 Mac Mini | 120 mins | 6 Frames dropped | 9.8ms | 🟡 Borderline |
| **Run 03** | 1024 Samples | M1 Mac Mini | 120 mins | **0 Frames dropped** | 5.2ms | 🟢 **SLA Met** |
| **Run 04** | 1024 Samples | M3 Max MacBook | 120 mins | **0 Frames dropped** | 2.1ms | 🟢 **SLA Met** |

## 5. Protocol Deviations & Anomalies Observed
- **Deviation 1:** Room ambient temperature on Test Machine 1 reached 28°C, triggering minor fan spin-up at minute 45. Thermal throttling observed but did not compromise the 1024-sample buffer.

## 6. Scientific Conclusion & Next Experimental Steps
> [!IMPORTANT] Verified Conclusion
> The hypothesis is confirmed. A 1024-sample ring buffer allocation provides sufficient scheduling headroom to guarantee zero audio frame drops even during intense synthetic system load on baseline hardware.

- [ ] Archive raw benchmark CSV logs in vault data folder (`data/exp-2026-104-raw.csv`).
- [ ] Incorporate verified 1024-sample buffer allocation into production release candidate build.

Filled Real-World Example

Here is a realistic example demonstrating how this template captures actual deliberations:

---
title: "Lab Protocol: EXP-2026-104 Audio Buffers"
date: 2026-10-06
experiment_id: "EXP-2026-104"
experiment_status: Completed & Verified
tags: [lab-notebook, experiment]
---

# Lab Protocol: EXP-2026-104 Audio Buffers — October 6, 2026

## 1. Result
1024-sample buffer eliminated all dropped audio frames under 120 minutes of 100% CPU load on M1.

## 2. Action
Approved 1024-sample buffer for production engine.

When to Use and When to Avoid

When to Use

• Use during wet laboratory experiments, physical hardware testing, or software performance benchmarking.
• Use to preserve an immutable, auditable scientific protocol with materials, steps, and raw observations.
• Use to ensure experimental reproducibility for academic papers and patent disclosures.

When to Avoid

• Avoid using for qualitative user interviews (use [[user-research-interview]]).
• Avoid using for weekly executive staff meetings.

On-Device AI Integration

Capture laboratory experiments with Oyma on macOS:

Analyze the laboratory experiment voice debrief or raw bench notes:
1. Synthesize experimental hypothesis, independent and dependent variables, and hardware/reagent apparatus.
2. Outline the step-by-step procedural protocol including calibration settings and controls.
3. Build the empirical results table displaying quantitative measurements, runs, and SLA verdicts.
4. Document protocol deviations, unexpected anomalies, and the formal verified scientific conclusion.
Output in rigorous, reproducible CommonMark format.

Your lab notebook protocols and proprietary experimental data remain safely on your Mac’s encrypted disk.