Hi HN, We're building Ota. Ota is open repo readiness infrastructure. It makes software repositories runnable and trustworthy for human, CI, and AI agents. The problem we kept seeing is that the real truth of how a repo gets set up and run is usually scattered across READMEs, scripts, CI config, env files, and maintainer memory. That slows onboarding, causes local and CI drift, and makes automation brittle. Ota gives each repo one explicit operational contract for what it needs, how it becomes ready, and how tasks should run. The core flow is: - `ota doctor` to diagnose what is missing - `ota up` to prepare the repo - `ota run` to execute named tasks from the contract The product idea is "doctor first, contract second." We want it to be useful even before a repo is perfectly modeled. What we're trying to build is not just another task runner or dev environment wrapper. We think repo readiness is its own layer: something between the repo, the developer, CI, and now agents. We'd especially love feedback on: - whether this problem feels real in your repos - whether the contract model feels like the right abstraction - what existing tools you think are the closest substitutes If this sounds relevant to your repos, you can check it out here: https://github.com/ota-run/ota |