Time runs down the bright center. Every accepted choice keeps the pipeline moving. Every rejected choice branches away. Select an ADR chip to see the source behind the junction.
System timelineAccepted pathRejected branch
01 · DemandLive truth
Re-derive the Campaign shortfall
The Sourcing Controller reads current inventory, active Claims, available headroom, and the Campaign target. The shortfall exists only as a fresh decision.
One controller30 minute checkNo stored day plan
01
02 · ObjectiveOne purpose
Launch a small whole-pipeline Attempt
The controller chooses Open Profile inventory, general inventory, or bounded recovery. One Attempt carries one objective and one delivered-lead Claim.
10 to 15 LeadsParallel enginesObjective-qualified Claim
02
03 · DiscoverAdditive lanes
Search compiled supply chunks
Provider-neutral chunks route discovery through available Sales Navigator and regular LinkedIn lanes. Provider mechanics stay behind the Sourcing Provider seam.
Cheap deterministic checks remove obvious misses. Evidence Enrichment adds judgment facts. The sourcing judge decides final ICP fit across all provider lanes.
Cheap work firstEvidence before verdictOne membership rule
04
05 · PrepareSafe to contact
Prove channel readiness
Contact Enrichment proves reachability. LinkedIn provider identity is preserved at source time. Activity and contact-safety gates can stop the Lead before fanout.
One Lead Item owns the Lead snapshot. Channel Conversations reference it. Fanout waits until the complete Campaign Sequence copy is ready.
One Lead ItemShared SequenceTruthful eligibility
06
07 · DispatchDue now
Walk each Account on its own clock
The universal execution engine resolves the next action. Exact due times, work hours, caps, and small randomized intervals keep Accounts temporally isolated.
Universal walkerExact due timeRandomized launch
07
08 · OutcomeVerified truth
Verify, fold, and learn
An uncertain send is verified before retry. A reply on either channel halts the whole Lead. A hard bounce stops locally and suppresses globally only when evidence is strong.
No blind retryReply dominatesEvidence-scaled suppression
08
Pipeline invariant
One Lead, one business outcome.
LinkedIn and email can each carry a Conversation. Reporting folds both paths into one Lead-centric result, so channel detail never double-counts product success.
Format experimentCan one visual object show sequence, trade-offs, and source evidence without making the Architect choose between three document views?