# 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
12 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-0008 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.