adr: gradual consumer migration from services to jobs

[0xgleb]

Motivation

ADR-0001 removes EventSourced::Services, so consumers need a reviewable path from inline command-handler side effects to durable jobs before they can take the breaking jobs API. st0x.liquidity has 10 EventSourced impls, st0x.issuance has 5, and issuance has an in-flight EventSourced migration that must not be disturbed.

Closes RAI-923.

Solution

• Add ADR-0002 to record the consumer rollout strategy: extract side effects into consumer-side jobs first, then land one mechanical jobs API bump per repo.
• Use liquidity as the lead repository because it already has conductor::job machinery and more aggregates exercising the pattern.
• Keep issuance extraction separate from its existing EventSourced migration, then apply the same mechanical bump only after extraction is complete.
• Place this PR at the top of the jobs stack because it documents how downstream repos adopt the API introduced below it.

[coderabbitai]

Warning

Review limit reached

@0xgleb, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 59 minutes and 58 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 92b90c0c-d44b-4187-93a9-b9297ed7a05a

📥 Commits

Reviewing files that changed from the base of the PR and between 2d6d324 and 8c7c6f7.

📒 Files selected for processing (1)

• adrs/0002-consumer-services-to-jobs-migration.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch adr/services-to-jobs-migration

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[0xgleb]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• adr: own the durable-job backend as an event-sourced apalis Backend #30
• adr: gradual consumer migration from services to jobs #19 👈 (View in Graphite)
• docs: migrate docs to the jobs model #20
• feat: migrate examples to the jobs model #16
• feat: replace EventSourced::Services with Jobs and wire atomic enqueue #15
• feat: add buffered JobQueue and apalis enqueue #14
• feat: add build_supervised_worker macro #13
• feat: job worker #12
• feat: add job module #11 : 1 other dependent PR (#31 )
• adr: jobs replace services #8
• master

---

How to use the Graphite Merge Queue

Add the label add-to-gt-merge-queue to this PR to add it to the merge queue.

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has required the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[linear-code]

RAI-923

[findolor]

Approved.

[graphite-app]

The text states "four aggregates that consume EquityTransferServices" but the table on lines 24-30 shows only two aggregates actually use EquityTransferServices: TokenizedEquityMint (line 27) and EquityRedemption (line 28). UnwrappedEquityRecovery uses UnwrappedEquityRecoveryServices and WrappedEquityRecovery uses WrappedEquityRecoveryServices. This count mismatch will confuse readers about which aggregates depend on the shared equity-transfer module.

# Should be changed to:
The shared equity-transfer module precedes the two aggregates that consume `EquityTransferServices`, so they don't grow divergent copies of the same SDK wrappers.

Suggested change

	request -> job -> outcome shape. The shared equity-transfer module precedes the
	four aggregates that consume `EquityTransferServices`, so they don't grow four
	divergent copies of the same SDK wrappers. The recoveries go last among
	request -> job -> outcome shape. The shared equity-transfer module precedes the
	two aggregates that consume `EquityTransferServices`, so they don't grow
	divergent copies of the same SDK wrappers. The recoveries go last among

Spotted by Graphite



Is this helpful? React 👍 or 👎 to let us know.