Pilot Design Kit · governed release 04
Make the pilot earn the right to continue—before it starts. Define one bounded hypothesis, the current baseline, affected-party input, measures, authority, incident handling, and precommitted stop and rollback conditions. Then preserve an explicit end-of-pilot decision instead of allowing a test to drift into deployment.
Go directly to the builder ↓ Private working space
Design one bounded pilot Nothing entered here is transmitted to Aloha AI. Do not paste confidential, privileged, personal, security-sensitive, or regulated information.
Restoring your local design… Jump to download and reset controls ↓
Do not start. 5 readiness gate(s) failed or unresolved.
01 Bound the testPilot title Name one bounded test. Testable hypothesis State what should change, for whom, and what evidence could disconfirm it. Scope, exclusions, and prohibited uses Define users, setting, workflow, consequences, and what the pilot must not do. Current baseline Record the current process, performance, harms, burden, and comparison method. Duration, sample, and end date Prevent indefinite testing and quiet expansion.
02 Assign authority and voiceAccountable owner Name the person with authority to stop the pilot. Required reviewers Identify domain, privacy, security, accessibility, legal, procurement, labor, or other review. Affected-party input and contestability How can affected people shape the design, report harm, challenge outcomes, and receive a response?
03 Precommit evidence and safeguardsData authority, minimization, retention, and prohibited data Record lawful authority, acceptable use, access, deletion, training restrictions, and limits. Success, harm, quality, and workload measures Include benefits, errors, false positives/negatives, human review burden, time, cost, and unintended effects. Disaggregation and equity checks Specify which groups, contexts, or edge cases require separate examination. Monitoring cadence and evidence owner Who checks what, using which sources, and how often? Incident handling and escalation Define reporting, containment, notification, investigation, and accountable response. Stop conditions Precommit thresholds or events that pause or end the pilot. Learning value cannot override them. Rollback and fallback Describe how to restore the prior process, preserve continuity, retrieve work, and remediate harm. End-of-pilot decision Name the authority and evidence needed to choose stop, revise and retest, or consider a separate deployment review.
04 Readiness gatesEvery gate must be evidenced as passed before the kit can stop saying “Do not start.” This is still not authorization.
Bounded purpose and hypothesis The task, intended benefit, people affected, exclusions, duration, and testable hypothesis are defined.
Status Unresolved / insufficient evidence Pass for this bounded pilot Fail / unacceptable condition Evidence, source, date, reviewer, and limits Baseline, measures, and evidence plan The current baseline, success and harm measures, disaggregation, evidence sources, and monitoring cadence are credible enough to learn.
Status Unresolved / insufficient evidence Pass for this bounded pilot Fail / unacceptable condition Evidence, source, date, reviewer, and limits Authority, review, and affected-party input An accountable owner, capable reviewers, and a practical route for affected-party input and contestability are named.
Status Unresolved / insufficient evidence Pass for this bounded pilot Fail / unacceptable condition Evidence, source, date, reviewer, and limits Data, incident, stop, and rollback safeguards Data authority and limits are documented, and incident, stop, rollback, and fallback paths are usable before testing.
Status Unresolved / insufficient evidence Pass for this bounded pilot Fail / unacceptable condition Evidence, source, date, reviewer, and limits End-of-pilot decision firewall A named authority will choose stop, revise and retest, or consider a separate deployment decision; learning value alone cannot excuse failed safeguards.
Status Unresolved / insufficient evidence Pass for this bounded pilot Fail / unacceptable condition Evidence, source, date, reviewer, and limits 05 Preserve uncertaintyUnknowns, conflicting evidence, and dissent Do not compress disagreement into a score or erase who raised it.
Deployment firewall
A pilot is not a quiet path to production. The end state must be stop, revise and retest, or consider a separate deployment decision. Completion, positive averages, or learning value do not erase failed safeguards.
Download pilot record Export portable JSON Delete local design