Skip to content

Python port: identical algorithm, same test scenarios, same output shape #5

Description

@emtcmca

Roadmap candidate — gauging interest. If you would use a Python version, a � or a comment about your stack genuinely helps prioritize.

What: A transparent-confidence Python package implementing the identical algorithm: same dimensions, same weights, same warning codes, same 0–100 normalization, same action policy — verified by porting the full test-scenario suite.

Ground rules if/when this happens:

  • Algorithm parity is versioned: the Python port ships pinned to a specific algorithmVersion and cross-checks against the TypeScript reference outputs
  • Zero runtime dependencies there too (stdlib only)
  • Sequenced after the v1.0 API freeze — porting a moving API doubles the work

Not started. This issue exists to collect demand signal and design constraints.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is needed

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions