> Minute-level accuracy

alrighty then...

This readme reads like I already know the project, what it does, what problems it solves, and how it works.

> A precise project scheduling engine with minute-level accuracy for resource allocation and dependency management.

I have no idea what that means.

I write firmware, so does that mean this project is a scheduler for a while(1) based mcu project?

> pip install scriptplan

Oh, it's python. ok, so it's a "resource allocation and dependency management" engine.. for a python project? I mean, I'm using pip to install it, so it's not a daemon style engine that my project can hook into, right?

> # Generate JSON report to stdout

> plan report project.tjp

Oh, it IS some kind of daemon or service that runs when I install it with pip?

> Certification Level: Airport-Grade / Mission Critical

Okay, so is there a standards bureau that certified it? if so shouldnt there be a certification number somewhere? then maybe I could figure out what this does.

Read to the end, I still don't know what the first line in the readme means. Maybe I need to look up 'TaskJuggler'?

> Credits to TaskJuggler for the original project definition language and concepts.

That's understating it.

Looks like (from conveniently-not-removed `.issue.db`) the entire project was made over last weekend by LLM-porting huge chunks of TaskJuggler from Ruby to Python, then vibe-coding in a loop until it started working. It begins with a chain of issues like

> Port Project.rb to core.project

> Port ProjectFileParser.rb to parser.tjp_parser

> Implement the main scheduling loop. Reference `Project.rb` method `scheduleScenario` and `Task.rb` method `schedule`.

> Make it work. [...instructions on how to test it...] if that doesn't work, you need to investigate why, create issues and solve it.

From that point, the LLM was making most of the issues itself. And finally, 12 hours after the first issue was created:

> remove any trace of the task juggler project.

EDIT: attribution aside, TaskJuggler is GPL and porting to another language preserves GPL virality, so AFAIK by relicensing they’re violating the license here.

So it's (per [0]) a license (and therefore copyright) violating vibe-coded port and relicense of another project, with a whole bunch of "certification" ("mission critical", "airport-grade:) claims with no reference to a certifying authority? From a company [1] incorporated this year [2] whose website claims to offer "bank-grade" solutions based on the fact that their solution uses Postgres for workflows and banks use Postgres for money?

The sheer boldness is...impressive. And not in a good way.

[0] https://news.ycombinator.com/item?id=46135719

[1] https://rodmena.co.uk/

[2] https://open.endole.co.uk/insight/company/16472788-rodmena-l...