EP050 Node 28 — Offline Attribution workflow
Boundary: deterministic local records only; no tracking transport, contact, routing, publishing, network, production data or external effect.
- Accept only a fully validated Node 27 structured-lead record with explicit granted consent and
external_action: false. - Validate the nested inherited Node 26 route and target/opportunity/asset/publication/search/CTA/destination/session/source lineage against strict, PII-free, HTTPS
.test constraints. - Require an explicit allowlisted attribution model, version and bounded confidence. Reject ambiguity rather than infer or fabricate lineage.
- Construct a deterministic
atr_ attribution ID from canonical input and model metadata, retaining consent and route context verbatim. - Persist only to caller-supplied local JSON storage. Identical replay is idempotent; an existing ID with different bytes is a conflict.
- Exercise the real offline Node 19→20→21→26→27→28 path while socket construction is blocked, plus negative, determinism, persistence, idempotency and conflict tests.
- Capture timestamped evidence and request allocator acceptance; do not self-declare 100%.