Guth
NewsDocs
Page actions
View as Markdown ↗
Explore MCP tools ↗

project template / candidate

Experiment run — tools

The distinct tools record for Experiment run. This page is proposal-only.

Status: proposedLifecycle: candidate

Record status

Record ID
project:experiment-run
Parent lifecycle
candidate
Page lane
app_features
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.

Authoritative app_features lane tools and interfaces

Canonical tools-page assignments

  • Notebook project workspace (interface · required) — Owns project grouping, record links, lifecycle, revisions, and local persistence.
  • Protocol editor (interface · required) — Provides structured fields for reproducible protocol and control definition.
  • Run log table (interface · required) — Supports repeatable run entry, filtering, sorting, deviation flags, and immutable run history.
  • Failure register (interface · required) — Keeps failures and deviations visible without conflating them with successful results.
  • Workback planner (interface · required) — Creates local NotebookTodo records with explicit due dates, priorities, tags, and completion state.
  • PointGuard room (interface · required) — Carries current experiment context across Notebook surfaces while keeping specialist records canonical.
  • Notebook records (record · required) — Preserve canonical IDs, provenance, source locators, hashes, revisions, links, attachments, and lifecycle.
  • Notebook Agenda (interface · required) — Shows source-bound deadlines and drafted schedule changes while holding provider writes.
  • Notebook Approvals (interface · required) — Provides local Needs review, Approved, and Held states with receipts.
  • Notebook Files (interface · required) — Stores source-labelled file references beside records without hidden upload.

Only the page's admitted lane is rendered as an assignment. Other lane inventories remain source records but are not merged here. Tool kind and required/optional status are preserved.

Authoritative lane instrument assignments

An instrument listed only for another lane does not become a tools-page assignment.

Use boundary

  • Confusing a planned protocol with an executed experiment.
  • Overwriting failed runs or protocol revisions and losing reproducibility.
  • Treating descriptive statistics or PointGuard projections as proof, prediction, qualification, or causal evidence.
  • Unverified fixture, material, safety, or environmental assumptions.
  • Silent timezone conversion causing incorrect deadlines.
  • Duplicate local IDs or stale browser state causing record collisions.
  • Sensitive experiment data exposed through shared screens, public routes, search, or attachments.
  • Accessibility failures in dense run tables, charts, dialogs, and color-coded statuses.
  • Accidental external effects through calendar, messaging, upload, publication, or provider controls.

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_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