Add docs for how the price alert threshold check runs after each trade event is indexed

[Chucks1093]

Summary

Contributors working on the indexer or alert system need to understand when and how the alert threshold check runs — whether it is synchronous with the trade write, a separate job, or event-driven — so they can modify either system without breaking the other.

Scope

• Document the sequence: trade event written → price snapshot updated → alert check triggered
• Explain whether the check is synchronous or queued
• Describe how multiple alerts for the same creator are evaluated in a single pass
• Add a note on what happens if the alert check fails after a successful trade write

Acceptance Criteria

• Execution sequence is documented step by step
• Synchronous vs queued nature is stated clearly
• Multi-alert evaluation for a single creator is explained
• Failure handling after a successful trade write is described

ETA: 12 hours

---

Coordinate on Telegram

[ayaoba24]

@ayaoba24 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Kindly assign, please and thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ayaoba24 to this issue.

[jotel-dev]

@jotel-dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Pls Assign me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @jotel-dev to this issue.

[Johnpii1]

@Johnpii1 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello Sir,

I came across your project and I’m really interested in contributing.

I have experience with React for building responsive, user-friendly interfaces, and I’m also familiar with smart contracts and blockchain basics. I focus on writing clean, scalable code and improving user experience.

I’m a fast learner and ready to get started immediately. Please let me know the next steps.

Thank you.

Best regards,
Johnpaul

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Johnpii1 to this issue.

[extolkom]

@extolkom has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Assign me pls

ℹ️ Repo Maintainers: To accept this application, review their application or assign @extolkom to this issue.

[dubemoyibe-star]

@dubemoyibe-star has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Can I work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dubemoyibe-star to this issue.

[Ghadaffijr]

@Ghadaffijr has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would love to take this on

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Ghadaffijr to this issue.

[grantfox-oss]

🦊 GrantFox — @jotel-dev has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #507)
2. Your PR will be reviewed by the accesslayerorg maintainers

Good luck! Track your progress on GrantFox.

[drips-wave]

Congratulations, @jotel-dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @jotel-dev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