Projects / homebrew-tap
The Homebrew tap that packages the released Knowledge Islands command-line tools.
A delivery repository, not an ecosystem authority. It implements the release transport that each tool repository owns: a validated formula per released tool, so Homebrew takes responsibility for installation, upgrade, and removal on a user's machine. It also fans a verified release event out to the repositories that consume one — this website among them.
Public platform repository · published
The problem
What this is for.
A curl-to-shell installer is fine once and awkward afterwards: nothing owns the upgrade and nothing owns the removal. The tap gives the released tools a single versioned install surface, so they are installed, upgraded and removed with the same commands as everything else on the machine.
Whose problem
Whether it is yours.
You want this if you are installing Knowledge Islands tools on macOS or Linux and would rather Homebrew owned them than a script you ran once and forgot.
Capabilities
What it actually does.
- One validated formula per released tool — currently ki, mgit, rig, git-almanac and techne.
- Implicit tapping: naming the tap in the install argument is enough, with no separate tap step.
- A verified release event fanned out to the repositories that consume one, this website among them.
State
How finished it is.
Published and in use, with five formulae packaged. A formula is bumped when its tool cuts a release, so the tap follows the tools rather than leading them.
Using it
How to start.
brew install knowledgeislands/tap/<tool> — naming the tap in the argument taps it implicitly.
Boundaries
What it deliberately does not do.
The tap holds no tool source. A formula points at an upstream release tarball and its checksum, which is why each tool repository remains the authority for what it released and the tap owns only the packaging.
Authority
What this repository owns.
Release transport for the command-line tools. Each tool repository remains the authority for what it released.
That boundary is deliberate. The ecosystem separates philosophy, engineering discipline, capability semantics, portable standards, and executable behaviour so that none of them can quietly absorb another. The full directory shows where this project sits relative to the rest.
Nearby
Other projects of the same kind.
ki-techne-harness— A runnable personal-controller execution fabric for the ecosystem.packages-stoa— Stoa: web components and styles that static sites share, rendered at build time.ki-website— The public publication layer — this site.
See every public project, or go straight to the released command-line tools.