# Adoption review package

EMERGENT-WP-0002 remains the live work record. This is the concrete review
package for its remaining gates; it is not an approval or a completed rollout.

## Doctrine and publication — T02 / T09

Requested reviewers: gate-house, net-kingdom, access-engine, security-canon;
tenant/zone/credential/observation owners for their respective mappings.

Review `docs/decisions/EMERGENT-DEC-2026-001-integration-profile.md`,
`docs/operational-contracts.md`, `docs/netkingdom-integration-map.md`, and the
14 cards. Decide whether these are an accurate orientation profile of current
owner boundaries and where the profile should be published/linked long term.
Specifically settle the reference-evaluator boundary, historical Gate-House
broker label, unavailable containment, build-mode limits and orthogonal scope
dimensions. This asks for documentation/integration disposition, not runtime
privilege or an amendment by an agent to its own authority.

Local disposition: source-backed, non-normative pilot. Existing owner contracts
continue to govern. No outside repository's policy or service was changed.
Eight instruction-file additions in four repos point to the common package;
their exact block has a tested rollback in `tools/pilot_entrypoints.py`.

## Agent sessions and independent evaluation — T05 / T07 / T08

The provider reports in `docs/evidence/` separate file-reading proof, scenario
answers, client/model metadata, and the implementing agent's semantic review.
They are not independent whitehat evidence. Requested next review:
whitehat-security applies its own offline adversarial judgment to the package,
retrieval tests and scenario corpus; no live targets or attack execution are
requested by this package.

Actual resume/compaction behavior and governed glas-harness sessions remain
separate proofs. The reload code is tested, and fresh sessions are exercised;
neither proves what an actual provider preserves after compaction. Honor the
blocked/unverified owner profile states. CUST-WP-0073 and GLAS-WP-0012 already
own credential/isolation/readiness concerns; this package does not close them.

The four real-repository read-only pilot reports cover doctrine, access,
tenant-envelope escalation and production-change routing. These are bounded
comprehension proofs, not live-effect exercises or broad tenant assurance.

## Fleet adoption — T09 / T10

After the above gates, publish an exact reviewed release, validate any changed
source references, and use the existing authorized standing-notice process to
track reach. Track understanding with scenarios rather than acknowledgments.
No global agent configuration or fleet broadcast was installed by this pilot.

Retain the 30-day source review deadline, source-change invalidation, and
withdrawal handling. A source check is not current authorization. Do not mark
the workplan finished until its provider, owner and rollout evidence exists.

## Decision surface and procedure handoff — release 0.2.0

Review `docs/decision-runbook-integration.md` and the two new journey cards.
`docs/decisions/profile-adoption-intake.draft.json` is an unsigned, unsubmitted
packet for the existing adoption question, checked against the real owner
validator with a synthetic test grant. Confirm class/group and submission route
with informed-decision; no grant or live intake service is assumed.
The native orientation pack prepares evidence only. It does not resolve the
existing RBT-WP-0006 execution decision or implement an authorization gate.


## Current closure audit — release 0.2.1

Review the corrected exact-release unsigned draft and
`docs/evidence/2026-10-03-closure-attempt.md`. The 14-card profile now explicitly
routes withdrawn credential guidance to its source owner/ops-warden and missing
events to their emitting source owner. The completion audit preserves failed
full runs, bounded retry passes and unresolved owner/provider/independent gates.
EMERGENT-WP-0002 is blocked; this review package does not claim adoption.


## Owner review and corrected release — 0.2.2

The current unsigned draft binds 0.2.2, digest
`19de26540c693b94ac8c19d7ed2ddd901acbc828c9b8a78b44c1a43ca468222c`.
`docs/evidence/2026-10-03-owner-reviews-and-022-fixes.md` indexes the owner
reviews, concrete publication/distribution proposal, Whitehat findings and
local fixes. Technical reviews retain 0.2.1 pins; they are not human adoption.
Whitehat close-out and independence acceptance remain incomplete after its
platform stop. Provider/continuity, pilot and rollout gates remain live.

## Source re-pin — 0.2.3

The current unsigned draft binds 0.2.3, digest
`60f8811c6b94b30d357a0d9e5022f2a8ea52e69b47138d3a536755f3295310b5`.
It re-pins Informed Decision at `f0c60637` after that owner's workplan recorded
the unadmitted 0.2.2 route. No card, intake, grant, or authority change is
included. The draft is still unsubmitted. See
`docs/evidence/2026-10-03-023-source-repin.md`. Provider evidence must be
renewed for this digest before it can count toward T05 or T07.

## Offline intake reconciliation — 0.2.4

The current unsigned draft binds 0.2.4, digest
`025aab4f38246219c924bc94954e70ea0e6e7f72bcaf8d4344cd599602d345c3`.
It reviews published Informed Decision revision `15c330cc`: offline intake
service, schema-3 ledger, empty registries, and the doctrine constraints on
retry, PDP eligibility, `view_hash`, `human_control`, and asserted `drafted_by`.
No live listener or grant is claimed. Whitehat's 0.2.3 library acceptance does
not cover this seal. See `docs/evidence/2026-10-03-024-offline-intake-repin.md`.