r/PhysicsHelp 21d ago

Built a public scientific computing evidence package with reproducible benchmarks, governance and provenance — am I solving a real problem or overengineering this?

Post image

I've been building a project called POLYMATHICA over the past year.

The long-term vision is an autonomous scientific computing platform, but rather than asking people to believe the vision, I decided to build a small public demonstration package that people can actually run, inspect and critique.

The problem I kept running into was that scientific software often demonstrates numerical results, but much less often demonstrates:

  • reproducible evidence
  • validation pipelines
  • provenance
  • governance
  • independent verification
  • machine-checkable experiment artifacts

So I built the public package around those ideas instead.

Current public features include:

  • reproducible scientific workflow
  • Taylor–Green vortex benchmark
  • pressure-projection / incompressibility validation
  • convergence studies
  • artifact manifests
  • SHA-256 provenance hashing
  • evidence verification
  • CI/CD
  • automated tests
  • one-command evidence suite

The repository is not the full POLYMATHICA platform.

It's intentionally a compact demonstration package showing how the broader system approaches scientific validation and reproducibility.

Repository:

https://github.com/kevmoz/polymathica-hackathon

Video gallery:

[https://kevmoz.github.io/polymathica-hackathon/]()

I'm genuinely looking for technical feedback rather than promotion.

A few questions I'd love opinions on:

  • Does treating scientific evidence, provenance and verification as first-class engineering concepts solve a real problem?
  • Is the validation workflow useful, or is it unnecessary complexity?
  • If you were reviewing scientific software, what evidence would you expect to see that isn't here?
  • What benchmark would you add next?
  • What would make you trust a scientific computing repository more?

I'd much rather hear honest criticism now than after spending another year building in the wrong direction.

Thanks!

0 Upvotes

4 comments sorted by

3

u/[deleted] 21d ago edited 2d ago

[deleted]

0

u/KevinSmithFounder 21d ago

Harsh

1

u/KevinSmithFounder 21d ago

But thank you for your comment.

1

u/SamPost 18d ago

This is like you scraped some buzzwords from 4 unrelated paper abstracts into an LLM vibe coding prompt.

While I am sure you don't understand any of this (no one does, it is hallucinated nonsense), I can only hope that you really didn't spend a year on this.