Intake AUDIT-IN-0002: register tenant-engine as a sender

Requested by tenant-engine TEN-WP-0011-T04. Attributive mutation
evidence, local outbox, non-blocking drain.

Assistant: grok
Assistant-Session: 01a04cea-e5e8-7081-a0fc-808ebbc35fa9

intakes/intakes.md

@@ -1,5 +1,38 @@
 # Intake records
 
+## AUDIT-IN-0002 — Register tenant-engine as an attributive audit-core sender
+
+```yaml
+id: AUDIT-IN-0002
+kind: intake
+title: 'Register tenant-engine as an attributive audit-core sender'
+status: open
+origin: cross-repo
+origin_ref: TEN-WP-0011-T04
+priority: high
+owner: audit-core
+requested_by: tenant-engine
+description: >
+  tenant-engine now emits mutation evidence through a local outbox
+  (audit-core.event.v1alpha1, source=tenant-engine, POST /v1/events).
+  The class is attributive and drain is non-blocking
+  (tenant-engine/docs/evidence-emission.md). Production cannot land
+  events until audit-core admits this sender: sender identity with
+  source tenant-engine, a projected token (no secret in Git; warden
+  route for custody), and NetworkPolicy if the current allow-list is
+  still user-engine only.
+
+  Envelope: schema_version audit-core.event.v1alpha1; tenant is the
+  affected tenant_id; action is the domain event type; resource
+  tenant:<id>. Duplicate event ids should 200. Credentials must not
+  travel via State Hub messages.
+
+  Requested: sender registration + token lane, or a correction if the
+  envelope needs a field this engine is not sending.
+created: '2026-08-29'
+updated: '2026-08-29'
+```
+
 ## AUDIT-IN-0001 — Proposed: audit-core takes the approval evidence half (security layer model v0.3 §9.4)
 
 ```yaml