Add "StartupStarterPackage" from "https://git.knownelement.com/RWSCP/StartupStarterPackage.git@master"

git-vendor-name: StartupStarterPackage
git-vendor-dir: vendor/git.knownelement.com/RWSCP/StartupStarterPackage
git-vendor-repository: https://git.knownelement.com/RWSCP/StartupStarterPackage.git
git-vendor-ref: master

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/README.md

@@ -0,0 +1,61 @@
+# Redwood Springs Capital Partners - Startup Starter Package
+
+## Introduction
+
+Welcome to the Startup Starter Package! This is a collection of resources to help you go from idea to execution. It's useful for bootstrappers and those looking to raise funds (whether from RWSCP or other investors).
+
+This package of materials is in production use by the TSYS Group portfolio of companies who have vendored this repository into their bizprodop plan repositories.
+
+## Contents Overview
+
+In the vendor/git.knownelement.com/RWSCP directory you'll see six sub directories:
+
+- BusinessModelCanvas
+- LLCOperatingAgreement
+- PitchDeck
+- ReadySET
+- StartupStrageicFramework
+- WardleyValueMap
+
+Those represent vendored repositories that are each independently developed/maintained by RWSCP.
+
+Go to the [rwscp git page](https://git.knownelement.com/RWSCP) to engaage with the development process if you find any errors, have feedback etc. Also each repository has extensive documentation which we won't repeat here.
+
+Please see the next sections for a synopsis of the contents of each vendored repository.
+
+### Business Model Canvas
+
+This is a nice visual representation of your startups business model, It's useful as the second slide of your pitch deck (after your eleveator pitch).
+
+### LLC Operating Agreement
+
+This is the standard set of company bootstrap documents:
+
+- operating agreement
+- NDA
+- IP Assignment
+- corporate governance documents
+
+that RWSCP requires it's portfolio companies to adopt as part of taking investment from us.
+
+### PitchDeck
+
+This is the pitch deck template we require any startups seeking funding from RWSCP to use.
+
+It will heavily utilize the canvas, strageic framework, wardely value map assets.
+
+### ReadySET
+
+This is a standardized comprehensive set of software engineering templates that we require portfolio companies to fully complete as part of the submission for funding process.
+
+### Startup Strageic Framework
+
+This serveas as a framework for your startups board/management (and the RWSCP board member) to effectively manage the portfolio company.
+
+### Wardley Value Map
+
+This is where you create your Wardely Value Chain Map.
+
+## Build
+
+Please see the [build readme file](./build/README.md) for details of how to create an output artifact suitable for RWSCP submission.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/build/README.md

@@ -0,0 +1,20 @@
+# Startup Starter Package Build Process
+
+## Introduction 
+
+The goal of this build process is to create a RWSCP submission package.
+
+
+## Build artificats
+
+### Business Model Canvas
+
+### Operating Agreement
+
+### Pitch Deck
+
+### ReadySET
+
+### Strategic Framework
+
+### Wardley Value Map

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/build/build-BusinessModelCanvas.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/bash
+
+# Build the business model canvas artifact

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/build/build-LLCOperatingAgreement.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/bash
+
+# Build the LLC operating agreement

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/build/build-PitchDeck.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/bash
+
+# Build pitch deck artifact

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/build/build-ReadySET.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/bash
+
+# Build ReadySET artifact

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/build/build-StartupStrategicFramework.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/bash
+
+# Build the startup strategic framework artifact

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/build/build-WardelyValueMap.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/bash
+
+# BUild wardley value map artifact

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/build/build-submission-package.sh

@@ -0,0 +1,3 @@
+#!/usr/bin/bash
+
+# Build the full RWSCP submission package

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/LICENSE

@@ -0,0 +1,235 @@
+GNU AFFERO GENERAL PUBLIC LICENSE
+Version 3, 19 November 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+                            Preamble
+
+The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works.  By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
+
+When we speak of free software, we are referring to freedom, not price.  Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate.  Many developers of free software are heartened and encouraged by the resulting cooperation.  However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
+
+The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community.  It requires the operator of a network server to provide the source code of the modified version running there to the users of that server.  Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
+
+An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals.  This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+                       TERMS AND CONDITIONS
+
+0. Definitions.
+
+"This License" refers to version 3 of the GNU Affero General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this License.  Each licensee is addressed as "you".  "Licensees" and "recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy.  The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based on the Program.
+
+To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy.  Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other parties to make or receive copies.  Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License.  If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+The "source code" for a work means the preferred form of the work for making modifications to it.  "Object code" means any non-source form of a work.
+
+A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form.  A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.  However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work.  For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+
+2. Basic Permissions.
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met.  This License explicitly affirms your unlimited permission to run the unmodified Program.  The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work.  This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.  You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright.  Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions stated below.  Sublicensing is not allowed; section 10 makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+
+4. Conveying Verbatim Copies.
+You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7.  This requirement modifies the requirement in section 4 to "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy.  This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.  This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit.  Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source.  This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+
+    d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge.  You need not require recipients to copy the Corresponding Source along with the object code.  If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source.  Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.  In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage.  For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product.  A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source.  The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information.  But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed.  Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+
+7. Additional Terms.
+"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law.  If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it.  (Additional permissions may be written to require their own removal in certain cases when you modify the work.)  You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10.  If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.  If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this License.  Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License.  If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the Program.  Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance.  However, nothing other than this License grants you permission to propagate or modify any covered work.  These actions infringe copyright if you do not accept this License.  Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.  You are not responsible for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations.  If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.  For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based.  The work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version.  For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement).  To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License.  You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.  If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+
+13. Remote Network Interaction; Use with the GNU General Public License.
+
+Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software.  This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
+
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work.  The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
+
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time.  Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation.  If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions.  However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program.  It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     BusinessModelCanvas-Markdown
+     Copyright (C) 2024  RWSCP
+
+     This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero General Public License for more details.
+
+     You should have received a copy of the GNU Affero General Public License along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source.  For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code.  There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.
+
+You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/README.md

@@ -0,0 +1,7 @@
+This is the RWSCP template for business model/plan
+
+Sourced from/inspired by:
+
+- https://github.com/jerik/mdCanvas
+- https://gist.github.com/pierrebeaucamp/fa2fec4f859d8d9ce3d0
+- https://github.com/GeorgLink/Business-Model-Canvas-MD-template

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/Channels.md

@@ -0,0 +1 @@
+# Channels

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/Customer_Relationships.md

@@ -0,0 +1 @@
+# Customer Relationships

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/Customer_Segments.md

@@ -0,0 +1 @@
+# Customer Segments

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/Financial_Plan.md

@@ -0,0 +1,21 @@
+# Cost Structure & Revenue Stream
+
+
+| Costs | Startup | Year 1 | Year 2 | Year 3 |
+|---|---|---|---|---|
+|Item | $$$ | $$$ | $$$ | $$$ |
+|Item | $$$ | $$$ | $$$ | $$$ |
+|Item | $$$ | $$$ | $$$ | $$$ |
+| | | | | |
+|TOTAL COST | $$$ | $$$ | $$$ | $$$ |
+| | | | | |
+| **Revenue** |Startup | Year 1 | Year 2 | Year 3 |
+|Number of Customers | 0 | x | x | x |
+|Item ($$$ revenue per customer) | 0 | $$$ | $$$ | $$$ |
+| | | | | |
+| TOTAL REVENUE | 0 | $$$ | $$$ | $$$ |
+| | | | | |
+| TOTAL PROFIT | $$$ | $$$ | $$$ | $$$ |
+
+
+Please document your assumptions of how you arrived at the dollar estimates.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/Key_Activities.md

@@ -0,0 +1 @@
+# Key Activities

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/Key_Partners.md

@@ -0,0 +1 @@
+# Key Partners

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/Key_Resources.md

@@ -0,0 +1 @@
+# Key Resources

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2020 Georg J.P. Link
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/README.md

@@ -0,0 +1,88 @@
+# Name of Business
+This is a Markdown template for developing a business model using the Business Model Canvas.
+Add logo of the business here. Remove this description.
+
+## Summary of Business
+Add a description that is about the length of an evelvator pitch for the business.
+
+## Website of Business
+Add here a link to your website design.
+
+## Business Model Canvas
+Add a very brief summary of each section in this table and provide details in the linked documents. Remove this description.
+
+<table>
+  <tr>
+    <td rowspan="2">
+      <b><a href="Key_Partners.md">Key Partners</a></b>
+      <p>Who are our Key Partners?<br>
+      Who are our key suppliers?<br>
+      Which Key Activities do partners perform?</p>
+    </td>
+    <td>
+      <b><a href="Key_Activities.md">Key Activities</a></b>
+      <p>What Key Activities do our Value Propositions require?<br>
+      Our Distribution Channels?<br>
+      Customer Relationships?<br>
+      Revenue Streams?</p>
+    </td>
+    <td rowspan="2" colspan="2">
+      <b><a href="Value_Propositions.md">Value Propositions</a></b>
+      <p>What value do we deliver to the customer?<br>
+      Which one of our customer's problems are we helping to solve?<br>
+      What bundles of products and services are we offering to each Customer Segment?<br>
+      are different and <br>
+      worth paying <br>
+      attention</p>
+      <br><br><br><br><br>
+    </td>
+    <td>
+      <b><a href="Customer_Relationships.md">Customer Relationships</a></b>
+      <p>What type of relationship does each of our Customer Segments expects us to establish and maintain with them?<br>
+      Which ones have we established?</p>
+    </td>
+    <td rowspan="2">
+      <b><a href="Customer_Segments.md">Customer Segments</a></b>
+      <p>For whom are we creating value?<br>
+      Who are our most important customers?</p>
+    </td>
+  </tr>
+  <tr>
+    <td>
+      <b><a href="Key_Resources.md">Key Resources</a></b>
+      <p>What Key Resources do our Value Propositions require?<br>
+      Our Distribution Channels?<br>
+        Customer Relationships?<br>
+        Revenue Streams?</p>
+    </td>
+    <td>
+      <b><a href="Channels.md">Channels</a></b>
+      <p>Through which Channels do our Customer Segments want to be reached?<br>
+      How are our Channels integrated?
+      How are we integrated with customer routines?</p>
+    </td>
+  </tr>
+  <tr>
+    <td colspan="3">
+      <b><a href="Financial_Plan.md">Cost Structure</a></b>
+      <p>What are the most important costs to our business?<br>
+      Which Key Resources are most expensive?<br>
+      Which Key Activities are most expensive?<br>
+      How does it coes to establish and run the business?</p>
+    </td>
+    <td colspan="3">
+      <b><a href="Financial_Plan.md">Revenue Streams</a></b>
+      <p>For what value are customers willing to pay? <br>
+      How would they prefer to pay? <br>
+      What is the revenue structure?</p>
+    </td>
+  </tr>
+</table>
+
+## Founders
+<!-- Team members -->
+* NAME, TITLE
+* NAME, TITLE
+* NAME, TITLE
+* NAME, TITLE
+* NAME, TITLE

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/Value_Propositions.md

@@ -0,0 +1 @@
+# Value Propositions

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/BusinessModelCanvas-Markdown/Template/team-leaders.md

@@ -0,0 +1,9 @@
+# Team Leader
+
+* T0: (add name)
+* T1: (add name)
+* T2: (add name)
+* T3: (add name)
+* T4: (add name)
+* T5: (add name)
+* T6: (add name)

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/.gitignore

@@ -0,0 +1 @@
+build-tempdir/

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/AccountsAndRecords.md

@@ -0,0 +1,93 @@
+
+# Accounts and Records
+
+## Records and Accounting; Reports; Fiscal Affairs
+
+Proper and complete records and books of accounting of the business of the Company,
+including a list of names, addresses and interests of all Members, shall
+be maintained under the direction of the Board Of Directors at the
+Company's principal place of business. Each Member or his or her duly
+authorized representative may examine the books of account of the
+Company records, reports and other papers regarding the business and
+financial condition of the Company, make copies and extracts therefrom
+at such Member's expense, and discuss the affairs, finances and accounts
+of the Company with independent public accountants of the Company, all
+at such reasonable times and as often as may be reasonably requested.
+
+The books and records of the Company shall be kept on a cash basis in
+accordance with generally accepted accounting principles applied on a
+consistent basis, and in all events shall conform with Generally
+Accepted Accounting Policies and Procedures.
+
+## Fiscal Year End
+The fiscal year end of the Company shall be December 31.
+
+## Keeper of the Books
+At all times during the term of existence of
+the Company, and beyond that term if deemed by Board Of Directors to be
+necessary, the CFO shall keep or cause to be kept the books of accounts
+referred to in this section and the following:
+
+* A current list of the full name and last known business or
+residence address of each Member and Director, together with the
+Capital Contribution and the share in Profits and Losses of each Member;
+
+* A copy of the Certificate of Formation, as amended;
+
+* Executed counterparts of this Agreement, as amended;
+
+* Executed Supplements and Consents, if any;
+
+* Any powers of attorney under which the Company takes action;
+
+* Copies of the Company's federal, state, and local income tax or
+information returns and reports, if any, for the six (6) most recent
+taxable years;
+
+* Financial statements of the Company for the six (6) most recent
+fiscal years; and
+
+* All Company records as they relate to the Company's internal
+affairs for the current and past four (4) fiscal years.
+
+## Member Examination of Records
+
+ Each Member, at its expense and under
+the circumstance and conditions set forth in the BOC, may at all
+reasonable times during usual business hours, audit, examine and make
+copies of account records, files and bank statements of the Company.
+Such right may be exercised by any Member or by its designated agents or employees.
+
+## Bank Accounts 
+All funds of the Company shall be deposited in one or
+more accounts with one or more recognized financial institutions in the
+name of the Company, at such locations as shall be determined by the
+Board Of Directors and CFO. Withdrawal from such accounts shall require
+the signature of such Person or Persons as the Board Of Directors and
+Members jointly designate.
+
+## Members' Tax Requirements
+Within fifteen (15) days after the end of
+each taxable year, the Company shall forward to each Member all
+information necessary for the Members to complete their federal and
+state income tax or information returns, and a copy of the Company's
+federal, state, and local income tax or information returns for such
+year.
+
+
+
+
+
+## Membership Records
+The 
+
+* name 
+
+* e-mail address
+
+* Capital Contributions 
+
+* Percentage Interest 
+
+of each of the Members is set forth in Supplement 4.
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/AdditionalMembershipInterests.md

@@ -0,0 +1,19 @@
+
+# Creation of Additional Membership Interests
+
+Additional Membership Interests may be created and issued to existing or new
+Members or Persons, and such other Persons may be admitted to
+the Company as Members in one or more classes, with the unanimous written
+conset of the Board Of Directors, and all Company Members on such terms and
+conditions as the Board Of Directors and Company Members may approve at
+the time of admission. 
+
+The creation of new Membership Interests, the
+admission of any new Members, or the creation of any new class or group
+of Members in accordance with this Agreement may 
+
+* (i) result in the dilution of the Sharing Ratios of existing Members
+
+* (ii) be reflected as an amendment to this Agreement or a Supplement which shall
+be valid if executed by the entirety of the Board Of Directors, all existing 
+Company Members and the new Member.  

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/Capcon.md

@@ -0,0 +1,37 @@
+
+# Capital Contributions and Finance
+
+## Capital Contribution
+
+No Member shall have any obligation to make any Capital Contribution.
+Company members, in their sole and absolute discretion, may at any time elect
+to fund or not fund further Capital Contributions with respect to the
+Company or any Investment, Investment Entity, without any
+liability whatsoever to the Company or any Member, even if such failure
+to contribute results in the loss of any opportunity or the forfeiture
+of any Investment or interest in any Investment Entity, or results in
+any other penalty or liability.
+
+## Return of Contributions
+
+Except as expressly provided herein, no
+Member shall be entitled to the return of any part of its Capital
+Contributions, to be paid interest in respect of either its Capital
+Account or any Capital Contribution made by it or paid for the fair
+market value of its Membership Interest upon withdrawal or otherwise.
+
+Unrepaid Capital Contributions shall not be a liability of the Company,
+or of any Member. 
+
+No Member shall be required to contribute or lend any cash or property 
+to the Company to enable the Company to return any Member's Capital Contributions.
+
+## Member Guaranties
+No Member shall undertake to guarantee or otherwise become liable for any obligation 
+of the Company, or any Investment Entity.
+
+## Investments
+
+Investments. All Investments by the Company shall be made on such
+terms and conditions as the Board Of Directors and Members may determine.
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/ClosingAndSignature.md

@@ -0,0 +1,17 @@
+
+# Closing
+
+IN WITNESS WHEREOF, the undersigned, intending to be legally bound hereby,
+has duly executed this 
+
+* Company NDA
+
+* Company IP Assignment
+
+* Company Operating Agreement 
+
+
+# Signature Page
+
+The parties sign this Agreement on the date below by their electronic signatures.
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/CommonTermsAndConditions.md

@@ -0,0 +1,268 @@
+
+# Common terms and conditions
+
+## Not registered securities
+
+THE LIMITED LIABILITY COMPANY UNITS REFERRED TO HEREIN (THE “UNITS”) HAVE NOT 
+BEEN REGISTERED UNDER THE SECURITIES ACT OF 1933, AS AMENDED (THE “1933 ACT”).  
+SUCH INTERESTS ARE BEING OFFERED OR SOLD UNDER THE EXEMPTION PROVIDED BY SECTION 
+4(2) OF THE 1933 ACT AND RULE 506 THEREUNDER NOR HAVE THEY BEEN REGISTERED UNDER 
+THE SECURITIES OR BLUE SKY LAWS OF ANY OTHER JURISDICTION. 
+
+A PURCHASER OR RECEIVER OF UNITS MUST BE PREPARED TO BEAR THE ECONOMIC RISK OF THE 
+INVESTMENT FOR AN INDEFINITE PERIOD OF TIME BECAUSE THE UNITS HAVE NOT BEEN REGISTERED 
+UNDER THE 1933 ACT AND, THEREFORE, CANNOT BE SOLD UNLESS THEY ARE SUBSEQUENTLY 
+REGISTERED OR AN EXEMPTION FROM REGISTRATION IS AVAILABLE.  
+
+THERE IS NO OBLIGATION OF THE ISSUER TO REGISTER THE UNITS UNDER THE 1933 ACT.
+
+## Entire Agreement
+
+All parties agree that this Agreement is the final, complete and exclusive statement of 
+the mutual understanding of the parties and supersedes and cancels all previous written 
+and oral agreements and communications relating to the subject matter of this Agreement.
+
+This Agreement and its exhibits constitute the entire agreement between the parties.
+Except as otherwise provided herein, no amendments to this Agreement shall be 
+binding upon any Member unless set forth in a document duly executed by such Member.
+
+The parties will amend this agreement only by cosigned, written agreement. 
+
+## Binding Arbitration and waiver of rights
+
+IF FOR ANY REASON THIS
+ARBITRATION CLAUSE BECOMES NOT APPLICABLE, THEN EACH PARTY, TO THE
+FULLEST EXTENT PERMITTED BY APPLICABLE LAW, HEREBY IRREVOCABLY WAIVES
+ALL RIGHT TO TRIAL BY JURY OR BENCH TRIAL AS TO ANY ISSUE RELATING HERETO IN ANY
+ACTION, PROCEEDING OR COUNTERCLAIM ARISING OUT OF OR RELATING TO THIS
+AGREEMENT OR ANY OTHER MATTER INVOLVING THE PARTIES HERETO.
+
+Any controversy, claim or dispute arising out of or relating to this
+Agreement, shall be settled by binding arbitration in Pflugerville TX
+at the companys primary place of business located at
+<>
+
+All such controversies, claims or disputes shall be settled in this manner 
+in lieu of any action at law or equity.
+
+The following rights are irrevocably waived now and forever more:
+
+* rights to sue in all possible venues
+
+* trial by Judge
+
+* trial by Judge/Jury 
+
+* trial by any other form either previously used, currently in use, or used in the 
+future
+
+* public or private disclosure of any Member conflict with the Company
+
+Such arbitration shall be conducted in accordance with the then prevailing
+commercial arbitration rules of American Arbitration Association
+("**AAA**"), with the following exceptions if in conflict: 
+
+* one arbitrator shall be chosen by the AAA (the "**Arbitrator**"); 
+
+* each party to the arbitration will pay its pro rata share of 
+the expenses and fees of the arbitrator, together with other expenses of the arbitration
+incurred or approved by the Arbitrator; 
+
+* arbitration may proceed in the absence of any party if written notice (pursuant to the
+Arbitrator's rules and regulations) of the proceeding has been given to
+such party. 
+
+* The parties agree to abide soley by all decisions and awards rendered in such proceedings. 
+
+* Such decisions and awards rendered by the arbitrator shall be final and conclusive. 
+
+* The Arbitrator shall not have the right to award punitive damages or 
+speculative damages to either party and shall not have the power to 
+amend this Agreement. 
+
+## Ownership of Property and No Right of Partition
+* A Member's interest in the Company shall be personal property for all purposes. 
+
+* No Member shall have any right to partition the property owned by the Company.
+
+* The Membership Interest:
+
+**IS NOT**
+
+and
+
+**SHALL NOT**
+
+be considered community property at any time (including but not limited to):
+
+* before the execution of this Agreement
+
+* after this Agreement is executed
+
+* while the Agreement is in effect 
+
+* after the Agreement is no longer in effect due to resignation or expulsion
+
+
+* By signing this agreement, Member hereby agrees that:
+
+*  any and all rights
+*  any and all interests
+
+under this agreement (and applicable law incorporated by reference) are hereby:
+
+* suspended
+* revoked 
+* rendered null and void now and forever more.
+
+for any 
+
+* spouse
+
+* significant other
+
+* domestic partner 
+
+* any future lawful definition of a similar type of close/constant party 
+
+## Involvement of Members in Certain Proceedings
+
+Should any Member become involved in legal proceedings unrelated to the 
+Company's business in which the Company is required to provide books, records, an
+accounting, or other information, then such Member :
+
+* shall indemnify the Company from all expenses incurred in conjunction therewith.
+
+* Member agrees that this involvement in such a proceeding may be considered a:
+
+* material breach of contract
+* violation of Duty Of Care
+* violation of Fidicuary Duty
+
+and agrees that the Member may face immediate expulsion for exposing the Company
+in such an irresonsible manner and that the Company may pursue the Member for any
+and all remedies under law.
+
+## No Third-Party Enforcement
+
+Only the parties to this agreement may enforce rights under this agreement. 
+
+## Waiver
+
+No consent or waiver, express or implied, by any Member of
+any breach or default by any other Member in the performance by the
+other Member of its obligations hereunder shall be deemed or construed
+to be a consent or waiver to or of any other breach or default in the
+performance by such other Member of the same or any other obligation
+hereunder. Failure on the part of any Member to complain of any act or
+to declare any other Member in default, irrespective of how long such
+failure continues, shall not constitute a waiver of rights hereunder.
+
+## Severability
+
+If any provision of this Agreement or the application
+thereof to any Person or circumstances shall be judged by 
+any court of competent jurisdiction to be unenforceable or invalid, 
+to any extent, and such invalidity or unenforceability does not destroy
+the basis of the bargain between the parties, then the remainder of this
+Agreement and the application of such provisions to other Persons or
+circumstances shall not be affected thereby and shall be enforced to the
+greatest extent permitted by law.
+
+## Legal Relationship
+
+The parties to this agreement remain independent parties. This agreement does not 
+create any partnership, joint venture, agency, or similar relationship between the 
+parties.
+
+## No Assignment or Delegation
+
+* No party may assign any right or delegate any obligation under this agreement 
+
+* This Agreement is not assignable or transferable by Member 
+
+* Any attempt to assign or delegate will have no legal effect.
+
+* No failure to exercise, and no delay in exercising, on the part of either party, any privilege, 
+any power or any rights hereunder will operate as a waiver thereof, nor will any single or 
+partial exercise of any right or power hereunder preclude further exercise of any other right 
+hereunder. 
+
+## Governing Law
+This Agreement and the obligations of the Members
+hereunder shall be construed and enforced in accordance with the laws of
+the State of Texas, excluding any conflicts of law rule or principle
+which might refer such construction to the laws of another state or
+country.
+
+## Signature
+
+An electronically signed copy of this agreement delivered by e-mail or other electronic 
+means has the same legal effect as delivering a printed and signed original.
+
+
+## Notices
+
+* The parties shall send every notice, demand, consent, request, or other communication 
+required or allowed by this agreement by e-mail to the e-mail address the other party provided 
+with their signature
+
+* All notices given in accordance with this Agreement shall be effective upon delivery 
+at the e-mail address of the addressee. 
+
+* By giving written notice thereof, each Member shall have the right from time to time to 
+change its address pursuant hereto.
+
+## No Agreement to Employ
+
+Nothing in this Agreement shall affect any right that Participant may have to be employed or to maintain employment or a similar relationship (if applicable) with the Company or with any affiliated entity. 
+
+## Captions, References
+
+Pronouns wherever used herein, and of
+whatever gender, shall include natural persons and corporations and
+associations of every kind and character, and the singular shall include
+the plural wherever and as often as may be appropriate. Article and
+section headings are for convenience of reference and shall not affect
+the construction or interpretation of this Agreement. Whenever the terms
+"hereof," "hereby," "herein," or words of similar import are used in
+this Agreement they shall be construed as referring to this Agreement in
+its entirety rather than to a particular section or provision, unless
+the context specifically indicates to the contrary. Any reference to a
+particular "Article" or a "Section" shall be construed as referring to
+the indicated article or section of this Agreement unless the context
+indicates to the contrary.
+
+## Place of Business and Office; Resident Agent
+The address of the registered agent of the Company for service of process on the
+Company in the State of Texas (and also the Company primary office)
+is located at: <>
+
+## Term
+The term of the Company shall commence upon the filing of the
+Certificate of Formation with the Texas Secretary of State and shall
+have perpetual existence unless it shall be dissolved and its affairs
+shall have been wound up as provided in Section Dissolution and Winding Up of Business.
+
+## Qualification in Other Jurisdictions. 
+The Company may register in any other jurisdiction upon the approval of the Board Of Directors.
+
+## No State Law Partnership. 
+The Company shall not be a partnership or
+joint venturer under any state or federal law, and no Member or Director 
+shall be a partner or joint venture of any other Member or Director for
+any purposes; other than under the Code or other applicable tax laws,
+and this Agreement may not be construed otherwise.
+
+## General Restrictions on Dispositions of Membership Interests
+A Member may not make an assignment, transfer or
+other disposition (voluntarily, involuntarily or by operation of law) (a
+"**Transfer**") of all or any portion of his or her Membership Interest,
+nor pledge, mortgage, hypothecate, grant a security interest in, or
+otherwise encumber (an "**Encumbrance**") all or any portion of its
+Membership Interest,
+
+Any attempted Transfer of all or any portion of a Membership Interest,
+shall be void and result in the immediate (no vote required) expulsion
+of the Member and forefiture of Member interest and the right of the Company
+to pursue the Member for any and all remedies under law.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/Definitions.md

@@ -0,0 +1,260 @@
+
+# Definitions
+
+The following terms as used in this Agreement shall be defined as follows:
+
+## "**Certificate of Formation**" 
+means the document filed with the Texas Secretary of State required to form a 
+limited liability company in Texas.
+
+## "**Person**" 
+whether capitalized or not, means any individual, sole
+proprietorship, joint venture, partnership, corporation, company, firm,
+bank, association, cooperative, trust, estate, government, governmental
+agency, regulatory authority, or other entity of any nature.
+
+## "**Company**" 
+means the organization defined in Section Company Name 
+
+## "**Membership Interest**" or "**Beneficial Interest**" 
+means a Person\'s right to share in the income, gains, losses, deductions,
+credit or similar items of, and to receive distributions from, the
+Company, but does not include any other rights of a Member,
+including the right to vote or to participate in management.
+
+## "**Member**" 
+means a Person who acquires a Membership Interest in the Company, 
+as permitted under this Agreement, and who remains a Member of the Company. 
+
+## "**Assignee**" 
+means a Person who has acquired a Member's Membership
+Interest in the Company , through a Transfer in accordance with the
+terms of this Agreement.
+
+## "**Board Of Directors**" 
+means the collective group of persons hereafter designated as Board Of Directors in 
+accordance with this Agreement.
+
+## "**Director**" 
+means any natural person elected to the Board Of Directors
+in accordance with this Agreement unti such time they are removed from the 
+Board Of Directors in accordance with this Agreement.
+
+## "**Indepdent Directors**"
+A natural person, that the Members and Board Of Directors has determined 
+has 'no material relationship' with the Company, either directly or as a 
+partner, shareholder or officer of an organization that has a relationship 
+with the company.
+
+## "**Accounting Policies and Procedures**" 
+means the policies and procedures adapted from time to time by the Board Of Directors for
+preparation of the Company financial statement, financial projects and
+other accounting reports.
+
+## "**Adverse Consequences**" 
+means all actions, suits, proceedings,
+hearings, investigations, charges, complaints, demands, injunctions,
+judgments, orders, decrees, rulings, damages, dues, penalties, fines,
+costs, amounts paid in settlement, liabilities, obligations, liens,
+losses, expenses, and fees, including court costs and reasonable
+attorney's fees and expenses.
+
+## "**Affiliate**" 
+means, with respect to a Person, another Person,
+directly or indirectly, through one or more intermediaries, controlling,
+controlled by, or under common control with the Person in question. The
+term "control" shall mean the possession, directly or indirectly, of the
+power to direct or cause the direction of the management or policies of
+the controlled Person.
+
+## "**Assigning Member**" 
+means a Member who by means of a Transfer
+has transferred his or her Membership Interest in the Company to an
+Assignee.
+
+## "**Business Day**" 
+means any day other than Saturday, Sunday or
+other day on which commercial banks in Texas are authorized or required
+to be closed under the laws of the state of Texas.
+
+## "**Capital Account**" 
+means, as to any Member, a separate account maintained and adjusted in accordance 
+with Section "Distributions To Members".
+
+## "**Capital Contribution**" 
+means, with respect to any Member, the
+amount of money, the forgiveness of any debt, the Fair Market Value of
+any services or property (other than money) contributed to the Company
+(net of liabilities secured by such contributed property that the
+Company is considered to assume or take "subject to" under IRC Section
+752) in consideration of a Percentage Interest held by such Member.
+Under no conditions shall a Capital Contribution be deemed a loan.
+
+## "**Code"** or "**The Code**" or "**IRC**" 
+means the Internal Revenue Code of 1986, as amended, and any successor provision.
+
+## "**Company Property**" 
+means all assets, real, personal and other,
+owned by the Company, whether or not contributed to the Company by a
+Member.
+
+## "**Encumbrance**" 
+means, with respect to any Membership Interest,
+or any element thereof, a mortgage, pledge, security interest, lien,
+proxy coupled with an interest (other than as contemplated in this
+Agreement), option, or preferential right to purchase.
+
+## "**Encumber**" 
+means the act of creating or purporting to create an
+Encumbrance, whether or not perfected under applicable law.
+
+## "**Fair Market Value**" or "**FMV**" 
+means, with respect to any
+item Company Property, the item\'s adjusted basis for federal income tax
+purposes, except as follows:
+
+A. The Fair Market Value of any property contributed by a Member to the
+Company shall be the value of such property, as mutually agreed by the
+contributing Member and the Company Members; and
+
+B. The Fair Market Value of any item of Company Property distributed
+to any Member shall be the value of such item of property on the date of
+distribution, as mutually agreed by the receiving Member and the Company.
+
+## "**Family**" 
+means, with respect to a specified individual, such
+individual's lineal or adopted descendants, his or her parents, spouse,
+domestic partner, significant other, siblings, and lineal or adopted
+descendants of any thereof, and any family limited partnership, trust or
+other fiduciary or other entity solely for the benefit of (x) such
+individual, (y) such individual's lineal or adopted descendants or (z)
+such individual's parents, spouse, domestic partner, significant other,
+siblings or lineal or adopted descendants of any thereof.
+
+## "**Fiscal Year**" 
+shall be from January 1 of each year until or unless changed by a Majority Vote of the Members.
+
+## "**Investment Entity**" 
+means any Person in which the Company has an Investment.
+
+## "**Involuntary Transfer**" 
+means, with respect to any Membership
+Interest, or any element thereof, any Transfer or Encumbrance, whether
+by operation of law, pursuant to court order, foreclosure of a security
+interest, execution of a judgment or other legal process, or otherwise,
+including a purported transfer to or from a trustee in bankruptcy,
+receiver, or assignee for the benefit of creditors.
+
+## "**Member Percentage Interest"** 
+means the percentage set forth in the Company agreement.
+
+## "**Profits and Losses**" 
+means, for each fiscal year or other
+period specified in this Agreement, an amount equal to the Company\'s
+taxable income or loss for such year or period, determined in accordance
+with Section 703 (a) of the Code.
+
+## "**Reserve Amount**" 
+means the amount from time to time established
+by the Board Of Directors as a reserve to meet the reasonably
+anticipated working capital needs of the Company.
+
+## "**Selling Member**" 
+means a Member desires to sell any of his or her Membership Interests.
+
+## "**Sharing Ratios**" 
+means the percentages in which Members participate in and bear, certain items. 
+
+## "**Substituted Member**" 
+means a Transferee, other than an existing Member, of the Membership Interest 
+who may be admitted as a Member with respect to such Membership Interest.
+
+## "**Successor in Interest**" 
+means an Assignee, a successor of a
+Person by merger or otherwise by operation of law, or a transferee of
+all or substantially all of the business or assets of a Person.
+
+## "**Cause**" 
+means (A) a finding by a court or other government body
+or a plea or similar agreement admitting that an act or omission
+constitutes a felony under the laws of the United States or the state of
+Texas, or a violation of the securities law of any United States
+governmental or self-regulatory body, (B) a material and/or fiduciary
+breach of this agreement, or (C) fraudulent behavior.
+
+## "**Adjusted Capital Account**" 
+means, with respect to a Member,
+such Member's Capital Account as of the end of each fiscal year, as the
+same is specially computed to reflect the adjustments required or
+permitted to be taken into account in applying Regulations Section
+1.704-1(b)(2)(ii)*(d)* (including adjustments for Partnership Minimum
+Gain and Partner Nonrecourse Debt Minimum Gain).
+
+## "**Code**" 
+means the Internal Revenue Code of 1986, as amended
+from time to time, and any corresponding provisions of succeeding law.
+
+## "**Depreciation**" 
+means, for each taxable year or other period,
+an amount equal to the depreciation, amortization or other cost recovery
+deduction allowable with respect to an asset for the year or other
+period, except that if the Gross Asset Value of an asset differs from
+its adjusted basis for federal income tax purposes at the beginning of
+the year or other period, Depreciation will be an amount which bears the
+same ratio to the beginning Gross Asset Value as the federal income tax
+depreciation, amortization or other cost recovery deduction for the year
+or other period bears to the beginning adjusted tax basis, provided that
+if the federal income tax depreciation, amortization, or other cost
+recovery deduction for the year or other period is zero, Depreciation
+will be determined with reference to the beginning Gross Asset Value
+using any reasonable method selected by the Board Of Directors.
+
+## "**Partner Nonrecourse Debt**" 
+has the meaning assigned to it in
+Regulations Sections 1.704-2(b)(4) and 1.752-2.
+
+## "**Partner Nonrecourse Debt Minimum Gain**" 
+has the meaning assigned to it in Regulations Section 1.704-2(i)(3).
+
+## "**Partner Nonrecourse Deductions**" 
+has the meaning assigned to it in Regulations Section 1.704-2(i)(2).
+
+## "**Partnership Minimum Gain**" 
+has the meaning assigned to it in Regulations Section 1.704-2(d).
+
+## "**Profits**" and "**Losses**" 
+mean, for each taxable year or
+other period, an amount equal to the Company's taxable income or loss
+ for the year or other period determined in
+accordance with Section 703(a) of the Code (including all items of
+income, gain, loss or deduction required to be stated separately under
+Section 703(a)(1) of the Code), with the following adjustments:
+
+* Any income that is exempt from federal income tax and not
+otherwise taken into account in computing Profits or Losses will be
+added to taxable income or loss;
+
+* Any expenditures described in Code Section 705(a)(2)(B) or treated
+as Section 705(a)(2)(B) expenditures under Regulations Section
+1.704-1(b)(2)(iv)*(i)*, and not otherwise taken into account in
+computing Profits or Losses, will be subtracted from taxable income or
+loss;
+
+* Gain or loss resulting from any disposition of property with respect
+to which gain or loss is recognized for federal income tax purposes will
+be computed by reference to the Gross Asset Value of the property,
+notwithstanding that the adjusted tax basis of the property differs from
+its Gross Asset Value;
+
+* In lieu of depreciation, amortization and other cost recovery
+deductions taken into account in computing taxable income or loss, there
+will be taken into account Depreciation for the taxable year or other
+period;
+
+## "**Regulations**" 
+means the regulations promulgated by the United
+States Department of the Treasury pursuant to and in respect of
+provisions of the Code. All references herein to sections of the
+Regulations shall include any corresponding provisions of succeeding,
+similar, substitute proposed or final Regulations.
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/Dissolution.md

@@ -0,0 +1,75 @@
+
+# Withdrawal, Dissolution, Liquidation and Termination
+
+## Dissolution, Liquidation, and Termination Generally
+
+The Company shall be dissolved upon the first to occur of any of
+the following:
+
+* The sale or disposition of all assets of the Company and the receipt, in cash, of 
+all consideration therefor, and the determination of the Board Of Directors and all 
+Members not to continue the business of the Company directly or through an Investment 
+Entity.
+
+* The occurrence of any event which, as a matter of law, requires that the 
+Company be dissolved.
+
+
+## Liquidation and Termination
+Upon dissolution of the Company such Person as the Board Of Directors 
+may designate shall act as liquidator. The liquidator shall 
+proceed diligently to wind up the
+affairs of the applicable Company and make final distributions
+as provided herein. The costs of liquidation shall be a Company 
+expense, as applicable. Until final distribution, the liquidator
+shall continue to operate the Company with all of the power
+and authority of the Board Of Directors, as applicable
+hereunder. The steps to be accomplished by the liquidator are as
+follows:
+
+* as promptly as possible after dissolution and again after final
+liquidation, the liquidator shall cause a proper accounting to be made
+by a firm of certified public liquidator, which shall cause a proper
+accounting to be made by a firm of certified public accountants
+acceptable to the Board Of Directors of the Company's 
+assets, liabilities, and operations through the last day of the
+calendar month in which the dissolution shall occur or the final
+liquidation shall be completed, as applicable
+
+* the liquidator shall cause the Company to
+satisfy all of the debts and liabilities of the Company and
+(whether by payment or the making of reasonable provision for payment
+thereof)
+
+* all remaining assets of the Company shall be distributed
+to the Members as follows:
+
+* (a) the liquidator may sell any or all applicable Company 
+property and the sum of:
+
+* (b) any resulting gain or loss from each sale plus
+
+* (c) the fair market value of such property that has not been sold
+shall be determined and (notwithstanding the provisions of Section 
+Capital Accounts income, gain, loss, and deduction inherent in such
+property (that has not been reflected in the Capital Accounts
+previously) shall be allocated among the Members to the extent possible
+to cause the Capital Account balance of each Member to equal the amount
+distributable to such Member under this Section.
+
+* Company property as applicable shall be distributed to
+the Members as provided in Section "Distributions to Members".
+
+## Cancellation of Certificate. 
+In the case of the dissolution,
+liquidation and termination of the Company, on completion of the
+distribution of Company assets, the Board Of Directors (or such other
+Person as the BOC may require or permit) shall file a Certificate of
+Cancellation with the Secretary of State of Texas, cancel any other
+filings made pursuant to Section "Qualification in Other Jurisdictions".
+and take such other actions as may be necessary to
+terminate the existence of the Company. In the case of the dissolution,
+liquidation and termination of the Company, the CEO shall file such
+certificates as may be required by the BOC or other law in respect
+thereof.
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/Distributions.md

@@ -0,0 +1,41 @@
+
+# Distributions to Members
+
+## Distributions in General
+
+From time to time, but not less often than
+monthly, the CEO and CFO shall determine (i) the amount, if any, by
+which the Company's funds then on hand exceed the Reserve Amount (such
+excess being referred to herein as "**Excess Funds**").
+
+If the CEO and CFO determines that there are 
+Excess Funds subject to distribution but that additional Capital Contributions
+will be required for future Company needs within the next two
+(2) calendar month period, then the CEO and CFO may elect to not make 
+a distribution of such Excess Funds.
+
+Not later than the 15th day of each calendar month, the Excess Funds derived 
+from the business shall be distributed to the Company Members in accordance with
+their Sharing Ratios.
+
+
+## Withholding
+
+The Company may withhold distributions or portions
+thereof if it is required to do so by any applicable rule, regulation,
+or law, and each Member hereby authorizes the Company to withhold from
+or pay on behalf of or with respect to such Member any amount of
+federal, state, local or foreign taxes that the Board Of Directors, CEO
+and CFO reasonably determines that the Company is required to withhold
+or pay with respect to any amount distributable or allocatable to such
+Member pursuant to this Agreement. Any amounts so paid or withheld with
+respect to a Member pursuant to this Section shall be treated as having
+been distributed to such Member and shall reduce any amounts otherwise
+distributable to such Member (either currently or in the future)
+pursuant to Section "Distributions to Members" or Section 
+"Withdrawl, Dissolution, Liquidation and Termination".
+
+The Company desires to issue Units in respect of the Company designated as 
+“Profits Interest Units” to Participant in connection with Participant’s performance 
+of services to or for the benefit of the Company.
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/DutyOfCare.md

@@ -0,0 +1,10 @@
+
+# Duty of care
+
+Each Member shall discharge their duties in a good and proper manner
+as provided for in this Agreement. Each Member, on behalf of the
+Company shall enforce agreements entered into
+by the Company and conduct or cause to be
+conducted the ordinary business and affairs of the Company in
+accordance with good industry practice and the provisions of this
+Agreement. 

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/Indemnification.md

@@ -0,0 +1,62 @@
+
+# Indemnification; Reimbursement of Expenses; Insurance
+
+To the fullest extent permitted by law, and subject to the limitations set
+forth in this Section, and with, in each case, the Board Of Directors
+prior approval: 
+
+* the Company may (at the Members sole discretion) indemnify each Director
+or Member for any Adverse Consequences 
+that a Director or Member may suffer including, but not limited to, any
+Director, or Member who, is to be made a party to any pending or
+completed action, suit or proceeding ("**Proceeding**"), any appeal
+therein, or any inquiry or investigation preliminary thereto, solely by
+reason of the fact that he or she is or was a Director, Member and was
+acting within scope of duties or under the authority of the Company and
+was not in breach of agreements or violating fiduciary responsibility 
+as determned by the Members;
+
+* the Company may (at the Members sole discretion) pay a Director or Member for expenses 
+incurred by him or her:
+
+(1) in advance of any deposition of a Proceeding to which such Director or Member is a party, and
+
+(2) in connection with his or her appearance as a witness or other participation in any 
+Proceeding. 
+
+Such indemnification may also include counsel fees. 
+
+The Company may indemnify and advance expenses to an employee or agent of the Company to
+the same extent and subject to the same conditions under which it may
+indemnify and advance expenses to the Director or Members under the
+preceding sentence. 
+
+The provisions of this Section shall not be exclusive of any other right 
+under any law, provision of the Certificate or this Agreement, or otherwise.
+
+Notwithstanding the foregoing, this indemnity shall not apply to actions constituting :
+
+* gross negligence
+
+* simple negligence
+
+* willful misconduct 
+
+* bad faith
+
+* involving a material or fiduciary breach of this Agreement or the duties set forth herein,
+
+* any other reason in the Members and/or Board Of Directors discretion
+which reason, in the Board Of Directors or Members reasonable opinion, causes a substantial
+loss to the Company.
+
+## Option to Purchase Insurance
+
+The Company may purchase and maintain insurance to protect itself and any
+Director, Member, employee or agent of the Company, whether or not the
+Company would have the power to indemnify such Person under this Section.
+
+## Limits of Coverage
+
+This indemnification obligation shall be limited to $1,000.00 and no Member 
+shall be required to make a Capital Contribution in respect thereof.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/IntelectualPropertAssign.md

@@ -0,0 +1,107 @@
+
+# Company IP Assignment
+
+## Assignment of Intellectual Property
+
+Member hereby assigns to Company exclusively and throughout the world and universe all right, 
+title and interest (whether or not now existing) in 
+
+* (a) work done for the Company 
+
+* (b) all precursors, portions and works in progress with respect thereto 
+
+* (c) and all inventions, works of authorship, mask works, technology, information, 
+know-how, materials and tools relating thereto or to the development, 
+support or maintenance thereof 
+
+(d) all copyrights, patent rights, trade secret rights, trademark rights, 
+mask works rights, sui generis, database rights and all other intellectual and 
+industrial property rights of any sort 
+
+(e) all business, contract rights, causes of action, and goodwill in, 
+incorporated or embodied in, used to develop, or related to any of the 
+foregoing (collectively, “Intellectual Property”). 
+
+To the extent allowed by applicable law, this Section includes all 
+rights of paternity (for example, including but not limited to the right 
+to be identified as author), integrity, disclosure and withdrawal and 
+any other rights that may be known as or referred to as moral rights, 
+artist’s rights, droit moral or the like (collectively, “Moral Rights”). 
+
+To the extent Member retains any Moral Rights under applicable law, 
+Member hereby ratifies and consents, and hereby provides all necessary 
+ratifications and consents, to any action that may be taken with respect 
+to such Moral Rights by or authorized by Company, 
+and Member agrees not to assert any Moral Rights with respect thereto. 
+
+The foregoing applies to the subject matter enumerated in Exhibit A. 
+Member will confirm any such ratification, consent or agreement from 
+time to time as requested by Company.
+
+## Consideration
+
+Company agrees to distribute to Member certain percentage of profit of the Company
+on an ongoing basis, pursuant to the provisions of this Agreement between Company 
+and Member. 
+
+Such distributions shall be the only consideration required of Company 
+with respect to the subject matter of this Agreement.
+
+
+## Further Assurances
+
+Member agrees to assist Company in every proper way to evidence, record 
+and perfect the Section (Assignment Of Intellectual Property) 
+and to apply for and obtain recording of 
+and from time to time enforce, maintain and defend the assigned rights. 
+
+If Company is unable for any reason whatsoever to secure Members 
+signature to any document it is entitled to under this Section, 
+Member hereby irrevocably designates and appoints Company and 
+its duly authorized officers and agents, as his agents and 
+attorneys-in-fact with full power of substitution to act for 
+and on his behalf and instead of Member, only to execute and 
+file any such document or documents and to do all other lawfully 
+permitted acts to further the purposes of the foregoing with the 
+same legal force and effect as if executed by Member.
+
+
+
+## Restrictions Of Use re Confidential Information and Intellectual Property of Third Parties
+
+Member will not use, assign, disclose to the Company any technical or business information 
+or plans of Third Parties , except to the extent Member 
+can document that it is generally available (through no fault of Member) 
+for use and disclosure by the public without any charge license or restriction, 
+such as public domain or approved OSI licensed or CC licensed code/documenation, 
+
+Member recognizes and agrees that any breach or threatened breach of this 
+Section will cause irreparable harm to Company for which damages would 
+not be an adequate remedy, and, therefore, Company will be entitled to equitable relief 
+(including without limitation, injunctions) with respect thereto in addition to any 
+other civil or criminal remedies.
+
+## Warranty
+
+Member represents and warrants to Company that Member 
+
+* (a) was the sole owner (other than Company) of all rights, title and interest 
+in and to the Technology and Intellectual Property, 
+
+* (b) has not assigned, transferred, licensed, pledged or otherwise encumbered any 
+Technology or Intellectual Property or agreed to do so,
+
+* (c) has full power and authority to enter into this Agreement and to make the 
+assignment provided in Section (Assignment Of Intellectual Property), 
+
+* (d) is not aware of any violation, infringement or misappropriation of any 
+third party’s rights (or any claim thereof) by the Technology or Intellectual Property, 
+
+* (e) was not acting within the scope of employment by any third party when conceiving, 
+creating or otherwise performing any activity with respect to anything 
+purportedly assigned in Section (Assignment Of Intellectual Property) 
+
+* (f) is not aware of any questions or challenges with respect to the patentability 
+or validity of any claims of any existing patents or patent applications 
+relating to the Intellectual Property.
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/LiabilityToThirdParties.md

@@ -0,0 +1,5 @@
+
+# Liability to Third Parties
+No Member or Director, solely by reason of being a
+member or Director, shall be liable for the debts, obligations, or liabilities of
+the Company.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/ManagementOfTheCompany.md

@@ -0,0 +1,126 @@
+
+# Management of the Company
+
+## Member authority
+Company Members shall be fully empowered and authorized to
+implement the terms and provisions of the Board Of Directors approved
+Business Plan and Annual Budget on behalf of the Company, subject to the
+limitations set forth in Section "Major Decisions".
+
+The Company may rely upon any action taken or document executed by the
+any Officer without duty of further inquiry and may assume that such 
+Officer has the requisite power and authority to take the action or 
+execute the document in question.
+
+## Major Decisions
+
+* causing the Company to enter into any agreement which
+would subject the Company or its assets to any recourse
+liability for borrowings, or for capital contributions to any Person;
+
+* causing the Company to grant any interests in the
+assets, profit, and income of the Company;
+
+* causing a dissolution of the Company;
+
+* regarding the Company assets, any sale, transfer, exchange,
+mortgage, financing, hypothecation or encumbrance of all or any part
+thereof, or any modification of the terms of the foregoing;
+
+* regarding the Company financial affairs, (A)
+determination of major accounting policies including selection of
+accounting methods and making various decisions regarding treatment and
+allocation of transactions for federal and state income, franchise or
+other tax purposes (B) determination of the terms and conditions of all
+borrowings of the Company and the identity of the lender
+thereof (or (i) applicable Budget therefor;
+
+* regarding the Company operations, approval of insurance coverages,
+the underwriters thereof and claims related thereto, the settlement of
+any litigation that is not fully covered by insurance involving more
+than $1000.00, entering into any contract which obligates the Company
+for more than $500.00 (except to the extent expressly set
+forth in an Annual Budget) or which cannot be cancelled without payment
+of a cancellation fee or other premium on not more than 30 days prior
+notice; and entering into any lease for office space;
+
+* filing of any petition or consenting to the filing of any petition
+that would subject the Company to a bankruptcy or similar
+proceeding;
+
+* any other action which, considered before the taking thereof,
+could reasonably be expected to have a material effect upon the business
+or affairs of the Company or is a breach of fiduciary duty.
+
+
+## Annual requirements of members
+Not later than February 1 of each year, the Members shall
+deliver to the Board Of Directors a detailed proposed business plan (the
+"**Business Plan**") for the Company's next succeeding fiscal year,
+which shall include the proposed budget for such year (the "**Annual
+Budget**").
+
+## Business Plan and Annual Budget
+
+The Business Plan and Annual Budget shall contain such other information
+as the Members wishes to include and shall contain such
+information as the Board Of Directors may request. 
+
+The Board Of Directors will review the proposed Annual Budget and Business Plan, 
+and subject to required revisions, approve the same for the next succeeding
+fiscal year no later than February 15 of each year.
+
+The Business Plan and Annual Budget shall include projected revenues,
+expenses for the year in question, projected investment activities and
+such other matters as the Members and Board Of Directos may deem appropriate. 
+If the Annual Budget provides for a contingency or similar line item, then
+unless otherwise specifically provided to the contrary therein, the
+Members shall be empowered to expend the amount set forth in such
+line item for the Company obligations. If the Business Plan is not
+approved by the date set forth above, then: 
+
+* any items or portions thereof that have been approved will become operative 
+immediately
+
+* with respect to the Annual Budget, the Members may expend,
+in respect of noncapital or recurring expenses in any quarter of the
+then current calendar year, an amount equal to the budget amount for the
+corresponding quarter of the immediately preceding calendar year, as set
+forth on the last approved Annual Budget after giving effect to any
+material changes to the Company or its properties during the prior year;
+however, if any contract approved as a part of any prior approved Annual
+Budget or Business Plan provides for automatic increases in costs
+thereunder after the beginning of the then current calendar year, then
+the Members may expend the amount of that increase.
+
+Following submission and recording of the final version of the
+Business Plan and Annual Budget, the Members shall be authorized
+to take the actions, incur obligations and make the expenditures therein
+expressly set forth. The Members shall not have any authority or
+power to take any action on behalf of the Company that would
+constitute a Major Decision, unless it has been
+expressly approved in writing by the Board Of Directors. 
+
+## Compensation of Members
+Except as otherwise specifically provided herein, no compensatory payment shall be made by
+the Company to any Member for the services to the Company.
+
+## Officers
+The Board Of Directors may from time to time, designate
+one or more Persons to be officers or agents of the Company (an
+"**Officer**"). Any Officer so designated shall have such title and
+authority and perform such duties as the Board Of Directors may, from
+time to time, designate. Unless the Board Of Directors decides
+otherwise, if the title is one commonly used for officers of a business
+corporation, the assignment of such title shall constitute the
+delegation to such Officer of the authority and duties that are normally
+associated with that office, subject to any specific delegation of
+authority and duties made to such Officer by the Board Of Directors.
+Each Officer shall hold office until his successor shall be duly
+designated and shall qualify or until his death or until he shall resign
+or shall have been removed. The salaries or other compensation, if any,
+of the Officers and agents of the Company shall be fixed from time to
+time by the Board Of Directors. Any Officer may resign as such at any
+time. Any Officer may be removed as such, with or without Cause, by the
+Board Of Directors. Designation of an Officer shall not, in and of
+itself, create contract rights. 

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/MemberRemoval.md

@@ -0,0 +1,24 @@
+
+# Resignation and Removal of Members  
+
+## Expulsion of a member for Cause
+
+Expulsion of a Member requires an affirmative vote by a 2/3 or greater majority of 
+the Board Of Directors (in accordance with the Board Manual and Charter in effect
+at that time)  and by written unanimous consent of the Company Members.
+
+The Member subject to expulsion is not eligible to vote in the proceeding.
+
+The Member subject to explulsion forefits all equity/interests/rights/contributions
+and any/all Membership interest immediately upon expulsion.
+
+## Self withdrawal of a Member 
+
+Self withdrawal of a Member requires an affirmative vote by a 2/3 or greater majority
+of the Board Of Directors (in accordance with the Board Manual and Charter in effect 
+at that time) and by written unanimous consent of the Company Members.
+
+The Member requesting self withdrawal is not eligible to vote in the proceeding.
+
+The Member subject to explulsion forefits all equity/interests/rights/contributions
+and any/all Membership interest immediately upon resignation.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/NonDisclosure.md

@@ -0,0 +1,203 @@
+
+# Company NDA
+
+## Purpose
+Joining the Company organization as a Member to discuss material non public information related 
+to the Company
+
+## Governing State Law
+Texas, USA
+
+## Parties involved and agreeing to Mutual Nondisclosure
+
+"Disclosing Party" describes each party with respect to Confidential Information it discloses to the other party. 
+
+"Receiving Party" describes each party with respect to Confidential Information it receives from the other party.
+
+## Purpose 
+
+The parties anticipate disclosure of Confidential Information for the purpose on
+the accompanying standard form certificate (the "Purpose").
+
+## Confidential Information
+
+### Categories of Confidential Information 
+
+Subject to Section (Exclusions from Confidential Information), "Confidential Information" 
+means the following kinds of information:
+
+* information disclosed by Disclosing Party during the term of this agreement that is related to the business of Disclosing Party;
+
+* the fact that the parties are pursuing the Purpose;
+
+* the terms of this agreement;
+
+* the fact that the parties have entered into this agreement; and
+
+* other information derived from these kinds of information.
+
+## Exclusions from Confidential Information
+
+* Public Information. 
+
+Information that is now public is not Confidential Information. Confidential Information that becomes public, other than as
+a result of breach of this agreement, ceases to be Confidential Information.
+
+### Otherwise Acquired Information
+
+Information that Receiving Party receives other than from Disclosing Party is not Confidential
+Information, unless the disclosure breached a confidentiality obligation to Disclosing Party that Disclosing Party made known to Receiving Party.
+
+* Independently Developed Information. 
+
+Information Receiving Party develops independently is not, or ceases to be, Confidential Information
+of Disclosing Party. Receiving Party shall bear the burden of proving independent development using contemporaneous documentary evidence.
+
+## Confidentiality Obligations
+
+### Nondisclosure
+
+Except as described in Section (Permitted Disclosure), Receiving Party shall not disclose Confidential Information to anyone.
+
+* (b) Permitted Disclosure. 
+
+Receiving Party may disclose Confidential Information to the following personnel:
+
+* if Receiving Party is a legal entity, employees, independent contractors, officers, directors, and agents of Receiving Party ("Personnel") who:
+
+* have a need to know the Confidential Information to advance the Purpose; 
+
+* have entered written confidentiality agreements with Receiving Party that impose 
+confidentiality obligations, affording as much or more protection as 
+those of this agreement, that apply to the Confidential Information
+
+* legal and financial advisers providing services to Receiving Party under 
+confidentiality obligations imposed either by law or by professional
+rules ("Advisers").
+
+* (c) Limited Use. 
+
+Receiving Party shall use Confidential Information only to advance the Purpose.
+
+* (d) Security Measures. 
+
+Receiving Party shall take measures to secure materials embodying Confidential Information at least as protective as those Receiving Party employs to 
+secure its own Confidential Information, but in any event no less than reasonable measures.
+
+* (e) Preserve Proprietary Notices. 
+
+Receiving Party shall not remove any proprietary notices attached to materials embodying Confidential Information.
+
+* (f) No Illegal Dealing in Securities.
+
+Receiving Party shall not break securities laws by purchasing, selling, or otherwise dealing in securities of Disclosing Party on the basis of 
+Confidential Information that is material, nonpublic information.  Receiving Party shall instruct anyone to whom it discloses Confidential
+Information that may be material, nonpublic information not to break securities laws by dealing in securities of Disclosing Party.
+
+* (g) No Reverse Engineering. 
+
+Receiving Party shall not reverse engineer any material embodying Confidential Information.
+
+* (h) Mitigate Legally Required Disclosure. 
+
+The following obligations apply when the law requires disclosure of Confidential Information and when Receiving Party reasonably expects that the law may 
+require disclosure of Confidential Information:
+
+* (i) Give Notice of Required Disclosure. 
+
+If legally permitted, Receiving Party shall promptly notify Disclosing Party of the nature of the requirement and the Confidential Information affected.
+If practical, Receiving Party shall give notice quickly enough to afford Disclosing Party practical chance to start a proceeding to protect the
+confidentiality of the Confidential Information. On Disclosing Party request, Receiving Party shall cooperate with Disclosing Party in any such 
+proceeding by providing reasonable assistance.
+
+* (ii) Reimburse Expenses of Cooperation. 
+
+Disclosing Party shall reimburse Receiving Party's reasonable out-of-pocket expenses of cooperating in
+any proceeding described in Section (Give Notice of Required Disclosure).
+
+* (i) Give Notice of Leaks. 
+
+Receiving Party shall give Disclosing Party notice when Receiving Party becomes aware, suspects, or anticipates that Confidential Information 
+has been or will be disclosed or used in breach of this agreement or other confidentiality agreements with Disclosing Party.
+
+* (j) Return and Destruction.
+
+(i) Subject to Section (Records Policy), when this agreement terminates, Receiving Party shall promptly:
+
+* (A) return all materials embodying Confidential Information that Disclosing Party provided with request to return; and
+
+* (B) destroy all parts of other materials that embody Confidential Information.
+
+* (k) Records Policy. 
+
+When this agreement terminates, if Receiving Party has a written records retention policy for the creation and 
+scheduled destruction of archival or backup records, and only specialized personnel can routinely access those records, then Receiving Party 
+may retain materials embodying Confidential Information until destroyed under that policy.
+
+* (l) Comply with Export Controls. 
+
+Both parties shall comply with export and reexport laws with respect to Confidential Information.
+
+* (m) Compliance and Oversight.
+
+* (i) Receiving Party shall ensure that its Advisers abide by the confidentiality obligations of Receiving Party under this agreement. 
+If Receiving Party is a legal entity, Receiving Party shall also ensure that its Personnel abide by the confidentiality obligations of 
+Receiving Party under this agreement.
+
+Breach of Receiving Party obligations by Receiving Party Personnel or Receiving Party Advisers will be deemed breach of this agreement by
+Receiving Party itself.
+
+* (ii) If Receiving Party is a legal entity, Receiving Party shall provide Disclosing Party copies of confidentiality agreements with Personnel
+who receive Confidential Information on Disclosing Party request.
+
+5. Clarifications.
+
+* (a) No Obligation to Disclose. No terms of this agreement obligate Disclosing Party to disclose any Confidential Information.
+
+* (b) No Obligation to Do Business. No terms of this agreement obligate either party to enter any business relationship or agreement, 
+related to the Purpose or otherwise.\
+
+* (c) No License. No terms of this agreement grant any license for any patent, trademark, copyright, or other intellectual property.
+
+* (d) No Warranty. Disclosing Party makes no warranty that Confidential Information will be complete or accurate.
+
+* (e) Freedom to Operate. No terms of this agreement prohibit either party from:
+
+* (i) entering into any business relationship with any non-party; or
+
+* (ii) assigning and reassigning Personnel and Advisers in its sole discretion.
+
+6. 18 U.S.C. 1833(b) Notice.
+
+* (a) An individual shall not be held criminally or civilly liable under any Federal or State trade secret law for the disclosure of a trade secret that:
+
+* (i) is made:
+
+* (A) in confidence to a Federal, State, or local government official, either directly or indirectly, or to an attorney; and
+
+* (B) solely for the purpose of reporting or investigating a suspected violation of law; or
+
+* (ii) is made in a complaint or other document filed in a lawsuit or other proceeding, if such filing is made under seal.
+
+* (b) An individual who files a lawsuit for retaliation by an employer for reporting a suspected violation of law may disclose the trade 
+secret to the attorney of the individual and use the trade secret information in the court proceeding, if the individual:
+
+* (i) files any document containing the trade secret under seal; and
+
+* (ii) does not disclose the trade secret, except pursuant to court
+order.
+
+7. Term.
+
+* (a) Expiration. 
+This agreement does not expire.
+
+* (b) Survival. 
+Obligations under Section (Confidentiality Obligations)
+for Confidential Information disclosed during the term survive the term of
+this agreement as follows:
+
+* (i) Obligations for Confidential Information that Receiving Party knew or reasonably should have known constituted a trade secret survive as long
+as the Confidential Information remains a trade secret.
+
+* (ii) Obligations for other Confidential Information survive forever.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/OutsideCapRaise.md

@@ -0,0 +1,115 @@
+
+# Outside Capital Raising
+
+insert any terms and conditions here....
+
+perhaps mention sources of revenue, markets being pursued etc...
+
+## Non Equity and Non Debt based
+
+Capital will be primarily sought through the pursuit of abc from xyz (but not
+limited to):
+
+* 
+* 
+*
+* 
+* 
+
+## Restrictions on Capital Sources
+
+* 
+*
+
+## Equity Based Raises
+
+### General Conditions and Requirements
+
+Any grant of equity in exchange for outside capital investment in the Company 
+shall be on the following (or substantially similiar) terms and conditions , 
+and require unamious written consent of the Members and the Board Of Directors.
+
+### Terms and Conditions
+
+[PUBLIC] Earnest Shared Earnings Agreement v1.3
+SHARED EARNINGS AGREEMENT BETWEEN EARNEST CAPITAL AND Company.
+
+Date
+
+The following is a summary of the principal terms with respect to the proposed financing of _______________ (the “Company”).  Except for the section entitled “Confidentiality,” this summary of terms does not constitute a legally binding obligation. The parties intend to enter into a legally binding obligation only pursuant to definitive agreements to be negotiated and executed by the parties.
+Amount of Investment
+
+$___________
+
+Shared Earnings
+By the 10th day of each quarter, the Company will pay the Investor the Percentage 
+(as defined below) of: the Company's Founder Earnings (as defined below) 
+less the proportional Founder Earnings Threshold (as defined below),  
+in the preceding quarter. 
+
+Shared Earnings shall continue until the Investor has received the Shared Earnings Cap. 
+
+The Percentage
+The Percentage shall be ___%.
+
+Net Income
+Net Income means net income determined in accordance with GAAP.
+
+Founder Earnings
+Founder Earnings means Net Income, adding back any founders' salaries.
+
+Founder Earnings Threshold
+$________ per founder per year.
+
+Shared Earnings Cap
+The Shared Earnings Cap will be __X the investment amount.
+
+Equity Basis
+The Equity Basis will be the greater of (i) any unpaid portion of the Shared Earnings Cap,
+or (ii) the Amount of Investment.
+
+Equity Conversion
+The Investor has the right, at its option, to convert the Equity Basis into the shares 
+sold by the Company in its next fixed-price round of financing, at a price per share 
+equal to the lesser of
+ (i) the price of the securities sold in the next financing, 
+or (ii) at a price per share calculated by dividing the Valuation Cap (defined below) 
+by all issued and outstanding shares plus all shares reserved for issuance 
+under any equity incentive plan at the time of the closing of the next financing. 
+
+Valuation Cap
+$_____________
+
+Sale
+On a sale of the Company, the Investor is entitled to receive the 
+greater of
+(i) any unpaid amount of the Shared Earnings Cap or 
+(ii) the amount the Investor would be entitled to receive if it converted the Equity Basis 
+at the Valuation Cap.
+
+Information Rights
+The Investor is entitled to standard information and inspection rights including any 
+records of accounting necessary to verify Shared Earnings calculations. 
+
+Board Observer
+The Investor will be entitled to attend Board Meetings as an observer upon its request,
+subject to executing a standard form observer confidentiality agreement. 
+
+Participation Rights
+The Investor will have the right to participate on a pro rata basis in subsequent 
+issuances of Membership Interests, subject to customary exclusions. 
+
+Confidentiality
+Without the consent of the Investor, the Company shall not disclose these terms to 
+anyone other than the Company's officers, directors, and key service providers. 
+
+COMPANY:
+                                        
+Name:                                  
+Title:                                          
+Date:                                          
+INVESTOR:
+                                        
+Name:  
+Title:  
+Date:  

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/ProfitInterest.md

@@ -0,0 +1,132 @@
+
+#Profit Interests
+
+## Introduction 
+
+The Profits Interest Units below are issued to Party on the terms and conditions 
+set forth in this Agreement.
+
+Party shall make no Capital Contribution to the Company in connection with the 
+Profits Interest Units issued hereunder and, as a result, 
+Parties Capital Account balance in the Company immediately after their receipt of 
+the Profits Interest Units shall be equal to zero.
+
+Notwithstanding anything to the contrary contained in the LLC Agreement or set forth 
+herein, with respect to the rights of Party related to, in respect of and in connection 
+with the Company, Board Of Directors and other Members, Party and the Profits Interest 
+Units owned thereby shall have only a right to share in or be allocated Net Profits and 
+Net Losses and receive or share in distributions of the Company as set forth in 
+the Agreement.
+
+Party agrees to execute a counterpart signature page to the Agreement, in the form 
+attached hereto and shall thereupon become a Member as of the Effective Date.
+
+The Profits Interest Units acquired pursuant to this Agreement shall be fully 
+subject to the terms and conditions contained in this Agreement, and Party
+hereby acknowledges that Participant has read and understands the terms and conditions 
+contained therein.
+
+
+## Prohibition on Transfer of Profits Interest Units
+
+The Profits Interest Units acquired pursuant to this Agreement may not be transferred, 
+sold, pledged, hypothecated or otherwise disposed of, voluntarily or involuntarily, by 
+operation of law or otherwise, 
+
+## Investment Representations
+
+Participant acknowledges that he or she is aware that the Profits Interest Units issued 
+to him by the Company pursuant to this Agreement have not been registered under the 
+Securities Act of 1933, as amended (the “Securities Act”), on the basis of certain exemptions 
+from such registration requirement. In this connection, 
+
+## Section 83(b) Election. 
+
+Participant shall execute and deliver to the Company with this executed Agreement, 
+a copy of the Acknowledgment and Statement of Decision Regarding Election Pursuant 
+to Section 83(b) of the Internal Revenue Code (the “Acknowledgment”) substantially in 
+the form attached hereto. 
+
+Participant shall execute and submit with the Acknowledgment a copy of the Election Pursuant 
+to Section 83(b) of the Internal Revenue Code, substantially in the form attached hereto
+if Participant has indicated in the Acknowledgment his or her decision to make such an election. 
+
+Participant represents that Participant is not relying on the Company with respect to 
+such decision and has consulted any tax consultant(s) that Participant deems advisable in 
+connection with the filing of an election under Section 83(b) of the Code and 
+similar tax provisions. 
+
+Participant acknowledges that it is Participant’s sole responsibility and not the Company’s to 
+timely file an election under Section 83(b) of the Code, even if Participant requests that the 
+Company or any representative of the Company make such filing on Participant’s behalf. 
+
+Participant should consult his or her tax advisor to determine if there is a comparable election 
+to file in the state of his or her residence and whether such filing is desirable under the 
+circumstances.
+
+## Taxes
+
+The Company and Party intend that (i) the Profits Interest Units be treated as “profits interests” within the meaning of the Code, Treasury Regulations promulgated thereunder, and any published guidance by the Internal Revenue Service with respect thereto, including, without limitation, Internal Revenue Service Revenue Procedure 93-27, as clarified by Internal Revenue Service Revenue Procedure 2001-43, (ii) the issuance of such interests not be a taxable event to the Company or Participant as provided in such Revenue Procedure, and (iii) the Agreement be interpreted consistently with such intent. 
+
+In furtherance of such intent, effective immediately prior to the issuance of the Profits Interest Units, the Company will cause the Gross Asset Value (as defined in the Agreement) of all Company assets to be adjusted to equal their respective gross fair market values, and make the resulting adjustments to the Capital Accounts of the Members, in each case as set forth in the Agreement. 
+
+The Company may withhold from Participant’s wages, or require Participant to pay to the Company, any applicable withholding or employment taxes resulting from the issuance of the Profits Interest Units hereunder, from the vesting or lapse of any restrictions imposed on the Profits Interest Units, or from the ownership or disposition of the Profits Interest Units.
+
+## Code Section 409A
+
+The Profits Interest Units are not intended to constitute or provide for “nonqualified deferred compensation” within the meaning of Section 409A of the Code (“Section 409A”), and, provided that Section 409A of the Code, Treasury Regulations and related Department of Treasury guidance do not require otherwise, the Company shall not treat the Profits Interest Units as nonqualified deferred compensation. However, notwithstanding any other provision of this Agreement, if at any time the Board Of Directors determine that the Profits Interest Units may be subject to Section 409A, the Board Of Directors 
+shall have the right, in their sole discretion, to adopt such amendments to this Agreement or take such other actions (including amendments and actions with retroactive effect) as the Board Of Directors determine are necessary or appropriate for the 
+Profits Interest Units to be exempt from the application of Section 409A or to comply with the requirements of Section 409A; provided, however, if such action would diminish the value of the Profits Interest Units, such action may not be taken without Members written consent.
+
+
+## ACKNOWLEDGMENT AND STATEMENT OF DECISION REGARDING ELECTION PURSUANT TO SECTION 83(b) OF THE INTERNAL REVENUE CODE
+
+The undersigned, a Member of the “Company” and holder of Profits Interest
+in the Company designated as “Profits Interest Units” (the “Award”) of the Company, 
+hereby states, as of the date of issuance of the Award, as follows:
+
+1.    The undersigned acknowledges receipt of a copy of the Agreement. The undersigned has carefully reviewed the Agreement.
+
+2.    The undersigned either [check as applicable]:
+____ (a) has consulted, and has been fully advised by, the undersigned’s own tax advisor, __________________________________________, whose business address is ________________________________, regarding the federal, state and local tax consequences of being issued the Award under the Agreement, and particularly regarding the advisability of making elections pursuant to Section 83(b) of the Internal Revenue Code of 1986, as amended (the “Code”), and pursuant to the corresponding provisions, if any, of applicable state laws; or
+
+____ (b) has knowingly chosen not to consult such tax advisor.
+
+3.    The undersigned hereby states that the undersigned either [check as applicable]:
+
+_____ (a) has decided to make an election pursuant to Section 83(b) of the Code and is submitting to the Company, together with the undersigned’s executed Agreement, a copy of an executed election form which is attached to the Agreement; or
+
+____ (b) has knowingly chosen not to make an election pursuant to Section 83(b) of the Code.
+
+4.    Neither the Company nor any subsidiary or representative of the Company has made any warranty or representation to the undersigned with respect to the tax consequences of the issuance of the Award to the undersigned pursuant to the Agreement or of the making or failure to make an election pursuant to Section 83(b) of the Code or corresponding provisions, if any, of applicable state law.
+
+5.    The undersigned is also submitting to the Company, together with the Agreement, a copy of an executed election form, if an election is made, of the undersigned pursuant to provisions of state law corresponding to Section 83(b) of the Code, if any, which are applicable to the issuance of the Award to the undersigned pursuant to the Agreement.
+
+
+ELECTION PURSUANT TO SECTION 83(b) OF THE INTERNAL REVENUE CODE TO INCLUDE IN GROSS
+INCOME THE EXCESS OVER THE PURCHASE PRICE, IF ANY, OF THE VALUE OF PROPERTY TRANSFERRED
+IN CONNECTION WITH SERVICES
+
+The undersigned hereby elects pursuant to Section 83(b) of the Internal Revenue Code of 1986, as amended, to include in the undersigned’s gross income for the taxable year the excess (if any) of the fair market value of the property described below, over the amount the undersigned paid for such property, if any, and supplies herewith the following information in accordance with the Treasury regulations promulgated under Section 83(b):
+
+1.    The undersigned’s name, address and taxpayer identification (social security) number are:
+Name:    
+Address:        
+TIN:
+
+2.    The property with respect to which the election is made consists of 
+[•] Units in the Company designated as “Profits Interest Units” (the “Award”) of the Company representing an interest in the future profits, losses and distributions of the Company.
+
+3.    The date on which the above property was transferred to the undersigned was [•], and the taxable year to which this election relates is [•].
+
+4.    The above property is subject to the following restrictions: 
+
+(a) forfeiture and/or a right of repurchase by the Company if the undersigned ceases 
+to be an employee of, or consultant or service provider to, the Company under certain circumstances pursuant to the LLC Agreement of the Company, as amended from time to time (the “LLC Agreement”), and
+ (b) certain other restrictions pursuant to the LLC Agreement should the undersigned wish to transfer the Award (in whole or in part).
+
+5.    The fair market value of the above property at the time of transfer (determined without regard to any restrictions other than those which by their terms will never lapse) is $0.
+
+6.    The amount paid for the above property by the undersigned was $0.
+
+7.    A copy of this election has been furnished to the Company, and the original will be filed with the income tax return of the undersigned to which this election relates.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/README.md

@@ -0,0 +1,14 @@
+
+# CommonBoilerplate
+
+This is the common and boilerplate items used across all op agreements and bylaws (as appropriate). 
+
+Common bits such as :
+
+* definitions 
+* conflict of interest policy
+* NDA
+* IP Assignment
+* Standard terms and conditions
+* Securities exemption
+* etc 

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/RightsToCompanyInformation.md

@@ -0,0 +1,27 @@
+
+# Rights to Company Information
+
+In addition to the other rights specifically
+set forth in this Agreement, each Member is entitled to the following
+information under the circumstances and conditions set forth in the BOC:
+
+* true and full information regarding the status of the business and
+financial condition of the Company
+
+* promptly after becoming available, a copy of the Company's federal,
+state and local income tax returns for each year 
+
+* a current list of the name and last known business, or mailing address 
+of each Member and Director
+
+* a copy of this Agreement ,the Company's Certificate of Formation, and all amendments to
+such documents
+
+* true and full information regarding the amount of cash and a description and statement
+of the agreed value of any other property or services contributed by
+each Member and which each Member has agreed to contribute in the
+future, and the date on which each became a Member 
+
+* other information regarding the affairs of the Company to which that 
+Member is entitled pursuant to the BOC (including all the Company books and
+records)

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/Taxes.md

@@ -0,0 +1,70 @@
+
+#Taxes 
+
+## Members Bound
+Members shall be bound by the provisions of this Section in reporting their shares of 
+Company income  for income tax purposes.
+
+## Tax Returns
+The Board Of Directors shall cause to be prepared and filed all
+necessary federal and state income tax returns for the Company,
+including making the elections described in Section "Tax Elections".
+
+Each Member shall furnish to the Board Of Directors all pertinent
+information in its possession relating to Company operations that is
+necessary to enable such income tax returns to be prepared and filed.
+
+## Tax Elections.
+
+The following elections shall be made on the appropriate returns of the Company:
+
+* to adopt the calendar year as the Company's fiscal year;
+
+* to keep the Company's books and records on the income-tax method;
+
+* if there is a distribution of Company property as described in
+section 734 of the Code or if there is a transfer of a Company interest
+as described in section 743 of the Code, upon written request of any
+Member, to elect, pursuant to section 754 of the Code, to adjust the
+basis of Company properties; and
+
+* to elect to amortize the organizational expenses of the Company
+ratably over a period of twelve (12) or sixty (60) months as permitted by section
+709(b) of the Code.
+
+No election shall be made by the Company or any Member to be excluded
+from the application of the provisions of subchapter K of chapter 1 of
+subtitle A of the Code or any similar provisions of applicable state
+laws.
+
+## Tax Matters Partner.
+
+The Board Of Directors and CFO collectivley shall be the "**tax matters partner**" 
+of the Company pursuant 
+to section 6231(a)(7) of the Code. As
+tax matters partner, they shall take such action as may be
+necessary to cause each other Member to become a "**notice partner**"
+within the meaning of section 6223 of the Code. Such Member shall inform
+each other Member of all significant matters that may come to its
+attention in its capacity as tax matters partner by giving notice
+thereof within ten days after becoming aware thereof and, within such
+time, shall forward to each other Member copies of all significant
+written communications it may receive in such capacity. Such Member
+shall not take any action contemplated by sections 6222 through 6232 of
+the Code without the consent of the Board Of Directors. This provision is not
+intended to authorize such Member to take any action left to the
+determination of an individual Member under sections 6222 through 6232
+of the Code.
+
+## Allocations on Transfer of Interests.
+The Company income, gain,
+loss or deduction allocable to any Member in respect of any interest in
+the Company which may have been transferred shall be allocated during
+such year based upon an interim closing of the Company's books as
+described in the first sentence of Treasury Regulations §
+1.706-1(c)(2)(ii), taking into account the actual results of Company
+operations during the portion of the year in which such Member was the
+owner thereof, and the date, amount and recipient of any distribution
+which may have been made with respect to such interest.
+
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/TimeAndCapitalRequirements.md

@@ -0,0 +1,5 @@
+
+# Time and Capital Requirements of members
+No Member shall be required to devote a particular
+amount of time or capital to the Company's business, 
+but shall devote sufficient time to perform their duties hereunder. 

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/boilerplate.md

@@ -0,0 +1,263 @@
+# Common terms and conditions
+
+## Not registered securities
+
+THE LIMITED LIABILITY COMPANY UNITS REFERRED TO HEREIN (THE “UNITS”) HAVE NOT 
+BEEN REGISTERED UNDER THE SECURITIES ACT OF 1933, AS AMENDED (THE “1933 ACT”).  
+SUCH INTERESTS ARE BEING OFFERED OR SOLD UNDER THE EXEMPTION PROVIDED BY SECTION 
+4(2) OF THE 1933 ACT AND RULE 506 THEREUNDER NOR HAVE THEY BEEN REGISTERED UNDER 
+THE SECURITIES OR BLUE SKY LAWS OF ANY OTHER JURISDICTION. 
+
+A PURCHASER OF UNITS MUST BE PREPARED TO BEAR THE ECONOMIC RISK OF THE INVESTMENT 
+FOR AN INDEFINITE PERIOD OF TIME BECAUSE THE UNITS HAVE NOT BEEN REGISTERED UNDER 
+THE 1933 ACT AND, THEREFORE, CANNOT BE SOLD UNLESS THEY ARE SUBSEQUENTLY 
+REGISTERED OR AN EXEMPTION FROM REGISTRATION IS AVAILABLE.  
+
+THERE IS NO OBLIGATION OF THE ISSUER TO REGISTER THE UNITS UNDER THE 1933 ACT.
+
+## Entire Agreement
+
+All parties agree that this Agreement is the final, complete and exclusive statement of the 
+mutual understanding of the parties and supersedes and cancels all previous written 
+and oral agreements and communications relating to the subject matter of this Agreement.
+
+This Agreement and its exhibits constitute the entire agreement between the parties.
+Except as otherwise provided herein, no amendments to this Agreement shall be 
+binding upon any Member unless set forth in a document duly executed by such Member.
+
+The parties will amend this agreement only by cosigned, written agreement. 
+
+## Binding Arbitration and waiver of rights
+
+IF FOR ANY REASON THIS
+ARBITRATION CLAUSE BECOMES NOT APPLICABLE, THEN EACH PARTY, TO THE
+FULLEST EXTENT PERMITTED BY APPLICABLE LAW, HEREBY IRREVOCABLY WAIVES
+ALL RIGHT TO TRIAL BY JURY AS TO ANY ISSUE RELATING HERETO IN ANY
+ACTION, PROCEEDING OR COUNTERCLAIM ARISING OUT OF OR RELATING TO THIS
+AGREEMENT OR ANY OTHER MATTER INVOLVING THE PARTIES HERETO.
+
+Any controversy, claim or dispute arising out of or relating to this
+Agreement, shall be settled by binding arbitration in Pflugerville TX
+at the companys primary place of business located at
+17801 Richelle Cv, Pflugrvile TX, 78660 (also known as Charles house).
+
+All such controversies, claims or disputes shall be settled in this manner 
+in lieu of any action at law or equity.
+
+The following rights are irrevocably waived now and forever more:
+
+* rights to sue in all possible venues
+
+* trial by Judge
+
+* trial by Judge/Jury 
+
+* trial by any other form either previously used, currently in use, or used in the future
+
+* public or private disclosure of any Member conflict with the Company
+
+Such arbitration shall be conducted in accordance with the then prevailing
+commercial arbitration rules of American Arbitration Association
+("**AAA**"), with the following exceptions if in conflict: 
+
+* one arbitrator shall be chosen by the AAA (the "**Arbitrator**"); 
+
+* each party to the arbitration will pay its pro rata share of 
+the expenses and fees of the arbitrator, together with other expenses of the arbitration
+incurred or approved by the Arbitrator; 
+
+* arbitration may proceed in the absence of any party if written notice (pursuant to the
+Arbitrator's rules and regulations) of the proceeding has been given to
+such party. 
+
+* The parties agree to abide soley by all decisions and awards rendered in such proceedings. 
+
+* Such decisions and awards rendered by the arbitrator shall be final and conclusive. 
+
+* The Arbitrator shall not have the right to award punitive damages or 
+speculative damages to either party and shall not have the power to 
+amend this Agreement. 
+
+## Ownership of Property and No Right of Partition
+* A Member's interest in the Company shall be personal property for all purposes. 
+
+* No Member shall have any right to partition the property owned by the Company.
+
+* The Membership Interest:
+
+**IS NOT**
+
+and
+
+**SHALL NOT**
+
+be considered community property at any time (including but not limited to):
+
+* before the execution of this Agreement
+
+* after this Agreement is executed
+
+* while the Agreement is in effect 
+
+* after the Agreement is no longer in effect due to resignation or expulsion
+
+
+* By signing this agreement, Member hereby agrees that:
+
+*  any and all rights
+*  any and all interests
+
+under this agreement (and applicable law incorporated by reference) are hereby:
+
+* suspended
+* revoked 
+* rendered null and void now and forever more.
+
+for any 
+
+* spouse
+
+* significant other
+
+* domestic partner 
+
+* any future lawful definition of a similar type of close/constant party 
+
+
+
+## Involvement of Members in Certain Proceedings
+
+Should any Member become involved in legal proceedings unrelated to the 
+Company's business in which the Company is required to provide books, records, an
+accounting, or other information, then such Member :
+
+* shall indemnify the Company from all expenses incurred in conjunction therewith.
+
+* Member agrees that this involvement in such a proceeding may be considered a:
+
+* material breach of contract
+* violation of Duty Of Care
+* violation of Fidicuary Duty
+
+and agrees that the Member may face immediate expulsion for exposing the Company
+in such an irresonsible manner.
+
+## No Third-Party Enforcement
+
+Only the parties to this agreement may enforce rights under this agreement. 
+
+## Waiver
+No consent or waiver, express or implied, by any Member of
+any breach or default by any other Member in the performance by the
+other Member of its obligations hereunder shall be deemed or construed
+to be a consent or waiver to or of any other breach or default in the
+performance by such other Member of the same or any other obligation
+hereunder. Failure on the part of any Member to complain of any act or
+to declare any other Member in default, irrespective of how long such
+failure continues, shall not constitute a waiver of rights hereunder.
+
+## Severability
+If any provision of this Agreement or the application
+thereof to any Person or circumstances shall be judged by 
+any court of competent jurisdiction to be unenforceable or invalid, 
+to any extent, and such invalidity or unenforceability does not destroy
+the basis of the bargain between the parties, then the remainder of this
+Agreement and the application of such provisions to other Persons or
+circumstances shall not be affected thereby and shall be enforced to the
+greatest extent permitted by law.
+
+## Legal Relationship
+
+The parties to this agreement remain independent parties. This agreement does not create any partnership, joint venture, agency,
+or similar relationship between the parties.
+
+## No Assignment or Delegation
+
+* No party may assign any right or delegate any obligation under this agreement 
+
+* This Agreement is not assignable or transferable by Member 
+
+* Any attempt to assign or delegate will have no legal effect.
+
+* No failure to exercise, and no delay in exercising, on the part of either party, any privilege, 
+any power or any rights hereunder will operate as a waiver thereof, nor will any single or 
+partial exercise of any right or power hereunder preclude further exercise of any other right 
+hereunder. 
+
+## Governing Law
+This Agreement and the obligations of the Members
+hereunder shall be construed and enforced in accordance with the laws of
+the State of Texas, excluding any conflicts of law rule or principle
+which might refer such construction to the laws of another state or
+country.
+
+## Signature
+
+An electronically signed copy of this agreement delivered by e-mail or other electronic 
+means has the same legal effect as delivering a printed and signed original.
+
+
+## Notices
+
+* The parties shall send every notice, demand, consent, request, or other communication 
+required or allowed by this agreement by e-mail to the e-mail address the other party provided 
+with their signature
+
+* All notices given in accordance with this Agreement shall be effective upon delivery 
+at the e-mail address of the addressee. 
+
+* By giving written notice thereof, each Member shall have the right from time to time to 
+change its address pursuant hereto.
+
+## No Agreement to Employ
+
+Nothing in this Agreement shall affect any right that Participant may have to be employed or to maintain employment or a similar relationship (if applicable) with the Company or with any affiliated entity. 
+
+## Captions, References
+
+Pronouns wherever used herein, and of
+whatever gender, shall include natural persons and corporations and
+associations of every kind and character, and the singular shall include
+the plural wherever and as often as may be appropriate. Article and
+section headings are for convenience of reference and shall not affect
+the construction or interpretation of this Agreement. Whenever the terms
+"hereof," "hereby," "herein," or words of similar import are used in
+this Agreement they shall be construed as referring to this Agreement in
+its entirety rather than to a particular section or provision, unless
+the context specifically indicates to the contrary. Any reference to a
+particular "Article" or a "Section" shall be construed as referring to
+the indicated article or section of this Agreement unless the context
+indicates to the contrary.
+
+## Place of Business and Office; Resident Agent
+The address of the registered agent of the Company for service of process on the
+Company in the State of Texas (and also the Company primary office)
+is located at: 17801 Richelle Cv , Pflugerville TX, 78660
+
+## Term
+The term of the Company shall commence upon the filing of the
+Certificate of Formation with the Texas Secretary of State and shall
+have perpetual existence unless it shall be dissolved and its affairs
+shall have been wound up as provided in Section Dissolution and Winding Up of Business.
+
+## Qualification in Other Jurisdictions. 
+The Company may register in any other jurisdiction upon the approval of the Board Of Directors.
+
+## No State Law Partnership. 
+The Company shall not be a partnership or
+joint venturer under any state or federal law, and no Member or Director 
+shall be a partner or joint venture of any other Member or Director for
+any purposes; other than under the Code or other applicable tax laws,
+and this Agreement may not be construed otherwise.
+
+## General Restrictions on Dispositions of Membership Interests
+A Member may not make an assignment, transfer or
+other disposition (voluntarily, involuntarily or by operation of law) (a
+"**Transfer**") of all or any portion of his or her Membership Interest,
+nor pledge, mortgage, hypothecate, grant a security interest in, or
+otherwise encumber (an "**Encumbrance**") all or any portion of its
+Membership Interest,
+
+Any attempted Transfer of all or any portion of a Membership Interest,
+shall be void and result in the immediate (no vote required) expulsion
+of the Member and forefiture of Member interest.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/CommonBoilerplate/profInterest.md

@@ -0,0 +1,105 @@
+#Profit Interests
+
+## Prohibition on Transfer of Profits Interest Units
+
+The Profits Interest Units acquired pursuant to this Agreement may not be transferred, 
+sold, pledged, hypothecated or otherwise disposed of, voluntarily or involuntarily, by 
+operation of law or otherwise, 
+
+## Investment Representations
+
+Participant acknowledges that he or she is aware that the Profits Interest Units issued 
+to him by the Company pursuant to this Agreement have not been registered under the 
+Securities Act of 1933, as amended (the “Securities Act”), on the basis of certain exemptions 
+from such registration requirement. In this connection, 
+
+## Section 83(b) Election. 
+
+Participant shall execute and deliver to the Company with this executed Agreement, 
+a copy of the Acknowledgment and Statement of Decision Regarding Election Pursuant 
+to Section 83(b) of the Internal Revenue Code (the “Acknowledgment”) substantially in 
+the form attached hereto. 
+
+Participant shall execute and submit with the Acknowledgment a copy of the Election Pursuant 
+to Section 83(b) of the Internal Revenue Code, substantially in the form attached hereto
+if Participant has indicated in the Acknowledgment his or her decision to make such an election. 
+
+Participant represents that Participant is not relying on the Company with respect to 
+such decision and has consulted any tax consultant(s) that Participant deems advisable in 
+connection with the filing of an election under Section 83(b) of the Code and 
+similar tax provisions. 
+
+Participant acknowledges that it is Participant’s sole responsibility and not the Company’s to 
+timely file an election under Section 83(b) of the Code, even if Participant requests that the 
+Company or any representative of the Company make such filing on Participant’s behalf. 
+
+Participant should consult his or her tax advisor to determine if there is a comparable election 
+to file in the state of his or her residence and whether such filing is desirable under the 
+circumstances.
+
+## Taxes
+
+The Company and Party intend that (i) the Profits Interest Units be treated as “profits interests” within the meaning of the Code, Treasury Regulations promulgated thereunder, and any published guidance by the Internal Revenue Service with respect thereto, including, without limitation, Internal Revenue Service Revenue Procedure 93-27, as clarified by Internal Revenue Service Revenue Procedure 2001-43, (ii) the issuance of such interests not be a taxable event to the Company or Participant as provided in such Revenue Procedure, and (iii) the Agreement be interpreted consistently with such intent. 
+
+In furtherance of such intent, effective immediately prior to the issuance of the Profits Interest Units, the Company will cause the Gross Asset Value (as defined in the Agreement) of all Company assets to be adjusted to equal their respective gross fair market values, and make the resulting adjustments to the Capital Accounts of the Members, in each case as set forth in the Agreement. 
+
+The Company may withhold from Participant’s wages, or require Participant to pay to the Company, any applicable withholding or employment taxes resulting from the issuance of the Profits Interest Units hereunder, from the vesting or lapse of any restrictions imposed on the Profits Interest Units, or from the ownership or disposition of the Profits Interest Units.
+
+## Code Section 409A
+
+The Profits Interest Units are not intended to constitute or provide for “nonqualified deferred compensation” within the meaning of Section 409A of the Code (“Section 409A”), and, provided that Section 409A of the Code, Treasury Regulations and related Department of Treasury guidance do not require otherwise, the Company shall not treat the Profits Interest Units as nonqualified deferred compensation. However, notwithstanding any other provision of this Agreement, if at any time the Board Of Directors determine that the Profits Interest Units may be subject to Section 409A, the Board Of Directors 
+shall have the right, in their sole discretion, to adopt such amendments to this Agreement or take such other actions (including amendments and actions with retroactive effect) as the Board Of Directors determine are necessary or appropriate for the 
+Profits Interest Units to be exempt from the application of Section 409A or to comply with the requirements of Section 409A; provided, however, if such action would diminish the value of the Profits Interest Units, such action may not be taken without Members written consent.
+
+
+## ACKNOWLEDGMENT AND STATEMENT OF DECISION REGARDING ELECTION PURSUANT TO SECTION 83(b) OF THE INTERNAL REVENUE CODE
+
+The undersigned, a Member of the “Company” and holder of Profits Interest
+in the Company designated as “Profits Interest Units” (the “Award”) of the Company, 
+hereby states, as of the date of issuance of the Award, as follows:
+
+1.    The undersigned acknowledges receipt of a copy of the Agreement. The undersigned has carefully reviewed the Agreement.
+
+2.    The undersigned either [check as applicable]:
+____ (a) has consulted, and has been fully advised by, the undersigned’s own tax advisor, __________________________________________, whose business address is ________________________________, regarding the federal, state and local tax consequences of being issued the Award under the Agreement, and particularly regarding the advisability of making elections pursuant to Section 83(b) of the Internal Revenue Code of 1986, as amended (the “Code”), and pursuant to the corresponding provisions, if any, of applicable state laws; or
+
+____ (b) has knowingly chosen not to consult such tax advisor.
+
+3.    The undersigned hereby states that the undersigned either [check as applicable]:
+
+_____ (a) has decided to make an election pursuant to Section 83(b) of the Code and is submitting to the Company, together with the undersigned’s executed Agreement, a copy of an executed election form which is attached to the Agreement; or
+
+____ (b) has knowingly chosen not to make an election pursuant to Section 83(b) of the Code.
+
+4.    Neither the Company nor any subsidiary or representative of the Company has made any warranty or representation to the undersigned with respect to the tax consequences of the issuance of the Award to the undersigned pursuant to the Agreement or of the making or failure to make an election pursuant to Section 83(b) of the Code or corresponding provisions, if any, of applicable state law.
+
+5.    The undersigned is also submitting to the Company, together with the Agreement, a copy of an executed election form, if an election is made, of the undersigned pursuant to provisions of state law corresponding to Section 83(b) of the Code, if any, which are applicable to the issuance of the Award to the undersigned pursuant to the Agreement.
+
+
+ELECTION PURSUANT TO SECTION 83(b) OF THE INTERNAL REVENUE CODE TO INCLUDE IN GROSS
+INCOME THE EXCESS OVER THE PURCHASE PRICE, IF ANY, OF THE VALUE OF PROPERTY TRANSFERRED
+IN CONNECTION WITH SERVICES
+
+The undersigned hereby elects pursuant to Section 83(b) of the Internal Revenue Code of 1986, as amended, to include in the undersigned’s gross income for the taxable year the excess (if any) of the fair market value of the property described below, over the amount the undersigned paid for such property, if any, and supplies herewith the following information in accordance with the Treasury regulations promulgated under Section 83(b):
+
+1.    The undersigned’s name, address and taxpayer identification (social security) number are:
+Name:    
+Address:        
+TIN:
+
+2.    The property with respect to which the election is made consists of 
+[•] Units in the Company designated as “Profits Interest Units” (the “Award”) of the Company representing an interest in the future profits, losses and distributions of the Company.
+
+3.    The date on which the above property was transferred to the undersigned was [•], and the taxable year to which this election relates is [•].
+
+4.    The above property is subject to the following restrictions: 
+
+(a) forfeiture and/or a right of repurchase by the Company if the undersigned ceases 
+to be an employee of, or consultant or service provider to, the Company under certain circumstances pursuant to the LLC Agreement of the Company, as amended from time to time (the “LLC Agreement”), and
+ (b) certain other restrictions pursuant to the LLC Agreement should the undersigned wish to transfer the Award (in whole or in part).
+
+5.    The fair market value of the above property at the time of transfer (determined without regard to any restrictions other than those which by their terms will never lapse) is $0.
+
+6.    The amount paid for the above property by the undersigned was $0.
+
+7.    A copy of this election has been furnished to the Company, and the original will be filed with the income tax return of the undersigned to which this election relates.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/LICENSE

@@ -0,0 +1,628 @@
+v3 ONLY 
+
+
+GNU GENERAL PUBLIC LICENSE
+
+Version 3, 29 June 2007
+
+Copyright © 2007 Free Software Foundation, Inc. <https://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license
+document, but changing it is not allowed.
+
+Preamble
+
+The GNU General Public License is a free, copyleft license for software and
+other kinds of works.
+
+The licenses for most software and other practical works are designed to take
+away your freedom to share and change the works. By contrast, the GNU General
+Public License is intended to guarantee your freedom to share and change all
+versions of a program--to make sure it remains free software for all its users.
+We, the Free Software Foundation, use the GNU General Public License for most
+of our software; it applies also to any other work released this way by its
+authors. You can apply it to your programs, too.
+
+When we speak of free software, we are referring to freedom, not price. Our
+General Public Licenses are designed to make sure that you have the freedom
+to distribute copies of free software (and charge for them if you wish), that
+you receive source code or can get it if you want it, that you can change
+the software or use pieces of it in new free programs, and that you know you
+can do these things.
+
+To protect your rights, we need to prevent others from denying you these rights
+or asking you to surrender the rights. Therefore, you have certain responsibilities
+if you distribute copies of the software, or if you modify it: responsibilities
+to respect the freedom of others.
+
+For example, if you distribute copies of such a program, whether gratis or
+for a fee, you must pass on to the recipients the same freedoms that you received.
+You must make sure that they, too, receive or can get the source code. And
+you must show them these terms so they know their rights.
+
+Developers that use the GNU GPL protect your rights with two steps: (1) assert
+copyright on the software, and (2) offer you this License giving you legal
+permission to copy, distribute and/or modify it.
+
+For the developers' and authors' protection, the GPL clearly explains that
+there is no warranty for this free software. For both users' and authors'
+sake, the GPL requires that modified versions be marked as changed, so that
+their problems will not be attributed erroneously to authors of previous versions.
+
+Some devices are designed to deny users access to install or run modified
+versions of the software inside them, although the manufacturer can do so.
+This is fundamentally incompatible with the aim of protecting users' freedom
+to change the software. The systematic pattern of such abuse occurs in the
+area of products for individuals to use, which is precisely where it is most
+unacceptable. Therefore, we have designed this version of the GPL to prohibit
+the practice for those products. If such problems arise substantially in other
+domains, we stand ready to extend this provision to those domains in future
+versions of the GPL, as needed to protect the freedom of users.
+
+Finally, every program is threatened constantly by software patents. States
+should not allow patents to restrict development and use of software on general-purpose
+computers, but in those that do, we wish to avoid the special danger that
+patents applied to a free program could make it effectively proprietary. To
+prevent this, the GPL assures that patents cannot be used to render the program
+non-free.
+
+The precise terms and conditions for copying, distribution and modification
+follow.
+
+TERMS AND CONDITIONS
+
+   0. Definitions.
+
+   "This License" refers to version 3 of the GNU General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of works,
+such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this License.
+Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals
+or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work in
+a fashion requiring copyright permission, other than the making of an exact
+copy. The resulting work is called a "modified version" of the earlier work
+or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based on the
+Program.
+
+To "propagate" a work means to do anything with it that, without permission,
+would make you directly or secondarily liable for infringement under applicable
+copyright law, except executing it on a computer or modifying a private copy.
+Propagation includes copying, distribution (with or without modification),
+making available to the public, and in some countries other activities as
+well.
+
+To "convey" a work means any kind of propagation that enables other parties
+to make or receive copies. Mere interaction with a user through a computer
+network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to the
+extent that it includes a convenient and prominently visible feature that
+(1) displays an appropriate copyright notice, and (2) tells the user that
+there is no warranty for the work (except to the extent that warranties are
+provided), that licensees may convey the work under this License, and how
+to view a copy of this License. If the interface presents a list of user commands
+or options, such as a menu, a prominent item in the list meets this criterion.
+
+   1. Source Code.
+
+The "source code" for a work means the preferred form of the work for making
+modifications to it. "Object code" means any non-source form of a work.
+
+A "Standard Interface" means an interface that either is an official standard
+defined by a recognized standards body, or, in the case of interfaces specified
+for a particular programming language, one that is widely used among developers
+working in that language.
+
+The "System Libraries" of an executable work include anything, other than
+the work as a whole, that (a) is included in the normal form of packaging
+a Major Component, but which is not part of that Major Component, and (b)
+serves only to enable use of the work with that Major Component, or to implement
+a Standard Interface for which an implementation is available to the public
+in source code form. A "Major Component", in this context, means a major essential
+component (kernel, window system, and so on) of the specific operating system
+(if any) on which the executable work runs, or a compiler used to produce
+the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all the source
+code needed to generate, install, and (for an executable work) run the object
+code and to modify the work, including scripts to control those activities.
+However, it does not include the work's System Libraries, or general-purpose
+tools or generally available free programs which are used unmodified in performing
+those activities but which are not part of the work. For example, Corresponding
+Source includes interface definition files associated with source files for
+the work, and the source code for shared libraries and dynamically linked
+subprograms that the work is specifically designed to require, such as by
+intimate data communication or control flow between those subprograms and
+other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate
+automatically from other parts of the Corresponding Source.
+
+   The Corresponding Source for a work in source code form is that same work.
+
+   2. Basic Permissions.
+
+All rights granted under this License are granted for the term of copyright
+on the Program, and are irrevocable provided the stated conditions are met.
+This License explicitly affirms your unlimited permission to run the unmodified
+Program. The output from running a covered work is covered by this License
+only if the output, given its content, constitutes a covered work. This License
+acknowledges your rights of fair use or other equivalent, as provided by copyright
+law.
+
+You may make, run and propagate covered works that you do not convey, without
+conditions so long as your license otherwise remains in force. You may convey
+covered works to others for the sole purpose of having them make modifications
+exclusively for you, or provide you with facilities for running those works,
+provided that you comply with the terms of this License in conveying all material
+for which you do not control copyright. Those thus making or running the covered
+works for you must do so exclusively on your behalf, under your direction
+and control, on terms that prohibit them from making any copies of your copyrighted
+material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions
+stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
+
+   3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+
+No covered work shall be deemed part of an effective technological measure
+under any applicable law fulfilling obligations under article 11 of the WIPO
+copyright treaty adopted on 20 December 1996, or similar laws prohibiting
+or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention
+of technological measures to the extent such circumvention is effected by
+exercising rights under this License with respect to the covered work, and
+you disclaim any intention to limit operation or modification of the work
+as a means of enforcing, against the work's users, your or third parties'
+legal rights to forbid circumvention of technological measures.
+
+   4. Conveying Verbatim Copies.
+
+You may convey verbatim copies of the Program's source code as you receive
+it, in any medium, provided that you conspicuously and appropriately publish
+on each copy an appropriate copyright notice; keep intact all notices stating
+that this License and any non-permissive terms added in accord with section
+7 apply to the code; keep intact all notices of the absence of any warranty;
+and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you
+may offer support or warranty protection for a fee.
+
+   5. Conveying Modified Source Versions.
+
+You may convey a work based on the Program, or the modifications to produce
+it from the Program, in the form of source code under the terms of section
+4, provided that you also meet all of these conditions:
+
+a) The work must carry prominent notices stating that you modified it, and
+giving a relevant date.
+
+b) The work must carry prominent notices stating that it is released under
+this License and any conditions added under section 7. This requirement modifies
+the requirement in section 4 to "keep intact all notices".
+
+c) You must license the entire work, as a whole, under this License to anyone
+who comes into possession of a copy. This License will therefore apply, along
+with any applicable section 7 additional terms, to the whole of the work,
+and all its parts, regardless of how they are packaged. This License gives
+no permission to license the work in any other way, but it does not invalidate
+such permission if you have separately received it.
+
+d) If the work has interactive user interfaces, each must display Appropriate
+Legal Notices; however, if the Program has interactive interfaces that do
+not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works,
+which are not by their nature extensions of the covered work, and which are
+not combined with it such as to form a larger program, in or on a volume of
+a storage or distribution medium, is called an "aggregate" if the compilation
+and its resulting copyright are not used to limit the access or legal rights
+of the compilation's users beyond what the individual works permit. Inclusion
+of a covered work in an aggregate does not cause this License to apply to
+the other parts of the aggregate.
+
+   6. Conveying Non-Source Forms.
+
+You may convey a covered work in object code form under the terms of sections
+4 and 5, provided that you also convey the machine-readable Corresponding
+Source under the terms of this License, in one of these ways:
+
+a) Convey the object code in, or embodied in, a physical product (including
+a physical distribution medium), accompanied by the Corresponding Source fixed
+on a durable physical medium customarily used for software interchange.
+
+b) Convey the object code in, or embodied in, a physical product (including
+a physical distribution medium), accompanied by a written offer, valid for
+at least three years and valid for as long as you offer spare parts or customer
+support for that product model, to give anyone who possesses the object code
+either (1) a copy of the Corresponding Source for all the software in the
+product that is covered by this License, on a durable physical medium customarily
+used for software interchange, for a price no more than your reasonable cost
+of physically performing this conveying of source, or (2) access to copy the
+Corresponding Source from a network server at no charge.
+
+c) Convey individual copies of the object code with a copy of the written
+offer to provide the Corresponding Source. This alternative is allowed only
+occasionally and noncommercially, and only if you received the object code
+with such an offer, in accord with subsection 6b.
+
+d) Convey the object code by offering access from a designated place (gratis
+or for a charge), and offer equivalent access to the Corresponding Source
+in the same way through the same place at no further charge. You need not
+require recipients to copy the Corresponding Source along with the object
+code. If the place to copy the object code is a network server, the Corresponding
+Source may be on a different server (operated by you or a third party) that
+supports equivalent copying facilities, provided you maintain clear directions
+next to the object code saying where to find the Corresponding Source. Regardless
+of what server hosts the Corresponding Source, you remain obligated to ensure
+that it is available for as long as needed to satisfy these requirements.
+
+e) Convey the object code using peer-to-peer transmission, provided you inform
+other peers where the object code and Corresponding Source of the work are
+being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from
+the Corresponding Source as a System Library, need not be included in conveying
+the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any tangible
+personal property which is normally used for personal, family, or household
+purposes, or (2) anything designed or sold for incorporation into a dwelling.
+In determining whether a product is a consumer product, doubtful cases shall
+be resolved in favor of coverage. For a particular product received by a particular
+user, "normally used" refers to a typical or common use of that class of product,
+regardless of the status of the particular user or of the way in which the
+particular user actually uses, or expects or is expected to use, the product.
+A product is a consumer product regardless of whether the product has substantial
+commercial, industrial or non-consumer uses, unless such uses represent the
+only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods, procedures,
+authorization keys, or other information required to install and execute modified
+versions of a covered work in that User Product from a modified version of
+its Corresponding Source. The information must suffice to ensure that the
+continued functioning of the modified object code is in no case prevented
+or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically
+for use in, a User Product, and the conveying occurs as part of a transaction
+in which the right of possession and use of the User Product is transferred
+to the recipient in perpetuity or for a fixed term (regardless of how the
+transaction is characterized), the Corresponding Source conveyed under this
+section must be accompanied by the Installation Information. But this requirement
+does not apply if neither you nor any third party retains the ability to install
+modified object code on the User Product (for example, the work has been installed
+in ROM).
+
+The requirement to provide Installation Information does not include a requirement
+to continue to provide support service, warranty, or updates for a work that
+has been modified or installed by the recipient, or for the User Product in
+which it has been modified or installed. Access to a network may be denied
+when the modification itself materially and adversely affects the operation
+of the network or violates the rules and protocols for communication across
+the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord
+with this section must be in a format that is publicly documented (and with
+an implementation available to the public in source code form), and must require
+no special password or key for unpacking, reading or copying.
+
+   7. Additional Terms.
+
+"Additional permissions" are terms that supplement the terms of this License
+by making exceptions from one or more of its conditions. Additional permissions
+that are applicable to the entire Program shall be treated as though they
+were included in this License, to the extent that they are valid under applicable
+law. If additional permissions apply only to part of the Program, that part
+may be used separately under those permissions, but the entire Program remains
+governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any
+additional permissions from that copy, or from any part of it. (Additional
+permissions may be written to require their own removal in certain cases when
+you modify the work.) You may place additional permissions on material, added
+by you to a covered work, for which you have or can give appropriate copyright
+permission.
+
+Notwithstanding any other provision of this License, for material you add
+to a covered work, you may (if authorized by the copyright holders of that
+material) supplement the terms of this License with terms:
+
+a) Disclaiming warranty or limiting liability differently from the terms of
+sections 15 and 16 of this License; or
+
+b) Requiring preservation of specified reasonable legal notices or author
+attributions in that material or in the Appropriate Legal Notices displayed
+by works containing it; or
+
+c) Prohibiting misrepresentation of the origin of that material, or requiring
+that modified versions of such material be marked in reasonable ways as different
+from the original version; or
+
+d) Limiting the use for publicity purposes of names of licensors or authors
+of the material; or
+
+e) Declining to grant rights under trademark law for use of some trade names,
+trademarks, or service marks; or
+
+f) Requiring indemnification of licensors and authors of that material by
+anyone who conveys the material (or modified versions of it) with contractual
+assumptions of liability to the recipient, for any liability that these contractual
+assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further restrictions"
+within the meaning of section 10. If the Program as you received it, or any
+part of it, contains a notice stating that it is governed by this License
+along with a term that is a further restriction, you may remove that term.
+If a license document contains a further restriction but permits relicensing
+or conveying under this License, you may add to a covered work material governed
+by the terms of that license document, provided that the further restriction
+does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place,
+in the relevant source files, a statement of the additional terms that apply
+to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form
+of a separately written license, or stated as exceptions; the above requirements
+apply either way.
+
+   8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided
+under this License. Any attempt otherwise to propagate or modify it is void,
+and will automatically terminate your rights under this License (including
+any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from
+a particular copyright holder is reinstated (a) provisionally, unless and
+until the copyright holder explicitly and finally terminates your license,
+and (b) permanently, if the copyright holder fails to notify you of the violation
+by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently
+if the copyright holder notifies you of the violation by some reasonable means,
+this is the first time you have received notice of violation of this License
+(for any work) from that copyright holder, and you cure the violation prior
+to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses
+of parties who have received copies or rights from you under this License.
+If your rights have been terminated and not permanently reinstated, you do
+not qualify to receive new licenses for the same material under section 10.
+
+   9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy
+of the Program. Ancillary propagation of a covered work occurring solely as
+a consequence of using peer-to-peer transmission to receive a copy likewise
+does not require acceptance. However, nothing other than this License grants
+you permission to propagate or modify any covered work. These actions infringe
+copyright if you do not accept this License. Therefore, by modifying or propagating
+a covered work, you indicate your acceptance of this License to do so.
+
+   10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives
+a license from the original licensors, to run, modify and propagate that work,
+subject to this License. You are not responsible for enforcing compliance
+by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an organization,
+or substantially all assets of one, or subdividing an organization, or merging
+organizations. If propagation of a covered work results from an entity transaction,
+each party to that transaction who receives a copy of the work also receives
+whatever licenses to the work the party's predecessor in interest had or could
+give under the previous paragraph, plus a right to possession of the Corresponding
+Source of the work from the predecessor in interest, if the predecessor has
+it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights
+granted or affirmed under this License. For example, you may not impose a
+license fee, royalty, or other charge for exercise of rights granted under
+this License, and you may not initiate litigation (including a cross-claim
+or counterclaim in a lawsuit) alleging that any patent claim is infringed
+by making, using, selling, offering for sale, or importing the Program or
+any portion of it.
+
+   11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this License
+of the Program or a work on which the Program is based. The work thus licensed
+is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned or controlled
+by the contributor, whether already acquired or hereafter acquired, that would
+be infringed by some manner, permitted by this License, of making, using,
+or selling its contributor version, but do not include claims that would be
+infringed only as a consequence of further modification of the contributor
+version. For purposes of this definition, "control" includes the right to
+grant patent sublicenses in a manner consistent with the requirements of this
+License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent
+license under the contributor's essential patent claims, to make, use, sell,
+offer for sale, import and otherwise run, modify and propagate the contents
+of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express agreement
+or commitment, however denominated, not to enforce a patent (such as an express
+permission to practice a patent or covenant not to sue for patent infringement).
+To "grant" such a patent license to a party means to make such an agreement
+or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the
+Corresponding Source of the work is not available for anyone to copy, free
+of charge and under the terms of this License, through a publicly available
+network server or other readily accessible means, then you must either (1)
+cause the Corresponding Source to be so available, or (2) arrange to deprive
+yourself of the benefit of the patent license for this particular work, or
+(3) arrange, in a manner consistent with the requirements of this License,
+to extend the patent license to downstream recipients. "Knowingly relying"
+means you have actual knowledge that, but for the patent license, your conveying
+the covered work in a country, or your recipient's use of the covered work
+in a country, would infringe one or more identifiable patents in that country
+that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement,
+you convey, or propagate by procuring conveyance of, a covered work, and grant
+a patent license to some of the parties receiving the covered work authorizing
+them to use, propagate, modify or convey a specific copy of the covered work,
+then the patent license you grant is automatically extended to all recipients
+of the covered work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the scope
+of its coverage, prohibits the exercise of, or is conditioned on the non-exercise
+of one or more of the rights that are specifically granted under this License.
+You may not convey a covered work if you are a party to an arrangement with
+a third party that is in the business of distributing software, under which
+you make payment to the third party based on the extent of your activity of
+conveying the work, and under which the third party grants, to any of the
+parties who would receive the covered work from you, a discriminatory patent
+license (a) in connection with copies of the covered work conveyed by you
+(or copies made from those copies), or (b) primarily for and in connection
+with specific products or compilations that contain the covered work, unless
+you entered into that arrangement, or that patent license was granted, prior
+to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied
+license or other defenses to infringement that may otherwise be available
+to you under applicable patent law.
+
+   12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise)
+that contradict the conditions of this License, they do not excuse you from
+the conditions of this License. If you cannot convey a covered work so as
+to satisfy simultaneously your obligations under this License and any other
+pertinent obligations, then as a consequence you may not convey it at all.
+For example, if you agree to terms that obligate you to collect a royalty
+for further conveying from those to whom you convey the Program, the only
+way you could satisfy both those terms and this License would be to refrain
+entirely from conveying the Program.
+
+   13. Use with the GNU Affero General Public License.
+
+Notwithstanding any other provision of this License, you have permission to
+link or combine any covered work with a work licensed under version 3 of the
+GNU Affero General Public License into a single combined work, and to convey
+the resulting work. The terms of this License will continue to apply to the
+part which is the covered work, but the special requirements of the GNU Affero
+General Public License, section 13, concerning interaction through a network
+will apply to the combination as such.
+
+   14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the
+GNU General Public License from time to time. Such new versions will be similar
+in spirit to the present version, but may differ in detail to address new
+problems or concerns.
+
+Each version is given a distinguishing version number. If the Program specifies
+that a certain numbered version of the GNU General Public License "or any
+later version" applies to it, you have the option of following the terms and
+conditions either of that numbered version or of any later version published
+by the Free Software Foundation. If the Program does not specify a version
+number of the GNU General Public License, you may choose any version ever
+published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of
+the GNU General Public License can be used, that proxy's public statement
+of acceptance of a version permanently authorizes you to choose that version
+for the Program.
+
+Later license versions may give you additional or different permissions. However,
+no additional obligations are imposed on any author or copyright holder as
+a result of your choosing to follow a later version.
+
+   15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE
+LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
+EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
+OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
+TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM
+PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR
+CORRECTION.
+
+   16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL
+ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM
+AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL,
+INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO
+USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED
+INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE
+PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER
+PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+   17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot
+be given local legal effect according to their terms, reviewing courts shall
+apply local law that most closely approximates an absolute waiver of all civil
+liability in connection with the Program, unless a warranty or assumption
+of liability accompanies a copy of the Program in return for a fee. END OF
+TERMS AND CONDITIONS
+
+How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible
+use to the public, the best way to achieve this is to make it free software
+which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program. It is safest to attach
+them to the start of each source file to most effectively state the exclusion
+of warranty; and each file should have at least the "copyright" line and a
+pointer to where the full notice is found.
+
+<one line to give the program's name and a brief idea of what it does.>
+
+Copyright (C) <year> <name of author>
+
+This program is free software: you can redistribute it and/or modify it under
+the terms of the GNU General Public License as published by the Free Software
+Foundation, either version 3 of the License, or (at your option) any later
+version.
+
+This program is distributed in the hope that it will be useful, but WITHOUT
+ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
+FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License along with
+this program. If not, see <https://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If the program does terminal interaction, make it output a short notice like
+this when it starts in an interactive mode:
+
+<program> Copyright (C) <year> <name of author>
+
+This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
+
+This is free software, and you are welcome to redistribute it under certain
+conditions; type `show c' for details.
+
+The hypothetical commands `show w' and `show c' should show the appropriate
+parts of the General Public License. Of course, your program's commands might
+be different; for a GUI interface, you would use an "about box".
+
+You should also get your employer (if you work as a programmer) or school,
+if any, to sign a "copyright disclaimer" for the program, if necessary. For
+more information on this, and how to apply and follow the GNU GPL, see <https://www.gnu.org/licenses/>.
+
+The GNU General Public License does not permit incorporating your program
+into proprietary programs. If your program is a subroutine library, you may
+consider it more useful to permit linking proprietary applications with the
+library. If this is what you want to do, use the GNU Lesser General Public
+License instead of this License. But first, please read <https://www.gnu.org/
+licenses /why-not-lgpl.html>.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/README.md

@@ -0,0 +1,90 @@
+# Redwood Springs Capital Partners - StartupStarterPackage
+
+## Welcome
+
+This is a collection of material that we've assembled over 10+ years of operational
+experience. 
+
+## Repo issues
+https://projects.knownelement.com/project/reachableceo-redwood-springs-capital-partners-rwscp/kanban
+
+## Repo discussion
+https://community.turnsys.com/t/about-the-chiefcommonsofficer-rwscp-category/24
+
+## Contents
+
+* CommonBoilerplate (what it says on the tin. lots of common legal stuff)
+* SingeLLCOpAgreement (non series LLC Op Agreement) (series stuff is..... L2/sysarch stuff, you don't want none of that)
+* StratFramework (key questions you've got to answer. our take on the business model canvas etc)
+* LICENSE (gplv3. viral. we ain't gonna let nobody hijack our hard work we're releasing to all you fine folk!)
+* README.md (this file)
+
+## Merge / TODO
+
+- Merge the following series language:
+
+```
+series language
+
+Notice of Limitation on Liability of Series
+
+The Company Agreement may establish or provide for the establishment of one or more designated series of members, managers, membership interests, or assets that (1) has separate rights,
+powers, or duties with respect to specified property or obligations of the Company or profits and losses associated with specified property or obligations, or (2)
+has a separate business purpose or investment objective.
+
+Subject to the provisions of the Texas Business Organizations Code (1) the debts, liabilities, obligations, and expenses incurred, contracted for, or otherwise existing with
+respect to a particular series shall be enforceable against the assets of that series only, and shall not be enforceable against the assets of the Company generally
+or any other series, and (2) none of the debts, liabilities, obligations, and expenses incurred, contracted for, or otherwise existing with respect to the Company generally –
+or any other series – shall be enforceable against the assets of a particular series.
+
+Specific series of assets shall be separately labeled or enumerated in such a manner as to identify each series’ assets, structure, and operations.
+Pursuant to §101.614 of the Texas Business Organizations Code, and as ore fully set forth in the Company Agreement,
+a specific series and its business and affairs ay be wound up and terminated without causing the winding up of the Company.
+The winding up of a series shall not affect the litigation of liability of members and managers of other series or the Company at large.
+```
+ 
+- Update RR/Subo LLC Operating Agreements using fairshares model
+- Contract execution
+  - NDA
+  - Updated operating agreement
+  - Non compete
+  - Invention Assignment
+  - anything else needed from <http://siliconhillslawyer.co/startup-formation-issues/>  <http://siliconhillslawyer.co/2013/05/01/austin-startup-form-yourself-avoid-crappy-lawyers/>
+
+- Finish federal government registration for all entities
+
+| Task       | Notes |
+| ---------- | ----- |
+| SBIR Reg   |       |
+| NASA SBIR  |       |
+| Grants.gov |       |
+| DOD SBIR   |       |
+| SAM        |       |
+| NSF        |       |
+| Grants.gov |       |
+| DOD SBIR   |       |
+| DHS SBIR   |       |
+| DOE        |       |
+
+| Entity Name    | Bank Account | Online Banking   | Stripe  | Paypal  | Fileshare | State Tax Filing | Federal Tax Filing | EIN        | EIN no dash | Other Federal Filings | Sales tax & Use Permit |
+|----------------|--------------|------------------|---------|---------|-----------|------------------|--------------------|------------|-------------|-----------------------|------------------------|
+| Subo LLC       | Y            | Y                | Y       | Y       | Y         | Y                |                    | 84-2245901 | 842245901   |                       | Y                      |
+| RackRental LLC | Y            | Pending Amp call | Blocked | Blocked | Y         | Y                |                    | 84-2251518 | 842251518   |                       | Y                      |
+| RWSCP Series   | N/A          | N/A              | N/A     | N/A     | Y         | N/A              | N/A                |            |             |                       | N/A                    |
+| RWSCP BDC Inc  | N/A          | N/A              | N/A     | N/A     | Y         |                  |                    |            |             |                       | N/A                    |
+| AFABN INC      | N/A          | N/A              | N/A     | N/A     | Y         | Y                |                    | 84-1825176 | 841825176   | N/A                   | N/A                    |
+| SDSG 501c4 INC | N/A          | N/A              | N/A     | N/A     | Y         | Y                |                    |            |             | N/A                   | N/A                    |
+| SDG PAC INC    | N/A          | N/A              | N/A     | N/A     | Y         | Y                |                    | 84-1855678 | 841855678   |                       | N/A                    |
+| HFNOC Series   | N/A          | N/A              | N/A     | N/A     | Y         | N/A              | N/A                |            |             | N/A                   | N/A                    |
+| Axios Series   | Y            | Y                | Y       | Y       | Y         | Y                | Y                  |            |             |                       | Y                      |
+
+#### Bizops Marketing
+
+| Brand Name         | Webstats | Facebook Page | Instagram | Twitter | Reddit  | Cross Social Integration | WP tech | WP social integration | Mautic |
+| ------------------ | -------- | ------------- | --------- | ------- | ------- | ------------------------ | ------- | --------------------- | ------- |
+| Suborbital Systems | Y        | Y             | Y         | Y       | Y       |                          | Y       |                       |         |
+| RackRental.net     | Y        | Y             | Y         | Y       | recover |                          | Y       |                       |         |
+| RWSCP              | Y        | Y             | Y         | Y       | Y       |                          | Y       |                       |         |
+| AFABN              | Y        | Y             | Y         | Y       | Y       |                          | Y       |                       |         |
+| SDG                | Y        | Y             | Y         | Y       | Y       |                          | Y       |                       |         |
+| HFNOC              | Y        | Y             | Y         | Y       | Y       |                          | Y       |                       |         |

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/SingeLLCOpAgreement/CompanyNameAndPurpose.md

@@ -0,0 +1,41 @@
+# Introduction
+In order to form a limited liability company pursuant to and in
+accordance with the Texas Business Organization Code (BOC), as amended
+from time to time, the Members hereby agree as follows:
+
+# Company Name
+The name of the limited liability company formed hereby shall be:
+<company name LLC>
+
+# Company Purpose
+The Company shall have the power (whether conducted
+directly or indirectly through any type of Investment in any type of
+Person)  to engage in the following activities:
+
+* acquiring
+
+* owning
+
+* holding
+
+* maintaining
+
+* improving
+
+* developing
+
+* operating
+
+* managing 
+
+* leasing
+
+* selling
+
+* exchanging
+
+* the financing of any of the foregoing activities
+
+* and otherwise dealing with 
+
+All things related to <Company name LLC>

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/SingeLLCOpAgreement/ProfitInterestGrant.md

@@ -0,0 +1,37 @@
+
+# Grant Of Profit Interests To Members (capitalization table)
+
+The Company desires to issue a percentage of the Company profits 
+designated as “Profits Interest Units” to the Member in connection with 
+Members performance of services for the benefit of the Company.
+
+The parties intend that the Profits Interest Units issued pursuant to this Agreement constitute “profits interests,” 
+as described in Section 4.01 of Rev. Proc. 93-27, 1993-2 C.B. 343, as clarified by 
+Rev. Proc. 2001-43, 2001-34 I.R.B. 191, issued by the Internal Revenue Service.
+
+The Company will revalue its assets as of the Effective Date in accordance with Treasury Regulations Section 
+1.704-1(b)(2)(iv)(f)(5)(iii) and the Capital Accounts of the Members of the Company will be adjusted to reflect 
+such revaluation.
+
+In consideration of Members providing services for the benefit of the Company, the Company hereby issues to Members 
+the percentage interests below:
+
+FILLTHISIN
+
+
+* 
+
+* 
+
+* 
+
+The above interests are fully vested. 
+
+* Reserved for future members pre SEAL capital raise : 
+
+* Reserved for SEAL raise : 
+
+The above two interests are subject to negoiation in regards to vesting.
+
+FILLTHISIN (put vesting terms if any here) (or remove this whole section as desired)
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/SingeLLCOpAgreement/README.md

@@ -0,0 +1,18 @@
+# Texas LLC Operating Agreement Template
+
+Hello.
+
+So you want to start a company in the great state of Texas, and you want to sink in
+years of blood/sweat/tears and not take any of Redwoods cash? 
+
+Awesome!!!! Welcome to the party!
+
+Let's get this out of the way:
+
+* No warranties express or implied. 
+
+Otherwise, here's the keys, hack as needed, stay out of court and don't fly too close
+to the sun! YeHah!
+
+All bits are licensed as "public domain, do what you want, don't sue us!"
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/SingeLLCOpAgreement/TitlePage.md

@@ -0,0 +1,3 @@
+---
+title: "company name Limited Liability Company NonDisclosure , Intellectual Property Assignment , Operating Agreement"
+---

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/SingeLLCOpAgreement/TxLLCExampleAgreement.md

@@ -0,0 +1,700 @@
+# Introduction
+In order to form a limited liability company pursuant to and in
+accordance with the Texas Business Organization Code (BOC), as amended
+from time to time, the Members hereby agree as follows
+
+
+# Outside Capital Raising
+
+## Non Equity and Non Debt based
+
+Capital will be primarily sought through the pursuit of R&D funding from (but not
+limited to):
+
+* Department Of Defense SBIR
+* NSF Seed Fund
+* Department Of Homeland Security SBIR
+* NASA SBIR
+* other similiar United States Federal Government funding vehicles
+
+## Restrictions on Capital Sources
+
+* At no time shall capital be raised from non US funding sources.
+
+* At no time shall capital be raised from non-accredited investors.
+
+## Equity Based Raises
+
+### General Conditions and Requirements
+
+Any grant of equity in exchange for outside capital investment in the Company 
+shall be on the following (or substantially similiar) terms and conditions , 
+and require unamious written consent of the Members and the Board Of Directors.
+
+### Terms and Conditions
+
+[PUBLIC] Earnest Shared Earnings Agreement v1.3
+SHARED EARNINGS AGREEMENT BETWEEN EARNEST CAPITAL AND Company.
+
+Date
+
+The following is a summary of the principal terms with respect to the proposed financing of _______________ (the “Company”).  Except for the section entitled “Confidentiality,” this summary of terms does not constitute a legally binding obligation. The parties intend to enter into a legally binding obligation only pursuant to definitive agreements to be negotiated and executed by the parties.
+Amount of Investment
+
+$___________
+
+Shared Earnings
+By the 10th day of each quarter, the Company will pay the Investor the Percentage 
+(as defined below) of: the Company's Founder Earnings (as defined below) 
+less the proportional Founder Earnings Threshold (as defined below),  
+in the preceding quarter. 
+
+Shared Earnings shall continue until the Investor has received the Shared Earnings Cap. 
+
+The Percentage
+The Percentage shall be ___%.
+
+Net Income
+Net Income means net income determined in accordance with GAAP.
+
+Founder Earnings
+Founder Earnings means Net Income, adding back any founders' salaries.
+
+Founder Earnings Threshold
+$________ per founder per year.
+
+Shared Earnings Cap
+The Shared Earnings Cap will be __X the investment amount.
+
+Equity Basis
+The Equity Basis will be the greater of (i) any unpaid portion of the Shared Earnings Cap,
+or (ii) the Amount of Investment.
+
+Equity Conversion
+The Investor has the right, at its option, to convert the Equity Basis into the shares 
+sold by the Company in its next fixed-price round of financing, at a price per share 
+equal to the lesser of
+ (i) the price of the securities sold in the next financing, 
+or (ii) at a price per share calculated by dividing the Valuation Cap (defined below) 
+by all issued and outstanding shares plus all shares reserved for issuance 
+under any equity incentive plan at the time of the closing of the next financing. 
+
+Valuation Cap
+$_____________
+
+Sale
+On a sale of the Company, the Investor is entitled to receive the 
+greater of
+(i) any unpaid amount of the Shared Earnings Cap or 
+(ii) the amount the Investor would be entitled to receive if it converted the Equity Basis 
+at the Valuation Cap.
+
+Information Rights
+The Investor is entitled to standard information and inspection rights including any 
+records of accounting necessary to verify Shared Earnings calculations. 
+
+Board Observer
+The Investor will be entitled to attend Board Meetings as an observer upon its request,
+subject to executing a standard form observer confidentiality agreement. 
+
+Participation Rights
+The Investor will have the right to participate on a pro rata basis in subsequent 
+issuances of Membership Interests, subject to customary exclusions. 
+
+Confidentiality
+Without the consent of the Investor, the Company shall not disclose these terms to 
+anyone other than the Company's officers, directors, and key service providers. 
+
+COMPANY:
+                                        
+Name:                                  
+Title:                                          
+Date:                                          
+INVESTOR:
+                                        
+Name:  
+Title:  
+Date:  
+
+
+# Creation of Additional Membership Interests
+
+Additional Membership Interests may be created and issued to existing or new
+Members or Persons, and such other Persons may be admitted to
+the Company as Members in one or more classes, with the unanimous written
+conset of the Board Of Directors, and all Company Members on such terms and
+conditions as the Board Of Directors and Company Members may approve at
+the time of admission. 
+
+The creation of new Membership Interests, the
+admission of any new Members, or the creation of any new class or group
+of Members in accordance with this Agreement may 
+
+* (i) result in the dilution of the Sharing Ratios of existing Members
+
+* (ii) be reflected as an amendment to this Agreement or a Supplement which shall
+be valid if executed by the entirety of the Board Of Directors, all existing 
+Company Members and the new Member.  
+
+
+# Rights to Company Information
+
+In addition to the other rights specifically
+set forth in this Agreement, each Member is entitled to the following
+information under the circumstances and conditions set forth in the BOC:
+
+* true and full information regarding the status of the business and
+financial condition of the Company
+
+* promptly after becoming available, a copy of the Company's federal,
+state and local income tax returns for each year 
+
+* a current list of the name and last known business, or mailing address 
+of each Member and Director
+
+* a copy of this Agreement ,the Company's Certificate of Formation, and all amendments to
+such documents
+
+* true and full information regarding the amount of cash and a description and statement
+of the agreed value of any other property or services contributed by
+each Member and which each Member has agreed to contribute in the
+future, and the date on which each became a Member 
+
+* other information regarding the affairs of the Company to which that 
+Member is entitled pursuant to the BOC (including all the Company books and
+records)
+
+
+# Liability to Third Parties
+No Member or Director, solely by reason of being a
+member or Director, shall be liable for the debts, obligations, or liabilities of
+the Company.
+
+# Management of the Company
+
+## Member authority
+Company Members shall be fully empowered and authorized to
+implement the terms and provisions of the Board Of Directors approved
+Business Plan and Annual Budget on behalf of the Company, subject to the
+limitations set forth in Section "Major Decisions".
+
+The Company may rely upon any action taken or document executed by the
+any Officer without duty of further inquiry and may assume that such 
+Officer has the requisite power and authority to take the action or 
+execute the document in question.
+
+## Annual requirements of members
+Not later than February 1 of each year, the Members shall
+deliver to the Board Of Directors a detailed proposed business plan (the
+"**Business Plan**") for the Company's next succeeding fiscal year,
+which shall include the proposed budget for such year (the "**Annual
+Budget**").
+
+## Business Plan and Annual Budget
+
+The Business Plan and Annual Budget shall contain such other information
+as the Members wishes to include and shall contain such
+information as the Board Of Directors may request. 
+
+The Board Of Directors will review the proposed Annual Budget and Business Plan, 
+and subject to required revisions, approve the same for the next succeeding
+fiscal year no later than February 15 of each year.
+
+The Business Plan and Annual Budget shall include projected revenues,
+expenses for the year in question, projected investment activities and
+such other matters as the Members and Board Of Directos may deem appropriate. 
+If the Annual Budget provides for a contingency or similar line item, then
+unless otherwise specifically provided to the contrary therein, the
+Members shall be empowered to expend the amount set forth in such
+line item for the Company obligations. If the Business Plan is not
+approved by the date set forth above, then: 
+
+* any items or portions thereof that have been approved will become operative 
+immediately
+
+* with respect to the Annual Budget, the Members may expend,
+in respect of noncapital or recurring expenses in any quarter of the
+then current calendar year, an amount equal to the budget amount for the
+corresponding quarter of the immediately preceding calendar year, as set
+forth on the last approved Annual Budget after giving effect to any
+material changes to the Company or its properties during the prior year;
+however, if any contract approved as a part of any prior approved Annual
+Budget or Business Plan provides for automatic increases in costs
+thereunder after the beginning of the then current calendar year, then
+the Members may expend the amount of that increase.
+
+Following submission and recording of the final version of the
+Business Plan and Annual Budget, the Members shall be authorized
+to take the actions, incur obligations and make the expenditures therein
+expressly set forth. The Members shall not have any authority or
+power to take any action on behalf of the Company that would
+constitute a Major Decision, unless it has been
+expressly approved in writing by the Board Of Directors. 
+
+
+
+## Compensation of Members
+Except as otherwise specifically provided herein, no compensatory payment shall be made by
+the Company to any Member for the services to the Company.
+
+## Officers
+The Board Of Directors may from time to time, designate
+one or more Persons to be officers or agents of the Company (an
+"**Officer**"). Any Officer so designated shall have such title and
+authority and perform such duties as the Board Of Directors may, from
+time to time, designate. Unless the Board Of Directors decides
+otherwise, if the title is one commonly used for officers of a business
+corporation, the assignment of such title shall constitute the
+delegation to such Officer of the authority and duties that are normally
+associated with that office, subject to any specific delegation of
+authority and duties made to such Officer by the Board Of Directors.
+Each Officer shall hold office until his successor shall be duly
+designated and shall qualify or until his death or until he shall resign
+or shall have been removed. The salaries or other compensation, if any,
+of the Officers and agents of the Company shall be fixed from time to
+time by the Board Of Directors. Any Officer may resign as such at any
+time. Any Officer may be removed as such, with or without Cause, by the
+Board Of Directors. Designation of an Officer shall not, in and of
+itself, create contract rights. 
+
+# Duty of care
+
+Each Member shall discharge their duties in a good and proper manner
+as provided for in this Agreement. Each Member, on behalf of the
+Company shall enforce agreements entered into
+by the Company and conduct or cause to be
+conducted the ordinary business and affairs of the Company in
+accordance with good industry practice and the provisions of this
+Agreement. 
+
+# Time and Capital Requirements of members
+No Member shall be required to devote a particular
+amount of time or capital to the Company's business, 
+but shall devote sufficient time to perform their duties hereunder. 
+
+# Indemnification; Reimbursement of Expenses; Insurance
+
+To the fullest extent permitted by law, and subject to the limitations set
+forth in this Section, and with, in each case, the Board Of Directors
+prior approval: 
+
+* the Company may (at the Members sole discretion) indemnify each Director
+or Member for any Adverse Consequences 
+that a Director or Member may suffer including, but not limited to, any
+Director, or Member who, is to be made a party to any pending or
+completed action, suit or proceeding ("**Proceeding**"), any appeal
+therein, or any inquiry or investigation preliminary thereto, solely by
+reason of the fact that he or she is or was a Director, Member and was
+acting within scope of duties or under the authority of the Company and
+was not in breach of agreements or violating fiduciary responsibility 
+as determned by the Members;
+
+* the Company may (at the Members sole discretion) pay a Director or Member for expenses 
+incurred by him or her:
+
+(1) in advance of any deposition of a Proceeding to which such Director or Member is a party, and
+
+(2) in connection with his or her appearance as a witness or other participation in any 
+Proceeding. 
+
+Such indemnification may also include counsel fees. 
+
+The Company may indemnify and advance expenses to an employee or agent of the Company to
+the same extent and subject to the same conditions under which it may
+indemnify and advance expenses to the Director or Members under the
+preceding sentence. 
+
+The provisions of this Section shall not be exclusive of any other right 
+under any law, provision of the Certificate or this Agreement, or otherwise.
+
+Notwithstanding the foregoing, this indemnity shall not apply to actions constituting :
+
+* gross negligence
+
+* simple negligence
+
+* willful misconduct 
+
+* bad faith
+
+* involving a material or fiduciary breach of this Agreement or the duties set forth herein,
+
+* any other reason in the Members and/or Board Of Directors discretion
+which reason, in the Board Of Directors or Members reasonable opinion, causes a substantial
+loss to the Company.
+
+## Option to Purchase Insurance
+
+The Company may purchase and maintain insurance to protect itself and any
+Director, Member, employee or agent of the Company, whether or not the
+Company would have the power to indemnify such Person under this Section.
+
+## Limits of Coverage
+
+This indemnification obligation shall be limited to $1,000.00 and no Member 
+shall be required to make a Capital Contribution in respect thereof.
+
+# Accounts and Records
+
+## Records and Accounting; Reports; Fiscal Affairs
+
+Proper and complete records and books of accounting of the business of the Company,
+including a list of names, addresses and interests of all Members, shall
+be maintained under the direction of the Board Of Directors at the
+Company's principal place of business. Each Member or his or her duly
+authorized representative may examine the books of account of the
+Company records, reports and other papers regarding the business and
+financial condition of the Company, make copies and extracts therefrom
+at such Member's expense, and discuss the affairs, finances and accounts
+of the Company with independent public accountants of the Company, all
+at such reasonable times and as often as may be reasonably requested.
+
+The books and records of the Company shall be kept on a cash basis in
+accordance with generally accepted accounting principles applied on a
+consistent basis, and in all events shall conform with Generally
+Accepted Accounting Policies and Procedures.
+
+## Fiscal Year End
+The fiscal year end of the Company shall be December 31.
+
+## Keeper of the Books
+At all times during the term of existence of
+the Company, and beyond that term if deemed by Board Of Directors to be
+necessary, the CFO shall keep or cause to be kept the books of accounts
+referred to in this section and the following:
+
+* A current list of the full name and last known business or
+residence address of each Member and Director, together with the
+Capital Contribution and the share in Profits and Losses of each Member;
+
+* A copy of the Certificate of Formation, as amended;
+
+* Executed counterparts of this Agreement, as amended;
+
+* Executed Supplements and Consents, if any;
+
+* Any powers of attorney under which the Company takes action;
+
+* Copies of the Company's federal, state, and local income tax or
+information returns and reports, if any, for the six (6) most recent
+taxable years;
+
+* Financial statements of the Company for the six (6) most recent
+fiscal years; and
+
+* All Company records as they relate to the Company's internal
+affairs for the current and past four (4) fiscal years.
+
+## Member Examination of Records
+
+ Each Member, at its expense and under
+the circumstance and conditions set forth in the BOC, may at all
+reasonable times during usual business hours, audit, examine and make
+copies of account records, files and bank statements of the Company.
+Such right may be exercised by any Member or by its designated agents or employees.
+
+## Bank Accounts 
+All funds of the Company shall be deposited in one or
+more accounts with one or more recognized financial institutions in the
+name of the Company, at such locations as shall be determined by the
+Board Of Directors and CFO. Withdrawal from such accounts shall require
+the signature of such Person or Persons as the Board Of Directors and
+Members jointly designate.
+
+## Members' Tax Requirements
+Within fifteen (15) days after the end of
+each taxable year, the Company shall forward to each Member all
+information necessary for the Members to complete their federal and
+state income tax or information returns, and a copy of the Company's
+federal, state, and local income tax or information returns for such
+year.
+
+# Capital Contributions and Finance
+
+
+
+
+## Membership Records
+The 
+
+* name 
+
+* e-mail address
+
+* Capital Contributions 
+
+* Percentage Interest 
+
+of each of the Members is set forth in Supplement 4.
+
+## Capital Contribution
+
+The Board Of Directors and Members 
+shall determine if Capital Contributions are required to enable the Company 
+to invest in any Investment Entity or to operate its business. No Member
+shall have any obligation to make any Capital Contribution.
+Notwithstanding the foregoing, Company members, in their sole 
+and absolute discretion, may at any time elect
+to fund or not fund further Capital Contributions with respect to the
+Company or any Investment, Investment Entity, without any
+liability whatsoever to the Company or any Member, even if such failure
+to contribute results in the loss of any opportunity or the forfeiture
+of any Investment or interest in any Investment Entity, or results in
+any other penalty or liability.
+
+## Return of Contributions
+
+Except as expressly provided herein, no
+Member shall be entitled to the return of any part of its Capital
+Contributions, to be paid interest in respect of either its Capital
+Account or any Capital Contribution made by it or paid for the fair
+market value of its Membership Interest upon withdrawal or otherwise.
+
+Unrepaid Capital Contributions shall not be a liability of the Company,
+or of any Member. 
+
+No Member shall be required to contribute or lend any cash or property 
+to the Company to enable the Company to return any Member's Capital Contributions.
+
+## Member Guaranties
+No Member shall undertake to guarantee or otherwise become liable for any obligation 
+of the Company, or any Investment Entity.
+
+# Investments
+
+Investments. All Investments by the Company shall be made on such
+terms and conditions as the Board Of Directors and Members may determine.
+
+# Distributions to Members
+
+## Distributions in General
+
+From time to time, but not less often than
+monthly, the CEO and CFO shall determine (i) the amount, if any, by
+which the Company's funds then on hand exceed the Reserve Amount (such
+excess being referred to herein as "**Excess Funds**").
+
+If the CEO and CFO determines that there are 
+Excess Funds subject to distribution but that additional Capital Contributions
+will be required for future Company needs within the next two
+(2) calendar month period, then the CEO and CFO may elect to not make 
+a distribution of such Excess Funds.
+
+Not later than the 15th day of each calendar month, the Excess Funds derived 
+from the business shall be distributed to the Company Members in accordance with
+their Sharing Ratios.
+
+
+## Withholding
+
+The Company may withhold distributions or portions
+thereof if it is required to do so by any applicable rule, regulation,
+or law, and each Member hereby authorizes the Company to withhold from
+or pay on behalf of or with respect to such Member any amount of
+federal, state, local or foreign taxes that the Board Of Directors, CEO
+and CFO reasonably determines that the Company is required to withhold
+or pay with respect to any amount distributable or allocatable to such
+Member pursuant to this Agreement. Any amounts so paid or withheld with
+respect to a Member pursuant to this Section shall be treated as having
+been distributed to such Member and shall reduce any amounts otherwise
+distributable to such Member (either currently or in the future)
+pursuant to Section "Distributions to Members" or Section 
+"Withdrawl, Dissolution, Liquidation and Termination".
+
+# 
+
+The Company desires to issue Units in respect of Series I of the Company designated as “Profits Interest Units” to Participant in connection with Participant’s performance of services to or for the benefit of the Company.
+
+
+# Withdrawal, Dissolution, Liquidation and Termination
+
+## Dissolution, Liquidation, and Termination Generally
+
+The Company shall be dissolved upon the first to occur of any of
+the following:
+
+* The sale or disposition of all assets of the Company and the receipt, in cash, of all consideration therefor, and the determination of the Board Of Directors and all Members not to continue the business of the Company directly or through an Investment Entity
+
+* The occurrence of any event which, as a matter of law, requires that the Company be dissolved.
+
+
+## Liquidation and Termination
+Upon dissolution of the Company such Person as the Board Of Directors 
+may designate shall act as liquidator. The liquidator shall 
+proceed diligently to wind up the
+affairs of the applicable Company and make final distributions
+as provided herein. The costs of liquidation shall be a Company 
+expense, as applicable. Until final distribution, the liquidator
+shall continue to operate the Company with all of the power
+and authority of the Board Of Directors, as applicable
+hereunder. The steps to be accomplished by the liquidator are as
+follows:
+
+* as promptly as possible after dissolution and again after final
+liquidation, the liquidator shall cause a proper accounting to be made
+by a firm of certified public liquidator, which shall cause a proper
+accounting to be made by a firm of certified public accountants
+acceptable to the Board Of Directors of the Company's 
+assets, liabilities, and operations through the last day of the
+calendar month in which the dissolution shall occur or the final
+liquidation shall be completed, as applicable
+
+* the liquidator shall cause the Company to
+satisfy all of the debts and liabilities of the Company and
+(whether by payment or the making of reasonable provision for payment
+thereof)
+
+* all remaining assets of the Company shall be distributed
+to the Members as follows:
+
+* (a) the liquidator may sell any or all applicable Company 
+property and the sum of:
+
+* (b) any resulting gain or loss from each sale plus
+
+* (c) the fair market value of such property that has not been sold
+shall be determined and (notwithstanding the provisions of Section 
+Capital Accounts income, gain, loss, and deduction inherent in such
+property (that has not been reflected in the Capital Accounts
+previously) shall be allocated among the Members to the extent possible
+to cause the Capital Account balance of each Member to equal the amount
+distributable to such Member under this Section.
+
+* Company property as applicable shall be distributed to
+the Members as provided in Section "Distributions to Members".
+
+## Deficit Capital Accounts. 
+No Member shall be required to pay to the
+Company, to any other Member or to any third party any deficit
+balance which may exist from time to time in the Member's Capital
+Account.
+
+## Cancellation of Certificate. 
+In the case of the dissolution,
+liquidation and termination of the Company, on completion of the
+distribution of Company assets, the Board Of Directors (or such other
+Person as the BOC may require or permit) shall file a Certificate of
+Cancellation with the Secretary of State of Texas, cancel any other
+filings made pursuant to Section "Qualification in Other Jurisdictions".
+and take such other actions as may be necessary to
+terminate the existence of the Company. In the case of the dissolution,
+liquidation and termination of the Company, the CEO shall file such
+certificates as may be required by the BOC or other law in respect
+thereof.
+
+
+
+
+# Board Oversight of the Company
+The Company itself and it's Members shall be overseen by Indepdent Directors, to be known as the “For Profit Committee”.  The committee shall be governed by 
+the For Profit Committee Charter. Changing the Committee Charter requires a unamious vote of written consent by the LLC members.
+
+### Profits, Losses and Distributive Shares of Tax Items
+
+
+### Members Bound
+Members shall be bound by the provisions of this Section in reporting their shares of Company income  for income tax purposes.
+
+### Tax Returns
+The Board Of Directors shall cause to be prepared and filed all
+necessary federal and state income tax returns for the Company,
+including making the elections described in Section "Tax Elections".
+
+Each Member shall furnish to the Board Of Directors all pertinent
+information in its possession relating to Company operations that is
+necessary to enable such income tax returns to be prepared and filed.
+
+### Tax Elections.
+
+The following elections shall be made on the appropriate returns of the Company:
+
+* to adopt the calendar year as the Company's fiscal year;
+
+* to keep the Company's books and records on the income-tax method;
+
+* if there is a distribution of Company property as described in
+section 734 of the Code or if there is a transfer of a Company interest
+as described in section 743 of the Code, upon written request of any
+Member, to elect, pursuant to section 754 of the Code, to adjust the
+basis of Company properties; and
+
+* to elect to amortize the organizational expenses of the Company
+ratably over a period of twelve (12) or sixty (60) months as permitted by section
+709(b) of the Code.
+
+No election shall be made by the Company or any Member to be excluded
+from the application of the provisions of subchapter K of chapter 1 of
+subtitle A of the Code or any similar provisions of applicable state
+laws.
+
+### Tax Matters Partner.
+
+The Board Of Directors and CFO collectivley shall be the "**tax matters partner**" 
+of the Company pursuant 
+to section 6231(a)(7) of the Code. As
+tax matters partner, they shall take such action as may be
+necessary to cause each other Member to become a "**notice partner**"
+within the meaning of section 6223 of the Code. Such Member shall inform
+each other Member of all significant matters that may come to its
+attention in its capacity as tax matters partner by giving notice
+thereof within ten days after becoming aware thereof and, within such
+time, shall forward to each other Member copies of all significant
+written communications it may receive in such capacity. Such Member
+shall not take any action contemplated by sections 6222 through 6232 of
+the Code without the consent of the Board Of Directors. This provision is not
+intended to authorize such Member to take any action left to the
+determination of an individual Member under sections 6222 through 6232
+of the Code.
+
+### Allocations on Transfer of Interests.
+The Company income, gain,
+loss or deduction allocable to any Member in respect of any interest in
+the Company which may have been transferred shall be allocated during
+such year based upon an interim closing of the Company's books as
+described in the first sentence of Treasury Regulations §
+1.706-1(c)(2)(ii), taking into account the actual results of Company
+operations during the portion of the year in which such Member was the
+owner thereof, and the date, amount and recipient of any distribution
+which may have been made with respect to such interest.
+
+
+
+
+
+
+
+#######################################################
+
+The Profits Interest Units below are issued to Party on the terms and conditions set forth in this Agreement.
+
+Party shall make no Capital Contribution to the Company in connection with the 
+Profits Interest Units issued hereunder and, as a result, 
+Parties Capital Account balance in the Company immediately after their receipt of 
+the Profits Interest Units shall be equal to zero.
+
+Notwithstanding anything to the contrary contained in the LLC Agreement or set forth herein, with respect to the rights of Party related to, in respect of and in connection with the Company, Board Of Directors and other Members, Party and the Profits Interest Units owned thereby shall have only a right to share in or be allocated Net Profits and Net Losses and receive or share in distributions of the Company as set forth in the Agreement.
+
+Party agrees to execute a counterpart signature page to the Agreement, in the form 
+attached hereto and shall thereupon become a Member as of the Effective Date.
+
+The Profits Interest Units acquired pursuant to this Agreement shall be fully 
+subject to the terms and conditions contained in this Agreement, and Party
+hereby acknowledges that Participant has read and understands the terms and conditions contained therein.
+
+
+# Closing
+
+IN WITNESS WHEREOF, the undersigned, intending to be legally bound hereby,
+has duly executed this 
+
+* Company NDA
+
+* Company IP Assignment
+
+* Company Operating Agreement 
+
+
+# Signature Page
+
+The parties sign this Agreement on the date below by their electronic signatures.
+

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/build-output/ignore-this-dir

@@ -0,0 +1 @@
+Ignore this directory. It's used by the build process for final output.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/build/StartupStarterPackage.yml

@@ -0,0 +1,14 @@
+title: "(DRAFT): Redwood Springs Capital Partners: Startup Starter Package (DRAFT) for YourLLC"
+titlepage: true
+author: "Redwood Springs Capital Partners LLC"
+date: \today
+toc: true
+toc-own-page: true
+header-left: "\\hspace{1cm}"
+header-center: "\\leftmark"
+header-right: "Page \\thepage"
+footer-left: "DRAFT/Example Document"
+footer-center: "Copyright Redwood Springs Capital Partners LLC"
+footer-right: "Not legally binding"
+page-background: "D:/tsys/@ReachableCEO/ExternalVendorCode/pandoc-latex-template/examples/page-background/backgrounds/background5.pdf"
+urlcolor: blue

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/LLCOperatingAgreement-Markdown/build/build.sh

@@ -0,0 +1,87 @@
+#!/bin/bash 
+
+export SSP_INPUT_MD="../build-tempdir/ssp-combined.md"
+
+export SSP_RENDERED_MD="../build-tempdir/RedwoodSpringsCapitalPartners-StartupStarterPackage.md"
+export SSP_RENDERED_PDF="../build-tempdir/RedwoodSpringsCapitalPartners-StartupStarterPackage.pdf"
+
+function prevRunCleanup()
+{
+ 
+# Start from a clean slate and remove all previous output
+
+rm $SSP_INPUT_MD
+rm $SSP_RENDERED_MD
+rm $SSP_RENDERED_PDF
+
+}
+
+function makeOutput()
+
+{
+#Company specfic bits
+company_files=(
+"../SingeLLCOpAgreement/TitlePage.md"
+"../SingeLLCOpAgreement/CompanyNameAndPurpose.md"
+"../SingeLLCOpAgreement/ProfitInterestGrant.md"
+
+)
+
+#Common template stuff
+boilerplate_files=(
+"../CommonBoilerplate/Definitions.md"
+"../CommonBoilerplate/CommonTermsAndConditions.md"
+"../CommonBoilerplate/ProfitInterest.md"
+"../CommonBoilerplate/MemberRemoval.md"
+"../CommonBoilerplate/OutsideCapRaise.md"
+"../CommonBoilerplate/AdditionalMembershipInterests.md"
+"../CommonBoilerplate/RightsToCompanyInformation.md"
+"../CommonBoilerplate/LiabilityToThirdParties.md"
+"../CommonBoilerplate/ManagementOfTheCompany.md"
+"../CommonBoilerplate/DutyOfCare.md"
+"../CommonBoilerplate/Indemnification.md"
+"../CommonBoilerplate/AccountsAndRecords.md" 
+"../CommonBoilerplate/Capcon.md" 
+"../CommonBoilerplate/Distributions.md" 
+"../CommonBoilerplate/Dissolution.md" 
+"../CommonBoilerplate/Taxes.md" 
+"../CommonBoilerplate/NonDisclosure.md"
+"../CommonBoilerplate/IntelectualPropertAssign.md"
+"../CommonBoilerplate/ClosingAndSignature.md" 
+)
+
+IFS=$'\n\t'
+
+for file in ${company_files[@]}; do
+	cat $file >> $MD_OUTPUT_FILE
+done
+
+for file in ${boilerplate_files[@]}; do
+	cat $file >> $MD_OUTPUT_FILE
+done
+
+}
+
+main()
+{
+
+
+
+# Expand variables into an intermediate markdown file for conversion to PDF
+
+./mo $SSP_INPUT_MD > $SSP_RENDERED_MD
+
+# Convert to PDF
+
+pandoc \
+$SSP_RENDERED_MD \
+--number-sections \
+--template eisvogel \
+--metadata-file=StartupStarterPackage.yml \
+--from markdown \
+--output ./build-output/$SSP_RENDERED_PDF
+
+}
+
+prevRunCleanup
+makeOutput

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/PitchDeck-Markdown/LICENSE

@@ -0,0 +1,235 @@
+GNU AFFERO GENERAL PUBLIC LICENSE
+Version 3, 19 November 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+                            Preamble
+
+The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works.  By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
+
+When we speak of free software, we are referring to freedom, not price.  Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate.  Many developers of free software are heartened and encouraged by the resulting cooperation.  However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
+
+The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community.  It requires the operator of a network server to provide the source code of the modified version running there to the users of that server.  Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
+
+An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals.  This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+                       TERMS AND CONDITIONS
+
+0. Definitions.
+
+"This License" refers to version 3 of the GNU Affero General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this License.  Each licensee is addressed as "you".  "Licensees" and "recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy.  The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based on the Program.
+
+To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy.  Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other parties to make or receive copies.  Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License.  If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+The "source code" for a work means the preferred form of the work for making modifications to it.  "Object code" means any non-source form of a work.
+
+A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form.  A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.  However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work.  For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+
+2. Basic Permissions.
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met.  This License explicitly affirms your unlimited permission to run the unmodified Program.  The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work.  This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.  You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright.  Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions stated below.  Sublicensing is not allowed; section 10 makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+
+4. Conveying Verbatim Copies.
+You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7.  This requirement modifies the requirement in section 4 to "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy.  This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.  This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit.  Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source.  This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+
+    d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge.  You need not require recipients to copy the Corresponding Source along with the object code.  If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source.  Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.  In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage.  For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product.  A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source.  The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information.  But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed.  Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+
+7. Additional Terms.
+"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law.  If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it.  (Additional permissions may be written to require their own removal in certain cases when you modify the work.)  You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10.  If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.  If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this License.  Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License.  If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the Program.  Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance.  However, nothing other than this License grants you permission to propagate or modify any covered work.  These actions infringe copyright if you do not accept this License.  Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.  You are not responsible for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations.  If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.  For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based.  The work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version.  For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement).  To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License.  You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.  If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+
+13. Remote Network Interaction; Use with the GNU General Public License.
+
+Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software.  This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
+
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work.  The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
+
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time.  Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation.  If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions.  However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program.  It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     PitchDeck-Markdown
+     Copyright (C) 2024  RWSCP
+
+     This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero General Public License for more details.
+
+     You should have received a copy of the GNU Affero General Public License along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source.  For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code.  There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.
+
+You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/PitchDeck-Markdown/README.md

@@ -0,0 +1,3 @@
+# PitchDeck-Markdown
+
+RWSCP standardized pitch deck template

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/LICENSE

@@ -0,0 +1,235 @@
+GNU AFFERO GENERAL PUBLIC LICENSE
+Version 3, 19 November 2007
+
+Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
+
+Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
+
+                            Preamble
+
+The GNU Affero General Public License is a free, copyleft license for software and other kinds of works, specifically designed to ensure cooperation with the community in the case of network server software.
+
+The licenses for most software and other practical works are designed to take away your freedom to share and change the works.  By contrast, our General Public Licenses are intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users.
+
+When we speak of free software, we are referring to freedom, not price.  Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.
+
+Developers that use our General Public Licenses protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License which gives you legal permission to copy, distribute and/or modify the software.
+
+A secondary benefit of defending all users' freedom is that improvements made in alternate versions of the program, if they receive widespread use, become available for other developers to incorporate.  Many developers of free software are heartened and encouraged by the resulting cooperation.  However, in the case of software used on network servers, this result may fail to come about. The GNU General Public License permits making a modified version and letting the public access it on a server without ever releasing its source code to the public.
+
+The GNU Affero General Public License is designed specifically to ensure that, in such cases, the modified source code becomes available to the community.  It requires the operator of a network server to provide the source code of the modified version running there to the users of that server.  Therefore, public use of a modified version, on a publicly accessible server, gives the public access to the source code of the modified version.
+
+An older license, called the Affero General Public License and published by Affero, was designed to accomplish similar goals.  This is a different license, not a version of the Affero GPL, but Affero has released a new version of the Affero GPL which permits relicensing under this license.
+
+The precise terms and conditions for copying, distribution and modification follow.
+
+                       TERMS AND CONDITIONS
+
+0. Definitions.
+
+"This License" refers to version 3 of the GNU Affero General Public License.
+
+"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
+
+"The Program" refers to any copyrightable work licensed under this License.  Each licensee is addressed as "you".  "Licensees" and "recipients" may be individuals or organizations.
+
+To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy.  The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
+
+A "covered work" means either the unmodified Program or a work based on the Program.
+
+To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy.  Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.
+
+To "convey" a work means any kind of propagation that enables other parties to make or receive copies.  Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.
+
+An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License.  If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.
+
+1. Source Code.
+The "source code" for a work means the preferred form of the work for making modifications to it.  "Object code" means any non-source form of a work.
+
+A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.
+
+The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form.  A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.
+
+The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities.  However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work.  For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those
+subprograms and other parts of the work.
+
+The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
+
+The Corresponding Source for a work in source code form is that same work.
+
+2. Basic Permissions.
+All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met.  This License explicitly affirms your unlimited permission to run the unmodified Program.  The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work.  This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
+
+You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.  You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright.  Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.
+
+Conveying under any other circumstances is permitted solely under the conditions stated below.  Sublicensing is not allowed; section 10 makes it unnecessary.
+
+3. Protecting Users' Legal Rights From Anti-Circumvention Law.
+No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.
+
+When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
+
+4. Conveying Verbatim Copies.
+You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
+
+You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
+
+5. Conveying Modified Source Versions.
+You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:
+
+    a) The work must carry prominent notices stating that you modified it, and giving a relevant date.
+
+    b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7.  This requirement modifies the requirement in section 4 to "keep intact all notices".
+
+    c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy.  This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged.  This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it.
+
+    d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so.
+
+A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit.  Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.
+
+6. Conveying Non-Source Forms.
+You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:
+
+    a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange.
+
+    b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge.
+
+    c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source.  This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b.
+
+    d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge.  You need not require recipients to copy the Corresponding Source along with the object code.  If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source.  Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements.
+
+    e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d.
+
+A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.
+
+A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling.  In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage.  For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product.  A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.
+
+"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source.  The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
+
+If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information.  But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
+
+The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed.  Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
+
+Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
+
+7. Additional Terms.
+"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law.  If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
+
+When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it.  (Additional permissions may be written to require their own removal in certain cases when you modify the work.)  You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
+
+Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
+
+    a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
+
+    b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
+
+    c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
+
+    d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
+
+    e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
+
+    f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
+
+All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10.  If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term.  If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
+
+If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
+
+Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+
+8. Termination.
+
+You may not propagate or modify a covered work except as expressly provided under this License.  Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
+
+However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.
+
+Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.
+
+Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License.  If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
+
+9. Acceptance Not Required for Having Copies.
+
+You are not required to accept this License in order to receive or run a copy of the Program.  Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance.  However, nothing other than this License grants you permission to propagate or modify any covered work.  These actions infringe copyright if you do not accept this License.  Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.
+
+10. Automatic Licensing of Downstream Recipients.
+
+Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License.  You are not responsible for enforcing compliance by third parties with this License.
+
+An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations.  If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
+
+You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License.  For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
+
+11. Patents.
+
+A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based.  The work thus licensed is called the contributor's "contributor version".
+
+A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version.  For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.
+
+Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.
+
+In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement).  To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.
+
+If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent
+license to downstream recipients.  "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.
+
+If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.
+
+A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License.  You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
+
+Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.
+
+12. No Surrender of Others' Freedom.
+
+If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License.  If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may
+not convey it at all.  For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.
+
+13. Remote Network Interaction; Use with the GNU General Public License.
+
+Notwithstanding any other provision of this License, if you modify the Program, your modified version must prominently offer all users interacting with it remotely through a computer network (if your version supports such interaction) an opportunity to receive the Corresponding Source of your version by providing access to the Corresponding Source from a network server at no charge, through some standard or customary means of facilitating copying of software.  This Corresponding Source shall include the Corresponding Source for any work covered by version 3 of the GNU General Public License that is incorporated pursuant to the following paragraph.
+
+Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work.  The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
+
+14. Revised Versions of this License.
+
+The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time.  Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Program specifies that a certain numbered version of the GNU Affero General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation.  If the Program does not specify a version number of the GNU Affero General Public License, you may choose any version ever published by the Free Software Foundation.
+
+If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.
+
+Later license versions may give you additional or different permissions.  However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.
+
+15. Disclaimer of Warranty.
+
+THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+16. Limitation of Liability.
+
+IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
+
+17. Interpretation of Sections 15 and 16.
+
+If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.
+
+END OF TERMS AND CONDITIONS
+
+            How to Apply These Terms to Your New Programs
+
+If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.
+
+To do so, attach the following notices to the program.  It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found.
+
+     ReadySET-Markdown
+     Copyright (C) 2024  RWSCP
+
+     This program is free software: you can redistribute it and/or modify it under the terms of the GNU Affero General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
+
+     This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU Affero General Public License for more details.
+
+     You should have received a copy of the GNU Affero General Public License along with this program.  If not, see <http://www.gnu.org/licenses/>.
+
+Also add information on how to contact you by electronic and paper mail.
+
+If your software can interact with users remotely through a computer network, you should also make sure that it provides a way for users to get its source.  For example, if your program is a web application, its interface could display a "Source" link that leads users to an archive of the code.  There are many ways you could offer source, and different solutions will be better for different programs; see section 13 for the specific requirements.
+
+You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU AGPL, see <http://www.gnu.org/licenses/>.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/README.md

@@ -0,0 +1,3 @@
+# ReadySET-Markdown
+
+ReadySET Markdown 

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Demo-Script.md

@@ -0,0 +1,181 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Project proposal](Proposal) > [Target audience and benefits](Target-and-Benefits)
+- [SRS](SRS) > [Use case suite](Use-Case-Suite)
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+### Demo Planning
+
+*TODO: Think through your goals for this demo.*
+
+#### Who is the target audience for this demo?
+
+- ::Investors and potential investors
+- ::Potential customers
+- ::Management, other developers, or partners
+- ::End users as part of training
+
+#### What is your main goal for this demo?
+
+- ::To convince the audience to make a decision and take action. E.g., a
+  sales call.
+- ::To inform the audience about the product and prompt
+  further discussions. E.g., showing another team where their product
+  would have to integrate with yours.
+- ::To provide evidence of progress. E.g., showing your boss that you
+  are done with the UI.
+
+#### What main points will you use to achieve your goal?
+
+- ::This product automates much of the user's task, thus increasing
+  productivity and cutting costs.
+- ::This product is very easy to use, which will encourage
+  rapid adoption.
+- ::This product supports use cases that are key to the customer's
+  overall business process or that enable new
+  business opportunities.
+- ::We have built only 4 of 10 screens, but the remaining screens
+  are much easier to build.
+- ::We have build 7 out of 10 features, and it turns out that one of
+  the remaining features cannot possibly work like the others.
+
+#### How much time is available to present the demo?
+
+- ::10 minutes, no questions
+- ::10 minutes, plus questions
+- ::30 minutes, including questions
+
+#### What equipment and setup is needed to give the demo?
+
+- ::One person. Any computer with a web browser.
+- ::One person. Any computer where we can install from CD or
+  the Internet.
+- ::Two people. Two high-powered laptops with specific software and data
+  pre-installed, a wireless networking base station, and a hand-held
+  with a wireless networking card.
+
+### Demo Script
+
+*TODO: Outline the steps of the demo. Plan out what you will do and say.
+Practice three times to make sure that all system features actually work
+as needed, and that there is enough time.*
+
+*TIP: Imagine that you are in the audience. Do you understand what is
+being shown at each step? Is the demo too fast? Too slow? Too long? Are
+you interested? What are your questions or concerns? Do you strongly
+disagree with any points?*
+
+#### ::Beginning
+
+- ::SET EXPECTATIONS
+- ::SET THE STAGE
+- ::KEY POINT
+  - ::DEMO STEP
+  - ::DEMO STEP
+
+#### ::Middle
+
+- ::KEY POINT
+  - ::DEMO STEP
+  - ::DEMO STEP
+- ::KEY POINT
+  - ::DEMO STEP
+  - ::DEMO STEP
+- ::KEY POINT (if there is time)
+  - ::DEMO STEP
+  - ::DEMO STEP
+
+#### ::Ending
+
+- ::FINAL POINT
+  - ::DEMO STEP
+  - ::DEMO STEP
+- ::CONCLUSION OR SUMMARY
+- ::CALL-TO-ACTION OR NEXT-STEPS
+
+### Anticipated Questions
+
+*TODO: Write down a few common questions that you expect to be asked, and
+good answers.*
+
+*TIP: You can leave some less critical points out of the demo and only
+use them if someone asks a question.*
+
+#### ::How does this compare to OTHER-PRODUCT?
+
+::ANSWER
+
+#### ::What happens if you do X or Y?
+
+::It would do Z.
+
+#### ::When will your product be ready?
+
+- ::We have announced a release date of July 17th.
+- ::We are planning a release this Winter, but no specific date has
+  been set.
+- ::We have not announced a release date yet.
+
+### Demo Checklist
+
+*TODO: Use the following questions to help you evaluate your demo.*
+
+#### Are you making the right points in the right order?
+
+::Yes, we feel that we will accomplish our goals.
+
+::No, we need to better prioritize our points.
+
+#### Can it be presented in the available time?
+
+::Yes, we could even add more or finish early.
+
+::Yes, we have optional sections that can be skipped to save time
+if needed.
+
+::No, we need to make the same points more quickly or make
+fewer points.
+
+::No, we need to change the available time.
+
+#### Do all system features actually work as needed?
+
+::Yes, everything is finished and working.
+
+::Yes, there are defects, but they will not matter for this demo.
+
+::Don't know, we need to plan alternative demo steps just in case
+something fails.
+
+::No, we need to quickly fix the system and/or change the demo to make
+our points without exposing defects.
+
+#### Does the demo end effectively?
+
+::Yes, viewers will be satisfied and convinced.
+
+::No, we need to make sure the demo stops at the natural end of a
+small but complete story, and that audience members understand our
+key points.
+
+#### Does the demo raise questions that it does not answer?
+
+::No, the demo is very complete.
+
+::Yes, but we anticipate those questions and can handle them in the
+Q&A period.
+
+::Yes, the goal of this demo is to raise questions and issues that we
+will then work to resolve.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Design-Architecture.md

@@ -0,0 +1,197 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+##### Project
+
+::PROJECT-NAME(Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Design](Design) > Design Architecture
+- [Software Requirements Specification](SRS)
+- [Glossary](Glossary)
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+_TODO: Answer the questions below to help you define your system
+architecture. Some example text is provided._
+
+### Overview
+
+#### What are the most important facts that a developer should know about this system architecture?
+
+::PARAGRAPH OR BULLETS
+
+#### What software architecture style is being used?
+
+- ::Single-process desktop application (with plug-in extension modules).
+- ::Client-server with a custom thick-clients and server.
+- ::2-tier web application: webserver/app-server, database.
+- ::3-tier web application: webserver, app-server, database.
+- ::Single web service: app-server, database.
+- ::Network of web services.
+- ::Peer-to-peer with/without central server.
+- ::Pipe-and-filter.
+- ::Computing grid / distributed servers.
+
+#### What are the ranked goals of this architecture?
+
+1. ::[Ease of integration](Glossary-Standard-Terms#ease_of_integration)
+2. ::[Extensibility](Glossary-Standard-Terms#extensibility)
+3. ::[Capacity matching](Glossary-Standard-Terms#capacity_matching)
+
+### Components
+
+#### What are the components of this system?
+
+::The components of this system are clearly defined in this [UML Model
+with Component Diagram](LINK-TO-MODEL).
+
+::The components of this system are listed below by type:
+
+- ::Presentation/UI Components
+  - ::[C-00: COMPONENT-NAME](Design-Components#c-00)
+- ::Application Logic Components
+  - ::[C-10: COMPONENT-NAME](Design-Components#c-10)
+- ::Data Storage Components
+  - ::[C-20: COMPONENT-NAME](Design-Components#c-20)
+
+### Deployment
+
+#### How will the components be deployed to processes and machines?
+
+::The deployment of components to processes and machines is clearly
+defined in this [UML Model with Deployment Diagram](LINK-TO-MODEL).
+
+::The deployment of components to processes and machines is clearly
+defined below:
+
+- ::All-in-one server
+  - ::Tomcat process
+    - ::[C-00: Tomcat web server](Design-Components#c-00)
+    - ::[C-10: PROJECT-NAME
+      application](Design-Components#c-10)
+  - ::Database process
+    - ::[C-20: COMPONENT-NAME](Design-Components#c-30)
+
+::The deployment of components to processes and machines is clearly
+defined below:
+
+- ::Load-balanced front-end servers
+  - ::[C-01: COMPONENT-NAME](Design-Components#c-00)
+- ::Back-end server
+  - ::JVM process
+    - ::[C-00: COMPONENT-NAME](Design-Components#c-00)
+    - ::[C-10: COMPONENT-NAME](Design-Components#c-10)
+    - ::[C-11: PLUG-IN COMPONENT-NAME](Design-Components#c-11)
+    - ::[C-12: PLUG-IN COMPONENT-NAME](Design-Components#c-12)
+  - Database process
+    - ::[C-20: COMPONENT-NAME](Design-Components#c-30)
+
+#### What aspects/resources of their environment are shared?
+
+::Everything is on one server so all machine resources are shared by
+all components.
+
+::All machines share the same bandwidth to the Internet. All machines
+access the same file server. So, if one component uses the resources
+heavily, other components may have to wait.
+
+#### How are requests allocated to redundant or load-balanced servers?
+
+::We are not doing any load-balancing or redundancy for fail-over.
+
+::Load-balancing among front-end servers is handled by a load
+balancing device that we can make very few assumptions about.
+However, once a user session is established, the same front-end
+server will be used for all requests during that session.
+
+#### What alternative deployment configurations are possible?
+
+::This is the only possible deployment.
+
+::The database could be moved to a different machine with a fairly
+simple change to a configuration file. Otherwise, nothing can be
+changed about the deployment.
+
+::We have the ability to move the database process to a
+separate machine. We have the ability to add more front-end servers.
+The application logic running on the application server cannot be
+split or load-balanced.
+
+### Integration
+
+#### How will components be integrated? Specifically, how will they communicate?
+
+::All of our code uses direct procedure calls. The database is
+accessed through a driver.
+
+::Components within the same process use direct procedure call or
+standard Java events. Plug-ins are also accessed through a API of
+direct procedure calls and standard events. Communication with the
+database uses a JDBC driver. Communication between the front end-and
+back-end servers uses XML-RPC.
+
+#### What architectural mechanisms are being used to ease future extensions or modifications?
+
+::We could change the database by switching drivers. Otherwise,
+extensions and modifications can only be done at the design level.
+
+::New front-end components could be added so long as they access the
+back-end the same way. New plug-in components can be dynamically
+loaded, so long as they satisfy the plug-in API. Otherwise, there is
+no ability to add or exchange components, because this architecture
+uses direct dependencies between its components rather than
+implicit invocation. Extensions and modifications can be made at the
+design-level, but deploying those changes requires recompilation
+and down-time.
+
+### Architectural Scenarios
+
+_TODO: Provide architecture scenarios that show how objects will
+communicate across components, processes, and machines. Focus on
+scenarios where the architecture itself is changing, e.g., system
+startup, shutdown, adding or upgrading components, load balancing or
+fail-over._
+
+The following sequence diagrams give step-by-step descriptions of how
+components communicate during some important usage scenarios:
+
+- ::[System startup](LINK-TO-DIAGRAM)
+- ::[System shutdown](LINK-TO-DIAGRAM)
+- ::[SCENARIO NAME](LINK-TO-DIAGRAM)
+
+### Architecture Checklist
+
+_TODO: Evaluate your architecture with respect to each of your goals._
+
+#### Ease of integration: Have mechanisms been provided for all needed types of integration?
+
+::Yes. In this system, all of the new components are designed to
+work together. And, the reused components are integrated via fairly
+simple interfaces.
+
+#### Extensibility: What types of components can be added later and how?
+
+::See above.
+
+#### Capacity matching: How has this architecture matched component resource needs to machines?
+
+::The database can be on a machine with RAID disks and a hot-swappable
+power supply, while the web front-end components can be on cheaper
+machines that could fail individually without causing
+system downtime. The front-end web servers and application server
+are both CPU-intensive, so they are deployed to different CPUs. The
+database is disk-intensive, so it can be deployed to the same
+machine as the CPU-intensive application server, with only moderate
+competition for resources.
+
+#### Has the architecture been communicated to the development team and other stakeholders?
+
+::Yes, everyone understands. Feedback is welcome.
+
+::No, this is a risk that is noted in the [Risk Management](Project-Plan#Risk-Management) section.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Design-Components.md

@@ -0,0 +1,128 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Design](Design) > [Architecture](Design-Architecture) > Design Components
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+_TODO: Briefly describe each component in the system. Focus on
+architectural issues such as communication mechanisms, environmental
+concerns that affect deployment options, and concurrency. Note key
+aspects of each interface, but avoid duplicating details of interfaces
+that are specified in the UML class diagrams or other documents._
+
+Each interface can be an API (application program interface), standard
+protocol (e.g., HTTP), config files, input data file format, or
+interactive user interface (e.g., command-line or GUI). One component
+may have multiple interfaces: e.g., a server may handle requests in a
+standard protocol, but also have a config file, command-line options, an
+administrative control panel GUI, and a performance monitoring API.
+
+_TIP: Use an HTML anchor for each component so that a direct link can be
+made from other documents, issues, and email messages._
+
+---
+
+### C-00: COMPONENT NAME
+
+**Description:**
+
+::DESCRIPTION
+
+**Environmental Constraints:**
+
+::REQUIRED OPERATING SYSTEM, RAM, ETC.
+
+**Available Interfaces:**
+
+::BRIEFLY DESCRIBE INTERFACES
+
+---
+
+### C-01: COMPONENT NAME
+
+**Description:**
+
+::DESCRIPTION
+
+**Environmental Constraints:**
+
+::REQUIRED OPERATING SYSTEM, RAM, ETC.
+
+**Available Interfaces:**
+
+::BRIEFLY DESCRIBE INTERFACES
+
+---
+
+### C-10: COMPONENT NAME
+
+**Description:**
+
+::DESCRIPTION
+
+**Environmental Constraints:**
+
+::REQUIRED OPERATING SYSTEM, RAM, ETC.
+
+**Available Interfaces:**
+
+::BRIEFLY DESCRIBE INTERFACES
+
+---
+
+### C-11: COMPONENT NAME
+
+**Description:**
+
+::DESCRIPTION
+
+**Environmental Constraints:**
+
+::REQUIRED OPERATING SYSTEM, RAM, ETC.
+
+**Available Interfaces:**
+
+::BRIEFLY DESCRIBE INTERFACES
+
+---
+
+### C-12: COMPONENT NAME
+
+**Description:**
+
+::DESCRIPTION
+
+**Environmental Constraints:**
+
+::REQUIRED OPERATING SYSTEM, RAM, ETC.
+
+**Available Interfaces:**
+
+::BRIEFLY DESCRIBE INTERFACES
+
+---
+
+### C-20: COMPONENT NAME
+
+**Description:**
+
+::DESCRIPTION
+
+**Environmental Constraints:**
+
+::REQUIRED OPERATING SYSTEM, RAM, ETC.
+
+**Available Interfaces:**
+
+::BRIEFLY DESCRIBE INTERFACES

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Design-Persistence.md

@@ -0,0 +1,197 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Design](Design) > Design Persistence
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+### Overview
+
+_TODO: Answer the questions below to help you design needed persistence
+features. Some example text is provided. Add or delete text as needed._
+
+#### What are the most important facts that a developer should know about persistent data storage in this system?
+
+::PARAGRAPH OR BULLETS
+
+#### What are the ranked goals for persistence in this system?
+
+1. ::[Expressiveness](Glossary-Standard-Terms#dg_expressiveness)
+2. ::[Ease of access](Glossary-Standard-Terms#dg_easy_access)
+3. ::[Reliability](Glossary-Standard-Terms#dg_data_reliability)
+4. ::[Data capacity](Glossary-Standard-Terms#dg_data_capacity)
+5. ::[Data security](Glossary-Standard-Terms#dg_data_security)
+6. ::[Performance](Glossary-Standard-Terms#dg_data_performance)
+7. ::[Interoperability](Glossary-Standard-Terms#dg_data_interop)
+
+### Central Database
+
+#### What is the logical database design?
+
+::The logical database design is described in this [UML
+model](LINK-TO-MODEL) or this [ER diagram](LINK-TO-DIAGRAM).
+
+::Additional logical constraints on the database are:
+
+- ::Students can repeat a course (and thus have two records for the
+  same course in their transcript), if and only if they got a
+  grade of "C-" or lower, or the course number is 198, 199, 298,
+  or 299.
+- ::A grade of "A+" is valid only for transcript entries during or
+  after Fall 1990. Prior to that term, the highest possible grade
+  was an "A".
+- ::LOGICAL CONSTRAINT THAT CANNOT BE EXPRESSED IN THE DIAGRAM
+- ::LOGICAL CONSTRAINT THAT CANNOT BE EXPRESSED IN THE DIAGRAM
+
+#### What are the physical tables and views?
+
+::The physical database design is described in this [UML
+model](LINK-TO-MODEL) or this [ER diagram](LINK-TO-DIAGRAM).
+
+#### How will objects in the application be stored in the database?
+
+::We will use one database table for each class, and one row in the
+database for each persistent instance of that class.
+
+::We will use a [library](LINK-TO-LIBRARY) to do our
+object-relational mapping. (E.g., torque, castor, JDO,
+ADO, hibernate)
+
+#### What database access controls will be used?
+
+::A database user account has been created that has access to the
+needed application database tables. The username and password for
+this account is stored in a configuration file read by the
+application server. The database limits login by that user to only
+the IP-address used by the application server.
+
+#### Is this application's central database accessible to other applications?
+
+::Yes. The database is an important point of interoperability for new
+applications to be added later. The database itself provides support
+for access controls and checks validity constraints so that a
+defective application cannot corrupt the database.
+
+::No. This database should always be accessed through
+this application. All relevant pieces of information are available
+through the application interfaces. The database itself does not
+protect against data corruption that could be caused by
+other applications.
+
+### File Storage
+
+#### What data needs to be stored in files?
+
+::Nothing is stored in files, everything is in the database.
+
+::The server stores most data in the database, but mailing list
+attachments are written to files on the server hard disk.
+
+::All user documents are stored in files on their computer hard disk.
+
+#### What are the conventions for directory structure and file naming?
+
+::N/A
+
+::Files are stored on the server as
+
+```bash
+
+/var/data/attachments/msgNNNN-MMM.dat
+
+```
+
+::Users store files anywhere on their computer, with the filename
+extension `.TST`.
+
+#### What file system access controls will be used?
+
+::N/A
+
+::Files for message attachments are only readable and writable by the
+mailing list archiving process that runs as operating system
+user "daemon".
+
+::Users can use whatever file permissions they like.
+
+#### What file format will be used?
+
+::The [XYZ](LINK-TO-STANDARD) standard file format.
+
+::A java .properties file.
+
+::A window's .ini file.
+
+::An XML file using [this DTD file](LINK-TO-DTD).
+
+::A simple text file with the following format: ...
+
+::A custom binary file in the following format: ...
+
+### Distributed Storage
+
+#### What information (if any) will be stored on client machines? For how long?
+
+::A cookie will be stored on the user machine for the purpose of
+identifying a user session. When the user logs out or closes their
+web browser, the cookie is deleted. Most browsers will not even
+write this cookie to the disk.
+
+::The a cookie is stored on the user's computer that is equivalent to
+their password (but it is NOT actually their password). This cookie
+is needed for the auto-login feature. The cookie lasts a maximum of
+30 days, and it can only be used from the same IP address.
+
+::User preferences for color scheme are stored in cookies in
+their browser. This information is not at all sensitive, so it is
+kept indefinitely.
+
+::All the user data will be stored on files on their computers.
+
+### Persistence Mechanisms Checklist
+
+#### Expressiveness: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Ease of access: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Reliability: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Capacity: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Security: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Performance: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Interoperability: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Has the persistence design been communicated to the development team and other stakeholders?
+
+::Yes, everyone understands. Feedback is welcome.
+
+::No, this is a risk that is noted in the [Risk Management](Project-Plan#Risk-Management)
+section.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Design-Scalability.md

@@ -0,0 +1,55 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Design](Design) > Scalability
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+### Overview
+
+_TODO: Briefly describe the approach to scalability. Rank your
+scalability goals for this design._
+
+::2-4 SENTENCES.
+
+### Relevant parameters
+
+| Parameter          | Description                                                                             |
+| ------------------ | --------------------------------------------------------------------------------------- |
+| ::registered_users | ::Number of registered users in the database.                                           |
+| ::concurrent_users | ::Number of users logged into the system at a given time.                               |
+| ::map_size         | ::Number of game squares in the playing area. E.g., a 10 x 25 map would be 250 squares. |
+| ::game_pieces      | ::Number of game pieces on the playing area at a given time.                            |
+
+### Scalability Mechanisms
+
+### Performance Goals and Estimates
+
+| Action        | Goal         | Time Formula                | Description                                                                 |
+| ------------- | ------------ | --------------------------- | --------------------------------------------------------------------------- |
+| ::login       | ::1 second   | ::O(Log(registered_users))  | ::Time that it takes to look up a user by their login name in the database. |
+| ::display_map | ::1/5 second | ::O(map_size + game_pieces) | ::Time that it takes to redraw the game map and all game pieces.            |
+
+### System Scalability Checklist
+
+How well do these mechanisms support the achievement of your goals?
+
+::2-4 SENTENCES
+
+#### Have these scalability mechanisms been communicated to the development team and other stakeholders?
+
+::Yes, everyone understands. Feedback is welcome.
+
+::No, this is a risk that is noted in the
+[Risk Management](Project-Plan#Risk-Management) section.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Design-Security.md

@@ -0,0 +1,145 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Design](Design) > Design Security
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+### Overview
+
+_TODO: Answer the questions below to help you design needed security features. Some example text is provided. Add or delete text as needed._
+
+#### What are the most important facts that a developer should know about the security of this system?
+
+::PARAGRAPH OR BULLETS
+
+#### What are the ranked goals for security in this system?
+
+1. ::[Data security](Glossary-Standard-Terms#data_security)
+2. ::[Intrusion prevention](Glossary-Standard-Terms#intrusion_prevention)
+3. ::[Abuse prevention](Glossary-Standard-Terms#abuse_prevention)
+4. ::[Auditability](Glossary-Standard-Terms#auditability)
+
+### Security Mechanisms
+
+#### What physical security mechanisms will be used?
+
+- ::Servers will be kept in a locked room with door code known only
+  to administrators.
+- ::Servers will be kept in a locked equipment rack.
+- ::Server case itself has a security cable that prevents the case
+  from being opened (so the hard-disk with sensitive data cannot
+  be removed).
+- ::Backup tapes are stored in a locked cabinet in a locked room.
+
+#### What network security mechanisms will be used?
+
+- ::A firewall device limits access to specific network ports (e.g.,
+  port 80 for web server access).
+- ::Firewall software limits access to specific network ports (e.g.,
+  port 80 for web server access).
+- ::Only the front-end machines are accessible over the Internet.
+  Other machines in the server cluster communicate over a private
+  LAN only.
+- ::Users can only connect to the server from specific ranges of
+  IP-address (e.g., university-owned computers in networks
+  on campus).
+- ::Certain users (e.g., administrators) can only connect from
+  specific ranges of IP-addresses.
+- ::All network communication takes place over a virtual private
+  network (VPN) that is encrypted and not accessible to outsiders.
+- ::All network communication takes place over a LAN that does not
+  have any connections to the Internet.
+
+#### What operating system security will be used?
+
+- ::Operating system user accounts will never be created on the
+  servers, other than those needed by the application itself.
+- ::Different components in the application execute as different
+  operating system users, have only the least possible privileges,
+  and may only access the particular files needed by
+  that component.
+- ::Operating system permissions on files and directories are set to
+  prevent undesired access or modification.
+- ::Intrusion detection software will be used on the server to
+  detect any modifications made by hackers.
+- ::Administrators will monitor security mailing lists for
+  announcements of security holes in any components that we use
+  and security patches and upgrades will be applied quickly.
+- ::Data on disks and backup tapes is stored using an encrypted file
+  system so that the data is protected if the media itself is
+  stolen or somehow accessed.
+
+#### What application security mechanisms will be used?
+
+- ::Values input into every field are validated before use
+- ::Usernames and passwords are required for access
+- ::Passwords are stored encrypted
+- ::Verification of user email address
+- ::The quality of passwords is checked
+- ::Users must have certificate files on their client machine before
+  they can connect to the server
+- ::Users must have physical security tokens (e.g., hasp, dongle,
+  smart-card, or fingerprint reader)
+- ::Users are given roles that define their permissions. Those roles
+  are:
+  - ::Guest: Visitor to the site is not logged in, no permissions
+    to change anything
+  - ::Guest: Visitor to the site is not logged in, can post messages anonymously
+  - ::RegisteredUser: User is logged in, has permissions for X, Y, and Z
+  - ::Administrator: Permission to change anything, even on behalf of other regular users
+- ::Each action (information display or change) requires that the
+  user has a role with proper permissions
+- ::Compromised or abused accounts can be quickly disabled by administrators.
+- ::Administrators can review user permissions
+- ::Administrators can audit all accesses and changes
+- ::All communications with the user are encrypted (e.g., SSL)
+- ::Some communications with the user (e.g., the username
+  and password) are encrypted (e.g., SSL)
+- ::Sessions are tied to a particular client IP-address so that
+  stolen cookies cannot be used.
+- ::Session cookies are long random strings that cannot be guessed.
+- ::Sessions time out so that unattended terminals cannot be abused.
+- ::Actions that seem to destroy data actually move it to a place
+  where it can still be reviewed by administrators.
+- ::Sensitive data, such as credit card numbers, are processed but
+  not retained in any database or file
+- ::The data access layer will be responsible for preventing SQL injection attacks (i.e., hackers attempting to enter SQL statements through application UI fields).
+- ::The data access layer will allow read-only connections, which will be used for most requests, as well as write connections for requests that update the database.
+- ::The HTML generation layer will be responsible for preventing cross-site-scripting (XSS) attacks.
+- ::The application will prevent Cross-Site Request Forgery (CSRF) attacks. It will do this by performing updates to the database only after a POST, and checking that the referring page was served by the system for every POST. Browsers that do not report HTTP-Referrer will not be supported.
+
+### Security Checklist
+
+#### Protection of data: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Prevention of intrusion: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Prevention of abuse: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Accountability/auditing: To what extent has this been achieved?
+
+::2-4 SENTENCES
+
+#### Have these security mechanisms been communicated to the development team and other stakeholders?
+
+::Yes, everyone understands. Feedback is welcome.
+
+::No, this is a risk that is noted in the [Risk Management](Project-Plan#Risk-Management) section.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Design-Src-Org.md

@@ -0,0 +1,128 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Design](Design) > Source Code Organization and Build System
+- ::[Example build.xml for Tomcat](http://jakarta.apache.org/tomcat/tomcat-4.1-doc/appdev/build.xml.txt)
+- ::[Apache Ant manual](http://ant.apache.org/manual/index)
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+### Overview
+
+_TODO: Answer the questions below to help you define your source code
+organization and build process. Some example text is provided. Add or
+delete text as needed. E.g., not all projects try to be platform
+independent._
+
+#### What are the most important facts that a developer should know about this source code organization and build system?
+
+::It roughly follows the standard proposed in the Tomcat documentation
+and is very similar to the organization used on many open source
+projects at the Apache Software Foundation.
+
+#### What are the ranked goals of this source code organization and build system?
+
+1. ::Separation of files by type
+2. ::Separation of version-controlled files from files generated by
+   the build process
+3. ::Compatibility with standard build processes
+4. ::Platform independence
+
+### Key Directories and Files in Developer Working Copies
+
+_TODO: Describe the purpose of each directory that will appear in a
+developer's work copy, also include any files that are important to the
+overall structure or build process._
+
+| Path                                 | VC    | Description                                                                     |
+| ------------------------------------ | ----- | ------------------------------------------------------------------------------- |
+| ::build.xml                          | ::Yes | ::Build file                                                                    |
+| ::build.properties                   | ::Yes | ::Build properties file                                                         |
+| ::src/                               | ::Yes | ::Source code                                                                   |
+| ::src/java/                          | ::Yes | ::Java source code                                                              |
+| ::src/java/\[Nested packages\]/      | ::Yes | ::Java source code of classes in each package                                   |
+| ::src/java/\[Nested packages\]/test/ | ::Yes | ::Java source code of unit tests for classes in each package                    |
+| ::web/                               | ::Yes | ::HTML and JSP files                                                            |
+| ::web/css/                           | ::Yes | ::CSS files, if any                                                             |
+| ::web/images/                        | ::Yes | ::Image files, if any                                                           |
+| ::web/WEB-INF/web.xml                | ::Yes | ::Java web application configuration file                                       |
+| ::conf/                              | ::Yes | ::Configuration files, if any                                                   |
+| ::data/                              | ::Yes | ::Initial data to load into database and/or file system, if any                 |
+| ::lib/                               | ::Yes | ::Libraries reused by this project, if any                                      |
+| ::scripts/                           | ::Yes | ::Command-line utility scripts used by this project, if any                     |
+| ::www/                               | ::Yes | ::Project documents (e.g., overview, plan, requirements, and design)            |
+| ::build/                             | ::No  | ::Output of build process                                                       |
+| ::build/WEB-INF/classes/             | ::No  | ::Compiled code output by build process                                         |
+| ::dist/docs/api/                     | ::No  | ::API documentation output from build process                                   |
+| ::dist/PROJECT-NAME-VERSION.war      | ::No  | ::Deployable web archive of classes and config files generated by build process |
+
+### Build Targets
+
+_TODO: Describe the build targets that developers will use in daily
+development. The examples below should fit most projects._
+
+| Target              | Description                                                                                                                                                                                                                        |
+| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ::compile = default | ::Compiles Java source code and creates .class files under the "build" directory.                                                                                                                                                  |
+| ::dist              | ::Packages the system for distribution/deployment to servers or end users. Specifically, it creates .war archive of compiled classes and configuration files.                                                                      |
+| ::install           | ::Places executable code into location where it will actually be executed. Specifically, it copies .war file into Tomcat's webapps directory for use. You must then restart Tomcat or use the "reload" link in the Tomcat Manager. |
+| ::javadoc           | ::Generates Java API documentation under "build/docs/api/".                                                                                                                                                                        |
+| ::clean             | ::Deletes files generated by previous build commands. Files under version control are not touched.                                                                                                                                 |
+
+### Build Configuration Options
+
+| Property       | Description                                                                                                                                                                                                                   |
+| -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ::app.name     | ::The name of this application. This should be one short word. Used in the name of resulting package files. Specifically, the .war file. And, it will be used to access the application via <http://localhost:8080/APP.NAME/> |
+| ::app.version  | ::Version number of this release. Used in the name of resulting package files. Specifically, the .war file.                                                                                                                   |
+| ::webapps.path | ::Path to the Tomcat "webapps" directory. Defaults to C:\Program Files\Apache Group\Tomcat 4.1\webapps\                                                                                                                       |
+
+::These build system properties can be modified by editing the
+build.properties file.
+
+### Source Code Organization and Build System Checklist
+
+#### Separation of files by type: Are files separated by type?
+
+::Yes. Except that application JSP and HTML files are in the same
+directory, which is convenient because sometimes we change an HTML
+file to be a JSP file.
+
+#### Separation of version-controlled and non-version controlled files: To what extent has this been achieved?
+
+::It has been achieved. Everything is under version control except for
+the "build" directory. No step in the build process should create or
+modify any file in any other directory.
+
+#### Compatibility with standard build processes: To what extent has this been achieved?
+
+::So far, so good. We can use build.xml files that are very close to
+the examples that come with Ant. One difference is that we keep our
+technical documentation under "www" rather than under "docs". Also,
+we have avoided the use of custom ant tasks.
+
+#### Platform independence: To what extent has this been achieved?
+
+::We are using Ant, which is itself platform independent. The names
+of the files and directories should work across platforms because
+they do not rely on case-sensitive names. We assume that the utility
+scripts in the "scripts" directory support all needed platforms and
+we have not created directories for different versions of these files
+aimed at specific platforms.
+
+#### Have these implementation decisions been communicated to the development team and other stakeholders?
+
+::Yes, everyone understands. Feedback is welcome.
+
+::No, this is a risk that is noted in the [Risk Management](Project-Plan#Risk-Management) section.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Design-UI.md

@@ -0,0 +1,213 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Design](Design) > User Interface
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+### Overview
+
+_TODO: Answer the questions below to help you design the user interface
+features of your system. Some example text is provided. Add or delete
+text as needed._
+
+#### What are the most important facts that a developer should know about the user interface of this system?
+
+::PARAGRAPH OR BULLETS
+
+#### What are the ranked goals for the user interface of this system?
+
+1. ::[Understandability and learnability](Glossary-Standard-Terms#understandability_and_learnability)
+2. ::[Task support and efficiency](Glossary-Standard-Terms#task_support_and_efficiency)
+3. ::[Safety](Glossary-Standard-Terms#safety)
+4. ::[Consistency and familiarity](Glossary-Standard-Terms#consistency_and_familiarity)
+
+### Metaphors, Exemplars, and Standards
+
+#### What is the central metaphor of this UI design?
+
+::PARAGRAPH
+
+#### What existing systems have user interfaces similar to the UI you want to build? What specific aspects are similar?
+
+- ::[amazon.com](http://www.amazon.com): Our e-commerce site will
+  have stores and departments, and search like this site.
+- ::[Microsoft Office](http://www.microsoft.com/office/using/default.asp): We
+  will use configurable toolbars the same way Office 2000 does.
+- ::[EXISTING-UI](LINK-TO-SYSTEM): DESCRIPTION
+
+#### What UI design standards, guidelines, and styles are you following?
+
+- ::[Microsoft UI guidelines](http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwue/html/welcome.asp)
+- ::[Java UI guidelines](http://java.sun.com/products/jlf/ed1/guidelines.html)
+- ::[Mac UI guidelines](http://developer.apple.com/techpubs/macosx/Essentials/AquaHIGuidelines/AHIGHIGs/index.html)
+- ::[W3C Accessibility guidelines](http://www.w3.org/TR/WCAG10/)
+
+### Task Models
+
+#### What types of users will use this system?
+
+::See the [user needs document](User-Needs).
+
+#### What types of tasks will those users perform?
+
+::See the [use case suite](Use-Case-Suite).
+
+### Content Model / Interaction Contexts
+
+_TODO: List interaction contexts. Each interaction context is a "place"
+where users see information and where they select commands or options.
+In a graphical user interface, a interaction context will eventually be
+implemented as a window or dialog box. In other applications, an
+interaction context may be implemented as, e.g., a web page, a voice
+menu prompt, or a physical control panel._
+
+_TIP: Each interaction context is an exclusive mode: the user can only
+use one interaction context at a time. All the components within one
+context are visible and usable at the same time. E.g., if a window has
+three tabs, that is three interaction contexts because only one tab can
+be used at a time._
+
+_TODO: For each interaction context, list the abstract components within
+that context. Each component is a piece of information, or a user
+interface affordance. In a GUI, each abstract component will eventually
+become a widget, but the choice of specific widgets happens later.
+Choice of abstract components corresponds to step 2 in the
+[HTML prototyping example](http://www.ics.uci.edu/~jrobbins/htmlproto/index.html)
+demonstrated in class._
+
+_TIP: Most high frequency use cases should be carried out in only one
+interaction contexts. A use case that requires three interaction
+contexts could be hard to use. However, interaction contexts with too
+many components can also be hard to use._
+
+| Interaction Context --Abstract UI Components | Purpose                                                                                                          | Contents / Constraints / Behavior                                                                                                                                                                                                            |
+| -------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ::[Login dialog](LINK-TO-MOCKUP)             | ::Verify that the current user is actually the person that they claim to be.                                     |                                                                                                                                                                                                                                              |
+| ::--Prompt                                   | ::Tell the user that this dialog is to log in.                                                                   | ::"Please log in".                                                                                                                                                                                                                           |
+| ::--Message area                             | ::Give the user some feedback about the login process.                                                           | ::Initially blank. Changes to "Checking username and password" when the user presses "Login". Changes to "Invalid username or password, please try again", if login fails.                                                                   |
+| ::--Username                                 | ::Identify the user account that the current user is trying to access.                                           | ::The name of the user account. Regex: [-_a-z0-9]{1-16}. The application should not do anything that would help users guess usernames. E.g., this should not be a combo-box with recent users listed, and it should not offer auto-complete. |
+| ::--Password                                 | ::Verify that the current user knows a secret password that only the true user of that user account should know. | ::The password of 4-16 characters. Do not display the password on the screen. The application should not do anything that would help users guess passwords.                                                                                  |
+| ::--Login                                    | ::Allow the user to indicate that they have completed entry of their username and password.                      | ::"Login" Only enabled when Username != "". If the username or password is incorrect, delay a few seconds, and then clear all fields.                                                                                                        |
+| ::--Lost Password                            | ::Allow the current user to start a process of generating a new password for a given username.                   | ::"Forgot your password? Click here." Only enabled when Username != "".                                                                                                                                                                      |
+| ::[PAGE-NAME](LINK-TO-MOCKUP)                | ::PURPOSE                                                                                                        |                                                                                                                                                                                                                                              |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::[PAGE-NAME](LINK-TO-MOCKUP)                | ::PURPOSE                                                                                                        |                                                                                                                                                                                                                                              |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::[MAIN-WINDOW-NAME](LINK-TO-MOCKUP)         | ::PURPOSE                                                                                                        |                                                                                                                                                                                                                                              |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::[DIALOG-NAME](LINK-TO-MOCKUP)              | ::PURPOSE                                                                                                        |                                                                                                                                                                                                                                              |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::[DIALOG-NAME](LINK-TO-MOCKUP)              | ::PURPOSE                                                                                                        |                                                                                                                                                                                                                                              |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+| ::--ABSTRACT-COMPONENT-NAME                  | ::PURPOSE                                                                                                        | ::CONTENTS                                                                                                                                                                                                                                   |
+
+### Technical Constraints / Operational Context
+
+#### What are your assumptions about the output devices?
+
+::We assume that the user has a 17-inch or larger screen with 1024x768
+pixels that can display thousands of colors (16 bit or more). We
+assume basic audio that can play simple sound files.
+
+::We make very few assumptions about the user's screen or web browser,
+other than the assumption that they can view page somehow. We will
+not use any audio features.
+
+::This "pay-at-the-pump" system has a 320x200 16-color display and
+can beep.
+
+#### What are your assumptions about the input devices that you will use?
+
+::We assume only that the user has a standard keyboard and mouse.
+
+::This "pay-at-the-pump" system has digits 0-9, "OK", "Cancel", and
+four menu buttons along the right-hand edge of the screen.
+
+#### What are your assumptions about the amount of time users will spend on tasks?
+
+- ::Use cases UC-02 and UC-04 are expected to take a few minutes each.
+- ::Use case UC-00 should take less than 5 seconds each. All other use
+  cases should take less than 30 seconds each.
+
+#### What windowing systems, UI libraries, or other UI technologies will you use?
+
+::Standard Java Swing with no extra libraries.
+
+::Simple HTML and CSS with simple GIF images.
+
+### User Interface Checklist
+
+_TODO: Answer the following questions to help evaluate the design. You
+may add or remove questions to fit your project._
+
+#### Understandability and learnability
+
+##### Are there any labels of icons that are likely to be misunderstood?
+
+::1-3 SENTENCES
+
+##### Is the user's current place and state clearly visible? E.g., wizard step 2 of 5, or edit-mode vs. play-mode
+
+::1-3 SENTENCES
+
+##### Are advanced options clearly separated from the most commonly used options?
+
+::1-3 SENTENCES
+
+##### Are there no invisible options or commands? E.g., hold down the control key when opening a dialog box to see advanced options
+
+::1-3 SENTENCES
+
+#### Task Support and Efficiency
+
+##### Which use cases force the user to work through more than two interaction contexts?
+
+::1-3 SENTENCES
+
+##### Which use cases force the user to perform slow or difficult UI steps? E.g., entering a long code number like an ISBN. E.g., long mouse-drag operations
+
+::1-3 SENTENCES
+
+#### Safety
+
+##### Are there any dangerous or irreversible actions that are done with only one step?
+
+::1-3 SENTENCES
+
+#### Consistency and Familiarity
+
+##### Do UI elements in your system work the same as they do in the existing example systems you identified?
+
+::1-3 SENTENCES
+
+##### Do all elements in your system that appear the same, actually function the same?
+
+::1-3 SENTENCES
+
+##### Are all elements share consistent visual characteristics such as font and color scheme, unless there is a reason for them to differ?
+
+::1-3 SENTENCES
+
+##### Are labels used consistently throughout the system? E.g., not "forward/back" in some contexts and "next/prev" in others
+
+::1-3 SENTENCES

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Design.md

@@ -0,0 +1,151 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Attached Worksheets
+
+- Design > [Architecture Worksheet](Design-Architecture)
+- Design > [Source Organization and Build Worksheet](Design-Src-Org)
+- Design > [Scalability Worksheet](Design-Scalability)
+- Design > [User Interface Worksheet](Design-UI)
+- Design > [Persistent Storage Worksheet](Design-Persistence)
+- Design > [Security Worksheet](Design-Security)
+
+##### Related Documents
+
+- [SRS](SRS) > [Use case suite](Use-Case-Suite)
+- [SRS](SRS) > [Feature set](Feature-Set)
+- [Glossary](Glossary)
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+**Process impact:**
+
+This design document describes a system that will satisfy the requirements of the [SRS](SRS). Decisions made in creating this design document are based on those requirements and an understanding of available technologies and components. Once the design has been drafted, work on the system implementation and unit testing may begin.
+
+_TODO: Fill in the sections below. Add ore remove items as needed for your project._
+
+### Introduction
+
+#### How is this design document organized?
+
+This main page describes the system design in terms of packages,
+classes, relationships, and behavior. Several attached worksheets
+address specific aspects of the overall system design, such as user
+interface and database design.
+
+#### What are the most important facts that a developer should know about this design?
+
+::PARAGRAPH or BULLETS
+
+#### What are the prioritized goals of this design?
+
+1. ::[Correctness](Glossary-Standard-Terms#correctness)
+2. ::[Feasibility](Glossary-Standard-Terms#feasibility)
+3. ::[Understandability](Glossary-Standard-Terms#understandability)
+4. ::[Implementation phase guidance](Glossary-Standard-Terms#implementation-and-phase-guidance)
+5. ::[Modularity](Glossary-Standard-Terms#modularity)
+6. ::[Extensibility](Glossary-Standard-Terms#extensibility)
+7. ::[Testability](Glossary-Standard-Terms#testability)
+8. ::[Efficiency](Glossary-Standard-Terms#efficiency)
+
+### UML Structural Design
+
+_TODO: Link to a design model and/or design diagrams that describe your
+system's structure in detail._
+
+#### The system's structural design is described in the following UML model
+
+::[MODEL-NAME](LINK-TO-MODEL-FILE).
+
+#### The system's structural design is described in the following UML structural diagrams
+
+- ::[PACKAGE OVERVIEW DIAGRAM](LINK-TO-DIAGRAM)
+- ::PACKAGE-NAME
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+- ::PACKAGE-NAME
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+- ::PACKAGE-NAME
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+
+::ANY ADDITIONAL NOTES OR COMMENTS
+
+### UML Behavioral Design
+
+_TODO: Link to a design model and/or design diagrams that describe your
+system's behavior in detail._
+
+#### The system's behavioral design is described in the following UML model
+
+::[MODEL-NAME](LINK-TO-MODEL-FILE)
+
+#### The system's behavioral design is described in the following UML behavioral diagrams
+
+- State Diagrams
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+- Sequence Diagrams
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+- Collaboration Diagrams
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+  - ::[DIAGRAM-NAME](LINK-TO-DIAGRAM)
+
+::ANY ADDITIONAL NOTES OR COMMENTS
+
+### UML Design Checklist
+
+_TODO: Answer the following questions to help evaluate your design. Add
+or remove questions to fit your project. If you cannot answer a question
+positively, that may indicate an aspect of the design that should be
+revised._
+
+#### Correctness: How do you know that this design is correct?
+
+::2-4 SENTENCES
+
+#### Feasibility: What indicates that this design can be implemented and tested with the planned amount of time and effort?
+
+::2-4 SENTENCES
+
+#### Understandability: What makes this design understandable?
+
+::2-4 SENTENCES
+
+#### Implementation phase guidance: Does the design suggest reasonable implementation tasks?
+
+::2-4 SENTENCES
+
+#### Modularity: How have concerns been separated and addressed in distinct modules?
+
+::2-4 SENTENCES
+
+#### Extensibility: How can new features can be easily added later?
+
+::2-4 SENTENCES
+
+#### Testability: What makes this system easy to test?
+
+::2-4 SENTENCES
+
+#### Efficiency: Does the system consume an acceptable amount of time, storage space, bandwidth, and other resources?
+
+::2-4 SENTENCES
+
+#### Has the design been communicated to the development team and other stakeholders?
+
+- ::Yes, everyone understands. Feedback is welcome.
+- ::No, this is a risk that is noted in the
+  [Risk Management](Project-Plan#Risk-Management) section.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Document-Cross-Ref.md

@@ -0,0 +1,22 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+_TODO: This template is not done yet. Feel free to contribute your ideas._
+
+This document defines the artifacts the team creates during your software
+development process. Documenting artifact types helps define the inputs and
+outputs of each development task. The producer/consumer matrix helps document
+the software development workflow.
+
+### Artifact Producer / Consumer Matrix
+
+| Read By \ Written By | Everyone                                           | Project Manager                                                          | Product Manager                                      | Dev Team                                                                                 | QA Team                                                      | Tech Writer                                              | Tech Support   | Operations | Sales                      |
+| -------------------- | -------------------------------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------- | ---------------------------------------------------------------------------------------- | ------------------------------------------------------------ | -------------------------------------------------------- | -------------- | ---------- | -------------------------- |
+| Everyone             | [Release-Checklist](Release-Checklist), [SDM](SDM) | [Overview](Overview), [Proposal](Proposal), [Plan](Plan), [Risks](Risks) | [SRS](SRS)                                           | Mockups, Prototyes, Working-product                                                      |                                                              | [User-Guide](User-Guide), [Release-Notes](Release-Notes) |                |            |                            |
+| Project Manager      | [Status-Report](Status-Report)                     | [Resource-Needs](Resource-Needs)                                         |                                                      | [Review-Report](Review-Report)                                                           | [QA-Plan](QA-Plan), [Test-Runs](Test-Runs), Defect-reports   |                                                          | Support-issues |            | Customer-feedback          |
+| Product Manager      |                                                    |                                                                          | [User-Needs](User-Needs)                             |                                                                                          |                                                              |                                                          | Support-issues |            | Customer-feedback          |
+| Dev Team             |                                                    | Task-assignments                                                         |                                                      | [Design](Design)                                                                         | [QA-Plan](QA-Plan), [Test-Runs](Test-Runs), Defect-reports   |                                                          |                |            |                            |
+| QA Team              |                                                    | Task-assignments                                                         |                                                      | [Design](Design), [Status-Report](Status-Report)                                         | [QA-Plan](QA-Plan), [Test-Suite](Test-Suite), Defect-reports | [FAQ](FAQ), [Install](Install)                           | Support-issues |            |                            |
+| Tech Writer          |                                                    | Task-assignments                                                         | [User-Needs](User-Needs)                             | [Design-UI](Design-UI)                                                                   |                                                              |                                                          | Support-issues |            | Customer-feedback          |
+| Tech Support         |                                                    |                                                                          |                                                      | [Design-UI](Design-UI)                                                                   |                                                              |                                                          | Support-issues |            | Customer-feedback          |
+| Operations           |                                                    |                                                                          | [User-Needs](User-Needs)                             | [Design-Architecture](Design-Architecture), [Implementation-Notes](Implementation-Notes) |                                                              | [Install](Install)                                       |                |            |                            |
+| Sales                |                                                    |                                                                          | [User-Needs](User-Needs), [Demo-Script](Demo-Script) | [Implementation-Notes](Implementation-Notes)                                             |                                                              | [Install](Install)                                       |                |            | [Demo-Script](Demo-Script) |

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/FAQ.md

@@ -0,0 +1,107 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+_TODO: Answer these common questions. Some sample answers are provided
+for you. Add new questions and new sections to fit the needs of your
+users._
+
+_TIP: This FAQ is for end users, you may want to write FAQ's for other
+types of stakeholders such as potential customers, open source
+contributors, members of a developers' network, or administrators._
+
+### General Information
+
+#### What is ::PRODUCT-NAME?
+
+::It is a XXXXX. Read our [PRODUCT-NAME overview](http://www.COMPANY.com/products/PRODUCT-NAME/).
+
+#### Who should use ::PRODUCT-NAME?
+
+::Anyone who wants XXXXXXX. Read more about our [target audience and benefits](Target-and-Benefits).
+
+### Download and Install
+
+#### How can I obtain ::PRODUCT-NAME?
+
+::You may [download PRODUCT-NAME](LINK-TO-DOWNLOAD).
+
+::You may [place an order for PRODUCT-NAME](LINK-TO-ORDER).
+
+#### What do I need to use ::PRODUCT-NAME?
+
+::System requirements are described in the [release notes](Release-Notes).
+
+::System requirements are a Intel-compatible PC with a processor speed
+of at least XXX MHz, XXX MB of RAM. XXX MB of free disk space, and
+one of the following operating systems: Windows 98/2000/XP, Mac
+OSX, Linux.
+
+#### How do I install ::PRODUCT-NAME?
+
+::[Installation instructions](install.html) are available on-line.
+
+#### How do I upgrade from an older version of PRODUCT-NAME?
+
+::[Installation instructions](install.html) are available on-line.
+
+### Getting Started
+
+#### What is ::TECHNICAL-TERM?
+
+::It means XXXXX. For additional technical terms, see the
+[glossary](Glossary).
+
+#### What is ::GUI-ELEMENT?
+
+::It is a XXXXX. It is used for YYYYY.
+
+#### How do I do ::COMMON-TASK?
+
+::You should understand that XXX. Once you are ready, you can:
+
+1. ::Step one
+2. ::Step two
+3. ::Step three
+
+### SECTION NAME
+
+#### ::QUESTION-1?
+
+::ANSWER.
+
+#### ::QUESTION-2?
+
+::ANSWER.
+
+#### ::QUESTION-3?
+
+::ANSWER.
+
+#### ::QUESTION-4?
+
+::ANSWER.
+
+### Troubleshooting
+
+#### I see an error message "::ERROR-MESSAGE". What's wrong?
+
+::ANSWER.
+
+#### I can't do ::COMMON-TASK. What's wrong?
+
+::ANSWER.
+
+### Other Questions
+
+#### My question is not on this page. How do I find the answer?
+
+::First read the [user guide](user-guide) and other
+on-line help. Your question may have already been asked and
+answered, to find it: search the project [mail archives](::tbd) and
+[issue tracking system](::tbd). If you still don't find it, you can ask
+the question on the [users' mailing list](::tbd) or the [developers'
+mailing list](::tbd) or you can [enter an issue](::tbd).
+
+#### Where should I send comments on this FAQ?
+
+::You can write to [EMAIL-ADDRESS](::mailto:#) or any of the developers
+on the [developers' mailing list](::mailto:#).

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Feature-Format.md

@@ -0,0 +1,84 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [SRS](SRS) > [Feature Set](Feature-Set) > Feature Specification Format
+
+---
+
+**Process impact:** This reference page documents the format of feature
+descriptions and gives tips on writing them. You can copy and paste the
+feature specification template into your [Features](Features)
+document. This file itself should not be edited to hold specific
+features.
+
+_TODO: Copy and paste this feature specification template as many times
+as needed in your [Features](Features) document._
+
+---
+
+### ::F-00: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risk | 2-Risk | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::NOTE
+- ::QUESTION
+- ::QUESTION
+
+---
+
+### Feature Attribute Values
+
+- Priority
+  - Essential: The system could not or would never be used without this feature. It would be much harder to test, document, or package the product without this feature.
+  - Expected: Key stakeholders strongly desire and expect this feature. It may have been promised to them in a certain release. It's absence would substantially reduce the success of the project.
+  - Desired: Stakeholders desire this feature. It's absence would reduce the success of the project.
+  - Optional: This feature would be nice to have. Adding it could have some advantage, but delaying it would not have a big effect on the success of the project.
+- Effort
+  - Months: A very large feature that is too big to estimate and should be broken in to smaller, better-defined features.
+  - Weeks: A large feature that will take 40 to 160 hours to add.
+  - Days: An average or easy feature that would take less than 40 hours to add.
+  - Hours: A very easy feature that would take less than 8 hours to add.
+  - Note that "adding" a feature means doing all of it's design, implementation, technical documentation, user documentation, and testing. Even the easiest feature takes hours to add.
+- Risk
+  - Dangerous: Implementing this feature successfully would require overcoming risk factors that are more than three or unknown in number. It should be broken down into parts, better specified, or risk factors should be eliminated prior to implementation.
+  - 3-Risks: Implementing this feature would require three risk factors to be overcome. Any single release should contain at most a few such high-risk features, and contingency plans should be considered. You should be able to list the risks.
+  - 2-Risks: Implementing this feature would require two risk factors to be overcome. This is normal for challenging features. You should be able to list the risks.
+  - 1-Risk: Implementing this feature as specified would require one risk factor to be overcome. This is normal for many features. You should be able to describe the risk.
+  - Safe: Implementing this feature as specified is just a matter of time and effort, there is no real risk of failure.
+  - A "risk factor" is a task or fact that is currently in doubt, but that must turn out well in order for the feature to be successfully implemented. See tips on managing risk below.
+
+### Further Information
+
+For more information on advice, see:
+
+- Words of wisdom on [feature sets](https://web.archive.org/web/20200701142616/http://readyset.tigris.org/words-of-wisdom/feature-set.html).
+
+- Words of wisdom on [feature specifications](https://web.archive.org/web/20200701142616/http://readyset.tigris.org/words-of-wisdom/features.html).

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Feature-Set.md

@@ -0,0 +1,122 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [SRS](SRS) > Feature Set
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [SRS](SRS) > [Use case suite](Use-Case-Suite)
+- [Feature format](Feature-Format)
+- ::LINK TO USE CASE DIAGRAM
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+**Process impact:** A feature set is simply a table of contents for the
+individual feature descriptions. Much like a test suite, organizing the
+feature set by priority, functional area, actor, business object, or
+release can help identify missing, extra, or poorly motivated features
+early.
+
+_TODO: Before writing individual feature descriptions, list all the
+features that you think you will need. Organize them so that missing
+features appear as blanks on this page, and extra features will appear
+to be extras that don't fit anywhere. See the
+[feature format](Feature-Format#further-information) document for more
+tips on specifying features and feature sets._
+
+_TIP: Refer back to the user stories in your [user needs](User-Needs)
+document and to the [use case suite](Use-Case-Suite).
+Use them for ideas and make sure that you cover all of them._
+
+### Features by Release and Priority
+
+_TODO: Select subset of features can be implemented for a given release.
+When features are listed in priority order, choosing the features to
+implement in a release simply becomes a matter of "drawing a line":
+features below the line must wait for a later release. Make sure to also
+consider estimated effort and risk._
+
+- ::Release 1.0
+  - ::Essential
+    - ::[F-00](Features#f-00_site_configuration) Site configuration
+    - ::[F-01](Features#f-01_user_regisration) User registration
+    - ::[F-21](Features#f-21_feature_name) NAME OF FEATURE
+    - ::[F-31](Features#f-31_feature_name) NAME OF FEATURE
+  - ::Expected
+    - ::[F-02](Features#f-02_feature_name) NAME OF FEATURE
+    - ::[F-03](Features#f-03_feature_name) NAME OF FEATURE
+    - ::[F-20](Features#f-20_feature_name) NAME OF FEATURE
+- ::Release 1.1
+  - ::Expected
+    - ::[F-22](Features#f-22_feature_name) NAME OF FEATURE
+    - ::[F-23](Features#f-23_feature_name) NAME OF FEATURE
+    - ::[F-33](Features#f-33_feature_name) NAME OF FEATURE
+  - ::Desired
+    - ::[F-10](Features#f-10_feature_name) NAME OF FEATURE
+    - ::[F-11](Features#f-11_feature_name) NAME OF FEATURE
+    - ::[F-12](Features#f-12_feature_name) NAME OF FEATURE
+- ::Later Releases
+  - ::Optional
+    - ::[F-30](Features#f-30_feature_name) NAME OF FEATURE
+    - ::[F-32](Features#f-32_feature_name) NAME OF FEATURE
+
+### Features by Release and Risk
+
+- ::Release 1.0
+  - ::[F-00](Features#f-00_site_configuration) Safe : Site configuration
+  - ::[F-01](Features#f-01_user_registration) Safe : User registration
+  - ::[F-21](Features#f-21_feature_name) Safe : NAME OF FEATURE
+  - ::[F-31](Features#f-31_feature_name) 1-Risk : NAME OF FEATURE
+  - ::[F-02](Features#f-02_feature_name) 1-Risk : NAME OF FEATURE
+  - ::[F-03](Features#f-03_feature_name) 2-Risks : NAME OF FEATURE
+  - ::[F-20](Features#f-20_feature_name) 2-Risks : NAME OF FEATURE
+  - ::Total unique risk factors: 4
+- ::Release 1.1
+  - ::[F-22](Features#f-22_feature_name) Safe : NAME OF FEATURE
+  - ::[F-23](Features#f-23_feature_name) Safe : NAME OF FEATURE
+  - ::[F-33](Features#f-33_feature_name) Safe : NAME OF FEATURE
+  - ::[F-10](Features#f-10_feature_name) 2-Risks : NAME OF FEATURE
+  - ::[F-11](Features#f-11_feature_name) 2-Risks : NAME OF FEATURE
+  - ::[F-12](Features#f-12_feature_name) 3-Risks : NAME OF FEATURE
+  - ::Total unique risk factors: 5
+- ::Later Releases
+  - ::[F-30](Features#f-30_feature_name) Safe : NAME OF FEATURE
+  - ::[F-32](Features#f-32_feature_name) 2-Risks : NAME OF FEATURE
+  - ::Total unique risk factors: 2
+
+### Features by Functional Area
+
+- ::FUNCTIONAL AREA ONE
+  - ::[F-00](Features#f-00_site_configuration) Site configuration
+  - ::[F-01](Features#f-01_user_registration) User registration
+  - ::[F-02](Features#f-02_feature_name) NAME OF FEATURE
+  - ::[F-03](Features#f-03_feature_name) NAME OF FEATURE
+- ::FUNCTIONAL AREA TWO
+  - ::[F-10](Features#f-10_feature_name) NAME OF FEATURE
+  - ::[F-11](Features#f-11_feature_name) NAME OF FEATURE
+  - ::[F-12](Features#f-12_feature_name) NAME OF FEATURE
+  - ::[F-13](Features#f-13_feature_name) NAME OF FEATURE
+- ::FUNCTIONAL AREA THREE
+  - ::[F-20](Features#f-20_feature_name) NAME OF FEATURE
+  - ::[F-21](Features#f-21_feature_name) NAME OF FEATURE
+  - ::[F-22](Features#f-22_feature_name) NAME OF FEATURE
+  - ::[F-23](Features#f-23_feature_name) NAME OF FEATURE
+- ::FUNCTIONAL AREA FOUR
+  - ::N/A: These features are completely automated and internal, users
+    never interact with them
+- ::FUNCTIONAL AREA FIVE
+  - ::TODO: need to write use cases here
+- ::Other functional areas
+  - ::[F-30](Features#f-30_feature_name) NAME OF FEATURE
+  - ::[F-31](Features#f-31_feature_name) NAME OF FEATURE
+  - ::[F-32](Features#f-32_feature_name) NAME OF FEATURE
+  - ::[F-33](Features#f-33_feature_name) NAME OF FEATURE

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Features.md

@@ -0,0 +1,493 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [SRS](SRS) > [Feature Set](Feature-Set) > Features
+- [Feature format](Feature-Format)
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- [SRS](SRS) > [Use case suite](Use-Case-Suite)
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+**Process impact:** This is a set of detailed feature descriptions.
+
+_TODO: For each feature listed in the [feature set](Feature-Set),
+give a detailed description of the feature here. Describe each feature
+in enough detail that it could be implemented by any member of the
+development team (not only someone who already informally knows what to
+do)._
+
+_TIP: Start with a short textual description of each feature. Then, add
+more formal information as needed to make each description precise and
+unambiguous. E.g.,_
+
+- _Precisely define valid inputs, and error handling_
+- _Specify data structures with UML or logical schema_
+- _Specify UI aspects of features with tiny mock-ups_
+- _Specify key decisions with decision trees or tables_
+- _Specify key algorithms with pseudo-code or flow charts_
+- _Specify state-based behavior with state machines or tables_
+- _Specify sequences of events with scenario diagrams_
+
+---
+
+### ::F-00: Site Configuration
+
+Priority: ::Essential
+
+Effort: ::Days
+
+Risk: ::Safe
+
+Functional area(s): ::Administration
+
+Use case(s): ::[UC-00](Use-Cases#UC-00) [UC-11](Use-Cases#UC-11)
+
+Description:
+
+::The site administrators will be able to configure:
+
+- ::The site appearance by choosing a predefined CSS file
+- ::Whether the site makes new clans public or private by default
+- ::The email address to be used to send critical error reports
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-01: User registration
+
+Priority: **::Essential**
+
+Effort: ::Days
+
+Risk: ::Safe
+
+Functional area(s): ::Administration
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+:: Visitors can come to the site and register themselves. They must provide the following information:
+
+- ::username
+- ::email address (twice to catch typos)
+- ::real name
+
+Precise Details:
+
+- ::username must be unique (not equal to any other existing user name)
+- ::username must be of the form ~~~[a-zA-Z0-9]{2,16}~~~ and is not case sensitive
+- ::email address must be of the form ~~~[-a-zA-Z0-9_.]{2,16}@[-a-zA-Z0-9_.]{6,64}~~~
+- ::both entries of the email address must match
+- ::email address will be verified by sending the user's initial password there
+- ::real name must not be empty
+- ::leading and trailing spaces are stripped from all fields
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-02: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+:: 1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-03: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-10: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-11: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-12: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-13: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-20: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-21: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-22: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-23: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-30: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-31: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-32: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION
+
+---
+
+### ::F-33: FEATURE NAME
+
+Priority: ::Essential | Expected | Desired | Optional
+
+Effort: ::Months | Weeks | Days | Hours
+
+Risk: ::Dangerous | 3-Risks | 2-Risks | 1-Risk | Safe
+
+Functional area(s): ::WORD, WORD, WORD
+
+Use case(s): ::[UC-01](Use-Cases#UC-01)
+
+Description:
+
+::1-4 PARAGRAPHS. USE BULLETS OR TABLES TO ORGANIZE INFORMATION. LINK TO WORKSHEETS OR ADDITIONAL INFORMATION.
+
+Precise Details:
+
+- ::LOGICAL CONSTRAINT
+- ::LOGICAL CONSTRAINT
+
+Notes and Questions:
+
+- ::NOTE
+- ::QUESTION

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Glossary-Standard-Terms.md

@@ -0,0 +1,539 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+**Process impact:** This file as a dictionary of standard terms defined
+as they are used across projects. Individual projects should not need to
+edit this file. Writing out the definitions of terms and acronyms here
+helps keep other documents more concise and easy to edit. Check the
+[ReadySET glossary](https://web.archive.org/web/20200702035436/http://readyset.tigris.org/templates/glossary-std.html) for
+updates.
+
+Jump to: [General](#general-terms) | [Computer science & technology](#computer-science-and-technology-terms) | [Process](#process-terms) | [Software development tools](#development-tool-terms) | [Requirements](#requirements-terms) | [Design](#design-terms) | [Design goals terms](#design-goals-terms) | [QA terms](#qa-terms) | [QA goals terms](#qa-goals-terms) | [Additional terms](#additional-standard-terms)| [Project terms](Glossary)
+
+## General Terms
+
+### Chipping away
+
+The process of removing sample text from templates when that text
+does not apply to the current project. Often some of the sample text
+will be kept or revised to fit the current project. Even if the
+sample text does not fit the current project, it provides a reusable
+example of how to phrase that type of description. The term
+"chipping away" comes from an old joke: when a sculptor is asked how
+he carved a marble statue of a horse, he replies "It was easy, I
+just started with a big block of marble and chipped away everything
+that did not look like a horse."
+
+### Attached worksheet
+
+The idea is similar to filling in an IRS form and using worksheets
+to calculate subtotals or make specific decisions. That is to say,
+there is a hierarchy to the templates: there are the main templates,
+and then worksheets for specific topics. We have divided the
+information into several files so that each file is focused on one
+topic, and so that each file can be worked on by one person in a
+reasonable amount of time.
+
+### Process impact
+
+The process impact box on each template explains where the current
+template fits into the software development process. It usually
+includes a brief comment on who should create the document, and who
+would be expected to make use of it. You can change the process
+impact box, but you should not need to.
+
+### Checklist
+
+There are two kinds of checklists:
+
+- Many of the templates have a section with questions that help
+  you check your work in that template. Often the sample answers
+  to the questions prompt you to take some corrective action.
+- For design and code review meetings, there are links to
+  guidelines and checklists that help you identify common errors
+  in those artifacts.
+
+### Sticky note
+
+The idea is similar to a post-it note attached to a document that
+tells you do "sign here" or fill in a certain part. There are two
+types of sticky notes:
+
+- *TODO:* Instructs you on how to fill in the template. This is the
+  minimum that you need to do. One of the main goals of ReadySET
+  is to help your team *quickly* carry out basic software
+  engineering activities. The TODO sticky notes make that easy by
+  making the templates more self-explanatory.*
+- TIP: Helps you think of better ways to fill in the template. One
+  of the other main goals of ReadySET is to help your team make
+  better decisions that can make your whole project more
+  successful. The TIP sticky notes help with that.
+
+After you have done what the sticky note says, you can delete the
+sticky note.
+
+## Computer Science and Technology Terms
+
+### ::API (Application Programming Interface)
+
+An API is a set of functions that one software component makes
+available to other software components. That allows other programs
+to "call" this program via direct function calls, or more indirect
+communications such as [SOAP](#soap) messages.
+
+### ::SOAP
+
+SOAP (Simple Object Access Protocol) is the message format used by
+standard web services. It entails sending an XML document to a
+server in order to invoke an operation on the server-side.
+[More information on SOAP](http://directory.google.com/Top/Computers/Programming/Internet/Web_Services/SOAP/?tc=1).
+
+## Process Terms
+
+### Change Control Board (CCB)
+
+A group of people who review proposed changes to the project
+requirements and/or source code to accept or reject changes in each
+particular release. Proposed changes are usually rejected if they
+introduce too much risk or would trigger additional effort (e.g.,
+the need to redo a lot of testing on new code). A CCB is usually
+composed of managers and representatives of other stakeholders such
+as the QA group and key customers.
+
+### Feature Complete
+
+A release is called "feature complete" when the development team
+agrees that no new features will be added to this release. New
+features may still be suggested for later releases. More development
+work needs to be done to implement all the features and
+repair defects.
+
+### Code Complete
+
+A release is called "code complete" when the development team agrees
+that no entirely new source code will be added to this release.
+There may still be source code changes to fix defects. There may
+still be changes to documentation and data files, and to the code
+for test cases or utilities. New code may be added in a
+future release.
+
+### Internal Release Number
+
+An internal release number is the number that the development team
+gives each release. Internal release numbers typically count up
+logically, i.e., they do not skip numbers. They may have many parts:
+e.g., major, minor, patch-level, build number, RC number.
+
+### External Release Number
+
+External release numbers are the numbers that users see. Often, they
+will be the same as the internal release number. That is especially
+true if the product being built is a component intended to be reused
+by another engineering group in the same development organization.
+External release numbers can be different for products that
+face competition. External release number are simpler, and may not
+count up logically. E.g., a certain major ISP jumped up to version 8
+of their client software because their competition had released
+version 8. Later, the competition used version "10 Optimized" rather
+than "10.1" or "11".
+
+### Release Number
+
+The term "release number" by itself refers to an
+[external release number](#external-release-number). Users normally are not aware
+of the existence of any internal release numbers.
+
+## Development Tool Terms
+
+### Version Control System
+
+::DEFINITION1
+
+### Commit Log Message
+
+::DEFINITION1
+
+### Issue Tracker
+
+::DEFINITION1
+
+### Unit Testing Automation
+
+::DEFINITION1
+
+### Automated Build System
+
+::DEFINITION1
+
+### Style Checker
+
+::DEFINITION1
+
+### Source Code Formatter (Pretty Printer)
+
+::DEFINITION1
+
+### System Test Automation
+
+::DEFINITION1
+
+## Requirements Terms
+
+### Feature specification
+
+A feature specification focuses on one feature of a software product
+and completely describes how that feature can be used. It includes a
+brief description of the purpose of the feature, the input and
+output, and any constraints. Individual bullet items give precise
+details on all aspects of the feature. One feature may be used in
+many different ways as part of many different use cases.
+
+### Use case
+
+The main part of a use case is a set of steps that give an example
+of how an [actor](#actor) can use the product to succeed at
+a goal. These steps are called the "Main success scenario", and they
+include both user intentions and system responses. One use case may
+show how the actor uses several features to accomplish a goal.
+
+### Actor
+
+A user or an external system that uses the system being built.
+
+## Design Terms
+
+### ::TERM2
+
+::DEFINITION2
+
+## Design Goals Terms
+
+### Correctness
+
+This design correctly matches the given requirements.
+
+### Feasibility
+
+This design can be implemented and tested with the planned amount of
+time and effort.
+
+### Understandability
+
+Developers can understand this design and correctly implement it.
+
+### Implementation phase guidance
+
+This design divides the implementation into components or aspects
+that can correspond to reasonable implementation tasks.
+
+### Modularity
+
+Concerns are clearly separated so that the impact of most design
+changes would be limited to only one or a few modules.
+
+### Extensibility
+
+New features or components can be easily added later.
+
+### Testability
+
+It is easy to test components of this design independently, and
+information is available to help diagnose defects.
+
+### Efficiency
+
+The design enables the system to perform functions with an
+acceptable amount of time, storage space, bandwidth, and
+other resources.
+
+### Ease of integration
+
+The components will work together.
+
+### Capacity matching
+
+The architecture deploys components onto machines that provide
+needed resources with reasonable total expense.
+
+### Expressiveness
+
+It allows for storage of all valid values and relationships
+
+### Ease of access
+
+Application code to access stored data is simple
+
+### Reliability
+
+Stored data cannot easily be corrupted by defective code, concurrent
+access, or unexpected process termination
+
+### Data capacity
+
+The system can store the amount of data needed.
+
+### Data security
+
+Protection of sensitive user and corporate data from unauthorized
+access or modification
+
+### Performance
+
+Data can be accessed quickly
+
+### Interoperability
+
+The database or data files can be accessed and updated by other
+applications
+
+### Intrusion prevention
+
+Prevent, e.g., hackers opening a command shell on our server.
+
+### Abuse prevention
+
+Prevention of abuse (e.g., using our system to send spam).
+
+### Auditability
+
+All changes can be accounted for later.
+
+### Understandability and learnability
+
+Users can reasonably be expected to understand the UI at
+first sight. Users will be able to discover additional features
+without aid from other users or documentation, and they will be able
+to recall what they have learned.
+
+### Task support and efficiency
+
+The UI is well matched to the users' tasks and it can be used with a
+reasonable number of clicks and keystrokes.
+
+### Safety
+
+Users are not likely to accidentally produce an undesired result
+(e.g., delete data, or send a half-finished email).
+
+### Consistency and familiarity
+
+Users can apply their knowledge of similar UIs or UI standards to
+this system.
+
+## QA Terms
+
+### Bug
+
+*n.* **Deprecated** since 1991. See [defect](#defect).
+
+### Error
+
+*v.* A mistaken thought in the developer's mind. Often caused by
+miscommunication or bad assumptions. Errors can create
+[defects](#defect). E.g., a developer might erroneously think that
+the square root of -4 is -2.
+
+### Defect
+
+*n.* The result of the developer's [error](#error) embodied in the
+product source code, initial data, or documents. E.g., a square root
+function which allows negative numbers as arguments is defective.
+Defects can be removed by changing the source code, initial data,
+or document.
+
+### Fault
+
+*n.* The execution of defective code. E.g., if a certain input is
+provided to defective code, it may cause an exception, or go into an
+infinite loop, or store an incorrect value in an internal variable.
+A fault is not normally visible to users, only the
+[failure](#failure) is visible.
+
+### Failure
+
+*n.* The user-visible result of a [fault](#fault). E.g., an error
+message or an incorrect result. This is evidence that can be
+reported in a defect report. Developers use failure evidence during
+debugging to eventually find and remove [defects](#defect).
+
+## QA Goals Terms
+
+### Functionality > Correctness
+
+Correctness is the most basic quality goal. It means that, when
+valid inputs are given and the system is in a valid state and under
+reasonable load, the system's behavior and results will be correct.
+
+### Functionality > Robustness
+
+Robustness is the system's ability to gracefully handle
+invalid inputs. It should never be possible for any user input to
+crash the system or corrupt data, even if that user input is
+abnormal, unexpected, or malicious.
+
+### Functionality > Accuracy
+
+Accuracy refers to the mathematical precision of calculations done
+by the system. Any system that does numeric calculations must
+consider accuracy, e.g., financial or scientific applications.
+
+### Functionality > Compatibility
+
+Systems that claim to follow standards or claim compatibility with
+existing systems must adhere to the relevant file formats,
+protocols, and APIs. The relevant standards are linked at the top of
+this document.
+
+### Functionality > Factual correctness
+
+Is the data in the system a true representation of the real world?
+Any system that contains initial data or gathers data about the real
+world should be sure that the data is factually correct. E.g., a tax
+preparation program should embody correct and up-to-date facts about
+tax law.
+
+#### Usability > Understandability and Readability
+
+Users need to understand the system to use it. The basic metaphor
+should be understandable and appropriate to user tasks. Some defects
+in understandability include unclear metaphors, poor or hard-to-see
+labels, lack of feedback to confirm the effects of user actions, and
+missing or inadequate on-line help.
+
+### Usability > Learnability and Memorability
+
+Every user interface contains some details that users will need to
+learn and remember. E.g., Alt-F to open the "File" menu. UI cues and
+rules can make these details easier to learn and remember. E.g., the
+"F" is underlined and, as a rule, the first letter is usually the
+accelerator key.
+
+### Usability > Task support
+
+This is the quality of match between user tasks and the system's UI.
+Task support defects are cases where the system forces the user to
+take unnatural steps to accomplish a task or where the user is given
+no support for a difficult step in a task. E.g., must the user
+invent an 8-character filename for their "Christmas card list"?
+E.g., must users total their own tax deductions?
+
+### Usability > Efficiency
+
+Users should be able to accomplish common tasks with
+reasonable effort. Common tasks should be possible with only one or
+two steps. The difficulty of each step should also be considered.
+E.g., does the user have to remember a long code number or click on
+a very small button?
+
+### Usability > Safety
+
+Humans are error-prone, but the negative effects of common errors
+should be limited. E.g., users should realize that a given command
+will delete data, and be asked to confirm their intent or have the
+option to undo.
+
+### Usability > Consistency and Familiarity
+
+Users should be able to apply their past experience from other
+similar systems. This means that user interface standards should be
+followed, and common conventions should be used whenever possible.
+Also, UI elements that appear in several parts of the UI should be
+used consistently, unless another UI quality takes priority. E.g.,
+if most currency entry fields do not require a dollar-sign, then one
+that does demand it is a consistency defect, unless there is a real
+chance that the user is dealing with another currency on that step
+in his/her task.
+
+### Usability > Subjective satisfaction
+
+Users should feel generally satisfied with the UI. This is a
+subjective quality that sums up the other user interface qualities
+as well as aesthetics.
+
+### Security
+
+The system should allow usage only by authorized users, and restrict
+usage based on permissions. The system should not allow users to
+side-step security rule or exploit security holes. E.g., all user
+input should be validated and any malicious input should
+be rejected.
+
+### Reliability > Consistency under load
+
+Every system has some capacity limits. What happens when those
+limits are exceeded? The system should never lose or corrupt data.
+
+### Reliability > Consistency under concurrency
+
+Systems that allow concurrent access by multiple users, or that use
+concurrency internally, should be free of race conditions
+and deadlock.
+
+### Reliability > Availability under load
+
+Every system has some capacity limits. What happens when those
+limits are exceeded? The system should continue to service those
+requests that it is capable of handling. It should not crash or stop
+processing all requests.
+
+### Reliability > Longevity
+
+The system should continue to operate as long as it is needed. It
+should not gradually use up a limited resource. Example longevity
+defects include memory leaks or filling the disk with log files.
+
+### Scalability
+
+Scalability is a general quality that holds when the system
+continues to satisfy its requirements when various usage parameters
+are increased. E.g., a file server might be scalable to a high
+number of users, or to very large files or very high capacity disks.
+Several specific scalability goals are listed below.
+
+### Scalability > Performance under load
+
+This is a specific type of scalability goal dealing with the
+performance of the system at times when it is servicing many
+requests from many users.
+
+### Scalability > Large data volume
+
+This is a specific type of scalability goal dealing with the ability
+for the system to handle large data sets. Operations should continue
+to be correct and efficient as data set size increases. Furthermore,
+the user interface should still be usable as the data presented to
+users increases in length.
+
+### Operability
+
+The long-term needs of system administrators should be
+reliably supported. E.g., is the system easy to install? Can the
+administrator recover from a crash? Is there sufficient log output
+to diagnose problems in the field? Can the system's data be backed
+up without downtime? Can the system be upgraded practically?
+
+### Maintainability > Understandability
+
+Will it be easy for (future) developers to understand how the system
+works?
+
+### Maintainability > Evolvability
+
+Can the system easily be modified and extended over time?
+
+### Maintainability > Testability
+
+Can the system easily be tested? Do the requirements precisely
+specify possible inputs and the desired results? Can the system be
+tested in parts? When failures are observed, can they be traced back
+to defects in specific components (i.e., debugging)? Is testing
+practical with the available testing tools?
+
+## Additional Standard Terms
+
+For additional standard terms, see the following reference sites:
+
+- [Dictionary.com](http://www.dictionary.com/)
+- [Whatis.com](http://www.whatis.com/)
+- [NIST Dictionary of Algorithms and Data Structures](http://www.nist.gov/dads/)
+- [Free on-line dictionary of computing](http://foldoc.doc.ic.ac.uk/foldoc/index.html)
+- [IBM's glossary of computing terms](http://www-3.ibm.com/ibm/terminology/goc/gocmain.htm)
+- [Jargon File](http://www.jargon.org/)

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Glossary.md

@@ -0,0 +1,116 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+**Process impact:** This file as a dictionary of terms defined as they
+are used during the project. Writing out the definitions of terms and
+acronyms here helps keep other documents more concise and precise. A
+shared glossary helps prevent misunderstandings and makes it easier for
+new team members to be productive.
+
+<!-- markdownlint-disable link-fragments -->
+Jump to: [A](#a) | [B](#b) | [C](#c) | [D](#d) | [E](#e) | [F](#f) |
+[G](#g) | [H](#g) | [I](#i) | [J](#j) | [K](#k) | [L](#l) | [M](#m) |
+[N](#n) | [O](#o) | [P](#p) | [Q](#q) | [R](#r) | [S](#s) | [T](#t) |
+[U](#u) | [V](#v) | [W](#w) | [X](#x) | [Y](#y) | [Z](#z) |
+<!-- markdownlint-enable link-fragments -->
+[Standard terms](Glossary-Standard-Terms)
+
+## Project-specific Terms
+
+_TIPs:_
+
+- _Define HTML anchors on your terms with id="TERMNAME" so that other
+  documents can link to the definition of specific terms._
+- _If there is any question about the meaning of a term, note it here.
+  If someone (e.g., the customer) gave you a definition to use, note
+  that here too. If something is best defined by using a hyperlink to
+  another document or website, include a hyperlink in the definition._
+- _If a term was used in the past, but is no longer going to be used,
+  you should keep it in the list, mark it as "deprecated", and link to
+  the term or terms that replace it. E.g., deprecated standard term
+  [bug](glossary-std.html#bug)._
+- _Define only project-specific terms, or ones that a new team member
+  would not know. Don't define standard textbook terms that can be
+  easily found elsewhere._
+- _This glossary can serve as simple domain model or data dictionary.
+  You can define important data objects by describing their meaning
+  and key attributes. For example, see [student](#student) and
+  [GPA](#gpa)._
+
+### A
+
+### B
+
+### C
+
+#### ::Class standing
+
+- ::Computed attribute of [student](#student) based on number of
+  academic units completed. Used to determine priority in
+  course enrollment.
+- ::Real-world meaning of values:
+
+|             |                                 |
+| ----------- | ------------------------------- |
+| ::Freshman  | ::Less than 90 units            |
+| ::Sophomore | ::Between 90 and 180 units      |
+| ::Junior    | ::Between 180 and 270 units     |
+| ::Senior    | ::More than 270 units completed |
+
+### D
+
+### G
+
+#### ::GEF
+
+::_n._ The [Graph Editing Framework](http://gef.tigris.org/). An open
+source library for editing diagrams (boxes and arrows).
+
+#### ::GPA
+
+::_n._ Grade Point Average. GPA is a float between 0.00 and 4.00,
+accurate to 2 decimal places. Computed from average of completed
+course grades in transcript weighted by course units. Used to
+determine student ranking, and to trigger Dean's List and
+academic probation.
+
+### I
+
+#### ::ICS
+
+::_n._ Acronym for the [School of Information and Computer
+Science](http://www.ics.uci.edu/) at [UC Irvine](http://www.uci.edu/).
+
+### S
+
+#### ::Student
+
+::_n._ A person who attends a school to earn a degree. Persistent
+attributes include: student_id_number (primary key), GPA, major,
+and years_at_school.
+
+#### ::Senior
+
+::_n._ A senior is special type of [undergraduate](#undergraduate) who
+has a certain number of course credits on his or her transcript.
+Years_at_school does not determine senior standing. TODO: how many
+credits needed?
+
+### T
+
+#### ::Term1
+
+::Definition1
+
+#### ::Term2
+
+- ::Definition2a
+- ::Definition2b
+
+#### ::Term3
+
+::Definition3
+
+### U
+
+#### ::Undergraduate
+
+::A type of [student](#student). _TODO: add more detail._

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Home.md

@@ -0,0 +1,61 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+## Project Overview
+
+### Mission and Scope
+
+<!-- markdownlint-disable-next-line no-emphasis-as-header -->
+_TODO: Answer these questions in your own words by filling in each_
+
+#### What problem does this project address?
+
+::2-4 SENTENCE PROBLEM
+
+#### What is the goal of this project?
+
+::2-4 SENTENCE GOAL
+
+#### What is the scope of this project?
+
+::2-4 SENTENCE SCOPE
+
+#### What development methodology is being used?
+
+::See our [software development methodology](SDM) document.
+
+#### Where should a new team member start?
+
+::For more information, see the [project proposal](Proposal).
+
+### Status
+
+_TODO: Briefly describe the status of this project. E.g., what phase are
+you in? And, what is your next major milestone? Detailed project status
+is written in the status reports, not here._
+
+::We have completed our second beta release and are currently working on
+adding more of the functionality described in our product
+[specification](srs) and fixing defects.
+
+::The next major milestone is a third beta release with nearly complete
+functionality and a wider set of testers.
+
+### Project Documents
+
+| By Activity   | Documents                                                                                                                                                                                              |
+| ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| Inception:    | [Home](Home), [Project Proposal](Proposal), [Target Audience and Benefits](Target-and-Benefits), [Statement of User Needs](User-Needs)                                                                 |
+| Reference:    | [Glossary](Glossary), [Software Development Methodology](SDM), [Document Cross Reference](Document-Cross-Ref), [All-in-one project summary](Summary)                                                   |
+| Elaboration:  | [Project Plan](Project-Plan), [Software Requirements Specification](SRS), [Feature Set](Feature-Set), [Use Case Suite](Use-Case-Suite), [Design](Design), [QA Plan](QA-Plan), [Test Suite](Test-Suite) |
+| Construction: | [Review Meeting Notes](Review-Meeting-Notes), [Implementation Notes](Implementation-Notes), [User Guide](User-Guide), [FAQ / Troubleshooting Guide](FAQ)                                               |
+| Transition:   | [Install / Quick Start](Installation-Guide), [Demo Script](Demo-Script), [Release notes](Release-Notes), [Release checklist](Release-Checklist), [Post Mortem](Post-Mortem)                            |
+| Continuous:   | [Status Report](Status-Report)                                                                                                                                                                         |
+
+| By Audience          | Documents                                                                                                                                                                                                                                                                      |
+| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| For Everyone:        | [Home](Home), [Project Proposal](Proposal), [Target Audience and Benefits](Target-and-Benefits), [Statement of User Needs](User-Needs), [Software Requirements Specification](SRS), [Project Plan](Project-plan), [Release Checklist](Release-Checklist), [Glossary](Glossary) |
+| For Management:      | [Project Resource Needs](Resource-Needs), [Status Report](Status-Report)                                                                                                                                                                                                       |
+| For Developers:      | [Design](Design), [Review Meeting Notes](Review-Meeting-Notes), [Software Development Methodology](SDM)                                                                                                                                                                        |
+| For QA:              | [QA Plan](QA-Plan)                                                                                                                                                                                                                                                             |
+| For End Users:       | [Install / Quick start](Installation-Guide), [User Guide](User-Guide), [Release Notes](Release-Notes)                                                                                                                                                                          |
+| For Support and Ops: | [Implementation Notes](Implementation-Notes), [FAQ / Troubleshooting Guide](FAQ)                                                                                                                                                                                               |
+| For Sales/Legal:     | [Demo Script](Demo-Script), [Legal Issues](Legal)                                                                                                                                                                                                                              |

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Implementation-Notes.md

@@ -0,0 +1,221 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Software Requirements Specification](SRS)
+- [Release notes](Release-Notes)
+- [FAQ](FAQ)
+- [Glossary](Glossary)
+
+---
+
+**Process impact:** This document is a brief and fairly technical
+discussion of how the system works under ideal conditions. It is also
+known as a "theory of operation" document. It should describe key
+algorithms, technology dependencies, and operational issues. Much of the
+content of this document can be drawn from design documents. This
+document will be used by the QA, technical support, and operations
+groups. The goal is to give those groups the information they need to
+understand, manage, or begin to troubleshoot the system (i.e., recognize
+certain behavior as normal or abnormal). If significantly more
+information is needed, it should be organized into a larger "operations
+guide".
+
+### Type of Implementation
+
+_TODO: Fill in information that will help other engineers understand this
+system at-a-glance. Feel free to use relevant technical terms and name
+specific technology platforms._
+
+#### Type of system
+
+- ::Desktop GUI application ||
+- ::Unix-style command ||
+- ::Server-side web application ||
+- ::Web service ||
+- ::Client-side applet ||
+- ::Embedded application ||
+- ::Reusable library ||
+- ::Reusable class framework ||
+- ::Browser Plug-in
+
+#### Programming Language(s)
+
+- ::Java ||
+- ::Perl, Unix shell scripts
+
+#### Data Storage
+
+- ::Flat files using XML ||
+- ::Flat files using Java properties file format ||
+- ::Flat files using Java object serialization format ||
+- ::SQL database: MySQL
+
+#### UI Technologies
+
+- ::Java Swing ||
+- ::XHTML, CSS, JavaScript
+
+##### Security Technologies
+
+- ::Authentication: None needed ||
+- ::Authentication: Local username and password file ||
+- ::Authentication: LDAP ||
+- ::Authorization: Operating system file ownership and read-write-execute flags ||
+- ::Authorization: Access control lists ||
+- ::Encryption: None needed ||
+- ::Encryption: SSL
+
+### Runtime Environment
+
+_TODO: List and describe runtime objects that make up a running system.
+These objects may be referred to by name in the sections below._
+
+#### Processes
+
+- ::Main application process
+- ::Client and server processes
+- ::Cron tasks
+- ::Operating system services or drivers
+
+#### Configuration Files
+
+- ::PRODUCT-NAME.conf: stores application configuration in Java properties file format.
+- ::Section of httpd.conf: configures components of the Apache webserver
+
+#### Database Table
+
+- ::TABLE_ONE: Each row represents a ...
+- ::TABLE_TWO: Each row represents a ...
+- ::TABLE_THREE: Each row represents a ...
+- ::See the persistence design document.
+
+#### Data Files
+
+- ::\*.ext: Data files saved by the user on their local hard disk.
+- ::/var/PRODUCT-NAME/upload-XXXX.dat: Files uploaded to the server.
+
+#### Temporary Files
+
+- ::/tmp/PRODUCT-NAME.pid: Process ID of the currently running server process.
+- ::/tmp/upload-XXXX.dat: Files uploaded to the server before they are processed.
+
+#### Log Files
+
+- ::error.log: Serious errors are put in the normal Apache error log. Must be writable by Unix user httpd.
+- ::PRODUCT-NAME.log: Messages indicating the progress of normal operations and some errors. Must be writable by Unix user httpd.
+- ::Log files are rotated nightly. Old logs are archived in ANOTHER LOCATION.
+
+### Implementation of Specific Features
+
+_TODO: Write short descriptions of interesting or unexpected algorithms,
+limiting assumptions, or any other implementation detail that will
+impact the work of other groups. E.g., long-running operations that must
+not be interrupted. E.g., start up or shutdown scripts that are
+automatically run by the operating system._
+
+- ::Feature name: 1-3 SENTENCE DESCRIPTION
+- ::Feature name: 1-3 SENTENCE DESCRIPTION
+- ::Feature name: 1-3 SENTENCE DESCRIPTION
+  - ::DETAILS
+  - ::DETAILS
+  - ::DETAILS
+- ::Feature name: 1-3 SENTENCE DESCRIPTION
+  - ::DETAILS
+  - ::DETAILS
+  - ::DETAILS
+
+### Operational Procedures
+
+_TODO: Briefly describe procedures that should be followed by operations
+engineers when the system is being run in an ASP production environment._
+
+#### Install
+
+::See the [installation guide](Installation-Guide)
+
+#### Upgrade
+
+::See the [installation guide](Installation-Guide)
+
+#### Start Server
+
+1. ::STEP 1
+2. ::STEP 2
+3. ::STEP 3
+
+#### Stop Server
+
+1. ::STEP 1
+2. ::STEP 2
+3. ::STEP 3
+
+#### Reload Config Files
+
+1. ::STEP 1
+2. ::STEP 2
+3. ::STEP 3
+
+#### Monitor Activity
+
+::Watch the PRODUCT-NAME.log and error.log.
+
+#### Periodic Cleanup
+
+::On rare occasion, /tmp/upload-XXXX.dat files can be left behind. Any such files that are more than a day old can safely be removed.
+
+### Security
+
+_TODO: Write notes on security to help operations engineers keep the
+system secure while it is in operation._
+
+We take the following precautions to make the system secure
+
+- ::STEP
+- ::STEP
+- ::STEP
+
+The security of the system depends on the following external factors
+
+- ::STEP
+- ::STEP
+- ::STEP
+
+### Performance and Scalability
+
+_TODO: Write notes on performance and scalability to help operations
+engineers operate the system efficiently._
+
+::NOTES ON PERFORMANCE.
+
+::NOTES ON SCALABILITY.
+
+### Implementation Notes Checklist
+
+Do these implementation notes provide enough information for operations engineers?
+
+- ::Yes, these notes have been reviewed by the operations team and
+  requested changes have been incorporated.
+- ::No, these notes only summarize parts of a larger
+  [operations manual](LINK-TO-OPERATIONS-MANUAL).
+- ::No, a member of the development team is available on-call whenever
+  the operations team may need help. This is listed in the
+  [Resource Needs](Resource-Needs) document and in the
+  [on-call schedule](LINK-TO-ON-CALL-SCHEDULE).
+
+Have these implementation notes been communicated to the operations and development teams and other stakeholders?
+
+- ::Yes, everyone has had a chance to review them. Feedback is welcome.
+- ::Yes, it has been posted to the project website.
+- ::No, some developers or operations engineers are not aware of
+  this document. This is a risk that is noted in the
+  [Risk Management](Project-Plan#risk-management) section of the
+  [Project Plan](Project-Plan).

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Installation-Guide.md

@@ -0,0 +1,97 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+_TODO: Fill in information about this product. Make sure to use the
+**product** name and **external** release number, not internal
+information._
+
+##### Product
+
+::PRODUCT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Release Date
+
+::YEAR/MONTH/DAY
+
+##### Customer Support
+
+:: For more information or support, please visit our
+[website](::http://www.COMPANY.com/products/PRODUCT-NAME/) or
+email us at <::support@COMPANY.com>
+
+---
+
+### Introduction
+
+::This document describes how to install and get started with
+PRODUCT-NAME.
+
+### Minimal System Requirements
+
+::System requirements are described in the [release notes](Release-Notes).
+
+### Installation
+
+_TODO: Give detailed installation instructions. Make sure to test these
+instructions by doing them yourself on a target machine._
+
+_TIP: For development releases, or products that are reusable components
+rather than end-user applications, you should include information on
+needed development and bugging tools, e.g., Ant and JUnit._
+
+#### What other software must be installed first?
+
+::Before you can install this product, you must install the following
+packages:
+
+- ::[Java SDK](http://java.sun.com/)
+- ::[Apache Tomcat](http://jakarta.apache.org/)
+- ::[MySQL database](http://mysql.com/)
+- ::[OTHER PACKAGES](http://)
+
+#### How do I install PRODUCT-NAME?
+
+:: Please follow these steps
+
+1. ::STEP
+2. ::STEP
+   - ::SUB-STEP
+3. ::STEP
+4. ::STEP
+
+#### How can I uninstall PRODUCT-NAME?
+
+1. ::STEP
+2. ::STEP
+   - ::SUB-STEP
+3. ::STEP
+4. ::STEP
+
+#### What if I encounter problems?
+
+::Please see the troubleshooting section in the [FAQ](FAQ).
+
+### Getting Started
+
+_TODO: Briefly describe how the user would accomplish one or two of the
+main use cases for new users. For development releases or reusable
+components, include instructions on running unit tests._
+
+#### How can I run post-install unit tests?
+
+1. :Compile the source code by typing "ant"
+2. :Run unit tests by typing "ant test"
+   - ::A brief report will be shown on the console
+   - ::A detailed test report for any failed tests will be
+     in build/test-out.
+
+#### ::How can I quickly get started using PRODUCT-NAME?
+
+1. ::STEP
+2. ::STEP
+   - ::SUB-STEP
+3. ::STEP
+4. ::STEP

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Interview-Checklist.md

@@ -0,0 +1,105 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Related Documents
+
+- [User Needs](User-Needs)
+- [Interview Notes](interview-notes.html)
+
+---
+
+**Process impact:** This checklist will help you plan customer
+interviews.
+
+### Pre-Interview Checklist
+
+1. Decide what goals you want to accomplish
+2. Prepare a list of questions
+   - Ask about things you know you need to find out, based on your
+     current understanding of the requirements
+   - Keep questions simple. Don't use multi-part questions, break
+     complex topics into individual questions.
+   - Confirm key assumptions. E.g., "You are the one who actually
+     would use this software, right?" "The total needs to be
+     displayed and updated as each item is scanned, right?"
+   - Avoid leading or multiple-choice questions because the right
+     answer might be one that you don't know about yet. E.g., WRONG:
+     "Would you log in to the system from your desk here or from
+     home?" RIGHT: "Where are some of the places you would be sitting
+     when you log in?" "Here in my office, but also when I work with
+     others sometimes I log in from their office or from a machine in
+     the lab or conference room... so, I don't want a cookie saved
+     there."
+   - Try to find out the priority of each requirement: essential,
+     expected, desired, or optional.
+   - Write some more open-ended questions to see if new important
+     requirements come up.
+   - Don't ask too many questions that seem out of scope, you could
+     accidentally change the scope or set incorrect expectations.
+     E.g., "Would you like the system to also do ten other cool
+     things?" "Sure!"
+3. Select interviewees that represent all important stakeholders
+4. Review your questions. Do you think they can be answered? Will they
+   help achieve your goals? If not, go back and revise.
+5. Decide whether you want to do this interview via email, telephone,
+   or in person
+6. Schedule an interview a time and place for the
+   interviewee's convenience. Plan on the interview lasting one hour.
+
+### Interview Checklist
+
+1. Be prompt, courteous, and business-like
+2. Introduce yourself and explain why you are there
+3. Make sure that you are interviewing the person you think you are.
+   Get their contact information (e.g., email address) if you don't
+   already have it.
+4. Ask permission to take notes. Don't record or video tape.
+5. Confirm the amount of time you and the interviewee have for
+   this session.
+6. Give a quick indication of the type and number of questions that you
+   have
+7. Work through the questions.
+8. Listen. That is why you are there.
+9. If the interviewee refers to existing documents, systems, equipment,
+   or people, make sure that you understand what he or she is
+   talking about. If it is important, ask if you may have a copy or
+   screenshot (but, don't ask for anything containing proprietary
+   information), or make a note of the important aspects of the items
+   referred to. Note the URLs of any existing public
+   websites discussed.
+10. Try not to answer the questions yourself, or to react to interviewee
+    requests by making promises to solve problems. Interviews are for
+    understanding the problems, not solving them or setting schedules
+    or deliverables.
+11. Write down action items to follow up on finding more information.
+    E.g., if the interviewee starts explaining at length something that
+    you know you can learn on your own, or if they don't know the answer
+    and start speculating at length, you should try to move on the
+    next question.
+12. If you find that you have prepared the wrong questions, focus on
+    getting information that will help you prepare the right
+    follow-up questions.
+13. Finish on time. If you need more time, continue via email or
+    another meeting.
+14. Summarize action items that you will follow up on
+15. Ask if the interviewee has any questions for you, or if there was
+    something more that they wanted you to ask.
+16. Make sure to leave contact information
+17. Thank the interviewee for their time
+
+### Post-Interview Checklist
+
+1. Within 24 hours, read your notes and fill in any important details
+   that were said but not written down
+2. Type up your notes so that they can be shared with the team and
+   archived
+3. Formulate any important follow-up questions
+4. Within 2-3 days, send a follow-up email message to
+   - Thank the interviewee again
+   - Confirm that you have their correct email address, and make it
+     easier for them to reply to you
+   - Ask any important follow-up questions
+   - Give status on your action items, if any. E.g., "I searched
+     Google for that product you mentioned and I couldn't find a
+     users manual, but I did find a magazine review of it." Or,
+     "After I interviewed you, I spoke with Bob, and he confirmed
+     that some current products do cost $0.00."

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Interview-Notes.md

@@ -0,0 +1,100 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Interviewer(s)
+
+::PERSON-NAME
+
+##### Interviewee(s)
+
+::PERSON-NAME
+
+##### Date of Interview
+
+::DATE
+
+##### Interview Location
+
+::LOCATION
+
+##### Related Documents
+
+- [Project proposal](Proposal) > [Target audience and benefits](Target-and-Benefits)
+- [Interview checklist](Interview-Checklist)
+- [Glossary](Glossary)
+
+---
+
+_TODO: Copy this file once for each interview. Fill in the details. Link
+to this file from the "Notes from Interviews and Brainstorming" section
+of user-needs.md._
+
+**Process impact:** Planning questions for interviews with stakeholders
+is key to effective requirements gathering. Good requirements are needed
+to build the right system. These notes should be kept as part of the
+documentation on [user needs](User-Needs) are referred to when the
+[software requirements specification](SRS) is written or updated.
+
+### Interview Questions and Answers
+
+_TODO: Before the interview, plan the questions you will ask. Afterwords,
+type up the answers you received and any additional questions and
+answers, and any new follow-up questions._
+
+#### ::How did you learn about the need for this product?
+
+::ANSWER
+
+#### ::What types of users are likely to use this product?
+
+::ANSWER
+
+#### ::Can you give an example of how a user might actually use the product?
+
+::ANSWER
+
+#### ::Is there any risk or downside to using the product?
+
+::ANSWER
+
+#### ::QUESTION1
+
+::ANSWER1
+
+#### ::QUESTION2
+
+::ANSWER2
+
+#### ::QUESTION3
+
+::ANSWER3
+
+#### QUESTION4
+
+::ANSWER4
+
+### New Questions and Action Items
+
+_TODO: Often early interviews will raise more questions than they answer.
+Note these new questions and what you must do to find the answer._
+
+- ::Can we do X?
+- ::Do we support Y?
+- ::Action item: research topic Z
+- ::Action item: Send follow-up email as per [post-interview checklist](Interview-Checklist#post-interview-checklist)
+- ::Action item: prepare for next interview with PERSON(S) on DATE
+
+### Other Interview Notes
+
+_TODO: Note anything else that came out of the interview, either
+explicitly or implicitly. Remember to confirm things that you picked up
+implicitly if there is any doubt. E.g., make a note if the interviewee
+uses an unusual meaning for a certain term. Add links to any documents
+provided to you by the interviewee._
+
+- ::NOTE
+- ::NOTE
+- ::NOTE

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Legal.md

@@ -0,0 +1,128 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Release Audience
+
+- ::General availability release ||
+- ::Customer-specific release: CUSTOMER(S) ||
+- ::Developer release (Internal usage only) ||
+- ::Early access release (Controlled external access)
+
+##### Intended Product License
+
+::Commercial license
+
+##### Related Documents
+
+- [Project proposal](Proposal) > [Target audience and benefits](Target-and-Benefits)
+- [Project Plan](Project-Plan) > [Resource needs](Resource-Needs)
+- [Glossary](Glossary)
+
+---
+
+**Process impact:** This document outlines legal issues that may affect
+this release. Failure to carefully consider these issues may put the
+development organization at risk for legal action.
+
+_TODO: Fill in the information above and below. Add or remove rows as
+needed. Use the worksheet to help identify legal issues. Seek
+professional counsel for review as needed._
+
+### Ownership of Intellectual Property
+
+| Component                  | Owner        | License              | Status                                        | Comments                                                       |
+| -------------------------- | ------------ | -------------------- | --------------------------------------------- | -------------------------------------------------------------- |
+| ::Product name             | ::Us         | ::Trademark          | ::Registration pending                        | ::We must use "(TM)", not "(R)"                                |
+| ::Database                 | ::VENDOR     | ::Commercial license | ::In compliance, paid normal fee              | ::Limits us to 2 CPUs/server                                   |
+| ::Encryption library       | ::VENDOR     | ::Commercial license | ::In compliance, signed partnership agreement |                                                                |
+| ::Clip-art graphics        | ::None       | ::Public Domain      | ::In compliance                               |                                                                |
+| ::Sound driver library     | ::OS Project | ::BSD                | ::In compliance                               |                                                                |
+| ::Search engine indexer    | ::OS Project | ::GPL                | ::In compliance                               | ::Indexer runs in separate process, does not make our code GPL |
+| ::Other library            | ::OS Project | ::BSD                | ::In compliance                               |                                                                |
+| ::Other data               | ::Us         | ::Copyrighted        | ::In compliance                               |                                                                |
+| ::Special algorithm patent | ::Us         | ::Patent pending     | ::In compliance                               | ::Patent search done, patent application submitted             |
+
+### Regulatory Compliance
+
+| Type                     | Regulation                                        | Status          | Comments                                                  |
+| ------------------------ | ------------------------------------------------- | --------------- | --------------------------------------------------------- |
+| ::Export                 | ::Strong encryption exports must be declared      | ::In compliance | ::We will not distribute out of country                   |
+| ::Privacy                | ::Cannot collect personal information from minors | ::In compliance | ::We ask for user age before asking for other information |
+| ::Industry certification | ::Game industry rating                            | ::In compliance | ::We follow guidelines for "Everyone" rating              |
+
+> **Possible Status Values**
+>
+> - In compliance: we are OK to go ahead with this release
+> - Waived: we decided not to consider this aspect for this release
+> - Violated: we are not conforming. Comment should describe impact.
+
+### Legal Issues Checklist
+
+The goal of this checklist is to help expose legal issues that might
+otherwise be missed. It does not help with the actual management of
+legal issues.
+
+_TODO: Answer the questions below. If multiple sample answers are
+provided, delete the ones that do not apply. Edit any provided answers
+as needed._
+
+#### Does the development organization hold trademarks on the product name and any other names used in marketing the product?
+
+::Yes. Make sure to defend your ownership.
+
+::No. Make sure not to impinge on the trademarks of others.
+
+#### Does the development organization hold or license patents on intellectual property that is used in the product?
+
+::Yes. Make sure to defend your ownership.
+
+::No. Make sure not to impinge on the patents of others.
+
+#### Does the development organization hold or license copyrights on source code that is used in the product?
+
+::Yes. Make sure to defend your ownership.
+
+::No. Make sure not to impinge on the patents of others.
+
+#### For each component in the product, is that component being used in a way that complies with its license?
+
+::Fill in details in table above.
+
+#### For each piece of copyrighted data in the product, is that data being used in a way that complies with its license?
+
+::Fill in details in table above.
+
+#### Was any component or data produced by another organization under contract?
+
+::Yes. Review the contract details for ownership and licensing.
+
+::No. No action required.
+
+#### Does the product use technologies that are under export control?
+
+::Yes. But, we have no plans to export.
+
+::Yes. Take steps to obtain needed export permissions.
+
+::No. No action required.
+
+#### Does the product need to meet industry-specific regulations?
+
+::Yes. Take steps to meet them. Specifically...
+
+::No. No action needed.
+
+#### Does the product satisfy corporate policies (e.g., on privacy and security)?
+
+::Yes. Describe how each policy is satisfied..
+
+::No. Describe steps to bring the product into compliance.
+
+::No. No policies apply.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/License.md

@@ -0,0 +1,73 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+Do not modify or delete this file. This file describes the license under
+which you may use the ReadySET templates.
+
+### Copyright and License
+
+Copyright (C) 2003-2004 Jason Robbins. All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions
+are met:
+
+1. Redistributions of these files must retain the above copyright notice, this list of conditions and the following disclaimer. The individual template files must retain the copyright footnote whenever they are used as templates.
+2. The name "ReadySET" must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact jrobbins@jrobbins.org.
+
+THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED
+WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
+MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
+IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT,
+INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
+(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
+SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
+STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
+IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+### License FAQ
+
+---
+
+#### Can I use these templates at my company?
+
+Yes, absolutely. Once you fill in the template with detailed
+information about a specific project, you are free to do what you
+want with them in the context of that project. **_You may even hide the
+template copyright statement_**: the best way to do that is to edit the
+file inst.css.
+
+#### Can I modify these templates for use on several projects at my company?
+
+Yes, absolutely. You may modify and distribute these templates to
+others, so long as you retain this file and the footnote with the
+copyright statement clearly visible in each file.
+
+#### Can I include these templates as part of a commercial product?
+
+If you use the templates and fill in details about a given product,
+go ahead. If you are thinking of making a product that includes the
+templates for use _as templates_, you must retain this file and the
+copyright statement in a visible footnote. An enhanced commercial
+version of these templates, [ReadySETPro](http://www.readysetpro.com/),
+is already in development
+
+#### Can I combine these templates with other templates or documents?
+
+Sure, go ahead. This license is not "viral", it does not mean that
+anything you do must be open source or covered under the
+same license.
+
+#### If I enhance the templates, must I give those enhancements back to the open source project?
+
+No, but it would be very welcome. Even if you don't modify the
+templates, you can share your "words of wisdom". For more
+information on contributing, see the
+[ReadySET home page](https://web.archive.org/web/20200701142616/http://readyset.tigris.org/).
+
+#### ReadySET seems too good to be true. What is the catch? Why would anyone buy a commercial version?
+
+There is no catch. However, the scope of ReadySET is limited to only
+most common needs of development projects. It is easy to get started
+with ReadySET, but [ReadySET Pro](http://www.readysetpro.com/) holds
+much more value for corporate users.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Project-Plan.md

@@ -0,0 +1,264 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Project Time-frame
+
+::START-DATE - END-DATE
+
+##### Attached worksheets
+
+- Plan > [Resource Needs](Resource-Needs)
+
+##### Related Documents
+
+- [Project Proposal](Proposal) > [Target audience and benefits](Target-and-Benefits)
+- [Software development methodology](SDM)
+- [Glossary](Glossary)
+
+---
+
+**Process impact:** This plan will be used to evaluate and manage the
+project. Key assumptions that affect the plan should be documented here.
+The project plan should be updated throughout the life-time of the
+project.
+
+_TODO: Fill in the information above and below. Add or remove rows as
+needed. Use the worksheet to help identify and scope resource needs._
+
+### Summary of Project
+
+#### What are the business problem, scope, and goal of this project?
+
+For a summary of this project, see the [Project proposal](Proposal).
+
+#### Who will sponsor, manage, and lead the project?
+
+- ::Sponsor: PERSON-NAME
+- ::Manager: PERSON-NAME
+- ::Technical lead: PERSON-NAME
+
+#### What authority does the project manager have?
+
+- ::Hire, dismiss, or reassign personnel in his/her department
+- ::Hire contract employees or manage subcontractors
+- ::Purchase equipment, software, and other needed capital
+- ::Assign specific tasks to other departments
+- ::Negotiate requirements and schedules with customers
+- ::Negotiate with vendors, suppliers, and partners
+
+#### What planning lessons were learned in previous releases?
+
+::None yet. This is the first release.
+
+- ::We can reduce training time, but it significantly increases development time.
+- ::Maintaining a past release takes more than 20% of our time, due to low quality in that release.
+- ::The customer seems to always change the requirements after the second demo.
+- ::There are always defects. We planned time to test, but we forgot to plan time to fix the defects.
+  On this project, we will actually estimate the number of undetected defects.
+- ::Issue XXXX made us realize that we forgot to plan time for DEVELOPMENT-TASK.
+
+### Summary of Methodology
+
+#### What general development approach will be used?
+
+::THREE TO FIVE SENTENCES OR BULLETS HERE. COVER GENERAL APPROACH, IMPORTANT ASSUMPTIONS, KEY PRACTICES, AND PROJECT COORDINATION CONTROLS.
+
+For more information see the [Software Development Methodology](SDM).
+
+#### How will the project team be organized?
+
+- ::The development team will consist of ...
+- ::The change control board will consist of ...
+
+#### What development and collaboration tools will be use?
+
+::We plan to use the following tools extensively through out the project:
+
+- ::Project website
+- ::Project mailing lists
+- ::Issue tracking system
+- ::Version control system
+- ::Automated build system
+- ::Automated unit test system
+
+#### How will changes be controlled?
+
+- ::Requests for requirements changes will be tracked in the issue tracker
+- ::The change control board ([CCB](Glossary#ccb)) will review requested changes and authorize work on them as appropriate
+- ::After the [feature complete](Glossary#featurecomplete) milestone, no new features will be added to this release.
+- ::After the [code complete](Glossary#codecomplete) milestone, no entirely new product source code will be added to this release.
+- ::All source code commit log messages must refer to a specific issue ID, after the feature complete milestone.
+
+#### How will this plan be updated?
+
+::This project plan will be updated as needed throughout the project.
+It will be placed under version control and instructions for
+accessing it will be on the [project website](Home). Any
+change to the plan will cause an automatic notification to be sent
+to a project mailing list.
+
+### Work Breakdown Structure and Estimates
+
+_TODO: List tasks that will be needed for this project. Keep dividing
+tasks into subtasks until you feel that you have enough detail to expose
+risks and make reasonable estimates in ideal engineering hours._
+
+_TIP: Label each step uniquely to show its position in the WBS, e.g.,
+Step 1.1.4.A. Use numbers for steps that you intend to do in sequence,
+and use letters for steps that you intend to do in parallel. E.g., Step
+1.1 comes before Steps 1.2.A and 1.2.B, but those two steps may be done
+in parallel, and Step 1.3 will be done after all 1.2.\* steps have been
+finished. Don't worry about renumbering if you delete a step._
+
+| Step     | Description                                                | Estimate  |
+| -------- | ---------------------------------------------------------- | --------- |
+| 1.       | ::Preparation                                              |           |
+| 1.1.     | ::Developer training                                       | 30h       |
+| 2.       | ::Inception                                                |           |
+| 2.1.     | ::Requirements gathering                                   | 30h       |
+| 2.2.     | ::Requirements specification                               | 20h       |
+| 2.3.     | ::Requirements validation                                  | 10h       |
+| 3.       | ::Elaboration                                              |           |
+| 3.1.     | ::High-level design                                        | 5h        |
+| 3.2.     | ::Low-level design (break down by component)               |           |
+| 3.2.A.   | ::Object design                                            | 10h       |
+| 3.2.B.   | ::User interface design                                    | 10h       |
+| 3.2.C.   | ::Database design                                          | 3h        |
+| 3.3.     | ::Design review and evaluation                             | 5h        |
+| 4.       | ::Construction                                             |           |
+| 4.1.A.   | ::System implementation                                    |           |
+| 4.1.A.1. | ::Implement COMPONENT-NAME 1                               | 25h       |
+| 4.1.A.2. | ::Implement COMPONENT-NAME 2                               | 25h       |
+| 4.1.A.3. | ::Implement COMPONENT-NAME 3                               | 25h       |
+| 4.1.A.4. | ::Implement COMPONENT-NAME 4                               | 25h       |
+| 4.1.A.5. | ::Integrate Components (mostly done during implementation) | 5h        |
+| 4.1.B.   | ::Technical documentation (break down by component)        | 10h       |
+| 4.1.C.   | ::User documentation (break down by component)             | 10h       |
+| 4.1.D.   | ::Testing                                                  |           |
+| 4.1.D.1. | ::Test planning                                            | 10h       |
+| 4.1.D.2. | ::Test code implementation (break down by component)       | 30h       |
+| 4.1.D.3. | ::Test execution                                           | 10h       |
+| 4.2.     | ::Implementation review and evaluation                     | 15h       |
+| 5.       | ::Transition                                               |           |
+| 5.A.     | ::Release packaging                                        | 3h        |
+| 5.B.     | ::Documentation for other groups                           | 3h        |
+| 6.       | ::Reflection                                               |           |
+| 6.1.     | ::Postmortem report                                        | 10h       |
+|          | ::Total                                                    | 329 hours |
+
+### Deliverables in this Release
+
+_TODO: List project deliverables in detail, with delivery dates._
+
+| Deliverable Name | Description                                                   | Delivery Date |
+| ---------------- | ------------------------------------------------------------- | ------------- |
+| Deliverable Name | ::Description                                                 | Delivery Date |
+| Deliverable Name | ::Description                                                 | Delivery Date |
+| Deliverable Name | ::Description Description Description Description Description | Delivery Date |
+| Deliverable Name | ::Description                                                 | Delivery Date |
+
+### Schedule for this Release
+
+_TODO: Make the rows in this table match the steps in your WBS above. If
+you have a large number of detailed steps, you can skip the most
+detailed ones. The columns of the table represent weeks of calendar
+time. For each cell in the table, enter the number of hours ideal
+engineering time that the team will spend on that task that week. Total
+your hours across and down._
+
+_TIP: These hours should total to the same as the total of the hours
+listed in your [resource needs](Resource-Needs) document. And, the
+hours for each type of effort resources needed should correspond to the
+sum for each type of task._
+
+| Task \ Week     | W-01 | W-02 | W-03 | W-04 | W-05 | W-06 | W-07 | W-08 | W-09 | W-10 | W-11 | W-12 | Task Total |
+| --------------- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---- | ---------- |
+| ::1.            | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::2.            | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::3.            | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::4.1.A.        | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::4.1.B.        | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::4.1.C.        | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::4.1.D.        | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::4.2.          | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::5.            | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::6.            | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+| ::Weekly Totals | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00   | 00         |
+
+### Risk Management
+
+_TODO: List and rank the major risks of this project, and what you plan
+to do to mitigate each risk. If you don't plan to do anything to
+mitigate the risk, state that. Use the risk list below, or the [risks
+worksheet](Risks)._
+
+Please see the [risks worksheet](Risks).
+
+#### The main risks of this project are
+
+1. ::There is a potential conflict between the goals of a high-quality appearance and one that is completely customizable. We can only succeed if players find the web site appealing, and game vendors can customize it with no more effort than would be needed to build a static website. We already have a design in mind that will address this risk and we will review it with a web site designer who worked for a game vendor site.
+2. ::There are significant technical difficulties in building a web site and web application. This will be a risk because one person on our team has much experience with the relevant tools and technologies. Although the others will learn, we will certainly make some mistakes and sub-optimal choices. We will address this risk by scoping the project such that we have enough time to train and to review the design and implementation.
+3. ::The schedule for this project is very short. We will manage this by planning a conservatively scoped functional core and series of functional enhancements that can be individually slipped to later releases if needed.
+4. ::The performance of the system will be significantly impacted by the decisions made during the [database design task](#3.2.C). None of our current team members has experience with database optimization. To address this, we will arrange a review meeting with an experienced DBA or hire a consultant from the database vendor.
+5. ::We could be underestimating known tasks.
+   HOW TO AVOID/MITIGATE?
+6. ::We could be underestimating the impact of unknown tasks.
+   HOW TO AVOID/MITIGATE?
+7. ::We could be underestimating the dependencies between tasks.
+   HOW TO AVOID/MITIGATE?
+8. ::We could have misunderstood the customer's requirements.
+   HOW TO AVOID/MITIGATE?
+9. ::The customer could change the requirements.
+   HOW TO AVOID/MITIGATE?
+10. ::We could face major difficulties with the technology chosen for this project.
+    HOW TO AVOID/MITIGATE?
+11. ::We could have low quality that demands significant rework.
+    HOW TO AVOID/MITIGATE?
+12. ::We could incorrectly assess our progress until it is too late to react.
+    HOW TO AVOID/MITIGATE?
+13. ::We could lose resources. E.g., team members could get sick, spend time on other projects, or quit.
+    HOW TO AVOID/MITIGATE?
+14. ::There may be a mis-alignment of stakeholder goals or expectations.
+    HOW TO AVOID/MITIGATE?
+
+### Project Planning Dependencies
+
+#### Does this project conflict or compete for resources with any other project?
+
+::No, this is the only project that we are working on.
+
+::Yes, and we have determined how many hours each person can actually
+dedicate to this project.
+
+#### Are the same human or machine resources allocated to maintenance of past versions and/or planning of future versions during this release time period?
+
+::No, this is the first release and we will not plan the next release.
+
+::Yes, we predict that team members will spend an average of 20% of
+their time maintaining previous releases and planning future
+releases during this release time frame. Some weeks may be higher if
+an urgent patch to a previous release is needed.
+
+#### Does this project depend on the success of any other project?
+
+::No, this project stands alone.
+
+::Yes, project P1 must provide library L, and project P2 must prove
+the usability of feature F, and....
+
+#### Does any other project depend on this project?
+
+::No, project is not producing any components that will be used in
+other current projects.
+
+::Yes, we must produce library L for our project and support users of
+L in projects P1 and P2.
+
+#### Are there any other important dependencies that will affect this project?
+
+::No, everything is covered above.
+
+::Yes. DETAILS....

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Proposal.md

@@ -0,0 +1,222 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Project Time-frame
+
+::2003/1/16 to 2003/3/19
+
+##### Summary
+
+::2-4 SENTENCE SUMMARY
+
+##### Attached Worksheets
+
+Project Proposal > [Target audience and benefits](Target-and-Benefits)
+
+##### Related Documents
+
+- [Project plan](Project-Plan) > [Resource needs](Resource-Needs)
+- [Glossary](Glossary)
+
+---
+
+**Process impact:** This proposal, along with drafts of related
+documents, will be used by management to determine whether or not to
+approve work on this project. A clear and precise project plan helps set
+expectations that will be used later to evaluate the success of the
+project.
+
+### Background and Motivation
+
+_TODO: Replace the example text below with text that describes your
+project. What are the needs or problems that you are trying to address?
+Why do these needs (still) exist? Why are these problems worth solving?
+Who is the customer? Write 2-4 paragraphs._
+
+#### What is the setting and history behind this project?
+
+::Video games were originally designed and built as stand-alone
+systems with the user playing against the machine. Although many
+advances have been made in game AI, humans still tend to enjoy
+competing against other humans over a network. There is a social
+aspect to network gaming where people form teams that play and
+leagues that play at scheduled times and keep scores over a
+prolonged period. This is important to video game vendors because it
+can result in increased revenue and extend the sales life of
+their products.
+
+#### What is the problem to be addressed?
+
+::There are 100 million users on the Internet, and hundreds of
+websites dedicated to video game playing teams, called "clans". If
+users have to explore to find the good clans that they can join, it
+takes a lot of their time. There is a need for a faster way for
+users to find high quality clan websites that interest them and that
+will allow them to join.
+
+#### What are some current approaches to this problem?
+
+::Users can tell each other about clan websites, but that is not
+scalable because it depends on manual steps by people who may not be
+motivated or honest in their evaluations. There are already some
+clan directory web sites, but they are not automated so they are
+always out of date and do not rate the quality of the websites.
+
+- ::[Example of current manually maintained clan website](#tbd)
+- ::[Link to existing competitor](#tbd)
+
+#### Why is this problem worth solving or worth solving better?
+
+::A better clan directory service would be valuable because it could
+greatly increase player satisfaction and allow them to spend more
+time playing and less time searching. Implementing a better clan
+directory would cause players to use that website rather than the
+existing directories. The benefit to us could come in the form of
+revenue from advertising and service fees from video game vendors.
+
+#### How will this product be better than previous approaches?
+
+::We add innovative new features. Our affiliate directory will be
+larger an more detailed. We will offer built-in tools for managing
+membership and organizing events such as game nights or tournaments.
+
+::Our system will have similar functionality, but it will have much
+better maintainability, scalability, and security.
+
+::Our system will have similar functionality, but it is specifically
+aimed at a market segment that is not served by competing products.
+
+::This is a "me-too" product that will go head-to-head with very
+similar competing products in the same market. The market is large
+enough that we can be very happy with a share of it. Our unique
+competitive advantages are in non-product area of our business such
+as sales, marketing, partnerships, support, training, etc. The
+product will have some simple built-in "hooks" that leverage
+those advantages.
+
+#### Where is there more information on this problem?
+
+::The following pages provide additional background and motivation:
+
+- ::[Magazine article on this topic](#tbd)
+- ::[Industry analysis's report on massive-multi-player game market](#tbd)
+- ::[Quotes from game players](#tbd)
+
+### Goal
+
+#### What is the goal of this project?
+
+::This project will produce an engine for clan directory websites that
+allows players to quickly find, evaluate, and join clans.
+
+#### What are the defining features and benefits of this product?
+
+- ::Reusable website engine with functionality for creating,
+  editing, deleting, searching, categorizing, browsing, rating,
+  and commenting on clans. This automates all clan operations and
+  ensures that users will always find information that is
+  automatically up-to-date.
+- ::The reusable website engine will have a highly configurable
+  appearance that allows it to match the look and feel of the
+  game. This allows the reusable website engine to have a
+  high-quality appearance that is just as good as existing
+  clan directories.
+- ::The website engine will be secure and only allow users with the
+  proper permissions to edit, delete, or join a clan. This will
+  prevent cheating or the submission of false information.
+
+#### Where are other documents that further explain the goal of this project?
+
+- ::[Mock-up](LINK-TO-MOCKUP)
+- ::[Early user stories](LINK-TO-EARLY-STORIES)
+- ::[Quotes from potential customers](LINK-TO-QUOTES)
+- ::[Comparison to existing competitors](LINK-TO-COMPARISON)
+- ::[Draft feature list](LINK-TO-DRAFT-FEATURES)
+
+### Scope
+
+_TODO: Replace the sample text below with a clear statement of the scope
+of your project. What are the high-level things that you plan to do, and
+that you will not do? What are your important simplifying assumptions?
+Try to guard against reasonable misunderstandings that might arise if
+you did not explain the scope. It can take the form of a paragraph,
+bullet list, in/out list, and/or UML context diagram._
+
+::We want to focus on the web application itself, and the features of that
+application that help build a good gaming community.
+
+::See the [context diagram](LINK-TO-CONTEXT-DIAGRAM).
+
+- ::Work with common servers and browsers that we are already
+  familiar with.
+- ::Allow easy customizations of fonts and colors, with the same basic
+  page layout.
+- ::Enough security to greatly discourage abuse
+- ::The web site content discusses a game, but it will not need to
+  actually integrate with any game software
+
+| In Scope                                                                               | Out of Scope                                                                                                                                                                                              |
+| -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| ::Building a web application for use with standard web servers and application servers | ::Building a new web server or application server                                                                                                                                                         |
+| ::Working the most popular browsers (IE6, NN7/Mozilla)                                 | ::Working with uncommon or outdated browsers                                                                                                                                                              |
+| ::Security in the form of user accounts, passwords, and permissions                    | ::Special security against hackers. Finding or patching security holes in existing software components.                                                                                                   |
+| ::One simple sample look-and-feel and instructions for customization                   | ::Our own high-quality look-and-feel. A library of look-and-feel options.                                                                                                                                 |
+| ::Database and server load and data volume that can be handled by one computer.        | ::Managing a cluster of servers.                                                                                                                                                                          |
+| ::Keeping track of which users are in which clans                                      | ::Tracking all user activity on the site and producing custom reports                                                                                                                                     |
+| ::Displaying advertisements to visitors. Billing advertisers for impressions.          | ::Automatically selecting ads that fit the visitor's interests. On-line management of advertising or real-time reporting to advertisers. Participating in existing banner advertising affiliate networks. |
+
+### Deliverables
+
+_TODO: Briefly list project deliverables. When you are done, what will
+you deliver to the customer? This can be copied from the draft project
+plan and simplified to reduce technical detail._
+
+- ::Clan website directory engine
+- ::Customization guide
+- ::Sample look-and-feel
+- ::On-line help for end users
+- ::Command-line advertising configuration tool and report generator
+
+### Risks and Rewards
+
+#### What are the main risks of this project?
+
+1. ::There is a potential conflict between the goals of a
+   high-quality appearance and one that is completely customizable.
+   We can only succeed if players find the web site appealing, and
+   game vendors can customize it with no more effort than would be
+   needed to build a static website. We already have a design in
+   mind that will address this risk and we will review it with a
+   web site designer who worked for a game vendor site.
+
+2. ::There are significant technical difficulties in building a web
+   site and web application. This will be a risk because one person
+   on our team has much experience with the relevant tools
+   and technologies. Although the others will learn, we will
+   certainly make some mistakes and sub-optimal choices. We will
+   address this risk by scoping the project such that we have
+   enough time to train and to review the design
+   and implementation.
+
+3. ::The schedule for this project is very short. We will manage this
+   by planning a conservatively scoped functional core and series
+   of functional enhancements that can be individually slipped to
+   later releases if needed.
+
+#### What are the main rewards if this project succeeds?
+
+::If we accomplish the elements of our plan, our clan directory
+website engine will replace existing clan directory websites and
+generate traffic which will result in advertising revenue and/or
+hosting fees paid by game vendors. Our ability to overcome the
+challenges above will determine time to market, the speed of
+adoption, the amount of web traffic, and thus the generated revenue
+over time.
+
+### Project Plan
+
+See attached draft of [project plan](Project-Plan)
+and [resource needs](Resource-Needs).

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/QA-Plan.md

@@ -0,0 +1,310 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+_TODO: For each release, update this file by filling in answers to the
+questions. In cases where multiple answers are already written, delete
+those answers that do not apply._
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Release Audience
+
+- ::General availability release ||
+- ::Customer-specific release: CUSTOMER(S) ||
+- ::Developer release (Internal usage only) ||
+- ::Early access release (Controlled external access)
+
+##### Attached Worksheets
+
+- QA plan > [Review meeting notes](Review-Meeting-Notes)
+- QA plan > [System test case suite](Test-Suite)
+- QA plan > [System test runs](Test-Run-Suite)
+
+##### Related Documents
+
+- [Software Requirements Specification](SRS)
+- [Design](Design)
+- [Project plan](Project-Plan)
+- [Software development methodology](SDM)
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+
+---
+
+**Process impact:** This document specifies quality goals, selects
+strategies for assuring that those goals have been met, and details a
+plan of action to carry out those strategies.
+
+### Introduction
+
+#### Why is this QA plan needed?
+
+::"Quality" refers to all the good things that we would like to see in
+our product. We build a quality product and assure its quality by
+keeping quality in mind all the time and performing the selected
+activities below. Testing is one QA activity, but it is not the best
+or only one, other QA activities include the use of style guides and
+checklists, review meetings, use of analysis tools, and careful
+quality measurements and estimates. A plan is needed to select and
+coordinate all the QA activities.
+
+#### What QA lessons were learned in previous releases?
+
+::None yet. This is the first release.
+
+- ::Different browsers render the same HTML page differently, so we
+  must test each version of each supported browser.
+- ::In a previous release, customers found that punctuation (e.g.,
+  quotation marks and less-than signs) were entered and processed
+  properly, but not displayed properly. From now on, we must test
+  both validation and display of special characters.
+- ::Large data sets can sometimes make our system fail if the space
+  used for temporary data is used up. Our test plans should
+  include more data volume tests.
+
+#### What is the scope of this QA plan?
+
+::All components and aspects of the system will be evaluated in
+this release.
+
+::There are many quality goals and approaches to assuring them. Since
+we have limited time and resources for this release, we will focus
+on the following components and aspects:
+
+- ::COMPONENT-1
+- ::COMPONENT-2
+- ::COMPONENT-3
+- ::FEATURE-1
+- ::FEATURE-2
+
+#### What is the summary of this plan?
+
+::In this release we will continue to use development practices that
+support all of our quality goals, but we will focus on functional
+correctness and robustness. We will do that with the following major
+activities:
+
+- ::using if-statements to test preconditions and assert statements
+  to test invariants and post-conditions
+- ::conducting frequent reviews
+- ::performing automated unit and regression testing with JUnit
+- ::carrying out structured manual system testing
+- ::keeping all issues up-to-date in an issue tracking database
+
+### Quality Goals for this Release
+
+_TODO: Add or edit goals to fit your project. Group them by priorities
+that make sense for your project on this particular release._
+
+- ::Essential
+  - [Functionality > Correctness](Glossary-Standard-Terms#functionality--correctness)
+  - [Functionality > Robustness](Glossary-Standard-Terms#functionality--robustness)
+- ::Expected
+  - [Functionality > Accuracy](Glossary-Standard-Terms#functionality--accuracy)
+  - [Functionality > Compatibility](Glossary-Standard-Terms#functionality--compatibility)
+  - [Functionality > Factual correctness](Glossary-Standard-Terms#functionality--factual-correctness)
+  - [Usability > Understandability and Readability](Glossary-Standard-Terms#usability--understandability-and-readability)
+  - [Usability > Learnability and Memorability](Glossary-Standard-Terms#usability--learnability-and-memorability)
+  - [Usability > Task support](Glossary-Standard-Terms#usability--task-support)
+  - [Usability > Efficiency](Glossary-Standard-Terms#usability--efficiency)
+  - [Usability > Safety](Glossary-Standard-Terms#usability--safety)
+  - [Usability > Consistency and Familiarity](Glossary-Standard-Terms#usability--consistency-and-familiarity)
+  - [Usability > Subjective satisfaction](Glossary-Standard-Terms#usability--subjective-satisfaction)
+  - [Security](Glossary-Standard-Terms#security)
+- ::Desired
+  - [Reliability > Consistency under load](Glossary-Standard-Terms#reliability--consistency-under-load)
+  - [Reliability > Consistency under concurrency](Glossary-Standard-Terms#reliability--consistency-under-concurrency)
+  - [Reliability > Availability under load](Glossary-Standard-Terms#reliability--availability-under-load)
+  - [Reliability > Longevity](Glossary-Standard-Terms#reliability--longevity)
+  - [Efficiency](Glossary-Standard-Terms#efficiency)
+  - [Scalability](Glossary-Standard-Terms#scalability)
+  - [Scalability > Performance under load](Glossary-Standard-Terms#scalability--performance-under-load)
+  - [Scalability > Large data volume](Glossary-Standard-Terms#scalability--large-data-volume)
+  - [Operability](Glossary-Standard-Terms#operability)
+  - [Maintainability > Understandability](Glossary-Standard-Terms#maintainability--understandability)
+  - [Maintainability > Evolvability](Glossary-Standard-Terms#maintainability--evolvability)
+  - [Maintainability > Testability](Glossary-Standard-Terms#maintainability--testability)
+
+### QA Strategy
+
+_TODO: Consider the activities listed below and delete those that are not
+applicable to your project. Edit and add new activities if needed. For
+each activity, specify the coverage or frequency that you plan to
+achieve. If you do not plan to perform an activity, write "N/A"._
+
+<!-- Hint: view this large table with text wrapping turned off -->
+<!-- markdownlint-disable no-inline-html -->
+| Activity                             | Coverage or Frequency                                                                                                                           | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
+| ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
+| ::Preconditions                      | <ul><li>::Every public method</li><li>::Every public method in COMPONENT-NAME</li><li>::All public methods that modify data</li></ul>           | ::We will use if-statements at the beginning of public methods to validate each argument value. This helps to document assumptions and catch invalid values before they can cause faults.                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ::Assertions                         | <ul><li>::Every private method</li><li>::Every private method in COMPONENT-NAME</li><li>::All private methods that modify data</li></ul>        | ::Assertions will be used to validate all arguments to private methods. Since these methods are only called from our other methods, arguments passed to them should always be valid, unless our code is defective. Assertions will also be used to test class invariants and some postconditions.                                                                                                                                                                                                                                                                                                                                                            |
+| ::Static analysis                    | <ul><li>::Strict compiler warnings</li><li>::Automated style checking</li><li>::XML validation</li><li>Detect common errors</li></ul>           | ::We will use source code analysis tools to automatically detect errors. Style checkers will help make all of our code consistent with our coding standards. XML validation ensures that each XML document conforms to its DTD. Lint-like tools help detect common programming errors. E.g.: [lint](http://www.freebsd.org/cgi/man.cgi?query=lint), [lclint/splint](http://www.splint.org/), [jlint](http://artho.com/jlint/), [checkstyle](http://sourceforge.net/projects/checkstyle/), [Jcsc](http://sourceforge.net/projects/jcsc), [PyLint](https://www.pylint.org/), [PyChecker](http://pychecker.sourceforge.net/), [Tidy](http://www.html-tidy.org/) |
+| ::Buddy review                       | <ul><li>::All changes to release branches</li><li>::All changes to COMPONENT-NAME</li><li>::All changes</li></ul>                               | ::Whenever changes must be made to code on a release branch (e.g., to prepare a maintenance release) the change will be reviewed by another developer before it is committed. The goal is to make sure that fixes do not introduce new defects.                                                                                                                                                                                                                                                                                                                                                                                                              |
+| ::Review meetings                    | <ul><li>::Weekly</li><li>::Once before release</li><li>::Every source file</li></ul>                                                            | ::We will hold review meetings where developers will perform formal inspections of selected code or documents. We choose to spend a small, predetermined amount of time and try to maximize the results by selecting review documents carefully. In the review process we will use and maintain a variety of checklists.                                                                                                                                                                                                                                                                                                                                     |
+| ::Unit testing                       | <ul><li>::100% of public methods, and 75% of statements</li><li>::100% of public methods</li><li>::75% of statements</li></ul>                  | ::We will develop and maintain a unit test suite using the JUnit framework. We will consider the boundary conditions for each argument and test both sides of each boundary. Tests must be run and passed before each commit, and they will also be run by the testing team. Each public method will have at least one test. And, the overall test suite will exercise at least 75% of all executable statements in the system.                                                                                                                                                                                                                              |
+| ::Manual system testing              | <ul><li>::100% of UI screens and fields</li><li>::100% of specified requirements</li></ul>                                                      | ::The QA team will author and maintain a detailed written suite of manual tests to test the entire system through the user interface. This plan will be detailed enough that a person could repeatably carry out the tests from the test suite document and other associated documents.                                                                                                                                                                                                                                                                                                                                                                      |
+| ::Automated system testing           | <ul><li>::100% of UI screens and fields</li><li>::100% of specified requirements</li></ul>                                                      | ::The QA team will use a system test automation tool to author and maintain a suite of test scripts to test the entire system through the user interface.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
+| ::Regression testing                 | <ul><li>::Run all unit tests before each commit</li><li>::Run all unit tests nightly</li><li>::Add new unit test when verifying fixes</li></ul> | ::We will adopt a policy of frequently re-running all automated tests, including those that have previously been successful. This will help catch regressions (bugs that we thought were fixed, but that appear again).                                                                                                                                                                                                                                                                                                                                                                                                                                      |
+| ::Load, stress, and capacity testing | <ul><li>::Simple load testing</li><li>::Detailed analysis of each scalability parameter</li></ul>                                               | ::We use a load testing tool and/or custom scripts to simulate heavy usage of the system. Load will be defined by scalability parameters such as number of concurrent users, number of transactions per second, or number/size of data items stored/processed. We will verify that the system can handle loads within its capacity without crashing, producing incorrect results, mixing up results for distinct users, or corrupting the data. We will verify that when capacity limits are exceeded, the system safely rejects, ignores, or defers requests that it cannot handle.                                                                         |
+| ::Beta testing                       | <ul><li>::4 current customers</li><li>::40 members of our developers network</li><li>::1000 members of the public</li></ul>                     | ::We will involve outsiders in a beta test, or early access, program. We will beta testers directions to focus on specific features of the system. We will actively follow up with beta testers to encourage them to report issues.                                                                                                                                                                                                                                                                                                                                                                                                                          |
+| ::Instrumentation and monitoring     | <ul><li>::Monitor our ASP servers</li><li>::Remotely monitor customer servers</li></ul>                                                         | ::As part of our SLA, we will monitor the behavior of servers to automatically detect service outages or performance degradation. We have policies and procedures in place for failure notification, escalation, and correction.                                                                                                                                                                                                                                                                                                                                                                                                                             |
+| ::Field failure reports              | <ul><li>::Prompt users to report failures</li><li>::Automatically report failures</li></ul>                                                     | ::We want to understand each post-deployment system failure and actively take steps to correct the defect. The system has built-in capabilities for gathering detailed information from each system failure (e.g., error message, stack traceback, operating system version). This information will be transmitted back to us so that we may analyze it and act on it.                                                                                                                                                                                                                                                                                       |
+<!-- markdownlint-enable no-inline-html -->
+
+### QA Strategy Evaluation
+
+_TODO: Use the following table to evaluate how well your QA Strategy will
+assure your QA goals._
+
+| Goal            | Preconditions | Assertions | Buddy review | Review meeting | Unit testing | Manual system testing | Overall assurance |
+| --------------- | ------------- | ---------- | ------------ | -------------- | ------------ | --------------------- | ----------------- |
+| Functionality   | ::Medium      | ::Medium   | ::Medium     | ::High         | ::High       | ::High                | ::Strong          |
+| Correctness     | ::High        | ::High     | ::Medium     | ::Medium       | ::High       | ::Medium              | ::Strong          |
+| Robustness      | ::High        | ::High     | ::Medium     | ::Medium       | ::High       | ::Medium              | ::Strong          |
+| Usability       | ::None        | ::None     | ::None       | ::High         | ::None       | ::Medium              | ::Strong          |
+| Security        | ::Medium      | ::None     | ::Medium     | ::High         | ::None       | ::Medium              | ::Strong          |
+| Reliability     | ::None        | ::Medium   | ::Low        | ::Medium       | ::Medium     | ::Medium              | ::Weak            |
+| Efficiency      | ::None        | ::None     | ::Low        | ::Medium       | ::None       | ::Low                 | ::At-Risk         |
+| Scalability     | ::None        | ::None     | ::Low        | ::Medium       | ::Low        | ::Low                 | ::At-Risk         |
+| Operability     | ::None        | ::None     | ::None       | ::Low          | ::None       | ::Low                 | ::At-Risk         |
+| Maintainability | ::Medium      | ::Low      | ::Medium     | ::High         | ::Low        | ::None                | ::Weak            |
+
+Cell values in the table above are subjective estimates of the
+effectiveness of each activity. This table helps to identify quality
+goals that are not being adequately assured.
+
+#### Evaluation cell values
+
+- High: This activity gives a strong assurance that the goal has been
+  met in development.
+- Medium: This activity gives a medium assurance that the goal has
+  been met in development.
+- Low: This activity gives only a little assurance that the goal has
+  been met in development.
+- None: This activity does not address the goal.
+
+#### Overall assurance values
+
+- Strong: The set of activities together provide strong assurance that
+  the goal has been met in development.
+- Weak: The activities together provide limited assurance that the
+  goal has been met in development.
+- At-Risk: There is little or no assurance that this goal has
+  been met.
+
+Note: As a rule of thumb, it takes at least two "high" activities and
+one "medium" to give a "strong" overall rating. Likewise, it takes at
+least two "medium" and one "low" activities to rate a "weak" overall
+rating.
+
+### Plan of Action
+
+_TODO: Adjust this plan to fit your project._
+
+_TODO: Once the plan is outlined, tasks should be assigned to individuals
+and tracked to completion._
+
+1. Preconditions and Assertions
+
+   - ::Refine requirements document whenever preconditions are not
+     already determined
+   - ::Create validation functions for use by preconditions and
+     assertions, as needed
+   - ::Write preconditions and assertions in code
+
+2. Review meetings
+
+   - ::Assign buddy reviewers whenever a change to a release branch is
+     considered
+   - ::Select an at-risk document or section of code for weekly review
+     meetings
+   - ::Each week, identify reviewers and schedule review meetings
+   - ::Reviewers study the material individually for 2 hours
+   - ::Reviewers meet to inspect the material for 2 hours
+   - ::Place [review meeting notes](Review-Meeting-Notes) in the
+     repository and track any issues identified in review meetings
+
+3. Unit tests
+
+   - ::Set up infrastructure for easy execution of JUnit tests (this is
+     just an Ant target)
+   - ::Create unit tests for each class when the class is created
+   - ::Execute unit tests before each commit. All tests must pass
+     before developer can commit, otherwise open new issue(s) for
+     failed tests. These "smoke tests" will be executed in each
+     developer's normal development environment.
+   - ::Execute unit tests completely on each release candidate to check
+     for regressions. These regression tests will be executed on a
+     dedicated QA machine.
+   - ::Update unit tests whenever requirements change
+
+4. System tests
+
+   - ::Design and specify a detailed manual [test suite](Test-Suite).
+   - ::Review the system test suite to make sure that every UI screen
+     and element is covered
+   - ::Execute system tests completely on each release candidate. These
+     system tests will be carried out on a dedicated QA machine.
+   - ::Update system tests whenever requirements change
+
+5. QA Management
+   - ::Update this test plan whenever requirements change
+   - ::Document test results and communicate them to the entire
+     development team
+   - ::Estimate remaining (not yet detected) defects based on current
+     issue tracking data, defect rates, and metrics on code size and
+     the impact of changes.
+   - ::Keep all issues up-to-date in an issue tracking database. The
+     issue tracker is available to all project members
+     [here](LINK-TO-ISSUE-TRACKER). The meaning of issue states,
+     priorities, and other attributes are defined in the
+     [SDM](SDM#issue-tracking).
+
+### QA-Plan Checklist
+
+#### Do the selected activities in the QA Strategy provide enough assurance that the project will meet it's quality goals?
+
+::Yes, if all activities are carried out as planned, we are confident
+that the quality goals will be satisfied. We will, of course, adjust
+this plan as needed.
+
+::No, this plan leaves open several quality risks that have been noted
+in the [Risk Management](Project-Plan#Risk-Management) section of the
+[Project Plan](Project-Plan).
+
+#### Have human resources been allocated to carry out the QA activities?
+
+::Yes, human resources have been allocated. They are listed in the
+[Resource Needs](Resource-Needs) document.
+
+::No, human resources have not been allocated. They are listed as
+"pending" in the [Resource Needs](Resource-Needs) document.
+
+#### Have machine and software resources been allocated as needed for the QA activities?
+
+::Yes, the QA team will use desktop machines and servers that are
+already allocated to them.
+
+::Yes, a QA Lab has been set up. The needed machine and software
+resources are listed in the [Resource Needs](Resource-Needs) document.
+
+::No, needed machine and software resources are listed as pending in
+the [Resource Needs](Resource-Needs) document.
+
+#### Has this QA Plan been communicated to the development team and other stakeholders?
+
+::Yes, everyone is aware of our prioritized quality goals for this
+release and understands how their work will help achieve
+those goals. Feedback is welcome.
+
+::Yes, this document is being posted to the project website. Feedback
+is welcome.
+
+::No, some developers are not aware of the quality goals and planned
+QA activities for this release. This is a risk that is noted in the
+[Risk Management](Project-Plan#Risk-Management) section of the
+[Project Plan](Project-Plan).

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Release-Checklist.md

@@ -0,0 +1,135 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+_TODO: For each release, copy this file and fill in answers to the
+questions. In cases where multiple answers are already written, delete
+those answers that do not apply._
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### External release number
+
+::X.Y.Z
+
+##### Release audience
+
+- ::General availability release
+- ::Customer-specific release: CUSTOMER(S)
+- ::Developer release (Internal usage only)
+- ::Early access release (Controlled external access)
+
+---
+
+**Process impact:** The process of working through this checklist helps
+uncover any remaining concerns before the release, and reminds internal
+stakeholders of their upcoming responsibilities. Once this checklist has
+been satisfied, this release may be sent to manufacturing and sold to
+customers with the full support of the organization.
+
+_TODO: Discuss each item with the relevant stakeholders and update its
+status. Add comments as needed to record important decisions or link to
+resulting documents. Add new items as needed for your particular project
+or process. Any uncovered problems or tasks should be tracked in the
+issue tracker._
+
+### Marketing / Product Management
+
+| Item                                                                     | Status  | Comments |
+| ------------------------------------------------------------------------ | ------- | -------- |
+| ::All new requirements for this release have been tracked                | Pending |          |
+| ::All prior defects needing resolution in this release have been tracked | Pending |          |
+| ::All marketing documents have been updated                              | Pending |          |
+| ::Marketing / Product Management is satisfied with this release          | Pending |          |
+
+### Development
+
+| Item                                                   | Status  | Comments |
+| ------------------------------------------------------ | ------- | -------- |
+| ::All needed design work has been completed            | Pending |          |
+| ::All needed design work has been reviewed             | Pending |          |
+| ::All development work has been completed              | Pending |          |
+| ::All development work has been reviewed               | Pending |          |
+| ::All defects assigned to this release have been fixed | Pending |          |
+| ::All development documentation has been updated       | Pending |          |
+| ::All unit test code has been updated                  | Pending |          |
+| ::The development team is satisfied with this release  | Pending |          |
+
+### Quality Assurance {#quality-assurance}
+
+| Item                                            | Status  | Comments |
+| ----------------------------------------------- | ------- | -------- |
+| ::The QA plan and test cases have been updated  | Pending |          |
+| ::The QA plan has been completely carried out   | Pending |          |
+| ::All discovered defects have been tracked      | Pending |          |
+| ::All fixed defects have been verified as fixed | Pending |          |
+| ::The QA team is satisfied with this release    | Pending |          |
+
+### Release Engineering / Configuration Management
+
+| Item                                                                                                                 | Status  | Comments |
+| -------------------------------------------------------------------------------------------------------------------- | ------- | -------- |
+| ::All components have been properly tagged for release, and the release configuration is clearly defined             | Pending |          |
+| ::Change-control practices have been followed, meaning that the released product does not contain unapproved changes | Pending |          |
+| ::The RelEng team is satisfied with this release                                                                     | Pending |          |
+
+### User Experience
+
+| Item                                                      | Status  | Comments |
+| --------------------------------------------------------- | ------- | -------- |
+| ::Any new or changed functionality is deemed usable       | Pending |          |
+| ::On-line and printed user documentation has been updated | Pending |          |
+| ::The UE team is satisfied with this release              | Pending |          |
+
+### Technical Support / Operations
+
+| Item                                                                                                         | Status  | Comments |
+| ------------------------------------------------------------------------------------------------------------ | ------- | -------- |
+| ::Theory of operations document has been updated                                                             | Pending |          |
+| ::Tech support / Operations has successfully installed, upgraded, and used this release                      | Pending |          |
+| ::Any "Early access" or "Beta" program was conducted successfully and all resulting issues have been tracked | Pending |          |
+| ::The impact of any changes on operations offerings has been identified and tracked                          | Pending |          |
+| ::Troubleshooting guide has been updated                                                                     | Pending |          |
+| ::The tech support / operations teams are satisfied with this release                                        | Pending |          |
+
+### Services / Training
+
+| Item                                                                             | Status  | Comments |
+| -------------------------------------------------------------------------------- | ------- | -------- |
+| ::Services / Training has had access to this release                             | Pending |          |
+| ::The impact of any changes on service offerings has been identified and tracked | Pending |          |
+| ::Training materials have been updated                                           | Pending |          |
+| ::Services / Training is satisfied with this release                             | Pending |          |
+
+### Legal
+
+| Item                                                                          | Status  | Comments |
+| ----------------------------------------------------------------------------- | ------- | -------- |
+| ::Legal risks associated with this release have been identified and tracked   | Pending |          |
+| ::We hold proper licenses for all reused components and intellectual property | Pending |          |
+| ::We conform to all relevant laws and regulations (e.g., export, safety)      | Pending |          |
+| ::The legal team is satisfied with this release                               | Pending |          |
+
+#### Possible status values
+
+- Pending: Work still needs to be done
+- N/A: This item cannot logically apply
+- Waived: This item could apply, but the stakeholders deem it
+  unimportant
+- Done: The stakeholders agree that the item has been satisfied
+- Failed: This item has forced us to abandon this release
+
+_TIP: If a stakeholder hits difficulties with this release after it goes
+out, add those issues to the checklist template so that everyone knows
+that they will be explicitly managed on the next release. Conduct a
+postmortem review to help expose difficulties rather than repeat them._
+
+_TIP: You might consider some of the following additional stakeholders at
+your organization: Other engineering groups (i.e., hardware design),
+Manufacturing and Shipping, Software Process Improvement, Key customers
+and partners, External developers, Risk Management, Business
+Development, and Upper Management._

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Release-Notes.md

@@ -0,0 +1,176 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+_TODO: For each release, copy this file and fill in the needed
+information._
+
+_TODO: Make sure to use the **product** name and **external** release
+number, not internal information._
+
+##### Product
+
+::[PRODUCT-NAME](http://www.COMPANY.com/products/PRODUCT-NAME/)
+
+##### Release Number
+
+::X.Y.Z
+
+##### Release Date
+
+::YEAR/MONTH/DAY
+
+##### Customer Support
+
+::For more information or support, please visit our
+[website](http://www.COMPANY.com/products/PRODUCT-NAME/) or email us
+at <support@COMPANY.com>
+
+---
+
+### Introduction
+
+::This document contains the release notes for PRODUCT-NAME version X.Y.Z.
+The following sections describe the release in detail and provide
+late-breaking or other information that supplements the main
+documentation.
+
+_TODO: Consider using one of the following example paragraphs._
+
+::This is a developer release for internal evaluation only. Please report
+any issues via the internal issue tracker.
+
+::This is an early access release for evaluation and usage by select
+partners. Your feedback is important to us, please help us make this the
+best product possible.
+
+::This is an early access release for wide evaluation and usage. Your
+feedback is important to us, please help us make this the best product
+possible. Keep in mind that we are continuing to work on PRODUCT-NAME and
+things may change in the future.
+
+::This is the first full release of this product. See the product website
+for a complete description.
+
+::(WHEN X IN VERSION NUMBER CHANGES) This is a major release with many new
+features. Users of previous releases should check the "Version
+Compatibility" section below for instructions on how to use existing
+data with this new release.
+
+::(WHEN Y IN VERSION NUMBER CHANGES) This is an upgrade release with some
+significant enhancements. Users of previous releases are encouraged to
+upgrade.
+
+::(WHEN Z IN VERSION NUMBER CHANGES) This is a maintenance release that
+improves quality, reliability, and performance without adding any new
+functionality. All users of previous X.Y releases should upgrade to this
+release.
+
+::(WHEN DEFECT CORRECTION CLOSES SIGNIFICANT SECURITY HOLES) This is a
+critical upgrade release that addresses recently discovered security
+holes. All users of previous X.Y releases should upgrade immediately to
+this release.
+
+### What's New?
+
+_TODO: Briefly list major user-visible enhancements. Or, note that
+nothing major has been added. Technical issues should only be mentioned
+if this is a reusable software component that will be used to build
+larger products. Do not include issue numbers. Links to detailed
+information can be helpful._
+
+- ::Added 4 new play-back modes
+- ::Increased play-back speed by as much as 30%
+- ::(FOR REUSABLE COMPONENTS ONLY) Streamlined build process
+- ::(FOR REUSABLE COMPONENTS ONLY) Roughly doubled unit test coverage
+- ::Many improvements to the product's quality, reliability, ease of
+  use, and performance. See "Recent Changes" below for details.
+
+### Installation and Upgrade Notes
+
+_TODO: Fill in these sections. The text here is only an example._
+
+#### ::Installation
+
+::See the [installation instructions](Installation-Guide) for full details.
+Please note that in this release, ...
+
+::IMPORTANT: You must completely uninstall any previous "developer
+release" or "early access" version of this product before installing
+this release.
+
+#### ::Manifest
+
+::This release consists of the following items:
+
+- ::Release notes (this file)
+- ::Installation instructions / Quick start guide
+- ::Product installer binary
+- ::User guide
+- ::Product source code and build instructions
+
+### ::Minimum System Requirements
+
+#### ::System Processor
+
+::800MHz
+
+#### ::System Memory
+
+::256MB
+
+#### ::Free Disk Space
+
+::10MB
+
+#### ::Operating System
+
+::Windows 2000, Windows XP, Mac OS X, Linux (kernel 2.4)
+
+#### ::Networking
+
+::Internet access
+
+#### ::Existing Software
+
+- ::Standard e-mail client
+- ::Popular web browser (IE6, NN7)
+- ::SuperWaveEdit(TM) 2.0.2 (Needed for custom playback modes)
+
+#### ::Version Compatibility
+
+::Files saved by earlier versions of this product may be used with
+this version. However, wave files saved in version W.Y.Z, must be
+updated by using the WaveUpgrade utility.
+
+### Recent Changes
+
+_TODO: Query your public issue tracking system to produce a report of
+changes in this release. Include the issue number, type, and one-line
+summary. Include issues that were highlighted in the "What's New?"
+section above. You may revise one-line summaries in the issue tracker,
+prior to generating the report, if you notice that they are incorrect.
+You may exclude or summarize changes that might give away valuable
+proprietary information._
+
+- ::FIX [09823](#tbd) Screen frozen when caps-lock is on
+- ::FIX [09912](#tbd) Static heard while downloading
+- ::FIX [10923](#tbd) Repeat-mode cannot play more than 99 times
+- ::ENHANCEMENT [08237](#tbd) Scratch DJ-mode
+- ::ENHANCEMENT [08238](#tbd) Chill DJ-mode
+- ::ENHANCEMENT [08259](#tbd) Retro stereo-mode
+- ::ENHANCEMENT [10202](#tbd) Techno-mode
+
+### Known Problems and Workarounds
+
+_TODO: Query your public issue tracking system to produce a report of
+defects discovered in this release, or in previous releases that are
+still not resolved. Include information on workarounds from the issues.
+Otherwise, same as above._
+
+- ::DEFECT [07293](#tbd) Player skips on very loud playback.
+  - ::WORKAROUND: Limit volume to settings 1 through 9.
+- ::DEFECT [10509](#tbd) Cannot switch directly from random play mode to
+  Internet play-list.
+  - ::WORKAROUND: Switch to local play-list first. Click [here](#tbd) for
+    detailed instructions.
+- ::DEFECT [10589](#tbd) Static heard while booting
+- ::DEFECT [10944](#tbd) Repeat-mode cannot play more than 999 times

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Resource-Needs.md

@@ -0,0 +1,300 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Project Time-frame
+
+::START-DATE - END-DATE
+
+##### Related Documents
+
+- [Project proposal](Proposal)
+- [Project plan](Project-Plan)
+- [QA plan](QA-Plan)
+- [Software development methodology](SDM)
+- [Glossary](Glossary)
+
+---
+
+**Process impact:** Based on the project plan and the worksheet below,
+this project will need the following resources to meet its goals. If
+fewer resources are available, the scope of the release should be
+reconsidered or the process must be changed.
+
+_TODO: Fill in the information above and below. Add or remove rows as
+needed. Use the worksheet to help identify and scope resource needs.
+These rows are just examples. The total effort listed in this example
+may not even match the totals given in other examples of related
+documents._
+
+### Human Resource Needs
+
+| Need                                      | Resource                                | Amount     | Status     | Comments/Responsibilities |
+| ----------------------------------------- | --------------------------------------- | ---------- | ---------- | ------------------------- |
+| ::Project Management                      | ::PERSON-NAME                           | ::20 hours | ::Pending  |                           |
+| ::Requirements                            | ::PERSON-NAME                           | ::20 hours | ::Assigned |                           |
+| ::Requirements                            | ::PERSON-NAME, PERSON-NAME, PERSON-NAME | ::10 hours | ::Assigned |                           |
+| ::Consultation with domain expert         | ::PERSON-NAME                           | ::2 hours  | ::Pending  |                           |
+| ::Consultation with topic expert          | ::PERSON-NAME                           | ::4 hours  | ::Pending  |                           |
+| ::Training on use of component/technology | ::PERSON-NAME                           | ::8 hours  | ::Assigned |                           |
+| ::Overall Design                          | ::PERSON-NAME, PERSON-NAME, PERSON-NAME | ::20 hours | ::Assigned |                           |
+| ::Detailed UI Design                      | ::PERSON-NAME                           | ::5 hours  | ::Pending  |                           |
+| ::Detailed Database Design                | ::PERSON-NAME                           | ::5 hours  | ::Pending  |                           |
+| ::Development                             | ::PERSON-NAME, PERSON-NAME, PERSON-NAME | ::40 hours | ::Assigned |                           |
+| ::Development                             | ::PERSON-NAME, PERSON-NAME              | ::80 hours | ::Assigned |                           |
+| ::Development                             | ::PERSON-NAME                           | ::20 hours | ::Pending  |                           |
+| ::Technical writing                       | ::PERSON-NAME, PERSON-NAME              | ::10 hours | ::Assigned |                           |
+| ::QA Planning                             | ::PERSON-NAME                           | ::10 hours | ::Assigned |                           |
+| ::QA Testing                              | ::PERSON-NAME, PERSON-NAME, PERSON-NAME | ::40 hours | ::Assigned |                           |
+| ::Release Engineering                     | ::PERSON-NAME                           | ::4 hours  | ::Assigned |                           |
+
+### Capital Needs
+
+| Need                               | Resource                                              | Amount    | Status                    | Comments                                                                        |
+| ---------------------------------- | ----------------------------------------------------- | --------- | ------------------------- | ------------------------------------------------------------------------------- |
+| ::Training materials               | ::Book/Course on specific technology                  | ::1       | ::Allocated               | ::Book ordered                                                                  |
+| ::Development Workstations         | ::800MHz PC, 256MB RAM                                | ::4       | ::Satisfied               | ::Dev group will use existing workstations                                      |
+| ::Development DB Server            | ::Dual CPU 1GHz PC, 512MB RAM: SERVERNAME.company.com | ::1       | ::Allocated               |                                                                                 |
+| ::Interactive Testing Workstations | ::800MHz PC, 256MB RAM                                | ::2       | ::Allocated               |                                                                                 |
+| ::Load Test Server                 | ::800MHz PC, 256MB RAM: SERVERNAME.company.com        | ::1       | ::Pending                 |                                                                                 |
+| ::Load Test Clients                | ::500MHz PC or Mac, 128MB RAM                         | ::4       | ::Satisfied               | ::QA group will use existing machines                                           |
+| ::Automated Testing Slave          | ::800MHz PC, 256MB RAM: SERVERNAME.company.com        | ::1       | ::Satisfied               | ::QA group will use existing machine                                            |
+| ::Testing DB Server                | ::Dual CPU 1GHz PC, 512MB RAM: SERVERNAME.company.com | ::1       | ::Rejected                | ::Testing group will use development DB server and do load testing in off hours |
+| ::IDE Licenses                     | ::Standard development licenses                       | ::N/A     | ::Satisfied               | ::Will use open source tools                                                    |
+| ::SCM Licenses                     | ::Standard development licenses                       | ::N/A     | ::Satisfied               | ::Will use open source tools                                                    |
+| ::Testing Tool Licenses            | ::Standard development licenses                       | ::N/A     | ::Satisfied               | ::Will use open source tools                                                    |
+| ::DB Licenses                      | ::Standard development licenses                       | ::6       | ::Pending                 |                                                                                 |
+| ::DB Licenses                      | ::Production licenses                                 | ::4 CPU's | ::2 Pending; ::2 Rejected | ::Testing group will use development DB server and do load testing in off hours |
+| ::Software component               | ::GIS Library w/ source code                          | ::1       | ::Pending                 | ::One time fee, approx. $10,000                                                 |
+| ::Software component               | ::Encryption library                                  | ::1       | ::Pending                 | ::Revenue sharing at 2%                                                         |
+
+#### Possible Status Values
+
+- Pending: request is awaiting management decision
+- Assigned: task has been assigned to a person in the issue tracker
+- Allocated: capital request approved by management, but resource has
+  not arrived
+- Satisfied: request is satisfied, resource has arrived
+- Rejected: requested resource will not be allocated, plan must be
+  adjusted to work without this resource
+
+### Resource Needs Checklist
+
+The goal of this checklist is to help expose resource needs that might
+otherwise be missed. It does not help with the actual estimated number
+of hours needed. Those estimates should be based on the project plan.
+
+_TODO: Answer the questions below. If multiple sample answers are
+provided, [chip away](Glossary-Standard-Terms#chipping-away) the ones that do
+not apply. Edit any provided answers as needed. Use this exercise to
+help you fill in the tables above._
+
+#### Does this project need more than a few days work?
+
+:: Yes. A project manager role is needed to oversee the project.
+
+:: No. The developers can manage their own work.
+
+#### Are the requirements already completely defined and validated?
+
+:: Yes. No additional time is needed for requirements.
+
+:: No. Effort is needed for requirements.
+
+#### What aspects of the system need to be designed?
+
+:: General design. Group developer effort needed.
+
+:: User interface. UI designer and domain experts effort needed.
+
+:: Database design. Developer and DBA effort needed.
+
+:: Security design. Developer and topic expert effort needed.
+
+:: Other design. Developer, domain, and/or topic expert effort needed.
+
+#### Does the project plan include any new development?
+
+:: Yes. Development resources are needed.
+
+:: No. No developers are needed
+
+#### Does the project plan include complex configuration of existing components?
+
+:: Yes. Component expert needed. Also need time to coordinate with
+development and operations teams.
+
+:: No. No component experts are needed
+
+#### Does the development team have knowledge of all tools, components, and technologies to be used?
+
+:: Yes. No training time needed.
+
+:: No. Effort needed for training. Need training materials, courses, or
+time with experts or mentors. List specific training
+needs individually.
+
+#### Is the entire development team have an agreed upon software development methodology?
+
+:: Yes. No effort needed for defining a methodology.
+
+:: Yes. But, effort is needed to refine the methodology to the project
+at hand.
+
+:: No. Effort needed to define and document a methodology and train all
+team members. Additional effort needed for refinements throughout
+the project.
+
+#### Does the project plan include end-user documentation?
+
+:: Yes. Technical writing resources must be allocated.
+
+:: No.
+
+#### What is the complexity of the internal documentation?
+
+:: Significant. Technical writing resources must be allocated.
+
+:: Average. Developers can produce technical documents as they go.
+
+#### Will the technical support, training, operations, or services groups deal with the product of this project?
+
+:: Yes. Effort must be allocated to train the staff in those groups.
+
+:: No, but other developers will need training to reuse this component.
+
+:: No. Effort put into producing good technical documentation should
+be enough.
+
+#### Will the product of this project be sold to customers, directly or indirectly?
+
+:: Yes. The full SDM must be followed, including effort by a change
+control board and release engineering.
+
+:: No, it is for internal use only but it will be used repeatedly to
+help build a shipping product. Release engineering and CCB effort is
+still needed.
+
+:: No, it is for internal use only and will only be used once. Release
+engineering and CCB effort not needed.
+
+#### Does the QA plan call for the running of automated unit tests?
+
+:: Yes. Development effort will be needed to implement unit tests.
+
+:: No. Additional QA effort will be needed for manual testing.
+
+#### Does the QA plan call for more than the running of automated unit tests?
+
+:: Yes. QA effort will be needed.
+
+:: No. Unit tests will be enough for this component, full QA can be
+done on products that use this component.
+
+#### How many development workstations will be needed?
+
+:: 1 per developer.
+
+:: 1 per developer, plus extra for...
+
+#### What development servers are needed?
+
+:: None.
+
+:: One for the whole team.
+
+:: One for the one aspect of development, another for another aspect.
+
+:: One for the one branch of development, another for another branch.
+
+#### What database servers are needed?
+
+:: None. No database is being used.
+
+:: None. Database is integrated into product and does not require a
+separate server.
+
+:: One for the whole team.
+
+:: One for the developers, one for QA.
+
+:: One for one branch of development, another for another branch.
+
+:: One for the developers, one for QA, one for load testing.
+
+:: One for each developer or tester, plus one for load testing.
+
+#### What machines are needed for automated testing?
+
+:: None. Automated testing will not be done.
+
+:: None. Automated testing will be done on workstations.
+
+:: One for all nightly automated tests.
+
+:: One for one aspect of nightly automated tests, another for
+another aspect.
+
+:: One for one branch of development, another for another branch.
+
+#### What machines are needed for load testing?
+
+:: None. Load testing will not be done.
+
+:: None. Load testing will be done on workstations.
+
+:: One machine will do all load testing.
+
+:: Several machines needed to act as clients and servers.
+
+:: One cluster of load testing machines for each branch of development.
+
+#### What development tools must be licensed for this project?
+
+:: None. Everything is implemented by us.
+
+:: None. All development tools are open source.
+
+:: Some tools: IDE, database, testing tools. These tools have already
+been purchased, installed, and configured.
+
+:: Some tools: IDE, database, testing tools. Budget must be allocated
+to purchase these tools. Effort must be allocated to research and
+select tools for purchase, install, and configure them.
+
+#### What software components must be licensed for this project?
+
+:: None. Everything is implemented by us.
+
+:: None. All reused components are open source.
+
+:: Some components: database, server software, libraries. These
+components have already been selected, purchased, installed,
+and configured.
+
+:: Some components: database, server software, libraries. Effort must
+be allocated to research, select, install and configure
+these components. Budget must be allocated to purchase them.
+
+#### Are any of the personnel assignments of capital allocations conditional?
+
+:: Yes. All such conditions are written in the comments column above.
+We have a contingency plan that will still achieve (an
+acceptable subset) of the project goals.
+
+:: No. Management has set aside these resources as promised, and the
+needs of this project will take priority over any other project that
+is likely to need the same resources.
+
+#### Have these resource assignments been communicated to the people being assigned and their managers?
+
+:: Yes, everyone understands. Feedback is welcome.
+
+:: No, this is a risk that is noted in the [Risk
+Management](Project-Plan#Risk-Management) section.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Review-Meeting-Checklists.md

@@ -0,0 +1,21 @@
+# Review Meeting Checklists
+
+---
+
+## Checklists for Types of Artifacts
+
+- ::[Checklists for peer reviews](http://processimpact.com/pr_goodies.shtml)
+  by Karl E. Wiegers
+- ::[Checklists for UML design](http://www.modelingstyle.info/)
+  by Scott W. Ambler
+
+## Style Guides
+
+- ::[Sun's java style guide](http://java.sun.com/docs/codeconv/html/CodeConvTOC.doc.html)
+- ::[Sun's javadoc guide](http://java.sun.com/j2se/javadoc/writingdoccomments/)
+- ::[PHPBuilder.com's PHP style guide](http://www.phpbuilder.com/columns/tim20010101.php3)
+- ::[Alltasks.net PHP style guide](http://alltasks.net/code/php_coding_standard.html)
+- ::[C\# style guide](https://docs.microsoft.com/en-us/dotnet/csharp/programming-guide/inside-a-program/coding-conventions)
+- ::[More C++ style guides](http://directory.google.com/Top/Computers/Programming/Languages/C%2B%2B/Style/)
+- ::[More Java style guides](http://directory.google.com/Top/Computers/Programming/Languages/Java/Coding_Standards/)
+- ::[Python PEP 8 style guide](https://www.python.org/dev/peps/pep-0008/)

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Review-Meeting-Notes.md

@@ -0,0 +1,69 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Release Number
+
+::X.Y.Z
+
+##### Location of Meeting
+
+::LOCATION, BUILDING, ROOM
+
+##### Date and Time of Meeting
+
+::YEAR/MONTH/DAY HH:MM
+
+##### Attendees
+
+- ::PERSON-NAME
+- ::PERSON-NAME
+- ::PERSON-NAME
+- ::PERSON-NAME
+
+##### Related Documents
+
+- [QA Plan](QA-Plan) > Review Meeting Notes
+- [Review Meeting Checklists](Review-Meeting-Checklists)
+
+---
+
+### Documents and Code Reviewed at this Meeting
+
+- ::[Feature list section of requirements](#tbd)
+- ::[Multi-user section of requirements](#tbd)
+- ::[Hello.java](/source/browse/PROJECT-NAME/src/Hello.java)
+- ::[HelloStream.java](/source/browse/PROJECT-NAME/src/HelloStream.java)
+- ::[HelloPanel.java](/source/browse/PROJECT-NAME/src/HelloPanel.java)
+
+### Meeting Minutes
+
+_TODO: Fill in the information above and write a brief summary of what
+happened at the meeting. The text below is just a sample._
+
+::We started on time with 3 members and the other team members arrived
+shortly thereafter.
+
+::In the first hour of the review meeting, we went over issues that the
+team had entered individually. Most of the issues raised questions about
+the error handling capability of Hello.java, but there were also issues
+about multi-user robustness requirements and UI.
+
+::In the second hour, we read through all of the methods of
+HelloStream.java. All team members agreed that they understood each
+method and thought is was correct before we moved on to the next method.
+We raised issues of consistency between the constructors in that class
+and other classes. The checklist was helpful in identifying the fact
+that we needed to implement hash() and equals(). All raised issues were
+entered into the issue tracker and marked with the word "review".
+
+::Although, some issues were found, we do not feel that Hello.java and
+HelloStream.java need to be inspected again. HelloPanel was not
+inspected, it still needs review.
+
+### Action Items
+
+::All defects and tasks identified in this review are being tracked in the
+issue tracker.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Risks.md

@@ -0,0 +1,177 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Related Documents
+
+- [Project plan](Project-Plan)
+- [Software development methodology](SDM)
+
+##### References
+
+- [Risk Management during Requirements](http://www.systemsguild.com/pdfs/s5req.lo%201.pdf) by Tom DeMarco and Tim Lister
+- [Taxonomy-Based Risk Identification](http://www.sei.cmu.edu/pub/documents/93.reports/pdf/tr06.93.pdf) by Carr, Konda, Monarch, Ulrich, and Walker (SEI)
+
+---
+
+**Process impact:** This document records the major project risks, and
+plans to control them. For each risk the plan should include:
+
+- Mitigation plan
+  - Measures you will carry out now, to reduce the likelihood and/or
+    impact of the risk. Alternatively, you can decide to accept
+    the risk.
+- Indicator
+  - A sign you will monitor to determine if the risk is beginning to
+    have an impact on the project.
+- Contingency plan
+  - What you will do if the risk does arise. You can specify some
+    general contingency plans. In this case you only need to give a
+    contingency plan if you have a special one for the particular risk.
+
+The severity of a risk is its likelihood multiplied by its impact. Risks
+are classified as minor if they have low likelihood, negligible impact,
+or medium likelihood and marginal impact.
+
+_TODO: You should update these lists regularly. They should be reviewed
+by customers and developers from time to time._
+
+### General contingency plans
+
+#### Catastrophic risks
+
+::If a catastrophic risk occurs we will make an honest reassessment of
+the viability of the project and involve the relevant
+project stakeholders.
+
+::If a catastrophic risk occurs we will cancel the project. We will
+take away our lessons learned and any valuable project bi-products.
+
+::We do not recognize any catastrophic risks. If one occurs we will
+pretend everything is fine and hope that none of the
+stakeholders notice.
+
+#### Risks that consume development resources
+
+::The project has a fixed deadline. The requirements are prioritized.
+If we lose time, we will reduce project scope.
+
+::The features specified are all essential If we lose time, we will
+delay delivery.
+
+::If we lose time, we will make time estimates for the remaining
+features, and meet with the customers to reconsider scope and
+delivery date.
+
+#### ::OTHER RISK TYPE
+
+::OTHER CONTINGENCY PLAN
+
+### Major risks
+
+| Name            | Description                                                                                                                     | Likelihood | Impact                   | Plan                                                                                                                                                                       | Status | Owner             |
+| --------------- | ------------------------------------------------------------------------------------------------------------------------------- | ---------- | ------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------ | ----------------- |
+| ::Requirements  | Requirements are only partly known at project start. Customers may not allocate sufficient resources to exploring requirements. | Medium     | Critical to Catastrophic | Requirements will be detailed first for the top priority goals. Indicator: Track the rate at which requirements are discovered. Contingency: request more customer effort. | Amber  | Requirements Lead |
+| ::Goals         | Stakeholders goals may conflict.                                                                                                | Medium     | Critical                 | Keep an explicit list of stakeholders goals. The project manager will report progress to each declared goal.                                                               | Green  | Customers         |
+| ::Communication | Communication problems in development team. They are dispersed among several sites, and have not worked together before.        | Medium     | Critical                 | Use these [tools](SDM#communication) to help communication. The main indicator of miscommunication will be software defects detected by our [QA activity](qa-plan).        | Green  | QA lead           |
+| ::Acceptance    | Customer may accept delivery of the system although it does not really meet their goals.                                        | Medium     | Critical                 | Customers are asked to declare acceptance criteria as each release is planned.                                                                                             | Green  | Customers         |
+| ::Scope         | The total features requested may be beyond what the development team can deliver in the time available.                         | High       | Marginal                 | Assign levels of important to the use cases. Make the first review of project scope after 12 months.                                                                       | Green  | Customers         |
+
+### Minor risks
+
+_TODO: Review this list regularly, to decide whether the likelihood or
+impact of a risk has increased to make it a "major" risk._
+
+| Name              | Description                                                                                                                                                                                  | Likelihood            | Impact                                             | Mitigation Strategy                                                                                                                                                                                                                                                                                    | Status                | Owner           |
+| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | -------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------- | --------------- |
+| ::Estimate        | The development team might not be able to estimate the work time, preventing customers from deciding priorities effectively.                                                                 | Medium                | Marginal                                           | The development team will gain experience in estimating the work, and deliver the first estimates after 12 months. We will compare estimated work to actual work.                                                                                                                                      | Green                 | Project Manager |
+| ::Retention       | Some developers may leave the project before it is finished.                                                                                                                                 | Medium                | Marginal                                           | Employing locations should provide support for continuing professional development. The project manager will discuss career goals with each developer, and try to assign tasks appropriately.                                                                                                          | Green                 | Project Manager |
+| ::Correctness     | The system as delivered may have low take-up because of a lack of confidence in its correctness.                                                                                             | Low                   | Catastrophic                                       | State of the art [QA activity](QA-Plan). Contingency: stop development of new facilities until the quality of the existing code is assured.                                                                                                                                                            | Green                 | QA Lead         |
+| ::Usability       | The system as delivered may have low take-up because of poor usability.                                                                                                                      | Low                   | Critical                                           | We will have a UI style guide. Most of the development of the front end will be in close contact with customers. We will review usability later in the project.                                                                                                                                        | Green                 | UI design lead  |
+| ::Desire          | The stated requirements might not match the customers' desires and ambitions for the system.                                                                                                 | Low                   | Critical                                           | Incremental delivery of versions will provide experience of using the system, which will help the customers to identify the real requirements. Indicator: a developer saying "I think they mean ...", a customer saying "They know what I mean". Contingency: request customer review of requirements. | Green                 | Customers       |
+| ::Changes         | After requirements have been documented and agreed, development activities begin to based on them, first design then implementation. If the requirements change later then effort is wasted. | Low                   | Critical                                           | A change control procedure is required, so changes are only made when the cost is worthwhile. Indicator: compare cost of change to new development. Contingency: request customer review of requirements.                                                                                              | Green                 | Project Manager |
+| ::Process         | Some developers may not cooperate in common standards and processes.                                                                                                                         | Low                   | Critical                                           | QA to check conformance, then discussions in development team meetings to change the standard or the actual practice as appropriate.                                                                                                                                                                   | Green                 | QA Lead         |
+| ::Maintainability | The system as delivered might be hard to maintain.                                                                                                                                           | Low                   | Marginal                                           | We will review the code for maintainability.                                                                                                                                                                                                                                                           | Green                 | Lead Developer  |
+| ::RISK-NAME       | ONE-TO-THREE-SENTENCES                                                                                                                                                                       | Low or Medium or High | Negligible or Marginal or Critical or Catastrophic | ONE-TO-THREE-SENTENCES                                                                                                                                                                                                                                                                                 | Red or Amber or Green | PERSON-NAME     |
+
+#### Possible risk status values
+
+##### Red
+
+Active & impacting project
+
+##### Amber
+
+Active but contained without impact to scope or delivery time.
+
+##### Green
+
+Not yet active
+
+### Risk Checklist
+
+#### Do the plans provide an indicator to detect each of the risks becoming active?
+
+::Yes, if all activities are carried out as planned, we will know if any
+of the risks is becoming troublesome.
+
+::No, some risks could creep up on us.
+
+#### Are the right "risk owners" assigned to monitor the risks?
+
+::Yes, for each risk the assigned owner can detect the indicator, can
+launch the contingency plan, and is the person who will suffer by
+the risk.
+
+::No, in some cases the assigned owner may not notice or care, or does
+not have sufficient authority.
+
+#### Does each risk have a mitigation strategy, or is the risk acceptable?
+
+::Yes, we have plans to control each risk.
+
+::Yes, we have plans to control some risks, and have accepted others.
+
+::No, this plan leaves open several risks.
+
+#### Does each risk have a contingency plan?
+
+::Yes, most risks cost development time and the general plan applies,
+and for each of the others there is a contingency plan above.
+
+::No, there are some risks we still have to plan for.
+
+#### Has this Risk Control Plan been communicated to the development team and other stakeholders?
+
+::Yes, this document is being posted to the project website. It will
+also be discussed at an early team meeting, and discussed with the
+customers before the commit to the project. Comments are welcome.
+
+::No, our culture does not allow discussion of risks.
+
+#### Is there a procedure in place for identifying new risks and reviewing the existing ones?
+
+::TBD
+
+#### In the light of these risks, is the project worth carrying out?
+
+::Yes, it is a low risk project
+
+::No, other projects can deliver as much value at lower risk.
+
+::Yes. It is an unusually risky project by commercial standards, but
+we believe we have adequate plans here, considering the value that
+the project could deliver.
+
+#### Is there an anonymous reporting channel, to allow developers to communicate concerns to senior management?
+
+::Yes
+RISKNAME
+RISKNAME and strength of character of
+RISKNAME
+RISKNAME

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/SDM.md

@@ -0,0 +1,457 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+###### Project
+
+::PROJECT-NAME
+
+###### Internal Release Number
+
+::X.Y.Z
+
+###### Related Documents
+
+- [The Scrum Guide](https://www.scrumguides.org/scrum-guide.html)
+- [The Agile Manifesto](https://agilemanifesto.org)
+- [Agile Documentation: Methodology & Best Practices](https://document360.com/blog/agile-documentation)
+- [Scrum Documentation Template](https://www.infotech.com/research/scrum-documentation-template)
+- [What is Agile Scrum Methodology?](https://www.inflectra.com/Methodologies/Scrum.aspx)
+- [Glossary](Glossary)
+
+### Table of Contents
+
+- [Introduction](SDM#1-introduction)
+  - [Purpose](SDM#11-purpose)
+  - Scope
+  - Audience
+  - Document Overview
+
+- Scrum Overview
+  - What is Scrum?
+  - Scrum Roles
+  - Scrum Artifacts
+  - Scrum Events
+
+- Scrum Team Establishment
+  - Team Formation
+  - Roles and Responsibilities
+  - Team Composition
+
+- Scrum Process Flow
+  - Product Backlog Management
+  - Sprint Planning
+  - Daily Stand-up
+  - Sprint Review
+  - Sprint Retrospective
+
+- Scrum Ceremonies and Artifacts
+  - Sprint Backlog
+  - Definition of Done
+  - Burndown Charts
+  - Product Increment
+  - User Stories and Acceptance Criteria
+
+- Scrum Practices
+  - Sprint Length
+  - Definition of Ready
+  - Definition of Ready
+  - Sprint Backlog Refinement
+  - Release Management
+
+- Monitoring and Metrics
+  - Velocity
+  - Sprint Burndown
+  - Release Burndown
+  - Cumulative Flow Diagram
+  - Sprint Retrospective Actions
+
+- Communication and Collaboration
+  - Daily Stand-up Guidelines
+  - Sprint Review Guidelines
+  - Sprint Retrospective Guidelines
+  - Collaborative Tools
+
+- Scrum in the Organization
+  - Integrating Scrum with Existing Processes
+  - Scrum and Project Management
+  - Scrum and Product Management
+
+- Conclusion
+  - Summary
+  - Continuous Improvement
+  - Acknowledgments
+
+### Introduction
+
+#### Purpose
+
+The purpose of this document is to provide a comprehensive guide on how our software development team will use Scrum as the chosen methodology for product development. It outlines the roles, processes, ceremonies, and practices that the team will follow to ensure effective project delivery.
+
+#### Scope
+
+This document focuses on the implementation of Scrum within our software development team. It serves as a reference for team members, stakeholders, and anyone involved in the development process to understand how Scrum will be applied.
+
+#### Audience
+
+The primary audience for this document includes team members, Scrum Master, Product Owner, and other stakeholders associated with the software development project. It is assumed that the readers have a basic understanding of Agile principles.
+
+#### Document Overview
+
+This document will provide a comprehensive overview of Scrum, including its roles, events, and artifacts. It will then delve into the specifics of how our team will establish and apply Scrum practices throughout the software development lifecycle. Additionally, it covers metrics, communication guidelines, and integration with existing processes.
+
+### Scrum Overview
+
+#### What is Scrum?
+
+Scrum is an Agile software development framework designed to enable teams to deliver high-quality software products iteratively and incrementally. It is based on a set of principles and values that prioritize collaboration, transparency, inspection, and adaptation.
+
+Key characteristics of Scrum include:
+
+- Iterative and Incremental Development: Scrum follows a series of fixed-length iterations called "Sprints," typically lasting two to four weeks. During each Sprint, the team aims to create a potentially shippable product increment by completing a set of prioritized work items.
+
+- Empirical Process Control: Scrum is built on the three pillars of transparency, inspection, and adaptation. The team continuously inspects the product and the process to adapt and improve based on the observations.
+
+- Flexibility and Adaptation: Scrum encourages a flexible and adaptive approach. It acknowledges that requirements and priorities can change during a project, and the team should embrace change to deliver the most valuable product.
+
+- Transparency: Transparency is a fundamental value in Scrum. The process, progress, and challenges are visible to all stakeholders, fostering trust and collaboration.
+
+- Continuous Improvement: Scrum promotes a culture of continuous improvement through regular retrospectives, encouraging the team to inspect and adapt their processes for better outcomes.
+
+Scrum's focus on incremental progress, regular inspection, and adaptation allows teams to respond effectively to changing requirements and deliver valuable software in a collaborative and transparent manner.
+
+#### Scrum Roles and Responsibilities
+
+##### Scrum Master
+
+The Scrum Master is responsible for ensuring that the Scrum framework is understood and followed by the team. They act as facilitators, coaches, and servant leaders, removing impediments and fostering an environment where the team can thrive. The Scrum Master also helps in organizing Scrum events and collaborates with the Product Owner and the Development Team.
+
+##### Product Owner
+
+The Product Owner represents stakeholders and is accountable for maximizing the value of the product. They are responsible for managing the Product Backlog, ensuring that it is transparent, prioritized, and contains items with clear descriptions. The Product Owner collaborates with the Development Team and stakeholders to define product vision and ensure the team delivers the most valuable features.
+
+##### Development Team
+
+The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of the product at the end of each Sprint. They are self-organizing and cross-functional, meaning they collectively possess all the skills necessary to deliver the product. The Development Team collaborates with the Product Owner to clarify requirements and with the Scrum Master to continually improve their processes.
+
+#### Scrum Artifacts
+
+Scrum utilizes three essential artifacts to facilitate a clear understanding of the product being developed and the progress made during the development process:
+
+##### Product Backlog
+
+- Purpose: The Product Backlog is a dynamic and prioritized list of all the work items (user stories, features, bug fixes, improvements) needed to be completed for the product. It represents the requirements and the vision of the product.
+- Importance: The Product Backlog acts as the single source of truth for the development team and stakeholders, ensuring a shared understanding of the product's scope and priorities. It enables transparency and allows for the continuous inspection and adaptation of the project's requirements.
+
+##### Sprint Backlog
+
+- Purpose: The Sprint Backlog is a subset of the Product Backlog that includes the work items selected by the Development Team to complete during a Sprint. It represents the tasks the team commits to accomplishing during the Sprint.
+- Importance: The Sprint Backlog is crucial because it helps the Development Team understand what needs to be done during the Sprint. By selecting a set of items from the Product Backlog, the team commits to achieving specific goals within the Sprint. The Sprint Backlog serves as a guide during the Daily Stand-up, where team members can track progress and identify any obstacles or challenges that need to be addressed.
+
+##### Product Increment
+
+- Purpose: The Product Increment is the sum of all the completed and potentially releasable Product Backlog items at the end of a Sprint. It is the tangible output of the team's work during the Sprint.
+- Importance: The Product Increment's significance lies in providing a tangible outcome at the end of each Sprint. It allows stakeholders to see and experience the value delivered by the team continuously. A well-defined Increment, meeting the Definition of Done, demonstrates the team's ability to deliver a functional and potentially releasable product at regular intervals, even if the decision to release it or not is made by the Product Owner. This fosters trust, transparency, and collaboration between the team and stakeholders.
+
+#### Scrum Events
+
+##### Sprint Planning
+
+- Objective: The primary objective of Sprint Planning is to define what the Development Team will work on during the upcoming Sprint. It involves collaborative discussions between the Product Owner and the Development Team to select the most valuable Product Backlog items to be delivered in the Sprint.
+- Contribution to Team's Success: Sprint Planning ensures that the team has a clear understanding of the Sprint Goal and the scope of work for the Sprint. By collaboratively selecting and committing to work items, the team gains a sense of ownership and accountability for achieving the Sprint Goal. This event sets the direction for the Sprint and helps the team stay focused on delivering the highest value increments.
+
+##### Daily Stand-up (Daily Scrum)
+
+- Objective: The Daily Stand-up is a short, time-boxed meeting held every day during the Sprint. The objective is to facilitate communication and collaboration within the Development Team by providing a forum to share progress, discuss any impediments, and synchronize efforts.
+- Contribution to Team's Success: The Daily Stand-up promotes transparency and fosters a shared understanding of the team's progress and challenges. It enables quick identification and resolution of obstacles, promoting a sense of teamwork and collective accountability. The event helps the team stay on track towards achieving the Sprint Goal, and it encourages a culture of continuous improvement by addressing issues as they arise.
+
+##### Sprint Review
+
+- Objective: The Sprint Review is held at the end of the Sprint and involves a demo of the Product Increment completed during the Sprint. The Product Owner, stakeholders, and the Development Team collaborate to inspect the Increment and provide feedback.
+- Contribution to Team's Success: The Sprint Review ensures that the Product Increment aligns with stakeholders' expectations and provides valuable insights for future improvements. Feedback from stakeholders helps the Development Team understand the product's evolving requirements and refine the Product Backlog accordingly. It also fosters transparency and builds trust between the team and stakeholders.
+
+##### Sprint Retrospective
+
+- Objective: The Sprint Retrospective is a time-boxed meeting held after the Sprint Review, where the Development Team reflects on the Sprint's processes, actions, and collaboration. The team identifies strengths and areas for improvement to enhance future Sprints.
+- Contribution to Team's Success: The Sprint Retrospective promotes a culture of continuous improvement by encouraging the team to inspect their processes and adapt accordingly. By addressing challenges and building on successes, the team can become more efficient and effective over time. The retrospective also allows team members to voice concerns, identify bottlenecks, and make necessary adjustments to work collaboratively.
+
+### Scrum Team Establishment
+
+#### Team Formation
+
+Forming a successful Scrum Team is a crucial aspect of implementing Scrum effectively. The Scrum Team is a self-organizing and cross-functional group responsible for delivering the product increment. Here's a step-by-step explanation of how the Scrum Team will be formed, including selecting team members with the right skills and expertise for the project:
+
+##### Define Project Needs and Scope
+
+ Begin by defining the project's needs, objectives, and scope in collaboration with the Product Owner and relevant stakeholders. Understanding the project's requirements will help in identifying the necessary skills and expertise.
+
+##### Identify Core Scrum Roles
+
+Identify the core Scrum roles within the Scrum Team: the Product Owner, Scrum Master, and Development Team. Each role has distinct responsibilities that contribute to the project's success.
+
+##### Assess Required Skills and Competencies
+
+Determine the skills and competencies required for the project's successful execution. This assessment should align with the product vision and the items in the Product Backlog.
+
+##### Cross-Functional Expertise
+
+Ensure that the Scrum Team is cross-functional, meaning it possesses all the skills necessary to deliver the product increment. Look for team members who have diverse skills, such as design, development, testing, user experience, etc.
+
+##### Collaborative Team Building
+
+Team building should be a collaborative process involving the Product Owner, Scrum Master, and any existing team members. If the team is new, involve stakeholders or subject matter experts as needed.
+
+##### Skill Gap Analysis
+
+Conduct a skill gap analysis to identify any areas where expertise may be lacking within the team. Address these gaps by either hiring new team members or providing training to existing ones.
+
+##### Identify Potential Team Members
+
+Identify potential team members based on their expertise, experience, and track record of successful project delivery. Look for individuals with a proven ability to work well in collaborative, Agile environments.
+
+##### Soft Skills and Collaboration
+
+Consider the soft skills of potential team members, such as communication, adaptability, and teamwork. Effective collaboration and communication are crucial for a high-performing Scrum Team.
+
+##### Balancing Workload
+
+Ensure a balanced workload among team members to avoid overburdening individuals and to maintain sustainable pace throughout the project.
+
+##### Commitment and Empowerment
+
+Select team members who are committed to the project's success and embrace the values and principles of Scrum. Empowerment and a sense of ownership are essential for a self-organizing team.
+
+##### Formalize Roles and Responsibilities
+
+Once the Scrum Team members are selected, formalize their roles and responsibilities to establish clear expectations and promote accountability.
+
+##### Continuous Improvement
+
+The Scrum Team is not static, and continuous improvement is vital. Regularly inspect team dynamics and performance during Sprint Retrospectives and make necessary adjustments to optimize effectiveness.
+
+##### Promote Trust and Collaboration
+
+Foster a culture of trust, openness, and collaboration within the Scrum Team and with stakeholders. Encourage a safe environment for feedback and ideas.
+
+Forming the Scrum Team with the right mix of skills, expertise, and collaboration is fundamental to the project's success. A well-formed Scrum Team, working together cohesively and empowered to make decisions, will enhance the chances of delivering a high-quality product increment and achieving project goals.
+
+#### Team Collaboration
+
+Ensuring effective collaboration within the Scrum Team is essential to achieve cross-functionality and a shared understanding of project goals. Here's an explanation of how the team will collaborate to achieve these objectives:
+
+##### Cross-Functional Team
+
+The Scrum Team is designed to be cross-functional, meaning that it possesses all the skills and expertise required to deliver the product increment. This includes skills such as development, testing, design, user experience, and any other necessary disciplines. By having a diverse range of skills within the team, members can collaborate and contribute to different aspects of the project.
+
+##### Collaborative Environment
+
+Create a collaborative work environment where team members feel comfortable sharing ideas, discussing challenges, and seeking help from each other. Encourage open communication, active listening, and a culture of respect and trust among team members.
+
+##### Sprint Planning
+
+During Sprint Planning, the Product Owner collaborates with the Development Team to discuss the items from the Product Backlog and define the Sprint Goal. The team members contribute their insights, estimations, and concerns to ensure a shared understanding of what needs to be achieved in the upcoming Sprint.
+
+##### Definition of Done (DoD)
+
+Establish a clear and agreed-upon Definition of Done that defines the criteria for a Product Backlog item to be considered complete. This shared understanding ensures that all team members know what is expected and can work together to meet the DoD for each increment.
+
+##### Daily Stand-up
+
+Conduct Daily Stand-up meetings to promote collaboration and transparency within the team. Each team member briefly shares their progress, challenges, and plans for the day. The stand-up allows the team to identify any impediments or dependencies that require collective attention.
+
+##### Pair Programming and Peer Reviews
+
+Encourage pair programming, where two team members work together on the same piece of code, which fosters knowledge sharing and ensures higher code quality. Additionally, promote peer reviews of code, design, and other artifacts to leverage collective expertise and maintain high standards.
+
+##### Sprint Review
+
+The Sprint Review is an opportunity for the team to collaborate with stakeholders to demonstrate the completed increment and gather feedback. Collaboration during this event helps validate that the product increment aligns with stakeholder expectations.
+
+#### Sprint Retrospective
+
+The Sprint Retrospective allows the team to reflect on their processes and collaboration during the Sprint. Team members discuss what went well, what could be improved, and any action items to enhance collaboration and productivity.
+
+##### Continuous Improvement
+
+Emphasize the value of continuous improvement within the team. Encourage team members to propose process improvements, experiment with new approaches, and learn from both successes and failures.
+
+##### Knowledge Sharing
+
+Organize knowledge sharing sessions or workshops within the team to facilitate the transfer of expertise and best practices. Cross-training and skill development initiatives ensure that team members can contribute effectively in different areas.
+
+##### Agile Ceremonies and Artifacts
+
+Use Agile ceremonies (e.g., Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective) and Scrum artifacts (e.g., Product Backlog, Sprint Backlog) as tools for collaboration, transparency, and continuous alignment with project goals.
+
+By fostering a collaborative environment, promoting cross-functional expertise, and leveraging Agile practices, the Scrum Team can ensure effective collaboration, shared understanding of project goals, and a focus on delivering high-quality increments that meet the needs of stakeholders. Collaboration within the team is a cornerstone of Scrum, enabling it to adapt and succeed in a dynamic and changing environment.
+
+### Scrum Process Flow
+
+#### Product Backlog Management
+
+##### Creating the Product Backlog
+
+The Product Backlog is a dynamic and evolving list of all the work items needed to deliver the product. It is created during the initial stages of the project, driven by the product vision, user needs, and stakeholder requirements. Input from stakeholders, customers, market research, and the team's expertise contribute to populating the Product Backlog.
+
+##### Prioritizing the Product Backlog
+
+The Product Backlog items are prioritized based on their business value, customer needs, market demands, technical dependencies, and risks. The Product Owner plays a critical role in setting the priorities, aligning with stakeholders, and ensuring that the most valuable items are placed at the top.
+
+##### Refining the Product Backlog
+
+Backlog refinement, also known as "Backlog Grooming," is an ongoing process where the Product Owner and the Development Team collaboratively review, revise, and update the Product Backlog. This ensures that the backlog remains relevant, actionable, and ready for Sprint Planning.
+
+##### Involvement of the Product Owner
+
+The Product Owner (PO) is primarily responsible for managing the Product Backlog. Their involvement includes:
+
+- Defining and Communicating Vision: The PO defines the product vision and communicates it to the team and stakeholders. The vision serves as a guide for prioritizing the items in the Product Backlog based on their alignment with the product's overall goals.
+
+- Gathering Stakeholder Requirements: The PO collaborates with stakeholders, customers, and users to understand their needs, requirements, and feedback. They gather input and insights to ensure the Product Backlog reflects the most valuable features and improvements.
+
+- Prioritization: The PO prioritizes the items in the Product Backlog, considering the stakeholders' needs and the product's strategic goals. High-priority items are positioned at the top of the backlog to be addressed earlier.
+
+- Continuous Refinement: The PO continuously refines the Product Backlog, ensuring that it contains clear, well-defined, and actionable items. They add new items, revise existing ones, and remove obsolete or less valuable items based on changing priorities and feedback.
+
+- Collaboration with the Development Team: The PO collaborates closely with the Development Team to provide clarifications on requirements and answer questions during backlog refinement. This ensures that the team has a clear understanding of the items before Sprint Planning.
+
+##### Involvement of the Development Team
+
+The Development Team plays an active role in Backlog Refinement, ensuring that the items in the Product Backlog are "ready" for Sprint Planning. Their involvement includes:
+
+- Asking Clarifying Questions: During backlog refinement sessions, the Development Team seeks clarifications from the Product Owner regarding the details, acceptance criteria, and expected outcomes of the items.
+
+- Estimating Effort: The Development Team estimates the effort required to implement each item. These estimates help the Product Owner and stakeholders understand the relative size and complexity of the work items.
+
+- Providing Feedback: The Development Team provides feedback on the feasibility, technical constraints, and potential risks associated with the items. They offer insights into alternative approaches or potential improvements to enhance value delivery.
+
+- Splitting User Stories: If backlog items are too large or complex, the Development Team collaborates with the Product Owner to split them into smaller, more manageable user stories that can be completed within a single Sprint.
+
+- Commitment to Deliver: Before Sprint Planning, the Development Team commits to delivering a set of items from the Product Backlog for the upcoming Sprint. This commitment ensures a shared understanding and responsibility for achieving the Sprint Goal.
+
+Through effective collaboration between the Product Owner and the Development Team, the Product Backlog becomes a valuable tool for prioritizing and aligning the team's efforts with the product's vision and objectives. Continuous refinement ensures that the team works on the most valuable and relevant items, contributing to the success of the project.
+
+#### Sprint Planning
+
+::Describe the process of Sprint Planning, including the selection of items from the Product Backlog, defining the Sprint Goal, and creating the Sprint Backlog.
+
+#### 4.3 Daily Stand-up
+
+::Explain how the Daily Stand-up will be conducted, its purpose, and what questions each team member will answer.
+
+#### 4.4 Sprint Review
+
+::Describe the Sprint Review process, including the demonstration of the Product Increment and gathering feedback from stakeholders.
+
+#### 4.5 Sprint Retrospective
+
+::Explain how the Sprint Retrospective will be conducted to reflect on the previous Sprint and identify areas for improvement.
+
+### 5. Scrum Ceremonies and Artifacts
+
+#### 5.1 Sprint Backlog
+
+::Explain how the team will manage and update the Sprint Backlog throughout the Sprint.
+
+#### 5.2 Definition of Done
+
+::Outline the Definition of Done and how it will be applied to ensure the quality of the product increment.
+
+#### 5.3 Burndown Charts
+
+::Describe the use of Burndown Charts to track progress and identify potential issues during the Sprint.
+
+#### 5.4 Product Increment
+
+::Explain how the Product Increment will be reviewed and potentially released after each Sprint.
+
+#### 5.5 User Stories and Acceptance Criteria
+
+::Provide guidelines on writing clear and concise User Stories with well-defined Acceptance Criteria.
+
+### 6. Scrum Practices
+
+#### 6.1 Sprint Length
+
+::Explain how the team determined the appropriate Sprint length and the considerations behind the decision.
+
+#### 6.2 Definition of Ready
+
+::Outline the criteria for User Stories to be considered "Ready" for inclusion in a Sprint.
+
+#### 6.3 Definition of Done
+
+::Explain the team's agreed-upon Definition of Done for User Stories and increments.
+
+#### 6.4 Sprint Backlog Refinement
+
+::Describe how the team will conduct Sprint Backlog Refinement meetings to ensure that backlog items are ready for Sprint Planning.
+
+#### 6.5 Release Management
+
+::Outline how the team plans and executes product releases, including Sprint Reviews with stakeholders and customers.
+
+### 7. Monitoring and Metrics
+
+#### 7.1 Velocity
+
+::Explain how the team will measure and track Velocity to forecast future Sprint capacity.
+
+#### 7.2 Sprint Burndown
+
+::Describe how the team will use the Sprint Burndown chart to monitor progress during the Sprint.
+
+#### 7.3 Release Burndown
+
+::Explain how the team will use the Release Burndown chart to track progress towards achieving project milestones.
+
+#### 7.4 Cumulative Flow Diagram
+
+::Describe how the Cumulative Flow Diagram will be used to visualize work in progress and identify bottlenecks.
+
+#### 7.5 Sprint Retrospective Actions
+
+::Explain how the team will use Sprint Retrospective outcomes to implement improvements and action items.
+
+### 8. Communication and Collaboration
+
+#### 8.1 Daily Stand-up Guidelines
+
+::Provide guidelines for conducting effective Daily Stand-up meetings, including the recommended time and format.
+
+#### 8.2 Sprint Review Guidelines
+
+::Outline the structure and objectives of Sprint Review meetings and how stakeholders' feedback will be collected.
+
+#### 8.3 Sprint Retrospective Guidelines
+
+::Explain how the team will facilitate Sprint Retrospectives to encourage open feedback and identify areas for continuous improvement.
+
+#### 8.4 Collaborative Tools
+
+::List the tools and technologies that the team will use to facilitate collaboration and communication within the team.
+
+### 9. Scrum in the Organization
+
+#### 9.1 Integrating Scrum with Existing Processes
+
+::Describe how Scrum will integrate with other existing organizational processes to ensure smooth collaboration.
+
+#### 9.2 Scrum and Project Management
+
+::Explain the relationship between Scrum and project management, and how the Scrum framework will be used to manage projects effectively.
+
+#### 9.3 Scrum and Product Management
+
+::Describe how Scrum will collaborate with product management to ensure the alignment of product vision and development efforts.
+
+### 10. Conclusion
+
+#### 10.1 Summary
+
+::Provide a summary of the key points covered in this document, emphasizing the benefits and expected outcomes of adopting Scrum.
+
+#### 10.2 Continuous Improvement
+
+::Reiterate the importance of continuous improvement and the team's commitment to inspecting and adapting its practices.
+
+#### 10.3 Acknowledgments
+
+::Acknowledge the contributions of team members, stakeholders, and others who have supported the adoption of Scrum within the organization.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/SRS.md

@@ -0,0 +1,257 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+##### Project
+
+::PROJECT-NAME
+
+##### Internal Release Number
+
+::X.Y.Z
+
+##### Attached worksheets
+
+- SRS > [Use case suite](Use-Case-Suite)
+- SRS > [Feature set](Feature-Set)
+
+##### Related Documents
+
+- [Project proposal](Proposal) > [User needs](User-Needs)
+- ::LINKS TO RELEVANT STANDARDS
+- ::LINKS TO OTHER DOCUMENTS
+- [Glossary](Glossary)
+
+---
+
+**Process impact:** The SRS precisely defines the software product that
+will be built. Decisions made in writing the SRS are based on
+information in the [project proposal](Proposal) and [user
+needs](User-Needs) documents. The SRS sets requirements that must
+be satisfied by the [system design](Design). The SRS is verified
+and validated by activities outlined in the [QA plan](QA-Plan).
+
+### Introduction
+
+_TODO: Provide a brief overview of this release of the product. You can
+copy text from the project proposal, paste it here, and shorten it._
+
+::PARAGRAPH
+
+::PARAGRAPH
+
+For more information, see the project [proposal](Proposal).
+
+### Use Cases
+
+::ONE PARAGRAPH OVERVIEW
+
+Details:
+
+- Actors are described in the [user needs](User-Needs) document.
+- The [use case suite](Use-Case-Suite) lists all use cases in an
+  organized way.
+
+### Functional Requirements
+
+::ONE PARAGRAPH OVERVIEW
+
+Details:
+
+- The [feature set](Feature-Set) lists all features in an
+  organized way.
+
+### Non-Functional Requirements
+
+_TODO: Describe the non-functional requirements for this release. Some
+examples are provided below._
+
+#### What are the usability requirements?
+
+::Our main criteria for making the system usable is the difficulty of
+performing each high-frequency use case. Difficulty depends on the
+number of steps, the knowledge that the user must have at each step,
+the decisions that the user must make at each step, and the
+mechanics of each step (e.g., typing a book title exactly is hard,
+clicking on a title in a list is easy).
+
+::The user interface should be as familiar as possible to users who
+have used other web applications and Windows desktop applications.
+E.g., we will follow the UI guidelines for naming menus, buttons,
+and dialog boxes whenever possible.
+
+::PARAGRAPH
+
+Details:
+
+- ::Government customers will demand [section508
+  compliance](http://www.section508.gov/)
+- ::Support learnability with principles of [Instructive
+  Interaction](http://www.foruse.com/articles/instructive.htm)
+- ::The customer wants extensive on-line help, but is not demanding
+  a printed manual.
+
+#### What are the reliability and up-time requirements?
+
+::PARAGRAPH
+
+::PARAGRAPH
+
+Details:
+
+- ::DETAIL
+- ::DETAIL
+- ::DETAIL
+
+#### What are the safety requirements?
+
+::PARAGRAPH
+
+::PARAGRAPH
+
+Details:
+
+- ::DETAIL
+- ::DETAIL
+- ::DETAIL
+
+#### What are the security requirements?
+
+::Access will be controlled with usernames and passwords.
+
+::Only administrator users will have access to administrative
+functions, average users will not.
+
+Details:
+
+- ::Passwords must be 4-14 characters long
+- ::We will not use encrypted communications (SSL) for this website
+- ::DETAIL
+
+#### What are the performance and scalability requirements requirements?
+
+::PARAGRAPH
+
+::PARAGRAPH
+
+Details:
+
+- ::DETAIL
+- ::DETAIL
+- ::DETAIL
+
+#### What are the maintainability and upgradability requirements?
+
+::Maintainability is our ability to make changes to the product
+over time. We need strong maintainability in order to retain our
+early customers. We will address this by anticipating several types
+of change, and by carefully documenting our design
+and implementation.
+
+::Upgradability is our ability to cost-effectively deploy new versions
+of the product to customers with minimal downtime or disruption. A
+key feature supporting this goal is automatic download of patches
+and upgrade of the end-user's machine. Also, we shall use data file
+formats that include enough meta-data to allow us to reliably
+transform existing customer data during an upgrade.
+
+Details:
+
+- ::DETAIL
+- ::DETAIL
+- ::DETAIL
+
+#### What are the supportability and operability requirements?
+
+::Supportability is our ability to provide cost effective
+technical support. Our goal is to limit our support costs to only 5%
+of annual licensing fees. The product's automatic upgrade feature
+will help us easily deploy defect fixes to end-users. The user guide
+and product website will include a troubleshooting guide and
+checklist of information to have at hand before contacting
+technical support.
+
+::Operability is our ability to host and operate the software as an
+ASP (Application Service Provider). The product features should help
+us achieve our goal of 99.9% uptime (at most 43 minutes downtime
+each month). Key features supporting that are the ability to do hot
+data backups, and application monitoring.
+
+Details:
+
+- ::DETAIL
+- ::DETAIL
+- ::DETAIL
+
+#### What are the business life-cycle requirements?
+
+::The business life-cycle of a product includes everything that
+happens to that product over a period of several years, from initial
+purchase decision, through important but infrequent use cases, until
+product retirement. Key life-cycle requirements are listed below.
+
+Details:
+
+- ::Customers must be able to manage the number of licenses that
+  they have and make informed decisions to purchase more licenses
+  when needed
+- ::The product shall support daily operations and our year-end
+  audit
+- ::The customer data shall be stored in a format that is still
+  accessible even after the application has been retired
+
+### Environmental Requirements
+
+_TODO: Describe the environmental requirements for this release.
+Environmental requirements describe the larger system of hardware,
+software, and data that this product must work within. Some examples are
+provided below._
+
+#### What are the system hardware requirements?
+
+::PARAGRAPH
+
+::PARAGRAPH
+
+Details:
+
+- ::DETAIL
+- ::DETAIL
+- ::DETAIL
+
+#### What are the system software requirements?
+
+::PARAGRAPH
+
+::PARAGRAPH
+
+Details:
+
+- ::DETAIL
+- ::DETAIL
+- ::DETAIL
+
+#### What application program interfaces ([APIs](Glossary-Standard-Terms#api_application_programming_interface)) must be provided?
+
+::PARAGRAPH
+
+::PARAGRAPH
+
+Details:
+
+- ::We must implement this [standard API](LINK-TO-STANDARD).
+- ::DETAIL
+- ::DETAIL
+
+#### What are the data import and export requirements?
+
+::PARAGRAPH
+
+::PARAGRAPH
+
+Details:
+
+- ::The system will store all data in a standard SQL database, where
+  it can be accessed by other programs.
+- ::The system will store all data in an XML file, using a
+  [standard DTD](LINK-TO-STANDARD).
+- ::The system will read and write valid .XYZ files used by
+  OTHER APPLICATION
+- ::DETAIL

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Scrum-Guide.md

@@ -0,0 +1,472 @@
+# The Scrum Guide
+
+## The Definitive Guide to Scrum: The Rules of the Game
+
+## Ken Schwaber & Jeff Sutherland
+
+## November 2020
+
+## Purpose of the Scrum Guide
+
+We developed Scrum in the early 1990s. We wrote the first version of the Scrum Guide in 2010 to help people worldwide understand Scrum. We have evolved the Guide since then through small, functional updates. Together, we stand behind it.
+
+The Scrum Guide contains the definition of Scrum. Each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum. Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless.
+
+We follow the growing use of Scrum within an ever-growing complex world. We are humbled to see Scrum being adopted in many domains holding essentially complex work, beyond software product development where Scrum has its roots. As Scrum’s use spreads, developers, researchers, analysts, scientists, and other specialists do the work. We use the word “developers” in Scrum not to exclude, but to simplify. If you get value from Scrum, consider yourself included.
+
+As Scrum is being used, patterns, processes, and insights that fit the Scrum framework as described in this document, may be found, applied and devised. Their description is beyond the purpose of the Scrum Guide because they are context sensitive and differ widely between Scrum uses. Such tactics for using within the Scrum framework vary widely and are described elsewhere.
+
+Ken Schwaber & Jeff Sutherland November 2020
+
+```markdown
+© 2020 Ken Schwaber and Jeff Sutherland
+```
+
+```markdown
+This publication is offered for license under the Attribution Share-Alike license of Creative Commons, accessible at https://creativecommons.org/licenses/by-sa/4.0/legalcode and also described in summary form at https://creativecommons.org/licenses/by-sa/4.0/. By utilizing this Scrum Guide, you acknowledge and agree that you have read and agree to be bound by the terms of the Attribution Share-Alike license of Creative Commons.
+```
+
+- Purpose of the Scrum Guide
+- Scrum Definition
+- Scrum Theory
+  - Transparency
+  - Inspection
+  - Adaptation
+- Scrum Values
+- Scrum Team
+  - Developers
+  - Product Owner
+  - Scrum Master
+- Scrum Events
+  - The Sprint
+  - Sprint Planning
+  - Daily Scrum
+  - Sprint Review
+  - Sprint Retrospective
+- Scrum Artifacts
+  - Product Backlog
+    - Commitment: Product Goal
+  - Sprint Backlog
+    - Commitment: Sprint Goal
+  - Increment
+    - Commitment: Definition of Done
+- End Note
+  - Acknowledgements
+    - People
+    - Scrum Guide History
+
+## Scrum Definition
+
+Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems.
+
+In a nutshell, Scrum requires a Scrum Master to foster an environment where:
+
+1. A Product Owner orders the work for a complex problem into a Product Backlog.
+2. The Scrum Team turns a selection of the work into an Increment of value during a Sprint.
+3. The Scrum Team and its stakeholders inspect the results and adjust for the next Sprint.
+4. _Repeat_
+
+Scrum is simple. Try it as is and determine if its philosophy, theory, and structure help to achieve goals and create value. The Scrum framework is purposefully incomplete, only defining the parts required to implement Scrum theory. Scrum is built upon by the collective intelligence of the people using it. Rather than provide people with detailed instructions, the rules of Scrum guide their relationships and interactions.
+
+Various processes, techniques and methods can be employed within the framework. Scrum wraps around existing practices or renders them unnecessary. Scrum makes visible the relative efficacy of current management, environment, and work techniques, so that improvements can be made.
+
+## Scrum Theory
+
+Scrum is founded on empiricism and lean thinking. Empiricism asserts that knowledge comes from experience and making decisions based on what is observed. Lean thinking reduces waste and focuses on the essentials.
+
+Scrum employs an iterative, incremental approach to optimize predictability and to control risk. Scrum engages groups of people who collectively have all the skills and expertise to do the work and share or acquire such skills as needed.
+
+Scrum combines four formal events for inspection and adaptation within a containing event, the Sprint. These events work because they implement the empirical Scrum pillars of transparency, inspection, and adaptation.
+
+### Transparency
+
+The emergent process and work must be visible to those performing the work as well as those receiving the work. With Scrum, important decisions are based on the perceived state of its three formal artifacts.  Artifacts that have low transparency can lead to decisions that diminish value and increase risk. 
+
+Transparency enables inspection. Inspection without transparency is misleading and wasteful.
+
+### Inspection
+
+The Scrum artifacts and the progress toward agreed goals must be inspected frequently and diligently to detect potentially undesirable variances or problems. To help with inspection, Scrum provides cadence in the form of its five events. 
+
+Inspection enables adaptation. Inspection without adaptation is considered pointless. Scrum events are designed to provoke change.
+
+### Adaptation
+
+If any aspects of a process deviate outside acceptable limits or if the resulting product is unacceptable, the process being applied or the materials being produced must be adjusted. The adjustment must be made as soon as possible to minimize further deviation.
+
+Adaptation becomes more difficult when the people involved are not empowered or self-managing. A Scrum Team is expected to adapt the moment it learns anything new through inspection.
+
+## Scrum Values
+
+Successful use of Scrum depends on people becoming more proficient in living five values:
+
+```markdown
+Commitment, Focus, Openness, Respect, and Courage
+```
+
+The Scrum Team commits to achieving its goals and to supporting each other. Their primary focus is on the work of the Sprint to make the best possible progress toward these goals. The Scrum Team and its stakeholders are open about the work and the challenges. Scrum Team members respect each other to be capable, independent people, and are respected as such by the people with whom they work. The Scrum Team members have the courage to do the right thing, to work on tough problems.
+
+These values give direction to the Scrum Team with regard to their work, actions, and behavior. The decisions that are made, the steps taken, and the way Scrum is used should reinforce these values, not diminish or undermine them. The Scrum Team members learn and explore the values as they work with the Scrum events and artifacts. When these values are embodied by the Scrum Team and the people they work with, the empirical Scrum pillars of transparency, inspection, and adaptation come to life building trust.
+
+## Scrum Team
+
+The fundamental unit of Scrum is a small team of people, a Scrum Team. The Scrum Team consists of one Scrum Master, one Product Owner, and Developers. Within a Scrum Team, there are no sub-teams or hierarchies. It is a cohesive unit of professionals focused on one objective at a time, the Product Goal.
+
+Scrum Teams are cross-functional, meaning the members have all the skills necessary to create value each Sprint. They are also self-managing, meaning they internally decide who does what, when, and how.
+
+The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better and are more productive. If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, and Product Owner.
+
+The Scrum Team is responsible for all product-related activities from stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required. They are structured and empowered by the organization to manage their own work. Working in Sprints at a sustainable pace improves the Scrum Team’s focus and consistency.
+
+The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. Scrum
+defines three specific accountabilities within the Scrum Team: the Developers, the Product Owner, and
+the Scrum Master.
+
+### Developers
+
+Developers are the people in the Scrum Team that are committed to creating any aspect of a usable
+Increment each Sprint.
+
+The specific skills needed by the Developers are often broad and will vary with the domain of work.
+However, the Developers are always accountable for:
+
+```markdown
+- Creating a plan for the Sprint, the Sprint Backlog;
+- Instilling quality by adhering to a Definition of Done;
+- Adapting their plan each day toward the Sprint Goal; and,
+- Holding each other accountable as professionals.
+```
+
+### Product Owner
+
+The Product Owner is accountable for maximizing the value of the product resulting from the work of
+the Scrum Team. How this is done may vary widely across organizations, Scrum Teams, and individuals.
+
+The Product Owner is also accountable for effective Product Backlog management, which includes:
+
+```markdown
+- Developing and explicitly communicating the Product Goal;
+- Creating and clearly communicating Product Backlog items;
+- Ordering Product Backlog items; and,
+- Ensuring that the Product Backlog is transparent, visible and understood.
+```
+
+The Product Owner may do the above work or may delegate the responsibility to others. Regardless, the
+Product Owner remains accountable.
+
+For Product Owners to succeed, the entire organization must respect their decisions. These decisions
+are visible in the content and ordering of the Product Backlog, and through the inspectable increment at
+the Sprint Review.
+
+The Product Owner is one person, not a committee. The Product Owner may represent the needs of
+many stakeholders in the Product Backlog. Those wanting to change the Product Backlog can do so by
+trying to convince the Product Owner.
+
+### Scrum Master
+
+The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide. They do this by
+helping everyone understand Scrum theory and practice, both within the Scrum Team and the
+organization.
+
+The Scrum Master is accountable for the Scrum Team’s effectiveness. They do this by enabling the
+Scrum Team to improve its practices, within the Scrum framework.
+
+Scrum Masters are true leaders who serve the Scrum Team and the larger organization.
+
+The Scrum Master serves the Scrum Team in several ways, including:
+
+```markdown
+- Coaching the team members in self-management and cross-functionality;
+- Helping the Scrum Team focus on creating high-value Increments that meet the Definition of
+Done;
+- Causing the removal of impediments to the Scrum Team’s progress; and,
+- Ensuring that all Scrum events take place and are positive, productive, and kept within the
+timebox.
+```
+
+The Scrum Master serves the Product Owner in several ways, including:
+
+```markdown
+- Helping find techniques for effective Product Goal definition and Product Backlog management;
+- Helping the Scrum Team understand the need for clear and concise Product Backlog items;
+- Helping establish empirical product planning for a complex environment; and,
+- Facilitating stakeholder collaboration as requested or needed.
+```
+
+The Scrum Master serves the organization in several ways, including:
+
+```markdown
+- Leading, training, and coaching the organization in its Scrum adoption;
+- Planning and advising Scrum implementations within the organization;
+- Helping employees and stakeholders understand and enact an empirical approach for complex
+work; and,
+- Removing barriers between stakeholders and Scrum Teams.
+```
+
+## Scrum Events
+
+The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and
+adapt Scrum artifacts. These events are specifically designed to enable the transparency required.
+Failure to operate any events as prescribed results in lost opportunities to inspect and adapt. Events are
+used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.
+Optimally, all events are held at the same time and place to reduce complexity.
+
+### The Sprint
+
+Sprints are the heartbeat of Scrum, where ideas are turned into value.
+
+They are fixed length events of one month or less to create consistency. A new Sprint starts immediately
+after the conclusion of the previous Sprint.
+
+All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint
+Review, and Sprint Retrospective, happen within Sprints.
+
+During the Sprint:
+
+```markdown
+- No changes are made that would endanger the Sprint Goal;
+- Quality does not decrease;
+- The Product Backlog is refined as needed; and,
+- Scope may be clarified and renegotiated with the Product Owner as more is learned.
+```
+
+Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at
+least every calendar month. When a Sprint’s horizon is too long the Sprint Goal may become invalid,
+complexity may rise, and risk may increase. Shorter Sprints can be employed to generate more learning
+cycles and limit risk of cost and effort to a smaller time frame. Each Sprint may be considered a short
+project.
+
+Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While
+proven useful, these do not replace the importance of empiricism. In complex environments, what will
+happen is unknown. Only what has already happened may be used for forward-looking decision making.
+
+A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the
+authority to cancel the Sprint.
+
+### Sprint Planning
+
+Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting
+plan is created by the collaborative work of the entire Scrum Team.
+
+The Product Owner ensures that attendees are prepared to discuss the most important Product Backlog
+items and how they map to the Product Goal. The Scrum Team may also invite other people to attend
+Sprint Planning to provide advice.
+
+Sprint Planning addresses the following topics:
+
+Topic One: Why is this Sprint valuable?
+
+The Product Owner proposes how the product could increase its value and utility in the current Sprint.
+The whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is
+valuable to stakeholders. The Sprint Goal must be finalized prior to the end of Sprint Planning.
+
+Topic Two: What can be Done this Sprint?
+
+Through discussion with the Product Owner, the Developers select items from the Product Backlog to
+include in the current Sprint. The Scrum Team may refine these items during this process, which
+increases understanding and confidence.
+
+Selecting how much can be completed within a Sprint may be challenging. However, the more the
+Developers know about their past performance, their upcoming capacity, and their Definition of Done,
+the more confident they will be in their Sprint forecasts.
+
+Topic Three: How will the chosen work get done?
+
+For each selected Product Backlog item, the Developers plan the work necessary to create an Increment
+that meets the Definition of Done. This is often done by decomposing Product Backlog items into
+smaller work items of one day or less. How this is done is at the sole discretion of the Developers. No
+one else tells them how to turn Product Backlog items into Increments of value.
+
+The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are
+together referred to as the Sprint Backlog.
+
+Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints,
+the event is usually shorter.
+
+### Daily Scrum
+
+The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint
+Backlog as necessary, adjusting the upcoming planned work.
+
+The Daily Scrum is a 15-minute event for the Developers of the Scrum Team. To reduce complexity, it is
+held at the same time and place every working day of the Sprint. If the Product Owner or Scrum Master
+are actively working on items in the Sprint Backlog, they participate as Developers.
+
+The Developers can select whatever structure and techniques they want, as long as their Daily Scrum
+focuses on progress toward the Sprint Goal and produces an actionable plan for the next day of work.
+This creates focus and improves self-management.
+
+Daily Scrums improve communications, identify impediments, promote quick decision-making, and
+consequently eliminate the need for other meetings.
+
+The Daily Scrum is not the only time Developers are allowed to adjust their plan. They often meet
+throughout the day for more detailed discussions about adapting or re-planning the rest of the Sprint’s
+work.
+
+### Sprint Review
+
+The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future
+adaptations. The Scrum Team presents the results of their work to key stakeholders and progress
+toward the Product Goal is discussed.
+
+During the event, the Scrum Team and stakeholders review what was accomplished in the Sprint and
+what has changed in their environment. Based on this information, attendees collaborate on what to do
+next. The Product Backlog may also be adjusted to meet new opportunities. The Sprint Review is a
+working session and the Scrum Team should avoid limiting it to a presentation.
+
+The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours
+for a one-month Sprint. For shorter Sprints, the event is usually shorter.
+
+### Sprint Retrospective
+
+The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.
+
+The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes,
+tools, and their Definition of Done. Inspected elements often vary with the domain of work.
+Assumptions that led them astray are identified and their origins explored. The Scrum Team discusses
+what went well during the Sprint, what problems it encountered, and how those problems were (or
+were not) solved.
+
+The Scrum Team identifies the most helpful changes to improve its effectiveness. The most impactful
+improvements are addressed as soon as possible. They may even be added to the Sprint Backlog for the
+next Sprint.
+
+The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-
+month Sprint. For shorter Sprints, the event is usually shorter.
+
+## Scrum Artifacts
+
+Scrum’s artifacts represent work or value. They are designed to maximize transparency of key
+information. Thus, everyone inspecting them has the same basis for adaptation.
+
+Each artifact contains a commitment to ensure it provides information that enhances transparency and
+focus against which progress can be measured:
+
+```markdown
+- For the Product Backlog it is the Product Goal.
+- For the Sprint Backlog it is the Sprint Goal.
+- For the Increment it is the Definition of Done.
+```
+
+These commitments exist to reinforce empiricism and the Scrum values for the Scrum Team and their
+stakeholders.
+
+### Product Backlog
+
+The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the
+single source of work undertaken by the Scrum Team.
+
+Product Backlog items that can be Done by the Scrum Team within one Sprint are deemed ready for
+selection in a Sprint Planning event. They usually acquire this degree of transparency after refining
+activities. Product Backlog refinement is the act of breaking down and further defining Product Backlog
+items into smaller more precise items. This is an ongoing activity to add details, such as a description,
+order, and size. Attributes often vary with the domain of work.
+
+The Developers who will be doing the work are responsible for the sizing. The Product Owner may
+influence the Developers by helping them understand and select trade-offs.
+
+#### Commitment: Product Goal
+
+The Product Goal describes a future state of the product which can serve as a target for the Scrum Team
+to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to
+define “what” will fulfill the Product Goal.
+
+```markdown
+A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined
+users or customers. A product could be a service, a physical product, or something more abstract.
+```
+
+The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one
+objective before taking on the next.
+
+### Sprint Backlog
+
+The Sprint Backlog is composed of the Sprint Goal (why), the set of Product Backlog items selected for
+the Sprint (what), as well as an actionable plan for delivering the Increment (how).
+
+The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work
+that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal.
+Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have
+enough detail that they can inspect their progress in the Daily Scrum.
+
+#### Commitment: Sprint Goal
+
+The Sprint Goal is the single objective for the Sprint. Although the Sprint Goal is a commitment by the
+Developers, it provides flexibility in terms of the exact work needed to achieve it. The Sprint Goal also
+creates coherence and focus, encouraging the Scrum Team to work together rather than on separate
+initiatives.
+
+The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog. As the
+Developers work during the Sprint, they keep the Sprint Goal in mind. If the work turns out to be
+different than they expected, they collaborate with the Product Owner to negotiate the scope of the
+Sprint Backlog within the Sprint without affecting the Sprint Goal.
+
+### Increment
+
+An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all
+prior Increments and thoroughly verified, ensuring that all Increments work together. In order to
+provide value, the Increment must be usable.
+
+Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the
+Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders
+prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.
+
+Work cannot be considered part of an Increment unless it meets the Definition of Done.
+
+#### Commitment: Definition of Done
+
+The Definition of Done is a formal description of the state of the Increment when it meets the quality
+measures required for the product.
+
+The moment a Product Backlog item meets the Definition of Done, an Increment is born.
+
+The Definition of Done creates transparency by providing everyone a shared understanding of what
+work was completed as part of the Increment. If a Product Backlog item does not meet the Definition of
+Done, it cannot be released or even presented at the Sprint Review. Instead, it returns to the Product
+Backlog for future consideration.
+
+If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams
+must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a
+Definition of Done appropriate for the product.
+
+The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams
+working together on a product, they must mutually define and comply with the same Definition of Done.
+
+## End Note
+
+Scrum is free and offered in this Guide. The Scrum framework, as outlined herein, is immutable. While
+implementing only parts of Scrum is possible, the result is not Scrum. Scrum exists only in its entirety
+and functions well as a container for other techniques, methodologies, and practices.
+
+### Acknowledgements
+
+#### People
+
+Of the thousands of people who have contributed to Scrum, we should single out those who were
+instrumental at the start: Jeff Sutherland worked with Jeff McKenna and John Scumniotales, and Ken
+Schwaber worked with Mike Smith and Chris Martin, and all of them worked together. Many others
+contributed in the ensuing years and without their help Scrum would not be refined as it is today.
+
+#### Scrum Guide History
+
+Ken Schwaber and Jeff Sutherland first co-presented Scrum at the OOPSLA Conference in 1995. It
+essentially documented the learning that Ken and Jeff gained over the previous few years and made
+public the first formal definition of Scrum.
+
+The Scrum Guide documents Scrum as developed, evolved, and sustained for 30-plus years by Jeff
+Sutherland and Ken Schwaber. Other sources provide patterns, processes, and insights that complement
+the Scrum framework. These may increase productivity, value, creativity, and satisfaction with the
+results.
+
+The complete history of Scrum is described elsewhere. To honor the first places where it was tried and
+proven, we recognize Individual Inc., Newspage, Fidelity Investments, and IDX (now GE Medical).
+
+```markdown
+© 2020 Ken Schwaber and Jeff Sutherland
+```
+
+This publication is offered for license under the Attribution Share-Alike license of Creative Commons,
+accessible at <https://creativecommons.org/licenses/by-sa/4.0/legalcode> and also described in summary
+form at <https://creativecommons.org/licenses/by-sa/4.0/>. By utilizing this Scrum Guide, you
+acknowledge and agree that you have read and agree to be bound by the terms of the Attribution
+Share-Alike license of Creative Commons.

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Status-Report.md

@@ -0,0 +1,164 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+_TODO: Copy this file for each status report. Fill in the information
+below. Email a notification to stakeholders when this report is made
+available._
+
+_TODO: Edit the rows in the following table. In some rows, multiple
+examples are given, you should select/edit only one._
+
+##### Project
+
+::[PROJECT-NAME](Home)
+
+##### Status Report Date
+
+::YEAR/MONTH/DAY
+
+##### Next Internal Release Number
+
+::X.Y.Z
+
+##### Release Date
+
+- ::Original estimate: YEAR/MONTH/DAY
+- ::Current estimate: YEAR/MONTH/DAY
+- ::Change Since Last Report: No change
+- ::Change Since Last Report: Slipped 2 days
+- ::Change Since Last Report: Saved 4 days
+
+##### Open Issues (needing development)
+
+- ::[17 defects](ISSUE-TRACKER-QUERY)
+- ::[8 enhancements](#tbd)
+
+##### Resolved Issues (pending verification)
+
+- ::[0 defects](#tbd)
+- ::[2 enhancements](#tbd)
+
+##### Closed Issues
+
+- ::[34 defects](#tbd)
+- ::[3 enhancements](#tbd)
+
+##### Resources used this period
+
+- ::PERSON-NAME: 18 hours.
+- ::PERSON-NAME: 15 hours.
+- ::PERSON-NAME: 10 hours.
+- ::PERSON-NAME: 12 hours.
+
+##### Status Summary
+
+- ::Project completed. This is the final status report.
+- ::Low risk. Project on track.
+- ::Medium risk. Problems are being dealt with.
+- ::High risk. Advice from management and stakeholders needed.
+- ::Project canceled. This is the final status report.
+
+##### Related Documents
+
+- [Project plan](Project-Plan) > [Resource needs](Resource-Needs)
+- [QA plan](QA-Plan)
+- [Glossary](Glossary)
+
+---
+
+**Process impact:** This helps keep stakeholders informed of project
+status so that they may correctly set expectations. Reasoned
+explanations of slight changes in schedule are much better than major
+unexplained slips.
+
+### Detailed Status
+
+TODO: Provide 1-4 paragraphs describing what has happened on this
+project. The text below is just an example, replace it with your own
+words.
+
+::This week we focused on...
+
+::Two major problems have been uncovered...
+
+::We are approximately 30% of the way through the project plan, and running about 2 days ahead of schedule...
+
+::The reason for the change in estimated release date is...
+
+::To stay on schedule, we have slipped enhancements [issue92](ISSUE-TRACKER-URL),
+[issue 101](ISSUE-TRACKER-URL), and [issue 129](ISSUE-TRACKER-URL) to a later
+release. These issues were selected because ...
+
+### Risk Management
+
+_TODO: List 3-10 of the top project risks that are still outstanding.
+This list may be an **updated** copy from [project plan](Project-Plan.html#Risk-Management)
+or a previous status report._
+
+- ::We could face major difficulties with the technology chosen for
+  this project. HOW TO AVOID/MITIGATE?
+- ::We could have low quality that demands significant rework. HOW TO
+  AVOID/MITIGATE?
+- ::We could incorrectly assess our progress until it is too late
+  to react. HOW TO AVOID/MITIGATE?
+- ::There may be a mis-alignment of stakeholder goals or expectations.
+  HOW TO AVOID/MITIGATE?
+
+### Upcoming Activity
+
+_TODO: Provide a few bullets describing what you will do between now and
+the next status report. The text below is just an example, replace it
+with your own words. Link to open issues in the issue tracker whenever
+possible._
+
+- ::Fix [issue 130](ISSUE-TRACKER-URL)
+- ::Fix [issue 133](ISSUE-TRACKER-URL)
+- ::Verify [issue 102](ISSUE-TRACKER-URL), [issue 103](ISSUE-TRACKER-URL),
+  [issue 107](ISSUE-TRACKER-URL), and [issue 109](ISSUE-TRACKER-URL)
+- ::Conduct regular team meeting: Tuesday, 1 hour
+- ::Conduct review meeting: Wednesday, 2 hours
+- ::Make major progress on COMPONENT
+- ::Work through next release checklist
+- ::Continue functional testing
+- ::Revise our integration procedure
+- ::Release version X.Y.Z
+
+### Tracking to Plan
+
+_TODO: Copy the Work Breakdown Structure from the [project plan](Project-Plan) and paste it here.
+Add a new column for actual effort spent so far by all team members._
+
+| Step       | Description                                                          | Planned Hours | Spent To-Date |
+| ---------- | -------------------------------------------------------------------- | ------------- | ------------- |
+| ::1.       | ::Preparation                                                        |               |               |
+| ::1.1.     | ::Developer training                                                 | ::30h         | ::0h          |
+| ::2.       | ::Inception                                                          |               |               |
+| ::2.1.     | ::Requirements gathering                                             | ::30h         | ::0h          |
+| ::2.2.     | ::Requirements specification                                         | ::20h         | ::0h          |
+| ::2.3.     | ::Requirements validation                                            | ::10h         | ::0h          |
+| ::3.       | ::Elaboration                                                        |               |               |
+| ::3.1.     | ::High-level design                                                  | ::5h          | ::0h          |
+| ::3.2.     | ::Low-level design (break down by component)                         |               |               |
+| ::3.2.A.   | ::Object design                                                      | ::10h         | ::0h          |
+| ::3.2.B.   | ::User interface design                                              | ::10h         | ::0h          |
+| ::3.2.C.   | ::Database design                                                    | ::3h          | ::0h          |
+| ::3.3.     | ::Design review and evaluation                                       | ::5h          | ::0h          |
+| ::4.       | ::Construction                                                       |               |               |
+| ::4.1.A.   | ::System implementation                                              |               |               |
+| ::4.1.A.1. | ::Implement Component 1                                              | ::25h         | ::0h          |
+| ::4.1.A.2. | ::Implement Component 2                                              | ::25h         | ::0h          |
+| ::4.1.A.3. | ::Implement Component 3                                              | ::25h         | ::0h          |
+| ::4.1.A.4. | ::Implement Component 4                                              | ::25h         | ::0h          |
+| ::4.1.A.5. | ::Integrate Components (mostly done during component implementation) | ::5h          | ::0h          |
+| ::4.1.B.   | ::Technical documentation (break down by component)                  | ::10h         | ::0h          |
+| ::4.1.C.   | ::User documentation (break down by component)                       | ::10h         | ::0h          |
+| ::4.1.D.   | ::Testing                                                            |               |               |
+| ::4.1.D.1. | ::Test planning                                                      | ::10h         | ::0h          |
+| ::4.1.D.2. | ::Test code implementation (break down by component)                 | ::30h         | ::0h          |
+| ::4.1.D.3. | ::Test execution                                                     | ::10h         | ::0h          |
+| ::4.2.     | ::Implementation review and evaluation                               | ::15h         | ::0h          |
+| ::5.       | ::Transition                                                         |               |               |
+| ::5.A.     | ::Release packaging                                                  | ::3h          | ::0h          |
+| 5.B.       | ::Documentation for other groups                                     | ::3h          | ::0h          |
+| ::6.       | ::Reflection                                                         |               |               |
+| ::6.1.     | ::Postmortem report                                                  | ::10h         | ::0h          |
+|            | Total                                                                | ::329 hours   |               |

vendor/git.knownelement.com/RWSCP/StartupStarterPackage/vendor/git.knownelement.com/RWSCP/ReadySET-Markdown/templates/Summary.md

@@ -0,0 +1,226 @@
+<!-- markdownlint-disable-next-line first-line-h1 -->
+
+### Mission and Scope
+
+_TODO: Answer these questions in your own words. This is condensed
+from the project [Home](Home)._
+
+#### What problem does this project address?
+
+::2-4 SENTENCE PROBLEM
+
+#### What is the goal of this project?
+
+::2-4 SENTENCE GOAL
+
+#### What is the scope of this project
+
+::2-4 SENTENCE SCOPE
+
+### Status
+
+_TODO: Briefly describe the status of this project. E.g., what phase are you in? And, what is your next major milestone? Detailed project status is written in the status reports, not here._
+
+::We have completed our second beta release and are currently working on
+adding more of the functionality described in our product
+[specification](SRS) and fixing defects.
+
+::The next major milestone is a third beta release with nearly complete
+functionality and a wider set of testers.
+
+#### Status reports
+
+- ::[Status report 1](status-report.html)
+- ::[Status report 2](status-report2.html)
+- ::Etc.
+
+### Resources and schedule
+
+_TODO: Briefly describe the project resources and schedule. This is
+condensed from the [project plan](Project-Plan), [resource needs](Resource-Needs),
+and [legal issues](legal.html) documents._
+
+#### What are the deadlines for this project?
+
+- ::DATE: MILESTONE
+- ::DATE: MILESTONE
+- ::DATE: MILESTONE
+- ::DATE: RELEASE-NUMBER
+
+#### Who is working on this project?
+
+- ::100% PERSON-NAME
+- ::100% PERSON-NAME
+- ::75% PERSON-NAME
+- ::33% PERSON-NAME
+
+#### What capital resources are allocated to this project?
+
+- ::HARDWARE
+- ::SOFTWARE LICENSE
+- ::FACILITIES
+
+#### What are the main legal concerns for this project?
+
+- ::Intellectual property: DESCRIPTION
+- ::Privacy and security: DESCRIPTION
+- ::Potential harm: DESCRIPTION
+
+### Requirements
+
+_TODO: Briefly describe the most important system requirements. This is
+condensed from the [user needs](User-Needs),
+[interview notes](interview-notes.html), [SRS](SRS),
+[use case suite](Use-Case-Suite),
+and [feature set](Feature-Set) documents._
+
+#### Who are the project stakeholders?
+
+- ::PROJECT CHAMPION / EXECUTIVE SPONSOR
+- ::DEPARTMENTS WITHIN YOUR COMPANY
+- ::CORPORATE PARTNERS
+- ::KEY CUSTOMERS
+
+#### What user needs have you gathered?
+
+- ::[User stories](LINK-TO-USER-STORIES)
+- ::[Interview notes](LINK-TO-INTERVIEW-NOTES)
+
+#### What are the requirements specifications?
+
+- ::[Use cases](LINK-TO-USE-CASES)
+- ::[Feature specifications](LINK-TO-FEATURE-SPECS)
+- ::[Environmental requirements](LINK-TO-ENV-REQ)
+- ::[Other requirements](LINK-TO-OTHER-REQ)
+
+### Design
+
+_TODO: Briefly describe the most important aspects of the design. This is
+condensed from the [design](Design) template and associated
+worksheets._
+
+#### What are your ranked design goals?
+
+1. ::Correctness
+   - ::This design correctly matches the
+     given requirements.
+2. ::Feasibility
+   - ::This design can be implemented and tested with the
+     planned amount of time and effort.
+3. ::Understandability
+   - ::Developers can understand this design and
+     correctly implement it.
+4. ::Implementation phase guidance
+   - ::This design divides the
+     implementation into components or aspects that can correspond to
+     reasonable implementation tasks.
+5. ::Modularity
+   - ::Concerns are clearly separated so that the impact of
+     most design changes would be limited to only one or a
+     few modules.
+6. ::Extensibility
+   - ::New features can be easily added later.
+7. ::Testability
+   - ::It is easy to test components of this design
+     independently, and information is available to help
+     diagnose defects.
+8. ::Efficiency
+   - ::The design enables the system to perform functions
+     with an acceptable amount of time, storage space, bandwidth, and
+     other resources.
+
+#### Where are your design documents?
+
+- ::[UML class diagram](LINK-TO-CLASS-DIAGRAM)
+- ::[UML class diagram](LINK-TO-CLASS-DIAGRAM)
+- ::[UML state diagram](LINK-TO-STATE-DIAGRAM)
+- ::[UML sequence diagram](LINK-TO-SEQUENCE-DIAGRAM)
+- ::[UML deployment diagram](LINK-TO-DEPLOYMENT-DIAGRAM)
+- ::[Other design](LINK-TO-OTHER-DESIGN)
+
+### Quality Assurance
+
+_TODO: Briefly describe your quality goals and how you will achieve them.
+This is condensed from the [QA plan](QA-Plan), [test
+suite](test-suite), and [test cases](test-cases.html) documents._
+
+#### What are your ranked quality goals?
+
+1. ::Correctness
+2. ::Robustness
+3. ::Accuracy
+4. ::Compatibility
+5. ::Usability
+6. ::Security
+7. ::Reliability
+8. ::Scalability
+9. ::Operability
+10. ::Maintainability
+
+#### What QA activities will you use?
+
+- ::Preconditions and assertions
+- ::Buddy reviews
+- ::Review meetings
+- ::Unit testing
+- ::System testing
+
+#### Where are the test cases?
+
+- ::[Test case](LINK-TO-TEST-CASE)
+- ::[Test case](LINK-TO-TEST-CASE)
+- ::[Test case](LINK-TO-TEST-CASE)
+- ::[Test case](LINK-TO-TEST-CASE)
+
+### Packaging, Delivery, and Deployment
+
+Where is the release checklist or sign-off document?
+
+::[Release checklist](LINK-TO-RELEASE-CHECKLIST)
+
+#### How is the product packaged and deployed?
+
+- ::Packaging: DESCRIPTION
+- ::Deployment: DESCRIPTION
+- ::[Release notes](LINK-TO-RELEASE-NOTES)
+
+#### How is the product installed?
+
+- ::System requirements: DESCRIPTION
+- ::STEP
+- ::STEP
+- ::STEP
+
+### User Support
+
+Where is the user documentation?
+
+- ::[User guide](LINK-TO-USER-GUIDE)
+- ::[User FAQ](LINK-TO-FAQ)
+
+#### How can users get technical support or report problems?
+
+- ::Support: DESCRIPTION
+- ::Issue tracking: DESCRIPTION
+
+### Glossary
+
+_TODO: Define any technical terms that you use above, if a new member of
+the team would not already know them. This is condensed from the
+[glossary](Glossary) documents._
+
+#### ::TECHNICAL TERM 1
+
+::DEFINITION
+
+#### ::TECHNICAL TERM 2
+
+::DEFINITION
+
+#### ::TECHNICAL TERM 3
+
+::DEFINITION
+
+#### ::TECHNICAL TERM 4
+
+::DEFINITION