# Contact Consent Review

> Decide and record conservative contact-consent transitions from bounded engagement, bounce, and consent evidence before any send.

- Skill: `runxhq/contact-consent-review` (Agent Skill, multi-file: 22 files)
- Install (CLI): `npx get-skill add runxhq/contact-consent-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/runxhq/contact-consent-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: runxhq (https://skillmd.com/u/runxhq)
- Updated: 2026-11-18
- Page: https://skillmd.com/skills/runxhq/contact-consent-review

---


# Contact Consent Review

Use this skill after collecting current contact evidence and before preparing a
campaign. It decides whether a contact remains eligible, needs re-permission,
must be suppressed, or needs human review. When policy justifies a state
transition, it records that decision in the operator's consent ledger with
optimistic concurrency. The native operation owns atomic commit, independent
readback and completed-key recovery.

This skill never sends a message and never mutates a mailing provider. The operator-selected mail delivery capability must read the current ledger
decision and provider unsubscribe/bounce state again at delivery time. This
skill does not wire that check into a sender; a delivery lane that cannot
enforce it must remain unused. The
ledger records the operator's policy decision; it does not replace provider
unsubscribe or bounce data.

## Operating model

The caller supplies one bounded engagement observation, the current consent
observation, and the policy threshold that applies to the contact. The evidence
must be marked `read` and versioned to the same ledger head that the method
reads through the store's `events.read`, in this skill's own `consent` stream,
which only it writes. The read returns only the latest event, its ledger
version and chain digest. Once a transition exists, its
recorded state must agree with the caller observation; matching versions alone
are insufficient. A conflicting or unrecognized ledger head requires review.
Missing, stale, ambiguous, or conflicting
evidence produces `human_review` without a write.

The deterministic decision order is conservative:

1. An unsubscribe marker stops automation.
2. An existing suppression is preserved; age alone can never relax it.
3. Supplied hard-bounce evidence suppresses when policy permits that automatic
   action, otherwise it stops for review.
4. A subscribed contact whose last engagement exceeds the decay threshold is
   moved to `re_permission`.
5. A clean, recent subscribed contact returns `verify` without writing.

Only `re_permission` and `suppress` can create transitions. A transition
decides whether a person can be sent to, so its append waits on a person's
approval of the exact event (`consent_transition`), whatever the run's
`effects`. The append uses the observed ledger version and the caller's stable
idempotency key. The public `provider_operation` is the complete native append packet;
a later head is not compared to the appended event. No-write decisions return
the actual initial observation and perform no second read. Observations are
snapshots, not locks or promises that state remained unchanged.

## Authority and finality

The store reader requires `store.read` and, only for an admitted transition,
the append requires `store.append`. These scopes authorize a bounded consent-ledger operation;
they do not authorize delivery or changes to a CRM or mailing provider. The
store instance owns storage and credentials.

A completed method can return a native version/idempotency conflict without
recording a transition. Inspect `provider_operation.result`, not the policy recommendation,
to determine the storage outcome. A repeated completed key returns the original
act: `provider_operation.already_done` preserves its receipt and plan even if later inputs
propose a different state. This skill does not relabel that original record
with the current proposal's state.

The supplied engagement/consent snapshot is not independently verified provider
evidence. `observed_state_source` distinguishes supplied evidence from a
recognized native record. Every result keeps `downstream_send.status` at
`not_run` and leaves `downstream_send.skill` null. Neither a stored policy
recommendation nor a sealed receipt proves campaign approval or delivery.

## Decisions and recovery

- `verify`: current evidence supports no transition. Nothing is appended.
- `re_permission`: engagement has decayed past policy and a subscribed contact
  must regain permission before sending. The transition is recorded once.
- `suppress`: hard-bounce evidence requires suppression, or an existing
  suppression is preserved. A write occurs only when state actually changes.
- `human_review`: evidence or policy cannot safely support automation. Nothing
  is appended.

If the ledger version changes, refresh the observation and evidence. Reuse a
key only for the same intended act; a distinct transition needs a new key.
The existing state checks may instead return a no-write review when stale
inputs are retried. Read the current native record and any original receipt
before deciding whether another transition is needed.

## Inputs and result

Provide the contact's key in the consent ledger, the observed version, stable transition key, bounded engagement counts and recency,
bounce policy, and current consent evidence. Counts must be non-negative and
the policy threshold must be between 1 and 3,650 days.

The public `list_hygiene_result` preserves the decision and reason, the observed
consent state, the native `observed_contact`, a human escalation only when review
is required, and the untouched downstream send boundary. An attempted append
returns the complete native `provider_operation` alongside that report; no-write
paths omit it.

## Agent rules

- Never invent engagement, bounce, consent, or version evidence.
- Never relax suppression from contact age alone.
- Never re-permission an unsubscribed contact automatically.
- Never describe an internal ledger append as a provider update.
- Never dispatch, send, or claim delivery from this result.

