Partner Performance Scorecards · Documentation
Architecture
Partner Performance Scorecards's pipeline, its owned data, the events it emits/consumes, and what is out of scope.
← Partner Performance ScorecardsDeterministic rollup, no metered stage
The scorecard is computed deterministically from the shared core and #08's analyzed contracts — there is no LLM stage and no cost ($0). The composite weights (bookings 0.30, reviews 0.30, service 0.25, contract 0.15) and the under-performance threshold (62) are fixed, so the board is reproducible across server render, hydration, and tests.
Owned data, connections + out of scope
The app owns demo_eco_c6_scorecard (per-partner sub-scores, composite, trend, flagged). It consumes the contract.analyzed result from #08 (the contract sub-score) and the shared bookings (the booking sub-score). Scorecards are canonical/seeded only — there is no viewer-mutating path — so the data invariant is satisfied by construction. The honesty layer is inspector-only; the surface shows only the scores. Stage-2 reads demo_eco_c6_scorecard behind the same adapter surface.