Proof

Proof you can inspect

Before you hand code to an agent loop, you should know what can be verified. Hal uses source, docs, license, commands, and reviewable output—not fake logos or invented adoption metrics.

Source

Public GitHub repository

Review the code, README, releases, issues, and license directly instead of trusting a marketing badge.

License

MIT license stated in the site footer

The site surfaces the license claim plainly and routes developers to the source repository for confirmation.

Docs

Command-forward workflow

The docs show the actual loop commands: init, plan, convert, validate, run, and review before merge.

Ecosystem

ReScience Lab context

Hal is part of the ReScience Lab toolchain for agent workflows, pages, research, knowledge, and publishing.

Why this is not a testimonial page yet

Placeholder logos and anonymous praise create the shape of trust without giving developers anything to verify. This page avoids customer, adoption, star-count, or testimonial claims that are not sourced in the repo.

What would make testimonials publishable?

Add named quotes only when the person, company, permission, and exact wording are available. Until then, Hal should earn developer trust with source, docs, license, commands, and transparent product behavior.