# Phase 1 Evidence Manifest

**Status**: Test foundation established; runtime implementation not yet accepted.

## Source

- Git revision: record at validation time
- Working-tree status: record at validation time
- Feature: `001-enterprise-experience`
- Product coverage: one representative Workstation and one representative Server

## Required Evidence

| Gate | Evidence | Status |
|---|---|---|
| Specification | Requirements checklist 16/16 | Complete |
| Test foundation | Isolated Python, browser, deployment and fixture guidance | Complete |
| Migration | Versioned migration and rollback design | Complete |
| Backend contracts | State, error, operation, audit, authorization and entitlement tests | Complete |
| Browser journeys | Setup, interruption, readiness and WCAG evidence | Pending |
| Workstation | Clean install and recovery evidence | Pending |
| Server | Clean install and recovery evidence | Pending |
| Package provenance | Source-to-package and ISO checksum evidence | Pending |
| Pilot | Controlled pilot evidence | Not authorized |
| Approval | Product owner plus delivery/support | Pending |

## Review Boundary

The test harness adds only `tests/` and specification evidence files. It does not require runtime
product changes. Runtime work begins only after the harness and contract tests are reviewable.

## Foundational Contract Evidence

- Versioned, idempotent schema migration creates durable operations and audit correlation fields.
- Newer unsupported schemas are rejected before feature mutation.
- Customer-state and error envelopes expose stable, non-secret fields.
- Operation kinds and idempotency constraints are durable in SQLite.
- New operation creation requires an administrator identity server-side.
- Structured and text audit detail tests redact secret categories.
- Canonical and deployed license helpers are byte-identical.
- Isolated backend contract suite passed using synthetic in-memory SQLite on 2026-07-12.

## Artifact Record

Record source revision, ISO/package path, build timestamp, size, SHA-256, included portal/backend/
installer revisions, environment, results, known limitations, and reviewer for each candidate.