# Founder-led pilot delivery

17 November 2026 | Five working sessions | No new external spend

This is an execution sequence for the internal pilot, not a promise of customer delivery dates. “Day” means a focused working session; supplier waiting time is tracked separately. The current build can complete the synthetic local work without waiting for contracting or external recruitment.

| Session | Work | Exit evidence |
|---|---|---|
| Day 1: Scope | Name the workload and owner, select the synthetic dataset, record objective, baseline boundary, target, exclusions and rollback owner. | Completed scope fields; source manifest; no unsupported customer assumptions |
| Day 2: Rehearse | Run the browser guided demo. Separately execute the isolated disk export/restore path. Keep their environment and timing scopes distinct. | Per-run results, original baseline, restored manifest and functional-check outputs |
| Day 3: Challenge | Run changed/missing-content and malformed-input cases; confirm a forged self-consistent bundle cannot override the retained source baseline. Exercise rollback and recheck the source. | Failed recovery attempts correctly detected; rollback result; source-preservation evidence |
| Day 4: Review | Review integrity separately from functional coverage. Complete the acceptance form without pre-filling business sign-off. Translate unresolved provider facts into precise evidence requests. | Supported local conclusion, Unknowns, Not tested checks and prioritised corrections |
| Day 5: Package | Demonstrate the pilot, export the evidence, record actual effort and choose whether a provider rehearsal is justified. | Portable package, concise result report, time ledger and one next scoped decision |

## Roles

- **Founder sponsor, Max:** owns scope, priorities, commercial decisions and acceptance of limitations. Existing authorisation covers this local build.
- **Operator:** preserves the original, executes the runbook, records failures and time, and keeps cleanup inside the run-owned boundary.
- **Reviewer:** checks the result against the retained baseline and the stated scope. Record when operator and reviewer are the same person; do not call that independent review.
- **Workload owner for a later customer pilot:** defines the business task, required permissions, acceptable loss and recovery objective. No external owner is assumed committed.

## Time and effort ledger

Record actuals. The previous charter's budgets and prices are not approved spending, and this ledger is not a quote.

| Date / operator | Task | Active minutes | Waiting minutes | Rework minutes | Evidence / issue | Repeatable step? |
|---|---|---:|---:|---:|---|---|
| Not recorded | Scope and source preparation | 0 | 0 | 0 | Not recorded | Not decided |
| Not recorded | Export / transfer preparation | 0 | 0 | 0 | Not recorded | Not decided |
| Not recorded | Restore and integrity checks | 0 | 0 | 0 | Not recorded | Not decided |
| Not recorded | Functional and permission checks | 0 | 0 | 0 | Not recorded | Not decided |
| Not recorded | Negative cases and rollback | 0 | 0 | 0 | Not recorded | Not decided |
| Not recorded | Evidence review and reporting | 0 | 0 | 0 | Not recorded | Not decided |

Zeroes above are empty worksheet defaults, not measured work or evidence that a task was free of labour. Record dataset count/bytes beside any throughput or duration comparison. Keep build/debug time separate from repeat delivery time.

## Prioritise the result

| Priority | Trigger | Next action |
|---|---|---|
| P0 | A run touches the original unexpectedly, discloses files outside scope or accepts an unsafe restore path | Stop the exercise, preserve evidence and correct the boundary before retrying |
| P1 | Missing/changed files pass; independent baseline is lost; required user task fails; rollback cannot be demonstrated | Block acceptance and fix the precise failure |
| P2 | Useful extra format checks, clearer wording or a repeatable manual step can be automated | Record and schedule after the core result is reliable |

## Gate to the first provider rehearsal

Choose one accessible owned workload, ordinary non-sensitive files and already authorised accounts. Obtain exact source/target plans, destination region, scope, required permissions and a recovery/exit path. Retain the source as authoritative and start with a small reversible copy.

The actual provider rehearsal must add independent download/restore, allowed and denied access tests and evidence for provider-specific dependencies. It cannot inherit a pass from the local simulator. Expand only after the workload owner accepts measured results and documented losses.

External customer recruitment, contracts, raw private-data transfers, new spending, public publication and production changes are not part of this increment. Before external contracting, resolve the contracting/IP entity and data-handling terms. Drafts and unanswered evidence requests remain drafts and requests.

Delivery materials. [Pilot scope](pilot-scope.html) · [Operator walkthrough](walkthrough.html) · [Acceptance worksheet](acceptance.html).
