secrets-engine/tests/fixtures/flex-auth-replay/PROVENANCE.md

# flex-auth T03 replay fixtures

Copied verbatim from `flex-auth/examples/secrets-engine/replay/` (commit
`9e10d1c`, `FLEX-WP-0021-T03`). Real `DecisionEnvelope`s emitted by the
published `secrets-engine.catalog-lane.lifecycle` v1 package via
`go run ./cmd/flex-auth check`, from `flex-auth/local` in `standalone` mode.

Vendored so the digest contract test is hermetic. Regenerate upstream and
re-copy if the contract version changes.

**Pinned here** (stable across runs, per the upstream README):
`binding.request_digest`, `provenance.policy_package_digest`,
`provenance.registry_snapshot_digest`, and the presence/absence of
`provenance.input_claim_digests.context`.

**Never pin:** `id`, `provenance.decision_time`, `lifetime.not_before`,
`lifetime.expires_at` — all move with the clock.
fix: exclude correlation fields from the flex-auth request digest Verified the digest join against flex-auth's T03 replay fixtures and found request_digest was hashing fields docs/canonical-request-digest.md excludes. The material is tenant, subject, action, resource, context only: id is correlation, policy_version lives in provenance, caring_context is hashed separately. This engine included all three when present. Because the join adopts the served request id, every real production request would have carried one, so the computed digest would have matched no issued decision and failed closed against every correct allow. Same unsatisfiable shape as the removed AUTHORITY constant. The old pinned constant was computed with the id inside the material, so it was wrong and its passing proved nothing. Replaced with fixture-driven tests over two real envelopes (vendored with provenance) plus a structural test that correlation fields do not move the digest. Both fixtures are needed: input_claim_digests.context appears only with a non-empty context. Also stops computing the native claim digest. The claim's binding.action and binding.target speak approval-engine's vocabulary while ours speaks the catalog's, and no mapping is published; flex-auth makes no cross-check and states the correspondence is ours via pdp_digest. A claim recording no pdp_digest now fails closed naming the missing mapping rather than comparing two different languages. That mapping is a prerequisite for destroy. 274 tests pass. Production still fails closed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M65ovP3eiiPHubibvWs9mD Assistant: claude-code Assistant-Model: opus Assistant-Process: 393550@bnt-lap001 Assistant-Session: 4bb359f9-1f12-4410-9e76-079cf23c82e4 2026-09-06 14:17:38 +02:00			`# flex-auth T03 replay fixtures`

			Copied verbatim from `flex-auth/examples/secrets-engine/replay/` (commit
			`9e10d1c`, `FLEX-WP-0021-T03`). Real `DecisionEnvelope`s emitted by the
			published `secrets-engine.catalog-lane.lifecycle` v1 package via
			`go run ./cmd/flex-auth check`, from `flex-auth/local` in `standalone` mode.

			`Vendored so the digest contract test is hermetic. Regenerate upstream and`
			`re-copy if the contract version changes.`

			`Pinned here (stable across runs, per the upstream README):`
			`binding.request_digest`, `provenance.policy_package_digest`,
			`provenance.registry_snapshot_digest`, and the presence/absence of
			`provenance.input_claim_digests.context`.

			Never pin: `id`, `provenance.decision_time`, `lifetime.not_before`,
			`lifetime.expires_at` — all move with the clock.