anchor.diff:  Packages need to be signed with a private origin key at buildtime. Generate an origin key pair manually by running the following command on your host machine:
   
   ```bash
  -$ hab origin key generate <ORIGIN>
  +hab origin key generate <ORIGIN>
   ```
   
   The `hab-origin` subcommand will place the origin key files, originname-_timestamp_.sig.key (the private key) and originname-_timestamp_.pub files (the public key), in the `$HOME/.hab/cache/keys` directory. If you're creating origin keys in the Studio container, or you are running as root on a Linux machine, your keys will be stored in `/hab/cache/keys`.
  
positive.code: 2. Install or [build](/docs/developing-packages/#plan-builds) the Chef Habitat package from which you want to create a Marathon application, for example:
  
      ```bash
      $ hab pkg install <ORIGIN>/<NAME>
      ```
  
  3. Run the Mesos exporter on the package.
  
      ```bash
      $ hab pkg export mesos <ORIGIN>/<NAME>
      ```
  
  4. This will create a Mesos container-format tarball in the results directory, and also print the JSON needed to load the application into Marathon. Note that the tarball needs to be uploaded to a download location and the "uris" in the JSON need to be updated manually. This is an example of the output:
  
negative.code: 3. Install or [build](/docs/developing-packages/#plan-builds) the package that you want to export.
  
      ```bash
      hab pkg install <ORIGIN>/<NAME>
      ```
  
  4. Run the Cloud Foundry exporter on the package.
  
      ```bash
      hab pkg export cf <ORIGIN>/<NAME> /path/to/mapping.toml
      ```
  
     > **Note** To generate this image, a base Docker image is also created. The Cloud Foundry version of the docker image will have `cf-` as a prefix in the image tag.
  