Skip to content

Mejorar algoritmo de scoring #42

@Kalebtron1

Description

@Kalebtron1

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

  • Adjust the scoring logic and keep the formula readable.
  • Document the expected score behavior for the affected cases.
  • Add regression coverage for the edge cases that motivated the change.

Implementation guidance

  • Work in api/calculate-score.js and api/evaluate-and-mint.js.
  • Keep the formula readable enough for future contributors to reason about.
  • Document the score inputs that matter most for the updated logic.

Out of scope

  • Rebuilding the entire credit system.
  • Changing the wallet or minting flow unless it is required for the score fix.

Acceptance criteria

  • PR includes the scoring change plus tests or reproducible validation steps.
  • Reviewer can reproduce the same input and observe the changed score.
  • The PR description states how the new result should be reviewed.

Validation

  • Run npm run dev and reproduce the scoring input.
  • Run npm run build to verify the app still compiles.
  • Confirm the updated score path matches the documented expectation.

PR requirements

  • Include Closes #42.
  • Describe the before/after scoring behavior.
  • Mention any test data used to verify the fix.

Complexity

  • High (150 points)

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave programbackendBackend API and server workcomplexity:high200 points - complex integration or architecture workperformancePerformance and optimizationtestingTests, CI and E2E

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions