OUTCOME PLAYBOOK
Build commerce growth
Move from discovery and enrichment through audience selection, consent-aware outreach, checkout, and reconciled money movement.
- 1. Choose
- 2. Install
- 3. Run
- 4. Verify
- 5. Harden
- 6. Operate
#Choose the package boundaries
Required packages establish the local success path. Production and operate packages close durability and evidence boundaries.
Required
1. Discover
@absolutejs/discoverFinds candidates while retaining source identity.
Required2. Qualify
@absolutejs/enrichAdds typed attributes with provenance and confidence.
Required3. Select
@absolutejs/audienceBuilds repeatable segments and activation evidence.
Production4. Engage
@absolutejs/dispatchDelivers consent-aware outreach across channels.
Production5. Convert
@absolutejs/commerceOwns catalog, order, payment, fulfillment, refund, and aftercare state.
Operate6. Prove
@absolutejs/auditCorrelates provenance, activation, order, payment, and fulfillment evidence.
#Prerequisites
A canonical account-scoped identity model.
Provenance and consent retention requirements.
Idempotency keys for provider, order, and payment effects.
#Install the complete surface
BASH
bun add @absolutejs/discover @absolutejs/enrich @absolutejs/audience @absolutejs/dispatch @absolutejs/commerce @absolutejs/auditSmallest useful file tree
TXT
src/
discovery.ts # sourced entities
enrichment.ts # provenance-aware attributes
audience.ts # deterministic segment
outreach.ts # consent and dispatch
commerce.ts # order and fulfillment lifecycle#Run and verify
Build sourced truth
Discover and enrich one fixture entity without an external send.
Proof of success: Every accepted field retains source and confidence.
- 1. Choose
- 2. Install
- 3. Run
- 4. Verify
- 5. Harden
- 6. Operate
#Expected results
Every lead carries source and enrichment provenance.
Only consented audience members enter the dispatch workflow.
Checkout, fulfillment, refund, and aftercare share stable order/action identifiers.
#Development to production
DevelopmentFixture sources and memory adaptersProductionRate-bounded providers with durable checkpoints
External datasets, messaging, payments, and fulfillment fail independently.DevelopmentInline order effectsProductionLeased idempotent coordinators with quarantine
Ambiguous money and fulfillment effects require explicit reconciliation.#Failure decisions
Two discovered entities may be the same customer or supplier.
Check firstInspect provenance, confidence, and account-scoped identity before merging.
ThenQuarantine uncertain enrichment instead of overwriting canonical truth.
Checkout or cancellation has an ambiguous external effect.
Check firstReconcile payment and fulfillment independently by durable action id.
ThenResume only the incomplete side of the order lifecycle.