-
Notifications
You must be signed in to change notification settings - Fork 11
Mejorar algoritmo de scoring #42
Copy link
Copy link
Closed
Labels
Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave programbackendBackend API and server workBackend API and server workcomplexity:high200 points - complex integration or architecture work200 points - complex integration or architecture workperformancePerformance and optimizationPerformance and optimizationtestingTests, CI and E2ETests, CI and E2E
Metadata
Metadata
Assignees
Labels
Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave programbackendBackend API and server workBackend API and server workcomplexity:high200 points - complex integration or architecture work200 points - complex integration or architecture workperformancePerformance and optimizationPerformance and optimizationtestingTests, CI and E2ETests, CI and E2E
Why this matters
The scoring model should make credit decisions more reliable and less sensitive to edge cases.
Problem
The current formula can be too sensitive to recent spikes or unusual balance patterns.
Scope
Implementation guidance
api/calculate-score.jsandapi/evaluate-and-mint.js.Out of scope
Acceptance criteria
Validation
npm run devand reproduce the scoring input.npm run buildto verify the app still compiles.PR requirements
Closes #42.Complexity