diff --git a/intakes/intakes.md b/intakes/intakes.md
new file mode 100644
index 0000000..7db4949
--- /dev/null
+++ b/intakes/intakes.md
@@ -0,0 +1,34 @@
+# Intake records
+
+## AUDIT-IN-0001 — Proposed: audit-core takes the approval evidence half (security layer model v0.3 §9.4)
+
+```yaml
+id: AUDIT-IN-0001
+kind: intake
+title: 'Proposed: audit-core takes the approval evidence half (security layer model
+  v0.3 §9.4)'
+status: open
+origin: cross-repo
+origin_ref: net-kingdom security-layer-model_v0.3 §9.4
+priority: medium
+owner: audit-core
+requested_by: gate-house
+description: 'gate-house proposes that audit-core own the tamper-evident record of
+  approvals: issuance, use, supersession, and revocation emitted as audit events.
+  Rationale: principle 6 (signed or hash-chained manifests to prove a record set was
+  not changed, omitted, or truncated) is exactly what authenticated approval entries
+  need forensically, and audit-core independence is the property Canon core rule 13
+  wants — audit evidence protected from the actor being audited. What is NOT proposed:
+  the operative approval state. approval-engine owns the durable object, atomic supersession,
+  single consumption, and revocation, because those need mutable in-path current-state
+  semantics and audit-core operational custody is append-only Postgres by design;
+  coupling decision-time approval reads to the audit fabric would also make an audit
+  outage an authorization outage. Note audit-core INTENT lists policy decision making
+  as out of scope — this proposal respects that: approval evidence is a record of
+  what happened, never the authoritative answer to whether an approval is still valid.
+  Requested: assent, revision, or rejection. If audit-core would rather not carry
+  approval events as a distinct source, say so and gate-house will record the evidence
+  half as unowned rather than assume it.'
+created: '2026-08-28T20:35:09.148892Z'
+updated: '2026-08-28T20:35:09.148892Z'
+```