Reports

Tech Lab Reports turn BK Tech Labs hypotheses, methods, experiments, results, and revisions into durable records. A report should make its assumptions and failure conditions visible, distinguish observation from interpretation, and remain reproducible enough for a later report to challenge it.

Reports differ from the Tech Lab Brief. A Brief uses current events to develop and communicate an argument; a report establishes or evaluates a documented Tech Lab hypothesis. Briefs may introduce a report and report on its results, while the report remains the canonical experimental record.

Reports

• [[Reports/Tech-Lab-Report-001|Tech Lab Report 001: The Joule Hypothesis]] — establishes Joules as a visible, auditable AI-capacity measure and defines the first experiment across guests (anonymous), free members, and paid members.

Report Lifecycle

1. State one research question and falsifiable hypothesis.
2. Record the accounting, method, access conditions, and evidence required.
3. Distinguish approved policy from measured findings.
4. Run and preserve experiments in the systems that produced them.
5. Publish observations, limitations, and interpretations in a later report.
6. Version material changes so historical results retain their original conditions.