Repo Ops
How the .github repository is operated: how its changes are proved, how its files are generated, how it is released and which command does each job. This section says each thing once and links to the page that holds the detail, so read it as a map.
The repository is small on purpose. The organization's public profile, the installers of the machine, and commons/, the libraries that any company or harness of Intellectual Frontiers may use, with their specifications and generated tables. Everything else is in a private repository.
The pages of this section
- CI/CD: the workflows: the six workflows, what starts each, and how they are made (they are generated from typed definitions and never edited by hand).
- The release: one release, one package, and the three steps of it (
release plan,release apply,release publish) with the workflow that publishes. - The development loop: what you run between edits and before a push (
bun run dev:check,repoctl prove), and how a small step reachesmain. - The
repoctlcommand: every verb, what it does, its options and examples, generated from the program's own typed definitions.
The rules in one place
- Specification first. Change the specification in
commons/spec-kit/(or the library's own spec kit), then the code, then the tests. Every requirement has a test or says why it has none. - Generated files are never edited. A file under
commons/generated/and every.github/workflows/*.auto.ymlis made by a generator; change its source and runbun run repoctl sync. A test fails where one is stale. - Small steps to
main. Commit and push as soon asbun run dev:checkpasses; never force-push. Versions grow at the release and never per push. - No secret and no person's data, because the repository is public.
- The command line is the interface. Each job of this list is a verb of
repoctl, the same for a person and for an AI agent.
Where the evidence of all this is
The site shows how well the operation works as it runs: the Quality dashboard, the workflows and the DORA measures, the repository's health and what changed since the tests last ran. The concepts behind the loop are the release loop, proof by blast radius and the ladder.
Newcomers: start with the contributor path and how to add a library; this section is for the person or agent who keeps the repository running.