Know what a Phase 1 Evidence Package must contain

The outcome you are walking toward

A clear picture of what "Evidence Package" means at Phase 1 exit: a structured instrument mapped to the Pilot Charter, not a highlight reel. This page lists categories only. It is a public briefing aid — not a downloadable pack, and not a sample filled with invented results.

What this page is (and is not)

• Is: the category map every Foundation Pilot exit should cover before a Controlled Cohort decision.
• Is not: live customer metrics, ROI figures, logos, or a completed package from a named engagement.
• Is not: a substitute for conformance LEVEL honesty — LEVEL can be public; deep attestations stay on request.

Deal-specific evidence is shared through a diligence briefing when it exists. Until then, treat this leaf as template orientation.

When the package is produced

On the delivery path, Phase 1 — Foundation Pilot — exits with a Pilot Evidence Package among its artifacts (deployment phases). On the buyer path, that moment is Stage 5 — Evidence & Authority (buyer journey): turn pilot results into an institutional go or no-go.

Success criteria are written in Phase 0 / the Pilot Charter before the pilot runs. The package answers those criteria — it does not invent new ones at the finish line.

Categories the package must cover

Every Phase 1 exit package is expected to address these sections. Empty cells in the internal template mean "not yet collected," not "fill with theater."

1. Executive summary against Charter criteria — each Must-Achieve line marked Met, Partial, or Missed, with a pointer to evidence (or an explicit gap).
2. Operational metrics (Charter-agreed only) — baselines and pilot-window observations for metrics named in the Charter. No vanity KPIs bolted on at exit.
3. Agent traces and reconstructability — consequential actions reconstructable from the record (audit trail & evidence model), including mode and authority at the time (agent authority).
4. Offline continuity and reconciliation tests — critical loops exercised without uplink; gaps detected; rejoin outcome (offline contract).
5. Incident and integrity log — safety and integrity events, containment, residual risk; unresolved critical issues block a clean exit.
6. Authority posture — observe versus limited-act envelope during the pilot, and any Charter amendments.
7. Conformance status of deployed components — LEVEL per object where claimed; deeper evidence on request, never badge theater on a public page.
8. Lessons learned and playbook candidates — what worked, what did not, and candidates worth evaluating before network propagation.
9. Go / No-Go recommendation for Phase 2 — Go, Go-with-conditions, or No-Go, with named owners and explicit conditions.

What reviewers typically ask in each category

These are question shapes — not sample answers, and not invented results.

| Category | Reviewer asks | What counts as an honest answer | |----------|---------------|----------------------------------| | Charter summary | Did we meet what we wrote down? | Met / Partial / Missed plus a pointer — or an explicit gap | | Metrics | Which numbers were Chartered? | Only Charter-named metrics; name what you are not claiming | | Traces | Can an operator reconstruct the action without the presenter? | Timestamp, actor, mode, authority, outcome — or a listed gap | | Offline | Which critical loops ran disconnected? | Scenario class, result, reconciliation outcome | | Incidents | What is still open that should block exit? | Severity, containment, residual risk — none open is a claim that must be true | | Authority | What could agents actually do? | Observe vs limited-act envelope; amendments called out | | Conformance | What LEVEL is claimed where? | LEVEL labels only in public; depth stays briefing / NDA | | Lessons | What should not be propagated yet? | Candidates with evaluation status — not a victory lap | | Go / No-Go | Who owns the decision, and under what conditions? | Named owners; conditions stated; commercial language stays principles-only |

Evidence artifact types (labels only)

Internal packages tag sources so reviewers can find the record. Public surfaces name the types, not the exports:

• Charter verbatim criteria and metric names
• Time-bounded operational exports named in the Charter
• Reconstructable action / audit-trail records
• Offline-test and reconciliation worksheets
• Incident register entries
• Conformance register rows (LEVEL + evidence depth)
• Retrospective lessons and playbook candidates
• Named decision records for Go / Go-with-conditions / No-Go

How the exit review should feel

The close is evidence-first: restate the original criteria, walk the package (not a highlight reel), name what worked and what did not, state conformance posture, then recommend. Commercial commitment stays matched to proven value — pilot, then cohort, then network — the same discipline as Business-In-A-Box engagements.

Role-shaped rooms that prepare for this exit are mapped under who we brief by role.

Phase 1 exit walkthrough order (structure only)

This is the public skeleton of a Phase 1 Exit / Go-No-Go room (Script 7 on the delivery path; Stage 5 on the buyer journey). It is presentation order — not sample answers, not a filled package, and not commercial theater.

1. Restate original success criteria — Charter Must-Achieve lines, written before the pilot ran.
2. Walk the Evidence Package by category — sections above in order; not a highlight reel of wins.
3. What worked / did not / learned — lessons and playbook candidates with evaluation status.
4. Conformance status of deployed components — LEVEL labels only in public; depth stays briefing / NDA.
5. Recommendation — Go / Go-with-conditions / No-Go, with named owners.
6. What Phase 2 requires from both sides — conditions before Controlled Cohort (deployment phases).
7. Commercial and authority implications — principles only on public surfaces; dollars stay briefing / NDA until real numbers exist.

Close with an explicit decision and named owners — or an explicit stop. Diligence teams can continue from the diligence reading path.

Requesting a real package

If you are in an active engagement, ask your Engagement Lead for the filled instrument mapped to your Charter. If you are evaluating the platform, schedule a briefing or start from the diligence reading path. Public pages will not host fabricated sample results.