# Lifecycle and existing infrastructure alignment

Source review on 2026-10-04, INFD-WP-0007-T02/T03. No cluster inspection or
deployment occurred. Sources: access-engine `c0f3f25`, approval-engine `17f2225`,
audit-core `f1035a8`, railiance-platform `267814b`; local informed-decision
`deploy/sitting-admission.json` pins compact-sitting v11.

| Boundary | Finding and disposition |
| --- | --- |
| Store/schema | Lifecycle shares schema 4 and existing memo evidence; schema 1–3 migration/restart/backup tests pass. Legacy `save_memo` could write registered revisions without lifecycle events; it now refuses those ids. |
| Legacy UI | `memos_for` previously selected unpublished lifecycle records by named reviewer. Overview could show their ids as unavailable before authorization. Registered lifecycle records are now excluded pending explicit publication/review integration. Existing legacy review records remain eligible. |
| Runtime/audit | New pending events were invisible to readiness and admin inspection. Readiness now refuses immediately on pending lifecycle evidence; inspection reports record/event/pending counts without content. Receiver delivery remains unimplemented and pending rows are retained. |
| Access Engine | Current compact-sitting v11 contains exact-record human review and an attribute-admission branch with empty submitter/class sets. It does not admit `lifecycle.*`. Shared PolicyClient response validation is reused; a deployed review pin is not a lifecycle policy grant. |
| Approval Engine | Unbound registration creates no approval and cannot consume or accept one. Existing real-engine presentation/entry tests pass; publishing a lifecycle revision for binding still needs an explicit integration contract. |
| Identity | Human caller import reuses authenticated KeyCape session provenance. Workload lifecycle identity has only a trusted application interface; the private intake audience is not authorization for a new API. No issuer/audience/tenant claim is invented. |
| Platform | Source-phase requester composition still needs private listener/runtime configuration and CA-verified TokenReview. Platform's dependency-requirements file explicitly separates that source work from later native custody/rollout approval. Lifecycle HTTP development does not satisfy WP-0005-T05. |

Validation command:

```sh
INFD_APPROVAL_ENGINE_SOURCE=/home/worsch/approval-engine \
INFD_AUDIT_CORE_SOURCE=/home/worsch/audit-core \
INFD_STATE_HUB_SOURCE=/home/worsch/state-hub \
uv run --extra dev python -m pytest -q
```

Result before subsequent HTTP adapter development: **571 passed, 5 skipped**.
These use actual owner source APIs with synthetic identity/custody; they do not
prove native policy admission, live issuer custody or cluster routing. Lifecycle
policy admission and new event receiver/delivery contracts remain live work under
WP-0007-T02/T03; private intake runtime/admission delivery remains WP-0005.

Schema rollback requires a pre-upgrade database backup and reconciliation of any
subsequent writes. Simply deploying a schema-3 binary against schema 4 is not a
supported rollback. No production migration or image change was performed.