Source: https://guthlabs.ai/docs/project-templates/experiment-run/forms/ project template / candidate # Experiment run โ€” forms The distinct forms record for Experiment run. This page is proposal-only. Status: **proposed**Lifecycle: **candidate** ## Record status **Record ID**: project:experiment-run **Parent lifecycle**: candidate **Page lane**: forms **Lane lifecycle**: proposed **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]() โ€” 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. ## Proposed form sections Each section is a candidate schema for inspectable records. Required-field presence does not establish factual truth. ### Intake Capture the experiment request, intended decision, and accountable people before planning begins. - experiment name - requestor - date submitted - business or research question - decision this experiment should inform - hypothesis or expected relationship - success definition - out-of-scope questions - priority - confidentiality or visibility level - intake reviewer - intake review due date ### Scope and protocol Define what will be tested and the bounded protocol that operators must follow. - objective - independent variables - dependent variables - controlled variables - control groups or baseline - sample or input definition - sample size or run count - inclusion criteria - exclusion criteria - measurement method - units and precision - protocol steps - stop conditions - safety or handling notes - known limitations - protocol version - protocol owner - protocol review status ### Milestones Break the work into reviewable stages with owners, outputs, and dates. - milestone name - milestone purpose - milestone owner - planned start - planned finish - required output - acceptance condition - status - completion date - completion evidence link - blocked reason ### Deadlines and workback Create explicit due items and calculate the sequence backward from the decision deadline. - decision deadline - final evidence deadline - interpretation review deadline - last allowable run date - setup readiness deadline - protocol approval deadline - intake completion deadline - workback anchor - calendar assumptions - buffer days - owner for each deadline - priority - recurrence candidate - completion state - revision note ### Dependencies Record prerequisites and external or internal blockers without implying that held integrations are connected. - dependency name - dependency type - description - required-by milestone - dependency owner - status - due date - evidence of readiness - failure impact - fallback or workaround - escalation owner - external system or provider name if applicable - connection state: not verified, held, or verified by supplied record ### Owners and responsibilities Make accountability explicit for every material activity and approval. - role - person or team - responsibility - decision authority - backup owner - availability window - handoff condition - acknowledgement state - assignment date - assignment evidence ### Fixtures and setup Define the physical, software, or procedural setup required for each run. - fixture or setup name - version or identifier - configuration - location or custody note - calibration or readiness state - setup owner - setup checklist - required files or references - pre-run inspection result - inspection date - inspection reviewer - known setup limitations ### Run plan and run records Plan individual runs and preserve observed outcomes, inputs, and operator receipts. - run identifier - planned date - actual start - actual end - operator - protocol version used - control or treatment label - input identifiers - fixture identifier - environmental conditions - planned measurements - observed measurements - raw evidence reference - run status: planned, ready, completed, failed, invalidated, or held - operator notes - reviewer disposition ### Failures and deviations Capture anything that invalidates, changes, or limits interpretation of a run. - failure or deviation identifier - related run - detected date - detected by - description - expected condition - observed condition - severity - immediate containment - impact on validity - rerun required - corrective action owner - corrective action due date - resolution evidence - review disposition ### Evidence and receipts Link source-labelled notes, files, captures, calculations, and review receipts to claims. - evidence identifier - evidence type - claim or result supported - source record or locator - file reference if applicable - capture date - created by - source SHA-256 if available - provenance note - revision - visibility - review status - reviewer - review date - limitations or missing context ### Interpretation Separate observations, calculations, interpretations, and unsupported conclusions. - analysis question - dataset or run set - calculation method - assumptions - observed result - uncertainty or variability note - interpretation - alternative explanations - unsupported claims explicitly held - recommendation - analyst - analysis revision - review due date ### Approvals Require human review for protocol changes, run validity, interpretation, and closure. - approval type - item under review - proposed decision - reviewer - review deadline - status: needs review, approved, or held - conditions - decision date - receipt or rationale - reopen trigger ### Risks Track threats to safety, validity, schedule, custody, accessibility, and interpretation. - risk identifier - risk statement - category - likelihood - impact - risk owner - mitigation - contingency - trigger - review date - residual risk - status - escalation path ### Closure Confirm that the experiment is complete, bounded, reviewable, and not overstated. - closure decision - completion status - all required runs dispositioned - failed or invalid runs dispositioned - evidence completeness check - interpretation approved - open risks - unresolved dependencies - lessons learned - follow-up project or to-do - retention or custody note - closure owner - closure date - closure receipt - public claims allowed - public claims held ### Accessible state contract - Every field requires a visible and programmatic label. - Required and optional fields must be stated in text. - Invalid entries require an actionable message linked to the field. - Blocked and Held states remain visible without relying on color alone. ## Supporting documentation fields These fields come from the app_features lane and remain separate from the primary operating form. ### Run identity Name and scope the experiment without implying approval or execution. - title - objective - owner - reviewer - status - tags - visibility - source references ### Protocol and controls Capture the planned method, variables, controls, fixtures, prerequisites, and stopping rules. - protocol summary - hypothesis - independent variables - dependent variables - controlled variables - control groups - fixture IDs - materials or inputs - prerequisites - safety notes - exclusion criteria - stopping rules ### Deadlines and workback Turn the intended run date into explicit local tasks and review gates. - target run date - protocol freeze deadline - fixture readiness deadline - materials readiness deadline - review deadline - analysis deadline - receipt deadline - timezone - task priority - task recurrence candidate - task tags ### Run log Record each planned or completed run with reproducible inputs and observed state. - run ID - planned or actual start - planned or actual end - operator - protocol revision - fixture ID - input values - environment notes - observations - completion state - deviation flag - linked files ### Failures and deviations Separate failed runs, protocol deviations, and unknown causes from successful observations. - failure ID - run ID - failure type - observed symptom - timestamp - suspected cause - evidence links - containment action - retest decision - review state ### Interpretation Capture analysis, uncertainty, competing explanations, and a bounded conclusion. - analysis question - calculation inputs - summary statistics - uncertainty notes - alternative explanations - interpretation - confidence label - reviewer comments - decision state ### Receipts and evidence Preserve provenance and review history for every material claim. - receipt type - claim or decision - source locator - source SHA-256 - record origin - linked records - attachment reference - revision - reviewer - approval state - notes ## Required or proposed record references No record existence is asserted by this documentation page. - 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 - protocol record - control record - fixture record - run record - failure record - interpretation record - receipt record - NotebookTodo records for deadlines and workback steps ## 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`