codeeval_adjudication_engine
I. Introduction and Scope
1.1 Purpose
The codeeval_adjudication_engine package orchestrates the business logic for Phase 2 of the MMM experiment (Blinded Comparative Adjudication). It is responsible for managing the flow of "Delta" concepts to the Adjudicators, ensuring strict adherence to the blinding and randomization protocols (BRD F3), recording votes with high integrity under concurrent load, calculating consensus in real-time (BRD F4.1), managing operational overrides required for live event resilience, and ultimately constructing the True Gold Standard (TGS) (BRD F4.2).
1.2 Scope
This package manages the logic between the backend data layer (provided by platform) and the front-end user interface.
| Area | In-Scope | Out-of-Scope |
|---|---|---|
| Workflow Management | Managing the state of concepts, Clinical Ideas, and the active Adjudicator Roster. | |
| Blinded Data Filtering | CRITICAL: Actively filtering the Concept Pool to ensure restricted information (e.g., Agreement Level) is never exposed. (BRD F3.3.2, NFR7) | Arm Anonymization (identity blinding) (handled by security_core). |
| Randomization | Ensuring the sequence of Delta concepts is randomized independently per user session. (BRD F3.2.1) | |
| Vote Recording | Recording votes within robust transaction boundaries utilizing concurrency control mechanisms. (BRD F3.4) | Implementation of the Data Access Layer (DAL) or locking mechanisms (handled by platform). |
| Consensus Calculation | Implementation of the Unanimity consensus rule, accounting for dynamic adjudicator assignments. (BRD F4.1) | |
| TGS Construction | Finalizing the TGS based on the Intersection and consensus outcomes. (BRD F4.2) | Statistical analysis (handled by sap_engine). |
| Operational Overrides | Logic for handling dynamic adjudicator removal/replacement (e.g., dropout) and triggering consensus recalculation. | The API endpoints or RBAC enforcement for overrides (handled by platform). |
1 maintainer
Metadata
1 maintainer
Release files for codeeval-adjudication-engine 0.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| codeeval_adjudication_engine-0.0.3.tar.gz | 53.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| codeeval_adjudication_engine-0.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 78.0 kB
Release files / codeeval_adjudication_engine-0.0.3.tar.gz
| Download URL | codeeval_adjudication_engine-0.0.3.tar.gz |
|---|---|
| Size | 53.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
04dc26025e22848c0676739d4abc97598de482a2c23435f2db6b51c5955f4c12
|
|
BLAKE2b-256 checksum How to use checksums |
bf57dd120ffb8c27122631c42ef7d506cc4f9add6fd702eb4f0ba8f48e4892e0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2025.
Transparency logRelease files / codeeval_adjudication_engine-0.0.3-py3-none-any.whl
| Download URL | codeeval_adjudication_engine-0.0.3-py3-none-any.whl |
|---|---|
| Size | 24.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
933d33b4fcbec5f1f7417954a307cce6b5844976828ff60a439fa4eae5728e90
|
|
BLAKE2b-256 checksum How to use checksums |
c6d923b061f9d9fdc125a80fc513a0bc2da4d567f1721471ac9a772feb7b6a4a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2025.
Transparency log
