docs: license under the Apache License 2.0

LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. 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.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor 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, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You 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 the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You 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 such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its 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. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

README.md

@@ -129,3 +129,8 @@ post-handoff streaming panics become terminal errors.
 - [Repository working agreement](AGENTS.md)
 - [Release workflow and GitHub App setup](docs/releases.md)
 - [Initial codec benchmarks](docs/benchmarks.md)
+
+## License
+
+Copyright 2026 Andrew Beck.
+Licensed under the [Apache License, Version 2.0](LICENSE).

docs/decisions/0023-consumer-readiness.md

@@ -235,6 +235,12 @@ Do not infer a license from dependencies or Beakley, and do not change repositor
 **Consequence:** it does not block the example or local validation.
 The exact license remains an open owner question, even if R1–R5 are approved.
 
+**Resolution (2026-10-02):** the owner chose the Apache License, Version 2.0, with Andrew Beck as copyright holder.
+The tracked LICENSE is the unmodified text from apache.org (SHA-256 `cfc7749b96f63bd31c3c42b5c471bf756814053e847c10f3eb003417bc523d30`), identical to the copy shipped by aws-lambda-go;
+the README carries the copyright line.
+The patent grant and contribution terms suit a security-path library, and every linked dependency is already Apache-2.0 or BSD.
+Repository visibility is unchanged.
+
 ## Original review validation and accepted execution order
 
 On Go 1.27.1 darwin/arm64, the current implementation passes `go test -race ./...`, `go vet ./...`, `go mod verify` and CGO-disabled Linux arm64/amd64 builds.

docs/decisions/README.md

@@ -30,7 +30,7 @@ Keep related decisions small enough to review and implement independently.
 | [0020: Cognito verification](0020-cognito-verification.md) | Accepted; verifier, cache and local validation implemented | How should direct JSON v2 access-token verification, client/resource restrictions and bounded JWKS caching compose with authn? |
 | [0021: Authorization rules](0021-authorization-rules.md) | Accepted; rules, examples and local validation implemented | What rule API, IAM/JWT predicates, failure semantics and consumer resolution/dispatch boundaries should authz expose? |
 | [0022: Streaming writer review](0022-streaming-writer-review.md) | Accepted; writer, public entry points and local validation complete; SDK deployment gate retained | Should streaming omit inferred lengths, how should empty Content-Encoding affect sniffing, and what SDK evidence remains missing? |
-| [0023: Consumer readiness](0023-consumer-readiness.md) | R1–R5 accepted; local implementation complete; external release prerequisites open | What complete consumer example, test support, deferred scope and release preparation should follow the implemented packages? |
+| [0023: Consumer readiness](0023-consumer-readiness.md) | R1–R6 accepted (Apache-2.0 license); local implementation complete; AWS deployment qualifications open | What complete consumer example, test support, deferred scope and release preparation should follow the implemented packages? |
 | [0024: Release automation](0024-release-automation.md) | Accepted; PR-only validation and organization credentials; App installation verified, release execution pending | How should release PRs, validation, credentials and initial versioning work? |
 | [0025: Main-branch protection](0025-main-branch-protection.md) | Proposed; awaiting owner review | Should the existing four CI checks and PR workflow be enforced before merging to main? |
 | [0026: Exported API review](0026-exported-api-review.md) | E1–E6 accepted and implemented in stacked PRs; E7 rejected | Which exported API changes does Google's Go style guidance support before the first release? |

docs/plan.md

@@ -325,11 +325,11 @@ Acceptance: examples work both in Lambda and ordinary HTTP applications, while a
 The user authorized a consumer-readiness design review on 2026-09-20.
 [Decision 0023](decisions/0023-consumer-readiness.md) records the code/documentation evidence, the Beakley failure-case coverage matrix and recommendations R1–R6.
 The user approved R1–R5 on 2026-09-20, including deferring exported `edgetest` helpers.
-The license/copyright choice remains open and does not block local work.
+The owner resolved R6 on 2026-10-02: Apache-2.0, with Andrew Beck as copyright holder.
 
 - [x] Review public composition, existing examples, fixture provenance, deferred features, package dependencies and CI/release readiness.
 - [x] Approve R1–R5: complete reference application, deferred edgetest exports, consumer outcomes, precise support matrix and v0 preparation.
-  The license choice remains open.
+  R6 (license) was resolved on 2026-10-02.
 - [x] Implement the reference application and consumer-testing guide using the existing public APIs, with local provider fixtures.
 - [x] Reconcile support/status documentation, update the indirect Smithy patch in isolation, and record incremental streaming baselines.
 - [x] Obtain actual GitHub CI evidence for the foundation PR;
@@ -347,7 +347,7 @@ No library API or transport policy changed.
 
 Full local race tests, vet, module verification, formatting, external consumption and Linux arm64/amd64 builds pass on Go 1.27.1 (2026-09-21).
 The subsequent authorized push and passing PR CI are recorded below.
-The license and deployment qualifications remain open;
+The deployment qualifications remain open;
 no release publication or AWS deployment occurred.
 
 Release automation follow-up (2026-09-21): the user selected Release Please and its GitHub Action, plus checks on PRs against main.
@@ -367,7 +367,9 @@ read-only checks confirmed the new credentials and repository installation permi
 Both organization secrets and their repository access are verified, and the old repository credentials have been removed.
 The workflow now reads both values from secrets.
 Token creation and Release Please execution still need a successful run after merge.
-No release was published, and the license and deployment qualifications remain open.
+No release was published, and the deployment qualifications remain open.
+Release Please has since run successfully and opened the v0.1.0 release PR;
+the license was chosen on 2026-10-02.
 
 ### 7. Pre-release exported API alignment
 

docs/release-readiness.md

@@ -35,12 +35,11 @@ No branch protection was configured.
 
 The [first main run](https://github.com/asteroid-computing/go-lambda-edge/actions/runs/36281181036) passed the original repeated validation but failed at App token creation: the repository installation lookup returned 404.
 The owner subsequently installed astrocompute-release-please, and installation access is now verified.
-After the workflow credential migration merges, verify token creation, the generated v0.1.0 release PR and its checks.
-Release Please has not yet executed successfully.
+Release Please has since executed successfully: the App opened [the v0.1.0 release PR](https://github.com/asteroid-computing/go-lambda-edge/pull/3), updates it on each main push, and its Go checks pass.
 
-The owner's license and copyright holder remain undecided.
-No license, repository visibility change, release tag or release publication has been performed.
-Resolve the license before external publication.
+The owner chose the Apache License, Version 2.0 on 2026-10-02, with Andrew Beck as copyright holder ([decision 0023 R6](decisions/0023-consumer-readiness.md#r6-obtain-the-owners-distributionlicense-choice-before-publication)).
+LICENSE is the unmodified canonical text.
+No repository visibility change, release tag or release publication has been performed.
 
 REST streaming's SDK deployment qualification remains open: local probes cannot establish AWS acceptance of the observed mode-header/connection behavior.
 Authoritative clarification or a separately approved live test is still needed.