Release: 1.0-v3-alpha4-b9

.gitconfig

@@ -0,0 +1,7 @@
+[commit]
+	gpgsign = true
+	signoff = true
+[merge]
+	conflictstyle = diff3
+[tag]
+	gpgsign = true

.github/AUTHORS.md

@@ -0,0 +1,16 @@
+## Elide Project Authors
+
+This file lists the Elide project authors. A contributor is considered an _author_ to the extent their contributions are
+significant enough to impact copyright considerations. This is left to the discretion of project authors but typically
+applies when a full feature is contributed by a single author.
+
+### Sam Gammon (@sgammon)
+
+Sam is the original author of Elide and the primary maintainer. He is the code-owner by default unless otherwise
+specified. All administrative rights have been delegated to second parties. The previous major versions of Elide, `v1`
+and `v2`, were authored by Sam in Python and Java/Kotlin before being retired for Elide's current implementation.
+
+### Dario Valdespino (@darvld)
+
+Dario is a core contributor and maintainer of Elide. He is the code-owner and author of the Express JS intrinsics and
+the serving engine.

.github/CLA.md

@@ -0,0 +1,30 @@
+# Elide Contributor License Agreement
+
+> Version `1.0`
+
+In order to clarify the intellectual property license granted with Contributions from any person or entity, Elide Ventures LLC ("Elide") must have a Contributor License Agreement ("CLA") on file that has been signed by each Contributor, indicating agreement to the license terms below. This license is for your protection as a Contributor as well as the protection of Elide; it does not change your rights to use your own Contributions for any other purpose.
+You accept and agree to the following terms and conditions for Your present and future Contributions submitted to Elide. Except for the license granted herein to Elide and recipients of software distributed by Elide, You reserve all right, title, and interest in and to Your Contributions.
+
+## Definitions.
+
+"You" (or "Your") shall mean the copyright owner or legal entity authorized by the copyright owner that is making this Agreement with Elide. For legal entities, the entity making a Contribution and all other entities that control, are controlled by, or are under common control with that entity are considered to be a single Contributor. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"Contribution" shall mean any original work of authorship, including any modifications or additions to an existing work, that is intentionally submitted by You to Elide for inclusion in, or documentation of, any of the products owned or managed by Elide (the "Work"). For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to Elide or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, Elide for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by You as "Not a Contribution."
+
+## Grant of Copyright License
+
+Subject to the terms and conditions of this Agreement, You hereby grant to Elide and to recipients of software distributed by Elide a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Your Contributions and such derivative works.
+
+## Grant of Patent License
+
+Subject to the terms and conditions of this Agreement, You hereby grant to Elide and to recipients of software distributed by Elide a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by You that are necessarily infringed by Your Contribution(s) alone or by combination of Your Contribution(s) with the Work to which such Contribution(s) was submitted. If any entity institutes patent litigation against You or any other entity (including a cross-claim or counterclaim in a lawsuit) alleging that your Contribution, or the Work to which you have contributed, constitutes direct or contributory patent infringement, then any patent licenses granted to that entity under this Agreement for that Contribution or Work shall terminate as of the date such litigation is filed.
+
+You represent that you are legally entitled to grant the above license. If your employer(s) has rights to intellectual property that you create that includes your Contributions, you represent that you have received permission to make Contributions on behalf of that employer, that your employer has waived such rights for your Contributions to Elide, or that your employer has executed a separate Corporate CLA with Elide.
+
+You represent that each of Your Contributions is Your original creation (see section 7 for submissions on behalf of others). You represent that Your Contribution submissions include complete details of any third-party license or other restriction (including, but not limited to, related patents and trademarks) of which you are personally aware and which are associated with any part of Your Contributions.
+
+You are not expected to provide support for Your Contributions, except to the extent You desire to provide support. You may provide support for free, for a fee, or not at all. Unless required by applicable law or agreed to in writing, You provide Your Contributions on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON- INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE.
+
+Should You wish to submit work that is not Your original creation, You may submit it to Elide separately from any Contribution, identifying the complete details of its source and of any license or other restriction (including, but not limited to, related patents, trademarks, and license agreements) of which you are personally aware, and conspicuously marking the work as "Submitted on behalf of a third-party: [named here]".
+
+You agree to notify Elide of any facts or circumstances of which you become aware that would make these representations inaccurate in any respect

.github/CODE_OF_CONDUCT.md

