Source: https://guthlabs.ai/docs/project-templates/experiment-run/

project template / candidate

# Experiment run

Proposal-only project record for defining an experiment protocol, controls, fixtures, runs, failures, interpretation, evidence, approvals, and closure receipts without implying execution, provider connection, publication, or production state.

Status: **candidate**Lifecycle: **candidate**

## Record status

**Record ID**: project:experiment-run

**Parent lifecycle**: candidate

**Page lane**: catalog overview

**Lane lifecycle**: candidate

**Owner**: Not separately recorded

**Owner role**: Not separately recorded

**Owner status**: Not separately recorded

**Qualification result**: NOT RUN · held for evidence and human review

**Working browser surface:** [Project templates & workflows — overview](<https://guthlabs.ai/labs.html#templates-workflows>) — Create a local project from this template and validate its forms. This route is local-only; provider, credential, database, customer, publication, deployment, and production effects remain held.

## Purpose and audience

Proposal-only project record for defining an experiment protocol, controls, fixtures, runs, failures, interpretation, evidence, approvals, and closure receipts without implying execution, provider connection, publication, or production state.

- experiment owner

- protocol reviewer

- operator

- evidence reviewer

- approver

## Required or proposed record references

The list defines expected record classes. It does not assert that any instance exists.

- project record

- protocol note

- scope decision record

- milestone to-dos

- deadline and workback records

- dependency records

- owner assignments

- fixture or setup record

- run records

- failure and deviation records

- evidence records

- interpretation note

- approval records

- risk register

- closure receipt

## Route contract

The links below are this site's admitted canonical public records. Source-lane route suggestions are proposals only and are not represented as live or canonical until separately admitted.

[01**overview**/docs/project-templates/experiment-run/](<https://guthlabs.ai/docs/project-templates/experiment-run/>)[02**forms**/docs/project-templates/experiment-run/forms/](<https://guthlabs.ai/docs/project-templates/experiment-run/forms/>)[03**deadlines**/docs/project-templates/experiment-run/deadlines/](<https://guthlabs.ai/docs/project-templates/experiment-run/deadlines/>)[04**tools**/docs/project-templates/experiment-run/tools/](<https://guthlabs.ai/docs/project-templates/experiment-run/tools/>)[05**field guides**/docs/project-templates/experiment-run/field-guides/](<https://guthlabs.ai/docs/project-templates/experiment-run/field-guides/>)[06**qualification**/docs/project-templates/experiment-run/qualification/](<https://guthlabs.ai/docs/project-templates/experiment-run/qualification/>)

### Held source-proposed extensions

- /docs/projects/experiment-run/overview

- /docs/projects/experiment-run/protocol-and-controls

- /docs/projects/experiment-run/runs-and-failures

- /docs/projects/experiment-run/receipts-and-review

These extension paths are not generated by this record and must not be treated as resolving routes.

## Public claim boundary

Allowed items below are source-lane proposals, not verified current-state claims.

### Candidate claims allowed after source review

- This is a proposal for a project and form structure.

- The record distinguishes protocol, runs, failures, evidence, interpretation, approvals, risks, and closure.

- The design includes explicit deadlines, workbacks, dependencies, owners, revisions, and human review.

- The supplied native contract includes project collections, deadline payloads, provenance fields, and prototype or indexed app routes.

### Claims held

- That an experiment was executed or completed.

- That any provider, credential, database, customer, publication, export, upload, or production connection exists.

- That a result is valid, statistically significant, reproducible, safe, or qualified without reviewed evidence.

- That any route is a connected web feature or canonical backend.

- That an approval, deadline completion, evidence review, or closure occurred without its preserved receipt.

## Sources and evidence

These pointers bind the page to evidence. They do not grant authority or collapse verification into deployment.

- `source_record:project:experiment-run`

- `NotebookCollectionKind.project`

- `NotebookTodoPayload.dueAt`

- `Notebook Agenda deadlines/workbacks`

- `Notebook records provenance and revisions`

- `PointGuard persistent cross-app context surface`

- `/app/notebook/projects/`

- `/app/notebook/to-dos/`

- `/app/notebook/agenda/`

- `/app/notebook/approvals/`

- `/app/notebook/files/`

- `/app/notebook/capture/`

- `/app/notebook/agent-logs/`

- `APP_ROUTES /app/notebook/projects/`

- `APP_ROUTES /app/notebook/agenda/`

- `APP_ROUTES /app/notebook/approvals/`

- `APP_ROUTES /app/pointguard/`

- `ALLOWED_INSTRUMENTS:scientific-calculator`

- `ALLOWED_INSTRUMENTS:statistics-suite-descriptive-stats`

- `ALLOWED_INSTRUMENTS:date-duration-calculator`

- `PointGuard specialist-app ownership and held external effects`
