[Draft] Introduce generic post-processing framework

[mohamedelabbas1996]

Summary

This PR introduces a reusable and unified framework for post-processing in Antenna, providing a consistent pattern to implement and manage post-processing tasks.

List of Changes

TBD

Related Issues

TBD

Detailed Description

How to Test the Changes

TBD

Screenshots

TBD

Deployment Notes

TBD

Checklist

• I have tested these changes appropriately.
• I have added and/or modified relevant tests.
• I updated relevant documentation or comments.
• I have verified that this PR follows the project's coding standards.
• Any dependent changes have already been merged to main.

[netlify]

✅ Deploy Preview for antenna-preview canceled.

Name	Link
🔨 Latest commit	f46e88c
🔍 Latest deploy log	https://app.netlify.com/projects/antenna-preview/deploys/68cc1659b4d8730008200e9d

[mihow]

Thanks for thinking about the framework abstractly, @mohamedelabbas1996! This looks like a good start.

Another aspect to consider: How do we want to show the output of the post-processing functions in the UI and track what was applied an occurrence in the DB?

Right now we show the classification model that was used, the model type, and the date that the prediction was applied. I think we should add a new field for tracking the post-processing step that was applied as well.

Classification

• model
• date
• filter name / filter class or list of post_processing steps

Alternatively!

We could register each post processing step as an Algorithm. This may fit into our current structure more naturally with less effort (a Pipeline is already a series of algorithms applied).

It may work for some filters and not others. But most of them are types of algorithms. (rank rollups, tracking, etc).

In the AMI Data Companion we consider the tracking stage as the last algorithm applied.