@@ -1 +1,76 @@
-**Coming soon.**
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+  advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies within all project spaces, and it also applies when
+an individual is representing the project or its community in public spaces.
+Examples of representing a project or community include using an official
+project e-mail address, posting via an official social media account, or acting
+as an appointed representative at an online or offline event. Representation of
+a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/CONTRIBUTORS.md

@@ -0,0 +1,23 @@
+## Elide Project Contributors
+
+This file lists the Elide project contributors. A contributor is someone who has contributed code in any substantive
+(non-trivial) capacity to the project, but is not necessarily considered a project author.
+
+### Sam Gammon (@sgammon)
+
+Sam is the original author of Elide and the primary maintainer. He is the code-owner by default unless otherwise
+specified. All administrative rights have been delegated to second parties.
+
+### Dario Valdespino (@darvld)
+
+Dario is a core contributor and maintainer of Elide. He is the code-owner and author of the Express JS intrinsics and
+the serving engine.
+
+### Damien O'Hara (@mfwgenerics)
+
+Damien is a contributor to Elide and additionally the author of several upstream components (Kapshot, Koala, etc.). He
+has also helped with extensive code review and thought partnership in the design of Elide.
+
+### Sebastian Schuberth (@sschuberth)
+
+Sebastian is a contributor to Elide.

.github/DCO.md

@@ -0,0 +1,34 @@
+Developer Certificate of Origin
+Version 1.1
+
+Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
+
+Everyone is permitted to copy and distribute verbatim copies of this
+license document, but changing it is not allowed.
+
+
+Developer's Certificate of Origin 1.1
+
+By making a contribution to this project, I certify that:
+
+(a) The contribution was created in whole or in part by me and I
+have the right to submit it under the open source license
+indicated in the file; or
+
+(b) The contribution is based upon previous work that, to the best
+of my knowledge, is covered under an appropriate open source
+license and I have the right under that license to submit that
+work with modifications, whether created in whole or in part
+by me, under the same open source license (unless I am
+permitted to submit under a different license), as indicated
+in the file; or
+
+(c) The contribution was provided directly to me by some other
+person who certified (a), (b) or (c) and I have not modified
+it.
+
+(d) I understand and agree that this project and the contribution
+are public and that a record of the contribution (including all
+personal information I submit with it, including my sign-off) is
+maintained indefinitely and may be redistributed consistent with
+this project or the open source license(s) involved.

.github/GOVERNANCE.md

@@ -0,0 +1,48 @@
+# Elide Project Governance
+
+**The Elide project is an open source software framework and runtime.** It is supported in part by [Elide][1] the
+company, which is known formally as _Elide Ventures, LLC_, a registered Delaware Limited Liability Company. Elide is
+also supported by contributions from independent engineers all over the world.
+
+Elide is a community project, and we welcome new contributors. We are committed to fostering a welcoming environment.
+We expect contributors to follow the [Contributor Covenant Code of Conduct][2] when discussing the project in any forum.
+
+## Project Leadership
+
+The Elide project is led by a core team of authors. The current authorship includes:
+
+- **Sam Gammon (@sgammon)**: Primary author and maintainer of Elide. Code-owner by default unless otherwise noted.
+- **Dario Valdespino (@darvld)**: Core contributor and maintainer of Elide. Code-owner and author of the Express JS
+  intrinsics and the serving engine.
+
+## Process and Governance
+
+Most design and development discussion happens via [GitHub Discussions][3] in an open manner where anybody can join in.
+Proposals typically form in that area and move to a place of consensus before any implementation work begins.
+
+Once a proposal has been made and a consensus has been reached, the core team will work with the author(s) to determine
+the best path forward. This may include the author(s) implementing the proposal, or it may fall to the core team to
+implement the proposal.
+
+### Code review
+
+During the development process, code review is done via GitHub pull requests. The core team reviews and merges all pull
+requests. Contributors may opt to keep their pull requests as drafts until such time as they are ready for review.
+
+### Developer Certificate of Origin (DCO)
+
+Elide requires that all contributors **sign their commits** with a valid cryptographic key registered to their GitHub
+account and email address. **All commits** must also carry a `Signed-off-by` tag in order to be considered for merge.
+This tag indicates that the contributor has read and agreed to the [Developer Certificate of Origin (DCO)][4].
+
+### Contributor License Agreement (CLA)
+
+Elide requires that all contributors agree to the terms of the [Elide Contributor License Agreement (CLA)][5]. This
+agreement clarifies intellectual property rights with regard to the Elide Framework and Runtime. It does not change your
+rights to use your own contributions for any other purpose.
+
+[1]: https://elide.dev
+[2]: ./CODE_OF_CONDUCT.md
+[3]: https://github.com/orgs/elide-dev/discussions
+[4]: ./DCO.md
+[5]: ./CLA.md

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,3 +1,11 @@
-## Pull Request Template
+## Summary
 
