SentImperior666

boot

Run the TrialError session boot ritual at the start of a research-harness orchestrator session on a TrialError-scaffolded program — verifies the law pin, binds the account, and surfaces dangling launches, unread inbox, budget headroom, and the last handoff. Use this at the start of an orchestrator session, or when SessionStart reported it could not boot automatically.

create-custom-visualization

Guided procedure to build a custom dashboard panel for YOUR program -- inventory what your program's stores actually hold, design within the dashboard's legibility rules, scaffold a panel.toml + builder.py extension under your own program root, write an offline test, and verify it live with `trialerror dashboard serve`. Use this when the user wants a bespoke visualization, chart, or view on top of their program's data that the six built-in dashboard panels (session/budget/jobs/gates/corpus/doctor) don't cover, or asks to "add a panel", "build a custom view", "visualize X on the dashboard", or "make a dashboard extension".

gate-critic

Run a gated artifact through its two-tier review — a structural validator pass, then a tool-locked, read-only critic subagent — record the verdict, apply the edit union, and verify every blocking edit before advancing the gate to registered. Use this whenever a gated-template artifact (e.g. a keystone) needs review before registration, or when a submitted gate is sitting unreviewed.

ideation-round

Run a lens-roster ideation round — assign stratified corpus slices to each lens (near/moderate/far over embedding distance, AMENDMENT-3 machinery), book and spawn each lens, then collect full-text feed posts under each lens's own name. Use this when the user asks for a brainstorm/ideation round, a multi-lens pass over the corpus, or an assumption-buster review.

ingest

Batch-ingest documents into a TrialError program's knowledge store — register a source, acquire a document under it, confirm the pre-ingestion cost-estimate gate, and drive the normalize/OCR -> chunk -> embed -> index pipeline to completion. Use this when the user hands you paper(s)/book(s)/rulebook(s)/web pages to add to the corpus, or when resuming a pipeline a prior session left mid-flight.

lit-review

Answer a research question against the ingested corpus, paper-qa-shaped — search, gather evidence with citations, draft an answer, then re-search on any gap before finalizing. Use this whenever the user asks a question that should be answered FROM the corpus (not from general knowledge), or asks for a literature summary/survey over what's already ingested.

verify-hypothesis

Run the hypothesis-vs-literature pipeline — stratified retrieve, contracrow-classify each evidence chunk, aggregate a label distribution, and write a typed verdict artifact. Use this when the user asks you to check, test, or verify a hypothesis against the corpus, or when a keystone artifact needs its central claim gated on evidence rather than asserted.

import-existing-project

Guided procedure to bring an existing (non-TrialError) research project into TrialError WITHOUT moving or restructuring it — inventory the foreign project, interview the user on what maps where, bridge via trialerror.toml [paths] + [paths].ingest_roots (or a directory junction or symlink when a true link is unavoidable), register sources, and validate with doctor + a search smoke. Use this when the user has an existing research project (papers, notes, a corpus, ledgers, a differently-shaped repo) organized their own way and wants to start using TrialError against it, or asks how to "import"/"switch to"/"migrate into"/"get started with" TrialError without losing or restructuring their existing files.

close

Run the TrialError session close ritual at the end of an orchestrator session on a TrialError-scaffolded program — refuses if launches are dangling, the law pin has gone stale, hooks were never armed, or inbox items are still unread; on success renders a new suffixed handoff and marks the prior one superseded. Use this at the end of an orchestrator session.