# Intake records

## APPROVAL-IN-0001 — Publish the shared Taxonomy request-claim schema

```yaml
id: APPROVAL-IN-0001
kind: intake
title: Publish the shared Taxonomy request-claim schema
status: open
origin: residual
origin_ref: APPROVAL-WP-0001
priority: medium
owner: approval-engine
repo: approval-engine
lane: blue
tags:
- residual
created: '2026-09-01'
updated: '2026-09-01'
description: >-
  NetKingdom statute §17 calls for a shared request-claim schema, but ownership
  remains unassigned. approval-engine published a local approval claim contract
  with explicit issuer, freshness, and binding digests and marked it as yielding
  to the future Taxonomy artifact. Route this intake when the Taxonomy owner is
  assigned; preserve mechanical replay and freshness semantics during adoption.
state_hub_intake_id: "01a05ef0-a034-7ef8-bae1-45840392f40e"
```

## APPROVAL-IN-0002 — Confirm the claim envelope on the PEP consumption path

```yaml
id: APPROVAL-IN-0002
kind: intake
title: Confirm the claim envelope on the PEP consumption path
status: closed
origin: coordination
origin_ref: APPROVAL-WP-0002-T05
priority: high
owner: gate-house
repo: approval-engine
lane: blue
tags:
- decision-request
- cross-repo
created: '2026-09-06'
updated: '2026-09-06'
resolution: >-
  Resolved 2026-09-06. Confirmed in full as GH-DEC-2026-005 (recorded at
  gate-house as GH-IN-0002 and closed) and accepted as FLEX-DEC-2026-006. The
  approval-claim is the step-1 artifact; ActionAuthorization is not required
  and MUST NOT be served from the claim endpoint; PEPs validate across the
  claim and the step-2 DecisionEnvelope. The provenance.authority ==
  state-hub requirement was struck explicitly. approval-engine's claim schema
  is unchanged. The deferred option D G3 revisit trigger is spent: G3 closed
  by adding a lifetime field, not by composition.
description: >-
  secrets-engine's PEP validator expects a flex-auth ActionAuthorization but
  calls GET /v1/approvals/{id}/claim, which serves approval-engine's governed
  approval-claim. GH-DEC-2026-003 already names the claim as the step-1
  artifact, and ActionAuthorization is an unratified flex-auth proposal absent
  from gate-house and state-hub. Requests gate-house confirm the claim is the
  step-1 artifact and that ActionAuthorization is not required on that path;
  a ratified post-decision ActionAuthorization is recorded as a deferred
  option with revisit triggers. Full request in
  docs/gate-house-decision-request-claim-envelope.md. Does not gate
  APPROVAL-WP-0002-T03.
state_hub_intake_id: "01a073e3-2338-7168-b69d-0f699769550f"
```

## APPROVAL-IN-0003 — flex-auth → access-engine repository rename: confirm no live repository coordinate remains

```yaml
id: APPROVAL-IN-0003
kind: intake
title: "flex-auth → access-engine repository rename: confirm no live repository coordinate remains"
status: open
origin: cross-repo
origin_ref: FLEX-WP-0020
priority: low
owner: approval-engine
requested_by: flex-auth
description: >-
  flex-auth is renaming its repository coordinates to access-engine (old slug
  flex-auth, new slug access-engine; repository UUID
  fda8ad85-a7d7-4055-8f21-902a533e59df and Forge ID 42 unchanged; runtime and
  product names stay flex-auth per FLEX-DEC-2026-013). Required change here:
  confirm no live repository URL or path to flex-auth remains in this
  repository, and retain product/runtime terminology. The live rename
  (FLEX-WP-0020-T06) has not happened; act after flex-auth announces that
  access-engine resolves, and record completion evidence here. Request
  message: 2523510b-79d6-4123-b550-6386dae4d464.
```