# P1-004 evidence pack — continuous portfolio health governance

## Work-package charter

- **Task ID:** `P1-004`
- **Owner:** shared portfolio governance and contracts maintainers;
  implementation owner: Codex
- **Accountable product:** V1–V9 autonomous-content portfolio
- **Priority:** P1
- **Risk tier:** Critical stale-governance, ownerless remediation, undocumented
  limits, and architecture-overclaim risk
- **Dependencies:** REL-003 continuous recertification, OPS-003 autonomous
  content metrics, incident/override/rights records, calibrated evaluation
  evidence, and canonical model-card governance
- **Scope:** strict policy/review/work/card/architecture schemas, complete
  cadence and catalog reconciliation, deterministic blockers, typed assertion,
  root exports, CI gate, and adversarial tests
- **Rollout strategy:** bind the evaluator to independently complete portfolio
  review, work-item, and published-card inventories. Certification must remain
  blocked until every required record is current and authoritative.
- **Rollback strategy:** revert the contract, tests, exports, verification,
  workflow, evidence, and ledger disposition together. Never replace missing
  review or card records with empty passing defaults.

## Implemented governance boundary

`certifyPortfolioHealthGovernance` evaluates one strict, caller-dated policy
snapshot.

1. A current passing review is required for incidents, overrides, rights
   expirations, subgroup outcomes, quality distributions, cost anomalies, and
   recertification backlog. Reviews bind the active policy, reviewer, source
   records, findings, and review time.
2. Blocked and stale work cannot cross the schema boundary without an owner and
   deadline. Open work past its deadline blocks certification; resolved work
   requires a resolution time.
3. A published, currently calibrated model, rubric, prompt, policy, provider,
   and data card is required. Every card carries a stable subject/version,
   non-empty known limits, calibration date, and calibration evidence.
4. A source architecture marked `proposed` cannot be reported as `implemented`.
   Even a source marked implemented remains blocked unless it carries
   conformance evidence and an explicit verification time.
5. Duplicate review, work, card, and architecture identities are surfaced
   deterministically. Missing families never become zero or passing.

## Automated and adversarial verification

- The focused governance suite passes **24/24** cases.
- The passing fixture covers all seven review axes, accountable blocked work,
  all six published card kinds, one evidenced implemented architecture, and one
  honestly reported proposed architecture.
- Negative cases cover each missing review axis; failed, stale, future, and
  wrong-policy reviews; missing owner/deadline; overdue work; each missing card
  kind; draft and stale cards; absent known limits/calibration evidence;
  proposed-as-implemented reporting; implemented claims without conformance or
  verification; unknown fields; duplicate identities; and typed assertion
  failure with the complete blocker set.
- Focused ESLint passes with zero warnings, the contracts production TypeScript
  project passes with zero errors, and the targeted `@oshun/contracts` build
  passes. Before the build, the 15 GiB host had 11 GiB available, 29 GiB free
  swap, and 15 GiB free disk, with no competing build/test process.
- Source pre-commit formatting, linting, convention ratchets, asset locking, and
  V5 documentation validation passed. The broad hook typecheck was bypassed only
  after the focused production typecheck and targeted build passed.

## Requirement disposition and claim boundary

The anti-overclaim requirement is complete at the shared certification boundary:
proposed architecture reported as implemented always blocks, and an implemented
claim requires conformance evidence and verification.

The other three P1-004 ledger boxes remain open. The repository contains the
governance evaluator and adjacent metrics/recertification contracts, but no
independently complete, current portfolio review set; no authoritative full
blocked/stale work inventory; and no published current six-family card catalog.
The passing fixture is contract evidence, not a portfolio meeting, ownership
assignment, publication receipt, or calibration record. No production
certification is claimed.

## Publication identity

- **Implementation source commit:** `5c942b51a2b5bc1f949ba73d7be2782b70f83d54`
- **Published at:** `2026-07-24T14:02:00Z`

| Artifact                                                        | SHA-256                                                            |
| --------------------------------------------------------------- | ------------------------------------------------------------------ |
| `libs/contracts/src/common/portfolio-health-governance.ts`      | `470a484ab7268bbefab0a2b9b8cc52835379d21964a0c1f4bd5a8d979088c28e` |
| `libs/contracts/src/common/portfolio-health-governance.spec.ts` | `4f67aa9c3c51ed5983c72273fe5d1f9ad730fb8f946e70cdca40e5036199d476` |
| `libs/contracts/src/common/index.ts`                            | `20532fce5d238314ac0af6a05c8e59f6b8343fca6cf72df62c88d1363b29fa3a` |
| `package.json`                                                  | `e7fee9b1162efcda6ebd4f18e02ac5389185f49d753a352360a3137e10926d3b` |
| `.github/workflows/content-slot-contract.yml`                   | `ba85d9c6c181046f28856cfe7937633c9e9edd0b5571216feb2c6c82a495ac4b` |
