emergent-security/knowledge/cards/compatibility.md

Compatibility with the existing estate

The Emergent Security v0.8 text is generic architectural/reference material. This integration profile maps it onto existing owner contracts without amending those contracts or granting operational authority.

1. G9's historic Gate-House broker label is not the current Gate House role. Use gate-house for doctrine, secrets-engine for credential lifecycle, and OpenBao for custody. Ops Warden routes needs through those owners.
2. decide.py is offline reference conformance. Only access-engine renders the estate's operational authorization decision; never execute a reference allow.
3. Generic observer containment is future architecture. Kings Guard proposes; actual actuation requires an owned, implemented, authorized effect path.
4. HOT defaults are illustrative. The actual task delegation, owner policies, founder build directive, human decisions, and harness restrictions apply. Contradictions remain findings; no automatic choice of a permissive rule.
5. MODE @ SCOPE, L0–L4, temperature, zone identity, tenant and environment remain separate dimensions. The package carries no automatic privilege conversion.
6. Stale/conflicting owner prose remains a finding until owner evidence resolves it. Never advertise a live service, isolation, observation, or signature capability just because a reference implementation or interface exists.

The profile is a local integration interpretation of published owner boundaries. It is not cross-owner ratification of generic doctrine. Unresolved adoption and semantic changes are tracked under EMERGENT-WP-0002-T02/T09. A live action that depends on an unresolved interpretation must obtain the appropriate decision.

Source owner IDs (cite the relevant owner, not an invented umbrella): emergent-security, gate-house, access-engine, secrets-engine, zone-engine, tenant-engine, kings-guard, the-custodian, security-canon.