Augh.  More clearly:

```ruby
# Rakefile -- autogenerated by 'octopress new' or 'octopress init' or some such.  Basically, the octopress command becomes, like the `rails` command, a tool for scaffolding a repo.
require 'rubygems'
require 'bundler/setup'
Bundler.setup
require 'octopress/rake'
Octopress::Rake.init!(self)
# Anything after here is up for the user to add to as he/she sees fit.
```

The relevant method would look something like this:
```ruby
# lib/octopress/rake.rb
module Octopress
  module Rake
    def self.init!(ctx)
      # A clever option would be to have it so that plugins could publish rake tasks as well and they'd be swept up in here too.
      ctx.instance_eval do
        Dir[File.join(File.dirname(__FILE__), 'tasks', '*.rake')].each do |fname|
          load fname
        end
      end
    end
  end
end
```

This gives people:

1. Easy, familiar discoverability (everyone knows "rake -T")
2. Easy integration points for plugins that want to extend CLI behavior.
3. An easy way for users to incorporate their own CLI behavior
4. A deterministic way of finding the project root with certainty.