# P1-001 evidence pack — portfolio recovery certification

## Work-package charter

- **Task ID:** `P1-001`
- **Owner:** shared run-protocol and reliability maintainers; implementation
  owner: Codex
- **Accountable product:** shared V1–V9 consequential-pipeline control plane
- **Priority:** P1
- **Risk tier:** Critical duplicated-effect, stale-authority, lost-lineage, and
  false-certification risk
- **Dependencies:** RUN-002, RUN-003, RUN-005, HITL-003, OPS-001, and OPS-002
- **Scope of this increment:** fail-closed certification schema, reconciliation
  decision, typed blocker gate, root run-protocol export, and CI verification
  inclusion. This increment does not manufacture a product-pipeline inventory or
  deployed drill evidence.
- **Rollout strategy:** require each active consequential pipeline to appear in
  the authoritative manifest and independent complete observation, then attach
  fresh staging or production evidence for the exact pipeline revision and
  source commit before certification.
- **Rollback strategy:** revert the schema, export, verification target, and
  evidence record together. Never fall back to treating absent pipelines,
  omitted drills, hermetic fixtures, or stale receipts as passing evidence.

## Implemented certification boundary

`PortfolioRecoveryCertificationSnapshotSchema` defines one closed-world
certification input:

1. An `authoritative-complete` manifest names every active or retired
   consequential pipeline, product, owner, escalation, revision, and consequence
   class. At least one active pipeline is required, preventing an empty
   inventory from passing vacuously.
2. A separate `complete-snapshot` observation names the active runtime
   pipelines. Any manifested pipeline not observed or observed pipeline not
   manifested blocks certification.
3. Each active pipeline requires one certification bound to its exact manifest
   revision and the snapshot's exact 40-character source commit.
4. Every certification requires unique evidence for all six recovery drills:
   checkpoint/restart, duplicate delivery, stale approval, provider timeout,
   kill switch, and publication rollback.
5. Each outcome records environment, run, evidence, effect/rollback receipts,
   timing, pass/failure state, lineage preservation, and duplicate-side-effect
   count. Hermetic evidence remains useful for conformance but cannot certify an
   active deployed pipeline.
6. Freshness, deployed-environment, complete-lineage, zero-duplicate-effect, and
   independently reconcilable receipt requirements are evaluated separately so
   one green dimension cannot hide a failure in another.

The deterministic reconciliation result reports active, observed, and certified
pipeline counts; required and passing drill counts; success and
lineage-preservation basis points; repeated-effect count; and the complete typed
blocker list. `assertPortfolioRecoveryCertified` throws a typed gate error with
that same result whenever any blocker remains.

## Automated and adversarial verification

- The focused recovery-certification suite passes **12/12** cases covering the
  exact passing matrix, missing/unknown observed pipelines, missing/unknown
  certifications, wrong pipeline revision, wrong source commit, missing
  receipts, omitted drills, failed drills, broken lineage, repeated effects,
  hermetic-only evidence, stale/future evidence, duplicate identities,
  contradictory outcomes, vacuous all-retired manifests, deterministic
  reconciliation, and typed gate failure.
- The complete targeted run-protocol gate passes **68/68** tests across **6/6**
  files, including RUN-002/RUN-003/RUN-005 primitives and this P1-001
  certification layer.
- Focused ESLint passes with zero warnings and the contracts production
  TypeScript project passes with zero errors. The contracts spec TypeScript
  diagnostic reports no recovery-certification errors.
- Pre-commit linting, formatting, asset locking, convention ratchets, and V5
  document validation passed. The broad inferred pre-commit typecheck was
  bypassed only after the owning focused production typecheck and complete
  targeted run-protocol gate passed.

## Current blocker and negative proof

P1-001 is **not certified**. The repository does not yet contain:

- an owner-reviewed authoritative manifest of every active consequential product
  pipeline;
- an independently observed complete deployed pipeline inventory;
- fresh staging or production receipts for all six drills on every exact
  pipeline revision and source commit; or
- the production whole-host restore and external-provider reconciliation
  evidence already identified by OPS-002.

The passing tests prove that the certification gate rejects incomplete or weak
evidence; they do not prove that any V1–V9 product pipeline has supplied the
required deployed matrix. Both master-ledger P1-001 checkboxes therefore remain
open.

## Publication identity

- **Implementation source commit:** `249779de5035201d35ebc380cf2e49496da74d05`
- **Published at:** `2026-07-24T12:26:05Z`

| Artifact                                                         | SHA-256                                                            |
| ---------------------------------------------------------------- | ------------------------------------------------------------------ |
| `libs/contracts/src/run-protocol/recovery-certification.ts`      | `31a96a929281e93cf89102035c7578c8898a27efd224c2e92442cc3051bae520` |
| `libs/contracts/src/run-protocol/recovery-certification.spec.ts` | `73086bfcf332a8d9a3bb7837719551320524ac688dc0c08b17e523be1b87a77a` |
| `libs/contracts/src/run-protocol/index.ts`                       | `7049130209b8f8755b224b128ce703dc0e84e4ffc7bcf6baade8420f6f54038d` |
| `package.json`                                                   | `5a1dc0148c037e22d0df6728c6d1c7b91626535c23382135ef597ee744554114` |
