anchor.diff:  
   This section describes how Repour is intended to be employed within the collection of services that form a build system.
   
  -=== What Repour will do
  -
  -Repour provides these guarantees:
  +=== What Repour will do and not do
  +
  +Repour does not mirror or in any way store more from the origins than the files that are required to build from. In exchange Repour provides these guarantees:
   
   ==== Coordinate Immutability
   
  
positive.code: 
  Also, the repository provider _must not_ grant the following permissions to Repour and all other users:
  
  - Push non-fast-forward commits
  - Push existing tags (re-tagging)
  - Push non-fast-forward commits (force push)
  
negative.code: = Repour - Archival Code Service
  
  Repour archives source code from many untrusted origins into trusted git repositories. It supports SCMs like link:https://git-scm.com/[git], link:https://www.mercurial-scm.org/[hg], and link:https://subversion.apache.org/[svn], as well as archive formats link:http://www.libarchive.org/[like tar and zip]. Tools like link:https://github.com/release-engineering/pom-manipulation-ext[PME] can optionally be applied as ``adjust``ments, and the results archived alongside the unmodified sources.
  
  Why the name "Repour"? First, it contains the common short word for "repository" ("repo"); second, the action of "repouring" could be used to describe what the program does to the repositories.
  
  