-**Coming soon.**
+Add a summary about your PR here.
+
+- [ ] feat: task list here
+
+## Changelog
+
+- feat(cli): added a thing
+- fix(dev): fixed a thing
+- chore: updated → `1.0`

.github/SECURITY.md

@@ -1 +1,97 @@
-**Coming soon.**
+# Security Policy: Elide Project
+
+> Version: `1.0`
+
+The Elide project and team take security very seriously; a big point of Elide's existence is a lack of isolation in
+other runtimes.
+
+Security issues are addressed promptly, and we continuously enhance project security where at all possible.
+
+## Supported Versions
+
+The Elide project is still early, but we intend to support the latest release and immediate past release.
+Once the project hits a level of stability suitable for a `1.0` version we will update this document and issue an
+LTS release.
+
+**Current version support matrix:**
+
+| Version         | Supported                                   |
+|-----------------|---------------------------------------------|
+| `v3-alpha4-*`   | :white_check_mark:                          |
+| `v3-alpha3-*`   | :white_check_mark: (Immediate past release) |
+| `v2` and before | :x: No support (ancient)                    |
+
+## Reporting a Vulnerability
+
+**We use GitHub issues to track vulnerabilities.** [Click here][9] to report a new issue.
+If you need to report a vulnerability privately, please use the email address on our main GitHub organization page
+(`apps` at `elide` dot `cloud`).
+
+If you need to provide secure information or your report needs to be encrypted, please use our PGP key, as listed on
+public key servers at the same email address.
+
+The Elide team will respond to vulnerabilities promptly. We will work with you to understand the scope of the issue and
+confirm the vulnerability.
+
+Once confirmed, we will work to address the issue and release a patch as soon as possible, including backporting to the
+latest release and immediate past release.
+
+Other (older) releases may receive backports on a case-by-case basis.
+
+## Security Advisories
+
+We will publish security advisories for any vulnerabilities that we address.
+
+These advisories will be published on our GitHub organization page and will be linked to from this document;
+the main `elide` repository will also have a link to this document.
+
+**At this time, no security advisories have been announced.**
+
+## Supply Chain Security
+
+Elide leverages [dependency verification][1] and [dependency locking][2] for all supported tooling; in any case, we
+select the minimum set of high-quality dependencies necessary to deliver a feature.
+
+In most cases, Elide only depends on standard libraries and language-endorsed extensions.
+
+### Dependency Verification and Locking
+
+Elide employs Gradle for dependency assurance, with `SHA-256` and `PGP` used for hashing and signing.
+
+### Attestations and Signing
+
+Elide ships with [SLSA attestations][3] for all modules, and embeds an SBOM with each binary artifact.
+Library releases are signed with PGP and published to Maven Central; all releases are additionally registered with
+[Sigstore][4].
+
+Container image bases carry SLSA attestations and are registered with Sigstore.
+
+## Continuous Updates
+
+Elide pins to the latest versions of all dependencies, by default, modulo (1) known vulnerabilities and (2) support for
+current features. Every attempt is made to use only stable dependencies; sometimes this is not possible with the speed
+at which development occurs on Elide.
+
+Elide employs Dependabot and Renovate for automated dependency updates, and we continuously monitor for and adopt new
+releases of all software Elide depends on.
+
+## Upstream Policies
+
+Elide is a meta-framework and runtime.
+
+When used as a **library or framework**, the bulk of Elide's functionality is implemented by [Micronaut][5] and
+[Netty][6]. When used as a **runtime**, Elide is built on top of [GraalVM][10].
+
+You can find their security policies [here][7] (Micronaut), [here][8] (Netty), and [here][11] (GraalVM), respectively.
+
+[1]: https://docs.gradle.org/current/userguide/dependency_verification.html
+[2]: https://docs.gradle.org/current/userguide/dependency_locking.html
+[3]: https://slsa.dev/
+[4]: https://www.sigstore.dev/
+[5]: https://micronaut.io/
+[6]: https://netty.io/
+[7]: https://github.com/micronaut-projects/micronaut-core/security/policy
+[8]: https://github.com/netty/netty/security/policy
+[9]: https://github.com/elide-dev/elide/issues/new
+[10]: https://www.graalvm.org/
+[11]: https://github.com/oracle/graal/security/policy