The controlling distinctionA package manifest proves materialization. It does not prove `prepare`, runtime exports, Cordis patch targets, reconciliation, or bootability.

Five gates define usable installation.

Materialized

Package bytes and manifest exist.

Built

Every declared runtime export exists.

Declared

The manifest names a valid DSH bundle patch.

Reconciled

The profile includes the dependency-managed layer.

A fifth gate is operational: the resolved config and an isolated boot must succeed. Never collapse these gates into one filesystem-existence check.

Retry to zero, or remove to known-good.

Reviewed scriptPermit one exact build

Rerun the original DSH command and require a zero exit.

Untrusted or brokenRemove through DSH

Require successful removal and compare the known-good graph.

Still ambiguousPreserve the profile

Stop writers and retain manifest, lockfile, workspace policy, and output.

Do not append the bundle manually.

A blocked Git `prepare` may leave `package.json` while omitting `dist/` or `lib/`. Manual activation converts an install diagnostic into a profile boot failure.

Primary evidence.

Make partial success explicit.

The complete runbook includes the rc.8 branch trace, classification matrix, reviewed retry, known-good rollback, unsafe shortcuts, an upstream policy decision, and twelve regression gates.

Read the complete runbook