integration would provide a familiar interface to users, and simplify

  system administration for the organization.  It may be possible to build

  the system as a CiviCRM extension.  If so, we would get this feature for

  "free."

* Usable without JavaScript: For consistent mission advocacy, it's important

  that some organizations not require requestor to use JavaScript.  (e.g., Tor

  browsers typically have JavaScript disabled because it can undermine Tor's

  anonymity guarantees.)  It should be possible to submit payment

  requests without JavaScript.  The interface can be enhanced when JavaScript

  is available.

  Whether or not we do this in the first release probably depends on what

  framework we decide to build on.  If the framework itself requires

  JavaScript out of the box, it may make sense to have the first release go

  with the flow, then work to add JavaScript-free functionality in a later

  release.

  In any case, Javascript used will respect software freedom of users and, *if

  possible*, will adhere to LibreJS protocols.

## Requirements for later releases

These are features that we would ultimately like the system to have, but we

* Allow optional questions: With this, question conditions probably need to

be extended to address the case of "other question isn't answered"

* Additional exporters:

  * Export to SQLedger

  * [Certainly many more, feel free to add them here]

* Richer lifecycle management: A leader may need to approve a request before

  it's added to the books, like an employee's manager or a program director

* Various currency improvements:

   * Automatic currency conversion for validation (e.g., validate that an amount

     in an aribtrary currency is within a limit in USD)

   * Validate currency amounts from outside data sources: The main case for

     this is per diem, where many organizations use rates that are determined

     by another party (e.g., US GSA) and updated periodically.

   * Handle totaling the request based on currency (e.g., expenses can are in

     USD, EUR, CHR but the traveler may want payment in INR.)  Unclear what

     interface for this would look like, but real-time data about past

     currency rates might be available via an API somewhere, and we can use

     that to have the requestor give us "preferred currency for payment" so