Example use of module pattern and angular.module() usage to easily group classes by context... without using AMD.

PromisePathways.js

(function( angular, supplant ) {
    "use strict";

    angular.module( "Pathways", [ ] )

        /**
         *  Loader for topology data models
         */
        .service( "nodeLoader", function NodeLoader( $http )
        {
           // ...
        })

        /**
         * Create a topology diagram instance from `raw` node JSON data...
         */
        .service( "topology", function Topology()
        {
            // ...
        })

        /**
         * Processor will create a promise for each route and supports
         * building sophisticated chains of promises.
         *
         */
        .service( "processor", function NodeProcessor( $q, $timeout, $log )
        {

            //...
        });

}(window.angular, window.supplant ));

A few comments:

1. It would be easier not to have closures on the source files (save some whitespace & boilerplate), and then let the build process add closures.
2. There is the possibility of using CommonJS with browserify that should be discussed.
3. If the modules will be distributed individually, there will need to be a more in-depth approach for dependencies. The CI system could definitely upload each module in a tarball to a location, but it would have to be able to figure out dependent modules, and that may require some sort of bower.json or dependencies file in each component's folder. Note that the newest version of bower can install from a zip url: bower install ns-project.com/pathways.zip

edit: thought about commonJS some more, it's not worth the trouble it brings.