ORIGINAL FICTIONAL BUILDER ATTRIBUTION LEDGER Teaching labels, not an API schema, actual trades or reward eligibility proof. Assume valid third-party matches carrying builder ALPHA for F1/F2/F3. F1 40shares*.60=24.00 F1 duplicate delivery=0additional F2 60shares*.60=36.00 F3 50shares*.40=20.00 O4 accepted/unfilled100*.50=0matched O5 rejected100*.50=0matched F6 builderBETA20*.50=0forALPHA Unique eligible ALPHA notional=80.00; duplicate overcount=104.00. One-sided lesson, not an official aggregate-volume definition. Separate fee example:400notional*25bps/10000=1.00builder fee. Stipulated platform fee .80 -> combined1.80, not live quoted costs. Separate daily-unit budget:70planned+20reserved=90;100-90=10. Assume each planned unit consumes one quota unit only for this model. Actual failure/retry/batch accounting requires the real service rules. BLANK REVIEW FIELDS Product/program/eligibility/confirmed status: SDK/protocol/signed builder identity: Request accepted/order identity: Matched fill identity/time/settlement state: Builder attribution evidence/correction history: Deduplication key/source coverage/exclusions: Program dashboard credit/time: Actual platform fee/builder fee/other costs: Accrued earnings/payout/reward approval separately: Relayer daily usage/non-relayer endpoint limits separately: