anchor.diff:              <div class="panel-heading" role="tab" id="headingGuidance">
                   <h4 class="panel-title">
                       <a class="collapsed" role="button" data-toggle="collapse" href="#guidance" aria-expanded="false" aria-controls="headingGuidance">
  -                        Design Guidance: Commentary
  +                        Design Guidance: SknStrategy
                       </a>
                   </h4>
               </div>
               <div id="guidance" class="panel-collapse collapse" role="tabpanel" aria-labelledby="headingGuidance">
                   <div class="panel-body">
                       <p class="lead">DO NOT FOLLOW THE RAILS WAY.</p>
  -                    <p>The MVC model is a classic and used with success, as is, for many applications.  However, there are many maintenance, scaling, and growth issues when the codeset exceeds a certain size or features set mix.
  -                    Understanding these growth issues, it is recommended that you apply a more traditional <strong>Domain Driven Design(DDD)</strong> or <strong>Object Oriented(OO)</strong> approach to building web applications, with Rails isolated as a Web Interface as much as possible.</p>
  -                    <p>This would involve treating all of Rails as a Web Interface or adapter, and isolating our application business logic from it.  Calling on Rails only when absolutely needed to exchange
  -                        results with the user.</p>
  -                    <p>However, this is not another Web Framework! It is a thought provoking alternative to the Rails Way. An alternative that still builds applications using the full capabilities of Rails, while keeping your business logic components separate from Rails.
  -                     This avoids the negative impact of Rails release changes, and enables your ability to easily add or change features.</p>
  -                    <p class="lead">This application source, and implementation, serves as a model for how web applications can be engineered without sacrificing longevity or major reworks.</p>
  +                    <p>The MVC model is a classic and used with success, as is, for many applications.  However, when the project's code-set exceeds a certain size or feature-set mix,
  +                      your ability to grow the codebase by adding new features and/or upgrading to the next release of Rails can be severely hampered.  This is no surprise as MVC was
  +                      conceived for small Web Applications.</p>
  +                    <p>Understanding these growth issues, it is recommended that you apply a more traditional approach to building applications that use the Web, by isolating or
  +                      treating Rails as a Web Interface as much as possible.</p>
  +                    <p>Although there are many application architectures and patterns to choose from, isolating Rails APIs yields the greatest value.  These five actions will
  +                      deliver that value:</p>
  +                    <dl class="dl-horizontal">
  +                      <dt>Remove from Controller</dt>
  +                        <dd>Create Service or UseCase classes to contain the code you would otherwise put into Rails Controller URL-Methods.</dd>
  +                        <dd>&nbsp;</dd>
  +                      <dt>Remove from Models</dt>
  +                        <dd>Collect all ActiveRecord invocations and methods into a one or more classes which follow the Repository or Provider pattern, suitable for dependency injection.</dd>
  +                        <dd>&nbsp;</dd>
  +                      <dt>Remove from Views</dt>
  +                        <dd>Limit controller instance variables to one nested hash of pure ruby values.  UseCase methods should return this object as the sole results object to be rendered as HTML or JSON to requester.</dd>
  +                        <dd>&nbsp;</dd>
  +                      <dt>Wrap APIs in helpers</dt>
  +                        <dd>Create a few View helpers to aid in the HTML rendering or controller interface; to minimize Rails View API changes and the number of partials needed.</dd>
  +                        <dd>&nbsp;</dd>
  +                      <dt>Use seperate Directory</dt>
  +                      <dd>Establish a namespaced directory structure to contain your application components; possibly <code>app/strategy</code></dd>
  +                    </dl>
  +
  +                    <p>Having your business or application logic in PORO class containers, improves your understanding of its components and your ability to add or enhance features.  Depending on how successful
  +                      you were in separating your application code from Rails you may be able to run your full test suite by injecting memory-based dependencies for testing rather than Rails based dependencies; and never even startup Rails!</p>
  +                    <p>However, the <strong>SknStrategy</strong> is not another Web Framework! It is a thought provoking alternative to the Rails Way. An alternative that still
  +                      builds applications using the full capabilities of Rails, while keeping your business logic components separate from Rails; and enables you to easily add or change features.</p>
  +                    <p class="lead">SknServices serves as a model for how Ruby applications can be engineered to use the Web without sacrificing longevity or major reworks.</p>
                   </div>
               </div>
               <p>Rails is a Great Web Framework.  Your application can derive great benefit from Rails when engineered (Designed) to co-exist with Rails.</p>
  
positive.code:   # Application Services used in Controller methods
    ##
  
    def access_service
      @sf_access_service ||= ::AccessService.new({registry: self})
      yield @sf_access_service if block_given?
      @sf_access_service
    end
  
    ...
  
negative.code:               </code></pre>
  
                <pre><code class="language-ruby">
  class ContentProfileDomain
    ...
  end
                </code></pre>
  
              </div>
              <p>SknServices implements the SknStrategy as an example application.</p>
          </div>
  
          <div class="panel panel-info">
  