EngageNudge Intelligence
Open Attention Policy
A versioned, open format for describing how a site respects subscriber attention, plus a reference SDK to validate policies and compute a basic local score from the document alone.
What the format covers (v1)
Send budgets
Site-level daily campaign budget, subscriber daily/weekly caps, minimum spacing, and fatigue score threshold.
Quiet hours
Local send window (HH:mm) with IANA timezone. Routine sends respect the configured quiet period.
Dormancy
Inactive-day threshold and whether routine sends skip dormant subscribers.
Low-value send gate
Minimum content confidence required before a routine send is allowed.
Reference SDK
The MIT-licensed `@engagenudge/attention-policy-sdk` package validates v1 documents against the published JSON Schema and computes a 0–100 local policy score (rubric v1.0-basic). No subscriber telemetry or proprietary send models are required.
- Monorepo path
- packages/attention-policy-sdk
- JSON Schema
- schemas/attention-policy.v1.schema.json
Local policy score (v1.0-basic)
- Send budgets. Up to 40 points when enabled with reference-aligned caps and spacing
- Quiet hours. Up to 20 points when a local window is configured
- Dormancy. Up to 20 points when inactive subscribers can be suppressed
- Low-value gate. Up to 20 points when a confidence floor is enforced
The score reflects the policy document only. It does not measure live send behavior, click rates, or proprietary decision models.
Governance
Schema version bumps require a new integer `version` field and an updated JSON Schema. The public spec stays verified against the EngageNudge domain implementation. Decision-engine scoring, affinity models, and benchmark datasets remain product-internal.
Notification Respect Index →
Know when to nudge.
Know when a notification is worth sending.
The useful question is who should not get this one.