Prepare Notarius v0.8.1 source release

Update ConfigKit and PromptKit to their latest patches
Verify policy adoption and refine notice scope
2026-09-28 03:04:04 +00:00 · 2026-09-28 02:31:31 +00:00 · 2026-09-28 01:47:00 +00:00 · 2026-09-28 01:43:24 +00:00 · 2026-09-28 01:38:01 +00:00 · 2026-09-28 01:35:01 +00:00
32 changed files with 2529 additions and 633 deletions
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -1,5 +1,6 @@
-Please review `docs/development.md` for initial orientation in this repository
-and follow its task-specific reading guide.
+Start with `docs/development.md` for orientation and use its policy reading guide
+to select the policies applicable to the task. Do not read the entire suite by
+default.

-Review and follow `docs/policy/agents.md` before recommending, planning, or
-implementing any changes to this repository.
+Read and follow `docs/policy/agents.md` before recommending, planning, or
+implementing repository changes.
--- a/10
+++ b/10
@@ -5,15 +5,19 @@ Copyright (C) 2026 Eric Rakestraw
 SPDX-License-Identifier: GPL-3.0-or-later

 Notarius is free software: you can redistribute it and/or modify it
-under the terms of the GNU Lesser General Public License as published by
+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.

 The GNU General Public License version 3 is provided in LICENSE.

+Policy material copied or adapted from Standard Repository Policies remains
+licensed under CC-BY-SA-4.0. See docs/oss/attribution.md for the affected
+portions, upstream credit, and license links.
+
 Notarius 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 Lesser General Public License for more details.
+GNU General Public License for more details.

-Third-party code and assets are subject to their respective license terms.
+Third-party code and assets are subject to their respective license terms.
--- a/README.md
+++ b/README.md
@@ -60,3 +60,7 @@ Releases](docs/release.md).
 - [Developer guide](docs/development.md) — contributor orientation and
  validation guidance.
 - [Future work](docs/roadmap/future.md) — unimplemented ideas and priorities.
+
+Notarius is licensed under the [GPL v3.0 or later](COPYRIGHT).
+
+[Open Source attribution notices](docs/oss/attribution.md) are available.
--- a/docs/development.md
+++ b/docs/development.md
@@ -4,22 +4,41 @@ This is the first-read landing page for people and LLM coding agents working on
 Notarius. It provides a concise repository orientation and routes each kind of
 change to its canonical documentation.

-Notarius is a Go CLI for configured structured extraction workflows. Start with
-the [README](../README.md) for product context, [Architecture](policy/architecture.md)
-for system boundaries, and [Internal Overview](internal/overview.md) for the
-implemented component map.
+Notarius is a Go CLI for configured structured extraction workflows. The
+[README](../README.md) provides product context; [Architecture](policy/architecture.md)
+describes system boundaries, and [Internal Overview](internal/overview.md) maps
+implemented components. Read the documents applicable to your task.

 Read [Agent Policy](policy/agents.md) before recommending, planning, or
 implementing changes. It owns implementation discipline and local commit rules.

+## Policy Reading Guide
+
+| Policy | Read before… |
+| --- | --- |
+| [Policy set provenance](policy/meta.md) | Adopting policies, checking upstream revisions, or updating the adopted policy set. |
+| [Agents](policy/agents.md) | Recommending, planning, or implementing repository changes. |
+| [Architecture](policy/architecture.md) | Planning or changing application code or its structure. |
+| [Testing](policy/testing.md) | Selecting validation for code changes, or adding, changing, removing, or evaluating tests. |
+| [Documentation](policy/documentation.md) | Writing, revising, or reorganizing documentation. |
+| [OSS](policy/oss.md) | Adding or updating dependencies or incorporated third-party material, or changing licensing or attribution. |
+| [Release](policy/release.md) | Preparing or publishing a release, changing release procedures, or making versioning and compatibility decisions. |
+
+- Read applicable policies before making decisions they govern; multiple policies
+  may apply.
+- Select policies using the task triggers above. Follow cross-references to
+  relevant sections when needed to resolve a concrete question.
+- Reuse policies already available in context; reread when changed or no longer
+  available.
+- Expand reading when the task's scope expands.
+- When revising a policy itself, read that policy and any provisions elsewhere
+  affected by the revision.
+
 ## What To Read

 | When working on | Read | Why |
 | --- | --- | --- |
 | Finding the package or component that owns current behavior | [Internal Overview](internal/overview.md) | It is the implemented component inventory and routes to focused internals. |
-| Application shape, package boundaries, contracts, dependency direction, runtime guarantees, or safety properties | [Architecture](policy/architecture.md) and relevant [ADRs](adr/) | Architecture defines the intended system and its invariants; ADRs preserve significant decision rationale. |
-| Any documentation addition or revision | [Documentation Policy](policy/documentation.md) | It defines canonical homes, audiences, current-behavior rules, and maintenance requirements. |
-| Adding, changing, reviewing, or deleting tests | [Testing Policy](policy/testing.md) | It defines risk-based sufficiency, durable test boundaries, test-double guidance, and criteria for retaining tests. |
 | CLI composition or command behavior | [CLI Internals](internal/cli.md) and [CLI Reference](cli.md) | The internal guide owns composition and command flow; the reference owns public syntax. |
 | Building a subprocess caller or changing its result protocol | [Subprocess Consumer Guide](consumers/subprocess.md), [Complete D&D Consumer Guide](consumers/dnd-pipeline.md), [Run Result Receipt](integrations/run-result.md), and [CLI Internals](internal/cli.md) | These separate generic caller workflow, the complete D&D workflow, the durable receipt contract, and CLI implementation behavior. |
 | Configuration loading, resolution, or user-visible configuration behavior | [Configuration Internals](internal/configuration.md) and [Configuration](config.md) | The internal guide owns loading and resolution mechanics; the reference owns the configuration contract. |
@@ -28,7 +47,7 @@ implementing changes. It owns implementation discipline and local commit rules.
 | LLM clients, prompts, schemas, profiles, or scheduling | [LLM Runtime](internal/llm.md) | It documents the transport boundary and PromptKit integration. |
 | Output, cache, resume, or debug artifacts | [Run State Internals](internal/state.md), [Operations](operations.md), and [Configuration](config.md) | These separate implementation details, operator behavior, and configuration contracts. |
 | External input formats, artifact schemas, or durable output files | [Integration Contracts](integrations/) | Integration documents define external and durable data contracts. |
-| Release preparation, tagging, publication, or optional diagnostics | [Release Policy](policy/release.md) and [Source Releases](release.md) | Policy owns release requirements and completion; the runbook supplies the publication command and recovery procedure. |
+| Repository-specific release commands or diagnostics | [Source Releases](release.md) | The runbook supplies publication commands and recovery procedures. |
 | Proposed or unimplemented behavior | [Roadmap](roadmap/) | Future work belongs only in roadmap documentation until implemented. |

 For an existing subsystem, also inspect its focused tests and the package-local
--- a/docs/integrations/pkg-configkit.md
+++ b/docs/integrations/pkg-configkit.md
@@ -2,7 +2,7 @@

 Notarius uses the public root package
 [`gitea.maximumdirect.net/eric/ConfigKit`](https://gitea.maximumdirect.net/eric/ConfigKit)
-at v0.4.0 for version 5 configuration acquisition, imports, overlays, explicit
+at v0.4.2 for version 5 configuration acquisition, imports, overlays, explicit
 overrides, diagnostics, and safe inspection rendering.

 Notarius owns the typed document, domain defaults and validation, runtime
@@ -11,3 +11,8 @@ paths, and command discovery. It uses only ConfigKit's public path, result,
 diagnostic, and resolution-source APIs. Upstream documentation owns general
 ConfigKit semantics; [Configuration](../config.md) owns Notarius's file and
 operator contract.
+
+The v0.4.2 patch updates upstream release tooling and policy/licensing
+documentation without changing configuration behavior or the public API. See
+the canonical [ConfigKit attribution](../oss/attribution.md#configkit) for its
+license and notices.
--- a/docs/integrations/pkg-promptkit.md
+++ b/docs/integrations/pkg-promptkit.md
@@ -1,11 +1,11 @@
 # PromptKit Integration

 Notarius pins
-[`gitea.maximumdirect.net/eric/promptkit` v0.11.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0)
+[`gitea.maximumdirect.net/eric/promptkit` v0.11.2](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2)
 as its in-process prompt engine. The upstream
-[Go package consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/consumers/pkg-promptkit.md)
+[Go package consumer guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/docs/consumers/pkg-promptkit.md)
 owns the public engine API, and the upstream
-[format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md)
+[format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/docs/formats.md)
 owns prompt, profile, and schema file contracts.

 ## Supported Boundary
@@ -27,7 +27,7 @@ Notarius relies on the root `promptkit` package to:
  admission exhaustion through `ErrCapacityExceeded`.

 The pinned
-[`BackendLocal`, `LocalBackend`, and `WithBackend` API](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/backends.go)
+[`BackendLocal`, `LocalBackend`, and `WithBackend` API](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/backends.go)
 owns the registration and backend-capacity contract.

 For one completion, the adapter calls `PrepareExecution`, takes a
@@ -72,7 +72,7 @@ PromptKit capacity rejection into the provider-neutral Notarius
 `ErrLLMCapacityExceeded` contract. It may include the normalized selected
 backend ID in safe diagnostic context, without exposing PromptKit's capacity
 error type. PromptKit's built-in client retries eligible transient HTTP failures
-with its v0.11.0 default of two additional attempts per generation; Notarius
+with its v0.11.2 default of two additional attempts per generation; Notarius
 keeps pipeline-stage retries outside that completion boundary.

 The adapter projects built-in generation failures as the application-owned
@@ -94,7 +94,7 @@ configuration and deployment workflow are defined in
 [Operations](../operations.md#promptkit-profile-deployment).

 PromptKit owns `base_profile` resolution under its
-[pinned format rules](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/formats.md).
+[pinned format rules](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/docs/formats.md).
 Notarius records the selected leaf identity and resolved target without parsing
 or merging inheritance. An unset filesystem `api_key_env` is optional and may
 reach the provider without authorization, which can result in a 401 or 403.
@@ -133,7 +133,7 @@ PromptKit's opt-in `promptkit-openrouter-standard` and
 `promptkit-openrouter-auto` names provide name continuity within its
 selected-and-tested dependency scope, not a fixed model or provider availability
 guarantee. See the upstream
-[catalog compatibility policy](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/policy/release.md#catalog-profile-compatibility).
+[catalog compatibility policy](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.2/docs/policy/release.md#catalog-profile-compatibility).

 Use a complete operator-owned profile with explicit backend or endpoint, model,
 and settings when those choices must remain operator-controlled. The embedded
@@ -141,7 +141,7 @@ and settings when those choices must remain operator-controlled. The embedded
 external catalog profile. An upgrade updates Notarius's compiled-in catalog
 checkpoint identity so prior profile-source checkpoints are not reused.

-Notarius supports this boundary against PromptKit v0.11.0. Its fallback source,
+Notarius supports this boundary against PromptKit v0.11.2. Its fallback source,
 prepared-execution, inspection, and typed capacity APIs are used as public
 upstream contracts; other PromptKit APIs or file-format behavior are not
 implicitly supported. A dependency upgrade requires reviewing the adapter,
@@ -171,8 +171,8 @@ production prompts use PromptKit's bounded structural-repair contract; their
 current declaration is one additional repair attempt. Notarius retains the
 transport-neutral boundary and does not expose PromptKit types to modules.

-PromptKit v0.11.0 is licensed under
-[LGPL-3.0-or-later](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/LICENSE).
-Its accompanying [GPLv3 notice](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/COPYING)
-is incorporated by that license. This dependency change does not alter
-Notarius's source license or distribution workflow.
+The v0.11.2 patch updates upstream policy and licensing documentation without
+changing runtime APIs, profile settings, or dependency/catalog versions.
+See the canonical [PromptKit attribution](../oss/attribution.md#promptkit),
+[OpenRouter catalog notice](../oss/attribution.md#promptkit-openrouter-catalog),
+and [Rakestrawhome catalog notice](../oss/attribution.md#promptkit-rakestrawhome-catalog).
--- a/docs/operations.md
+++ b/docs/operations.md
@@ -371,7 +371,7 @@ Provider execution settings and the generation timeout come from the selected
 PromptKit profile. The invocation-only **--reasoning-effort** and
 **--clear-reasoning-effort** controls may replace or clear that profile setting
 for all LLM-backed calls in one run without changing the profile. PromptKit
-v0.11.0 also retries eligible transient HTTP failures with its built-in default
+also retries eligible transient HTTP failures with its built-in default
 of two additional attempts per generation. This retry work is separate from
 structural output repair, which happens within one structured-completion call. Its
 effective `structured_output_repair_attempts` limit is resolved from the
--- a/docs/oss/attribution.md
+++ b/docs/oss/attribution.md
@@ -0,0 +1,140 @@
+# Open Source Attribution Notices
+
+## Standard Repository Policies
+
+Material: policy documents under `docs/policy/`, adapted for this repository.
+Root `AGENTS.md` and the Policy Reading Guide in `docs/development.md`, copied
+without modification.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: CC-BY-SA-4.0
+
+License and notices: [CC BY-SA 4.0](licenses/CC-BY-SA-4.0.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843).
+
+## ConfigKit
+
+Selected module: `gitea.maximumdirect.net/eric/ConfigKit` at `v0.4.2`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL 3.0](licenses/LGPL-3.0.txt) |
+[GPL 3.0](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/67c03690181c5af8dde6be325abac241dae6732f/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/67c03690181c5af8dde6be325abac241dae6732f/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/67c03690181c5af8dde6be325abac241dae6732f).
+
+## PromptKit
+
+Selected module: `gitea.maximumdirect.net/eric/promptkit` at `v0.11.2`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: LGPL-3.0-or-later
+
+License and notices: [LGPL 3.0](licenses/LGPL-3.0.txt) |
+[GPL 3.0](licenses/GPL-3.0.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit/src/commit/12d6d80024e80c552d122a076c22429bf6f2f6c2/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/promptkit/src/commit/12d6d80024e80c552d122a076c22429bf6f2f6c2/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit/src/commit/12d6d80024e80c552d122a076c22429bf6f2f6c2).
+
+## PromptKit OpenRouter Catalog
+
+Selected module: `gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2` at `v2.20260926.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: MIT
+
+License and notices: [MIT](licenses/MIT.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/4f731d217e0bc39151c010f50fb5912706e7b6b3/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/4f731d217e0bc39151c010f50fb5912706e7b6b3/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit-backend-openrouter/src/commit/4f731d217e0bc39151c010f50fb5912706e7b6b3).
+
+## PromptKit Rakestrawhome Catalog
+
+Selected module: `gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2` at `v2.20260926.0`.
+
+Copyright (C) 2026 Eric Rakestraw
+
+SPDX-License-Identifier: MIT
+
+License and notices: [MIT](licenses/MIT.txt) |
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/48918a3ad39fd99843cda94a86133b1b3881d596/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/48918a3ad39fd99843cda94a86133b1b3881d596/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/src/commit/48918a3ad39fd99843cda94a86133b1b3881d596).
+
+## jsonschema
+
+Selected module: `github.com/santhosh-tekuri/jsonschema/v6` at `v6.0.2`.
+
+SPDX-License-Identifier: Apache-2.0
+
+License and notices: [Apache 2.0](licenses/Apache-2.0.txt) |
+[LICENSE](https://github.com/santhosh-tekuri/jsonschema/blob/29cbed948d24a04700eb94436416b18a07953b71/LICENSE).
+
+[Source](https://github.com/santhosh-tekuri/jsonschema/commit/29cbed948d24a04700eb94436416b18a07953b71).
+
+## Go text
+
+Selected module: `golang.org/x/text` at `v0.40.0`.
+
+Copyright 2009 The Go Authors.
+
+SPDX-License-Identifier: BSD-3-Clause
+
+License and notices: [BSD 3-Clause](licenses/BSD-3-Clause.txt) |
+[LICENSE](https://github.com/golang/text/blob/724af9c35838492dcaacc1ac51a8a0187c994c54/LICENSE) |
+[PATENTS](https://github.com/golang/text/blob/724af9c35838492dcaacc1ac51a8a0187c994c54/PATENTS).
+
+[Source](https://github.com/golang/text/commit/724af9c35838492dcaacc1ac51a8a0187c994c54).
+
+## go-yaml v3
+
+Selected module: `gopkg.in/yaml.v3` at `v3.0.1`.
+
+Copyright (c) 2006-2010 Kirill Simonov
+
+Copyright (c) 2006-2011 Kirill Simonov
+
+Copyright (c) 2011-2019 Canonical Ltd
+
+Copyright 2011-2016 Canonical Ltd.
+
+SPDX-License-Identifier: MIT AND Apache-2.0
+
+License and notices: [MIT](licenses/MIT-Kirill-Simonov.txt) |
+[Apache 2.0](licenses/Apache-2.0.txt) |
+[LICENSE](https://github.com/go-yaml/yaml/blob/f6f7691b1fdeb513f56608cd2c32c51f8194bf51/LICENSE) |
+[NOTICE](https://github.com/go-yaml/yaml/blob/f6f7691b1fdeb513f56608cd2c32c51f8194bf51/NOTICE).
+
+[Source](https://github.com/go-yaml/yaml/commit/f6f7691b1fdeb513f56608cd2c32c51f8194bf51).
+
+## go-yaml v4
+
+Selected module: `go.yaml.in/yaml/v4` at `v4.0.0-rc.6`.
+
+Copyright 2006-2010 Kirill Simonov
+
+Copyright 2011-2019 Canonical Ltd
+
+Copyright 2025 The go-yaml Project Contributors
+
+SPDX-License-Identifier: MIT AND Apache-2.0
+
+License and notices: [MIT](licenses/MIT-Kirill-Simonov.txt) |
+[Apache 2.0](licenses/Apache-2.0.txt) |
+[LICENSE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/LICENSE) |
+[NOTICE](https://github.com/yaml/go-yaml/blob/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125/NOTICE).
+
+[Source](https://github.com/yaml/go-yaml/commit/1c17b9cee72bf81ae73a8be50fbd7dd3a9985125).
--- a/docs/oss/licenses/Apache-2.0.txt
+++ b/docs/oss/licenses/Apache-2.0.txt
@@ -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.
--- a/docs/oss/licenses/BSD-3-Clause.txt
+++ b/docs/oss/licenses/BSD-3-Clause.txt
@@ -0,0 +1,27 @@
+Copyright 2009 The Go Authors.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
+met:
+
+   * Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+   * Redistributions in binary form must reproduce the above
+copyright notice, this list of conditions and the following disclaimer
+in the documentation and/or other materials provided with the
+distribution.
+   * Neither the name of Google LLC nor the names of its
+contributors may be used to endorse or promote products derived from
+this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
+"AS IS" AND ANY EXPRESS 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
+OWNER OR CONTRIBUTORS 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.
--- a/docs/oss/licenses/CC-BY-SA-4.0.txt
+++ b/docs/oss/licenses/CC-BY-SA-4.0.txt
@@ -0,0 +1,170 @@
+Creative Commons Attribution-ShareAlike 4.0 International
+
+ Creative Commons Corporation (“Creative Commons”) is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an “as-is” basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their terms and conditions, or any related information. Creative Commons disclaims all liability for damages resulting from their use to the fullest extent possible.
+
+Using Creative Commons Public Licenses
+
+Creative Commons public licenses provide a standard set of terms and conditions that creators and other rights holders may use to share original works of authorship and other material subject to copyright and certain other rights specified in the public license below. The following considerations are for informational purposes only, are not exhaustive, and do not form part of our licenses.
+
+Considerations for licensors: Our public licenses are intended for use by those authorized to give the public permission to use material in ways otherwise restricted by copyright and certain other rights. Our licenses are irrevocable. Licensors should read and understand the terms and conditions of the license they choose before applying it. Licensors should also secure all rights necessary before applying our licenses so that the public can reuse the material as expected. Licensors should clearly mark any material not subject to the license. This includes other CC-licensed material, or material used under an exception or limitation to copyright. More considerations for licensors.
+
+Considerations for the public: By using one of our public licenses, a licensor grants the public permission to use the licensed material under specified terms and conditions. If the licensor’s permission is not necessary for any reason–for example, because of any applicable exception or limitation to copyright–then that use is not regulated by the license. Our licenses grant only permissions under copyright and certain other rights that a licensor has authority to grant. Use of the licensed material may still be restricted for other reasons, including because others have copyright or other rights in the material. A licensor may make special requests, such as asking that all changes be marked or described.
+
+Although not required by our licenses, you are encouraged to respect those requests where reasonable. More considerations for the public.
+
+Creative Commons Attribution-ShareAlike 4.0 International Public License
+
+By exercising the Licensed Rights (defined below), You accept and agree to be bound by the terms and conditions of this Creative Commons Attribution-ShareAlike 4.0 International Public License ("Public License"). To the extent this Public License may be interpreted as a contract, You are granted the Licensed Rights in consideration of Your acceptance of these terms and conditions, and the Licensor grants You such rights in consideration of benefits the Licensor receives from making the Licensed Material available under these terms and conditions.
+
+Section 1 – Definitions.
+
+     a.	Adapted Material means material subject to Copyright and Similar Rights that is derived from or based upon the Licensed Material and in which the Licensed Material is translated, altered, arranged, transformed, or otherwise modified in a manner requiring permission under the Copyright and Similar Rights held by the Licensor. For purposes of this Public License, where the Licensed Material is a musical work, performance, or sound recording, Adapted Material is always produced where the Licensed Material is synched in timed relation with a moving image.
+
+     b.	Adapter's License means the license You apply to Your Copyright and Similar Rights in Your contributions to Adapted Material in accordance with the terms and conditions of this Public License.
+
+     c.	BY-SA Compatible License means a license listed at creativecommons.org/compatiblelicenses, approved by Creative Commons as essentially the equivalent of this Public License.
+
+     d.	Copyright and Similar Rights means copyright and/or similar rights closely related to copyright including, without limitation, performance, broadcast, sound recording, and Sui Generis Database Rights, without regard to how the rights are labeled or categorized. For purposes of this Public License, the rights specified in Section 2(b)(1)-(2) are not Copyright and Similar Rights.
+
+     e.	Effective Technological Measures means those measures that, in the absence of proper authority, may not be circumvented under laws fulfilling obligations under Article 11 of the WIPO Copyright Treaty adopted on December 20, 1996, and/or similar international agreements.
+
+     f.	Exceptions and Limitations means fair use, fair dealing, and/or any other exception or limitation to Copyright and Similar Rights that applies to Your use of the Licensed Material.
+
+     g.	License Elements means the license attributes listed in the name of a Creative Commons Public License. The License Elements of this Public License are Attribution and ShareAlike.
+
+     h.	Licensed Material means the artistic or literary work, database, or other material to which the Licensor applied this Public License.
+
+     i.	Licensed Rights means the rights granted to You subject to the terms and conditions of this Public License, which are limited to all Copyright and Similar Rights that apply to Your use of the Licensed Material and that the Licensor has authority to license.
+
+     j.	Licensor means the individual(s) or entity(ies) granting rights under this Public License.
+
+     k.	Share means to provide material to the public by any means or process that requires permission under the Licensed Rights, such as reproduction, public display, public performance, distribution, dissemination, communication, or importation, and to make material available to the public including in ways that members of the public may access the material from a place and at a time individually chosen by them.
+
+     l.	Sui Generis Database Rights means rights other than copyright resulting from Directive 96/9/EC of the European Parliament and of the Council of 11 March 1996 on the legal protection of databases, as amended and/or succeeded, as well as other essentially equivalent rights anywhere in the world.
+
+     m.	You means the individual or entity exercising the Licensed Rights under this Public License. Your has a corresponding meaning.
+
+Section 2 – Scope.
+
+     a.	License grant.
+
+          1. Subject to the terms and conditions of this Public License, the Licensor hereby grants You a worldwide, royalty-free, non-sublicensable, non-exclusive, irrevocable license to exercise the Licensed Rights in the Licensed Material to:
+
+               A. reproduce and Share the Licensed Material, in whole or in part; and
+
+               B. produce, reproduce, and Share Adapted Material.
+
+          2. Exceptions and Limitations. For the avoidance of doubt, where Exceptions and Limitations apply to Your use, this Public License does not apply, and You do not need to comply with its terms and conditions.
+
+          3. Term. The term of this Public License is specified in Section 6(a).
+
+          4. Media and formats; technical modifications allowed. The Licensor authorizes You to exercise the Licensed Rights in all media and formats whether now known or hereafter created, and to make technical modifications necessary to do so. The Licensor waives and/or agrees not to assert any right or authority to forbid You from making technical modifications necessary to exercise the Licensed Rights, including technical modifications necessary to circumvent Effective Technological Measures. For purposes of this Public License, simply making modifications authorized by this Section 2(a)(4) never produces Adapted Material.
+
+          5. Downstream recipients.
+
+               A. Offer from the Licensor – Licensed Material. Every recipient of the Licensed Material automatically receives an offer from the Licensor to exercise the Licensed Rights under the terms and conditions of this Public License.
+
+               B. Additional offer from the Licensor – Adapted Material. Every recipient of Adapted Material from You automatically receives an offer from the Licensor to exercise the Licensed Rights in the Adapted Material under the conditions of the Adapter’s License You apply.
+
+               C. No downstream restrictions. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, the Licensed Material if doing so restricts exercise of the Licensed Rights by any recipient of the Licensed Material.
+
+          6. No endorsement. Nothing in this Public License constitutes or may be construed as permission to assert or imply that You are, or that Your use of the Licensed Material is, connected with, or sponsored, endorsed, or granted official status by, the Licensor or others designated to receive attribution as provided in Section 3(a)(1)(A)(i).
+
+     b.	Other rights.
+
+          1. Moral rights, such as the right of integrity, are not licensed under this Public License, nor are publicity, privacy, and/or other similar personality rights; however, to the extent possible, the Licensor waives and/or agrees not to assert any such rights held by the Licensor to the limited extent necessary to allow You to exercise the Licensed Rights, but not otherwise.
+
+          2. Patent and trademark rights are not licensed under this Public License.
+
+          3. To the extent possible, the Licensor waives any right to collect royalties from You for the exercise of the Licensed Rights, whether directly or through a collecting society under any voluntary or waivable statutory or compulsory licensing scheme. In all other cases the Licensor expressly reserves any right to collect such royalties.
+
+Section 3 – License Conditions.
+
+Your exercise of the Licensed Rights is expressly made subject to the following conditions.
+
+     a.	Attribution.
+
+          1. If You Share the Licensed Material (including in modified form), You must:
+
+               A. retain the following if it is supplied by the Licensor with the Licensed Material:
+
+                    i.	identification of the creator(s) of the Licensed Material and any others designated to receive attribution, in any reasonable manner requested by the Licensor (including by pseudonym if designated);
+
+                    ii.	a copyright notice;
+
+                    iii. a notice that refers to this Public License;
+
+                    iv.	a notice that refers to the disclaimer of warranties;
+
+                    v.	a URI or hyperlink to the Licensed Material to the extent reasonably practicable;
+
+               B. indicate if You modified the Licensed Material and retain an indication of any previous modifications; and
+
+               C. indicate the Licensed Material is licensed under this Public License, and include the text of, or the URI or hyperlink to, this Public License.
+
+          2. You may satisfy the conditions in Section 3(a)(1) in any reasonable manner based on the medium, means, and context in which You Share the Licensed Material. For example, it may be reasonable to satisfy the conditions by providing a URI or hyperlink to a resource that includes the required information.
+
+          3. If requested by the Licensor, You must remove any of the information required by Section 3(a)(1)(A) to the extent reasonably practicable.
+
+     b.	ShareAlike.In addition to the conditions in Section 3(a), if You Share Adapted Material You produce, the following conditions also apply.
+
+          1. The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.
+
+          2. You must include the text of, or the URI or hyperlink to, the Adapter's License You apply. You may satisfy this condition in any reasonable manner based on the medium, means, and context in which You Share Adapted Material.
+
+          3. You may not offer or impose any additional or different terms or conditions on, or apply any Effective Technological Measures to, Adapted Material that restrict exercise of the rights granted under the Adapter's License You apply.
+
+Section 4 – Sui Generis Database Rights.
+
+Where the Licensed Rights include Sui Generis Database Rights that apply to Your use of the Licensed Material:
+
+     a.	for the avoidance of doubt, Section 2(a)(1) grants You the right to extract, reuse, reproduce, and Share all or a substantial portion of the contents of the database;
+
+     b.	if You include all or a substantial portion of the database contents in a database in which You have Sui Generis Database Rights, then the database in which You have Sui Generis Database Rights (but not its individual contents) is Adapted Material, including for purposes of Section 3(b); and
+
+     c.	You must comply with the conditions in Section 3(a) if You Share all or a substantial portion of the contents of the database.
+For the avoidance of doubt, this Section 4 supplements and does not replace Your obligations under this Public License where the Licensed Rights include other Copyright and Similar Rights.
+
+Section 5 – Disclaimer of Warranties and Limitation of Liability.
+
+     a.	Unless otherwise separately undertaken by the Licensor, to the extent possible, the Licensor offers the Licensed Material as-is and as-available, and makes no representations or warranties of any kind concerning the Licensed Material, whether express, implied, statutory, or other. This includes, without limitation, warranties of title, merchantability, fitness for a particular purpose, non-infringement, absence of latent or other defects, accuracy, or the presence or absence of errors, whether or not known or discoverable. Where disclaimers of warranties are not allowed in full or in part, this disclaimer may not apply to You.
+
+     b.	To the extent possible, in no event will the Licensor be liable to You on any legal theory (including, without limitation, negligence) or otherwise for any direct, special, indirect, incidental, consequential, punitive, exemplary, or other losses, costs, expenses, or damages arising out of this Public License or use of the Licensed Material, even if the Licensor has been advised of the possibility of such losses, costs, expenses, or damages. Where a limitation of liability is not allowed in full or in part, this limitation may not apply to You.
+
+     c.	The disclaimer of warranties and limitation of liability provided above shall be interpreted in a manner that, to the extent possible, most closely approximates an absolute disclaimer and waiver of all liability.
+
+Section 6 – Term and Termination.
+
+     a.	This Public License applies for the term of the Copyright and Similar Rights licensed here. However, if You fail to comply with this Public License, then Your rights under this Public License terminate automatically.
+
+     b.	Where Your right to use the Licensed Material has terminated under Section 6(a), it reinstates:
+
+          1. automatically as of the date the violation is cured, provided it is cured within 30 days of Your discovery of the violation; or
+
+          2. upon express reinstatement by the Licensor.
+
+     c.	For the avoidance of doubt, this Section 6(b) does not affect any right the Licensor may have to seek remedies for Your violations of this Public License.
+
+     d.	For the avoidance of doubt, the Licensor may also offer the Licensed Material under separate terms or conditions or stop distributing the Licensed Material at any time; however, doing so will not terminate this Public License.
+
+     e.	Sections 1, 5, 6, 7, and 8 survive termination of this Public License.
+
+Section 7 – Other Terms and Conditions.
+
+     a.	The Licensor shall not be bound by any additional or different terms or conditions communicated by You unless expressly agreed.
+
+     b.	Any arrangements, understandings, or agreements regarding the Licensed Material not stated herein are separate from and independent of the terms and conditions of this Public License.
+
+Section 8 – Interpretation.
+
+     a.	For the avoidance of doubt, this Public License does not, and shall not be interpreted to, reduce, limit, restrict, or impose conditions on any use of the Licensed Material that could lawfully be made without permission under this Public License.
+
+     b.	To the extent possible, if any provision of this Public License is deemed unenforceable, it shall be automatically reformed to the minimum extent necessary to make it enforceable. If the provision cannot be reformed, it shall be severed from this Public License without affecting the enforceability of the remaining terms and conditions.
+
+     c.	No term or condition of this Public License will be waived and no failure to comply consented to unless expressly agreed to by the Licensor.
+
+     d.	Nothing in this Public License constitutes or may be interpreted as a limitation upon, or waiver of, any privileges and immunities that apply to the Licensor or You, including from the legal processes of any jurisdiction or authority.
+
+Creative Commons is not a party to its public licenses. Notwithstanding, Creative Commons may elect to apply one of its public licenses to material it publishes and in those instances will be considered the “Licensor.” Except for the limited purpose of indicating that material is shared under a Creative Commons public license or as otherwise permitted by the Creative Commons policies published at creativecommons.org/policies, Creative Commons does not authorize the use of the trademark “Creative Commons” or any other trademark or logo of Creative Commons without its prior written consent including, without limitation, in connection with any unauthorized modifications to any of its public licenses or any other arrangements, understandings, or agreements concerning use of licensed material. For the avoidance of doubt, this paragraph does not form part of the public licenses.
+
+Creative Commons may be contacted at creativecommons.org.
--- a/docs/oss/licenses/GPL-3.0.txt
+++ b/docs/oss/licenses/GPL-3.0.txt
@@ -0,0 +1,674 @@
+                    GNU GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 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>.
--- a/docs/oss/licenses/LGPL-3.0.txt
+++ b/docs/oss/licenses/LGPL-3.0.txt
@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 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.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser 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
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.
--- a/docs/oss/licenses/MIT-Kirill-Simonov.txt
+++ b/docs/oss/licenses/MIT-Kirill-Simonov.txt
@@ -0,0 +1,20 @@
+Copyright (c) 2006-2010 Kirill Simonov
+Copyright (c) 2006-2011 Kirill Simonov
+
+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.
--- a/docs/oss/licenses/MIT.txt
+++ b/docs/oss/licenses/MIT.txt
@@ -0,0 +1,18 @@
+MIT License
+
+Copyright (c) 2026 Eric Rakestraw
+
+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.
--- a/docs/policy/agents.md
+++ b/docs/policy/agents.md
@@ -1,22 +1,17 @@
 # Agent Policy

-**Base Policy Version:** 1.1
+**Base Policy Version:** 1.3

-**Last Updated**: 2026-09-25
+**Last Updated**: 2026-09-28

-**Upstream Source:** `policy` commit `45591a79004c6811950f14dca554f6ff69b7f58e`.
-
-Notarius adaptations preserve operator choice, existing explicit contracts, and
-the deployment-permissions example below.
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/agents.md

 ## Purpose

-Agents working in this repository must read and adhere to the following house rules.
+Agents must read and follow these rules.

 ## Implementation Discipline

-Simplify the mechanism, not the user's choices.
-
 **KEY PRINCIPLES:** Write the simplest idiomatic code that satisfies the user's
 request. Do not implicitly strengthen requirements, restrictions, or guarantees
 beyond what the user actually requested.
@@ -46,25 +41,19 @@ idiomatic approach unless another path is expressly requested by the user.

 **An implementation detail is not repository policy.** Tests and documentation
 must not elevate incidental behavior into a durable guarantee or restriction
-unless that behavior was expressly selected as part of the contract. Existing
-explicit contracts remain authoritative; changing or weakening one requires a
-deliberate decision rather than being inferred from these principles.
-
-[ADR-0017](../adr/0017-defer-cache-access-policy-to-deployment.md) illustrates
-why Unix deployments own cache access policy through permissions, umask, setgid,
-and default ACLs. Notarius retains its separately adopted correctness boundaries.
+unless that behavior was expressly selected as part of the contract.

 ## Git Commit Policy

-By default, create a commit after completing each coherent unit of work, using a
+By default, commit each completed, nonempty unit of work using a
 concise, plain-English message describing what changed. This policy is standing
 authorization to create those local commits; a separate user request is not
 required. An explicit user instruction to leave work uncommitted takes precedence.

 A unit of work is a focused, reviewable outcome, including its relevant tests and
-documentation. Do not commit after every intermediate edit or create empty commits.
+documentation.
 Complete the appropriate validation before committing. If work is incomplete or
-validation is blocked, report that state rather than presenting it as completed.
+validation is blocked, report that state accurately.

 Before committing:

@@ -72,10 +61,10 @@ Before committing:
   changes. Identify changes that predate the current unit of work.
 2. Exclude secrets, local environment files, generated junk, and unrelated changes.
 3. Stage only the files or hunks belonging to the completed unit. Use `git add .`
-   only when every included change belongs to that unit. Do not disturb unrelated
-   staged or unstaged work.
-4. Review `git diff --staged` and run appropriate checks for the change. Do not
-   repeat checks already passed for unchanged content merely to create a commit.
+   only when every included change belongs to that unit. Preserve unrelated
+   staged and unstaged work.
+4. Review `git diff --staged` and run appropriate checks for the change. Reuse
+   successful checks for unchanged content.
 5. Review `git log --oneline -n 10` and use
   `git commit -m "<concise plain-English commit message>"`.
 6. Report the commit identifier and any remaining uncommitted work.
--- a/docs/policy/architecture.md
+++ b/docs/policy/architecture.md
@@ -1,24 +1,46 @@
-# Architecture
+# Architecture Policy

-**Base Policy Version:** 1.1
+**Base Policy Version:** 1.3

-**Last Updated**: 2026-09-25
+**Last Updated**: 2026-09-28

-**Upstream Source:** `policy` commit `45591a79004c6811950f14dca554f6ff69b7f58e`.
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/architecture.md

-Notarius adapts the base template to its fixed pipeline, artifact families,
-external adapters, state boundaries, and source-only distribution.
+## Purpose And Ownership

-This document defines the intended high-level architecture of Notarius and the
-invariants that changes must preserve. Implemented component details belong in
-[Internal Overview](../internal/overview.md) and its linked documents. The
-reasoning behind significant architectural choices belongs in
-[ADRs](../adr/).
+The adopted policy defines the application's purpose and the architectural
+constraints contributors must follow. It owns system boundaries, responsibility
+and dependency rules, established invariants, and explicit non-goals.

-An adopted constraint can govern future changes without implying that every
-component it could govern exists. Descriptions of implemented structure must
-remain accurate; proposals and transition status belong in roadmaps and ADRs.
-Constraints reflect selected requirements, not incidental implementation choices.
+Describe the concrete package inventory and implementation mechanics in internal
+documentation. Link to canonical public contracts for their exact behavior and
+to ADRs for decision rationale.
+
+## Architectural Approach
+
+Hexagonal architecture is strongly recommended, including encapsulating external
+integrations and APIs within internal adapters. Keep domain and application
+logic independent of external integration details, and make dependency direction
+clear in the adopted policy.
+
+Implement that separation with proportionate, idiomatic code. Choose interfaces
+and package layout to serve the application's actual boundaries. Use adapters
+for collaborators with external integration responsibilities.
+
+## Adopted Constraints And Implemented Structure
+
+Architectural constraints govern current and future development. Record
+implemented structure accurately, proposals and implementation status in the
+roadmap, and significant decisions and rationale in ADRs. Describe a target
+structure as implemented when its changes land.
+
+Constraints must reflect deliberately selected requirements and decisions.
+Do not promote incidental implementation choices into architectural invariants.
+
+Notarius's fixed pipeline, artifact-family boundaries, and deployment-owned
+cache permissions are established product decisions. The linked ADRs retain
+their rationale; the [internal overview](../internal/overview.md) inventories
+their implementation.

 ## System Shape

@@ -293,6 +315,21 @@ LLM provenance to make a run auditable after configuration changes. Manifests
 record identities and bounded validation summaries rather than secret, raw
 model, correction, or large payload content.

+## Trust Boundaries And Threat Scope
+
+Where useful, state the trust boundaries and threat scenarios relevant to the
+application's adopted requirements, along with scenarios it explicitly excludes.
+For example, distinguish handling untrusted application input from defending
+against a privileged actor concurrently modifying the host filesystem.
+
+Threat exclusions define the scope of the adopted requirements. Base defenses
+and guarantees on those requirements and raise unsettled scope for a deliberate
+decision under the [agent policy](agents.md).
+
+Keep this discussion proportionate to the application. Configuration,
+operations, and internal documents retain ownership of credential supply,
+runtime handling, and implementation mechanisms under the documentation policy.
+
 ## State, Output, And Safety

 Source material and model responses cross application validation boundaries.
--- a/docs/policy/documentation.md
+++ b/docs/policy/documentation.md
@@ -1,18 +1,15 @@
 # Documentation Policy

-**Base Policy Version:** 1.3
+**Base Policy Version:** 1.11

-**Last Updated**: 2026-09-25
+**Last Updated**: 2026-09-28

-**Upstream Source:** `policy` commit `45591a79004c6811950f14dca554f6ff69b7f58e`.
-
-Notarius retains subprocess-consumer ownership, the distinction between
-descriptive behavior and policy, and no placeholders for absent interfaces.
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/documentation.md

 ## Purpose

 This policy assigns each documentation topic to one canonical owner. Its goal is
-to keep Notarius documentation accurate, concise, discoverable, and resistant
+to keep this application's documentation accurate, concise, discoverable, and resistant
 to drift for users, operators, developers, integrators, and LLM coding agents.

 ## Core Rules
@@ -21,7 +18,7 @@ to drift for users, operators, developers, integrators, and LLM coding agents.

 Each authoritative fact belongs in one document. A non-owning document may give
 a short, stable summary for orientation, but it must link to the canonical owner
-instead of repeating volatile details.
+for volatile details.

 Volatile details include commands, flags, configuration fields and defaults,
 module keys, schemas, file names, paths, status codes, retry behavior, and
@@ -33,40 +30,26 @@ contract, maintain it only in the owning document.
 Outside `docs/roadmap/`, documentation describes implemented behavior only.
 Partial features may be described only to their implemented boundary.

-Architectural constraints may govern future changes without implying that the
-components or capabilities they would govern already exist. This does not permit
-describing a proposed system structure as implemented.
+Architectural constraints may govern future changes. Describe current structure
+from implemented behavior.

-ADRs may record an accepted architectural decision before implementation, but
-acceptance must not be presented as proof
-that the behavior exists. The roadmap owns implementation status and sequencing
-until the decision is implemented. Current architecture, user, operator,
-integration, and internal documentation are updated when the behavior lands.
-
-### Implementation Details And Policy
-
-Documentation must distinguish an explicit contract from an incidental
-implementation choice. Do not describe a restriction, guarantee, security
-policy, default, or limit as authoritative merely because the current code
-implements it. Documentation may accurately describe current behavior without
-making it a permanent requirement; distinguish descriptive behavior from
-normative policy. The
-[implementation-discipline rules](agents.md#implementation-discipline)
-own the criteria for adopting product restrictions and for elevating behavior
-into repository policy.
+ADRs may record an accepted architectural decision before implementation. The
+roadmap owns implementation status and sequencing until the decision is
+implemented. Current architecture, user, operator, integration, and internal
+documentation are updated when the behavior lands.

 ### Audience And Detail

 Write for the document's stated audience and include only the detail needed for
-its owned topic. User and operator docs should not expose implementation detail.
-Developer docs should link to user-facing and external contracts rather than
-restate them.
+its owned topic. Keep user and operator docs focused on using and operating the
+application. Developer docs should link to user-facing and external contracts
+for their definitions.

 ### Examples

 Complete copyable files belong in `examples/`. Documentation may use the
 smallest illustrative snippet needed to explain its owned topic, but should link
-to maintained examples instead of embedding a second complete copy.
+to maintained examples for complete copyable files.

 Examples must be valid, secret-free, and tested where practical. Commands and
 configuration used in documentation should match the application.
@@ -82,39 +65,41 @@ secret values.

 | Topic | Canonical owner | Owned content | Content owned elsewhere |
 | --- | --- | --- | --- |
-| Product orientation and minimal end-to-end quickstart | `README.md` | What Notarius is, why it is useful, one shortest successful invocation, and links onward. | Complete command reference, configuration reference, operational procedures, implementation detail. |
-| Contributor entry point | `docs/development.md` | Task-oriented reading guide, minimal contributor orientation, baseline validation commands, and links to canonical docs. | Package inventory, architecture rules, subsystem behavior, detailed change recipes. |
-| Application architecture policy | `docs/policy/architecture.md` | System shape, normative ownership, dependency direction, architectural boundaries, invariants, safety properties, and non-goals. | Concrete package inventory, implementation mechanics, contributor procedures, decision history, future work. |
-| Agent policy | `docs/policy/agents.md` | Implementation discipline, rules against invented restrictions or guarantees, and local commit authorization. | Application contracts, architecture, testing policy, and contributor procedures. |
-| Documentation organization | `docs/policy/documentation.md` | Documentation ownership, audience boundaries, maintenance rules, and ADR/document lifecycle. | Application architecture or product behavior. |
-| Testing policy | `docs/policy/testing.md` | Test philosophy, risk-based sufficiency, test boundaries, doubles, coverage guidance, regression-test policy, and criteria for adding, rewriting, or deleting tests. | Subsystem behavior, application contracts, subsystem-specific test inventories, and implementation plans. |
-| CLI contract | `docs/cli.md` | Commands, arguments, flags, invocation semantics, and exit codes. | End-to-end operating procedures, configuration field definitions, runtime filesystem layout, module implementation details. |
-| Configuration contract | `docs/config.md` | Discovery and precedence, file schema, fields, defaults, environment overrides, validation rules, and user-selectable module or validator keys. | Complete example files, CLI syntax, runtime state lifecycle, module implementation details. |
-| Operations | `docs/operations.md` | Runtime workflows, physical filesystem and state layout, output, cache, and debug handling, resume, cleanup, permissions, recovery, and operational limits. | CLI flag syntax, configuration field definitions, logical output schemas, implementation mechanics. |
-| Release policy | `docs/policy/release.md` | Versioning, compatibility, integrity, immutability, proportionate gate selection, publication controls, and release completion. | Concrete commands, product installation, historical notes, and CI implementation detail. |
-| Repository-specific release procedure | `docs/release.md` | Prerequisites, candidate preparation, publication command, automated guards, optional diagnostics, and failure recovery. | General release requirements, product installation guidance, historical summaries, and current compatibility contracts. |
-| Release-note history | `docs/releases/` | One checked-in historical summary for each source release made under the procedure. The note at the immutable tag is that release's record. | Current commands, behavior, contracts, and compatibility definitions. |
-| Public HTTP contract, if introduced | `docs/api.md` | Routes, authentication, media types, request and response schemas, status codes, pagination, caching, idempotency, rate limits, and HTTP retry semantics. | Client walkthroughs, upstream or downstream integration internals, implementation detail. |
-| Consumer guidance | `docs/consumers/` | Task-oriented subprocess use, minimal client examples, consumer responsibilities, and guidance for any future public package or API. | Wire semantics, external protocol contracts, internal implementation detail. |
-| External and durable integration contracts | `docs/integrations/` | External file formats and protocols, upstream and downstream contracts, logical output bundle paths and schemas, media types, and compatibility behavior. | Physical runtime placement and lifecycle, internal transformations, CLI syntax, configuration defaults. |
-| Implemented component inventory | `docs/internal/overview.md` | Current packages and components, their implemented responsibilities, and links to focused internal docs. | Normative architecture, contributor reading policy, external contracts. |
-| Internal component behavior | Other files under `docs/internal/` | Implementation flow, internal collaborators and state transitions, package-local guarantees and failures, and relevant tests. | Global architecture invariants, configuration definitions and defaults, external schemas, operator procedures. |
-| Architectural decision history | `docs/adr/` | Significant decisions, context, alternatives, rationale, consequences, and supersession history. | Current behavior reference, implementation status, task sequencing. |
-| Future work and implementation status | `docs/roadmap/` | Proposed, accepted, deferred, or rejected work; implementation status; sequencing; and task breakdowns. | Implemented behavior reference and architectural decision rationale. |
-| Complete copyable artifacts | `examples/` | Maintained configuration, inputs, and other files intended to be copied or run. | Field-by-field reference, command reference, prose explanation. |
+| Product orientation and minimal end-to-end quickstart | `README.md` | Purpose, value, shortest successful invocation, and navigation, including licensing and attribution. | Complete command reference, configuration reference, operational procedures, implementation detail. |
+| Contributor entry point | `docs/development.md` | Task-oriented reading guide, contributor orientation, baseline validation commands, and canonical links. | Package inventory, architecture rules, subsystem behavior, detailed change recipes. |
+| Application architecture policy | `docs/policy/architecture.md` | System shape, normative ownership, dependency direction, boundaries, invariants, safety properties, and non-goals. | Concrete package inventory, implementation mechanics, contributor procedures, decision history, future work. |
+| Policy-set provenance and upstream navigation | `docs/policy/meta.md` | Policy-set origin, local authority, adoption baselines, and upstream adoption and update links. | Task-specific reading triggers, detailed adoption procedures, and formal attribution notices. |
+| Agent policy | `docs/policy/agents.md` | Proportionate, idiomatic implementation; rules against inventing requirements, restrictions, guarantees, or policy. | Application contracts, architecture, testing policy, and contributor procedures. |
+| Documentation policy | `docs/policy/documentation.md` | Documentation ownership, audience boundaries, maintenance rules, and ADR/document lifecycle. | Application architecture or product behavior. |
+| Testing policy | `docs/policy/testing.md` | Test philosophy, risk sufficiency, boundaries, doubles, coverage, regressions, and test maintenance. | Subsystem behavior, application contracts, subsystem-specific test inventories, and implementation plans. |
+| Release policy | `docs/policy/release.md` | Versioning, compatibility, release integrity and immutability, release documentation, proportionate gates, publication controls, completion, and required versus optional checks. | Repository-specific commands, product installation guidance, CLI version semantics, historical release summaries, and CI implementation detail. |
+| Open source licensing and attribution policy | `docs/policy/oss.md` | License defaults and author choices, COPYRIGHT and attribution formats, license/notice links, discoverability, maintenance, and concrete exceptions. | Component entries, license texts, release commands, and dependency security review. |
+| Project copyright and license grant | `COPYRIGHT` | Project identity, copyright holders and years, SPDX expression, grant, warranty disclaimer, and third-party statement. | Complete license texts and upstream component attribution. |
+| Project license texts | `LICENSE` | Complete project and incorporated companion license texts, with required project-specific fields. | General licensing policy and upstream component attribution. |
+| Upstream component attribution | `docs/oss/attribution.md` | House Format component entries: identity, material scope and modifications where applicable, copyright, license, required notices, and license, notice, and source links. | General attribution policy, exception reasoning, research narratives, compliance commentary, and complete standard license texts. |
+| Standard dependency license texts | `docs/oss/licenses/` | Complete, verbatim standard license texts shared by applicable entries. | Project-specific upstream notices, attribution prose, and policy interpretation. |
+| Repository-specific release procedure | `docs/release.md` | Maintainer prerequisites, candidate preparation, validation and source-only publication commands and automated guards, optional consumer verification, and recovery. | General release requirements, product installation guidance, historical release summaries, and current compatibility contracts. |
+| CLI contract (if applicable) | `docs/cli.md` | Commands, arguments, flags, invocation semantics, and exit codes. | End-to-end operating procedures, configuration field definitions, runtime filesystem layout, module implementation details. |
+| Configuration contract (if applicable) | `docs/config.md` | Discovery, precedence, schema, fields, defaults, environment overrides, validation, and selectable module and validator keys. | Complete example files, CLI syntax, runtime state lifecycle, module implementation details. |
+| Operations (if applicable) | `docs/operations.md` | Runtime workflows, physical filesystem and state layout, output, cache and debug handling, resume, cleanup, permissions, recovery, and limits. | CLI flag syntax, configuration field definitions, logical output schemas, implementation mechanics. |
+| Subprocess consumer guidance | `docs/consumers/` | Task-oriented subprocess use, minimal examples, and consumer responsibilities. | CLI invocation semantics, external protocol contracts, internal implementation detail. |
+| Integration contracts for external components (if applicable) | `docs/integrations/` | External formats and protocols, upstream and downstream contracts, logical output paths and schemas, media types, and compatibility. | Physical runtime placement and lifecycle, internal transformations, CLI syntax, configuration defaults. |
+| Inventory of implemented internal packages | `docs/internal/overview.md` | Implemented packages and components, responsibilities, and links to focused internal docs. | Normative architecture, contributor reading policy, external contracts. |
+| Behavior and architecture of internal packages | Other files under `docs/internal/` | Implementation flow, collaborators, state transitions, package-local guarantees and failures, and relevant tests. | Global architecture invariants, configuration definitions and defaults, external schemas, operator procedures. |
+| Architectural decision records | `docs/adr/` | Significant decisions, context, alternatives, rationale, consequences, and supersession history. | Current behavior reference, implementation status, task sequencing. |
+| Future work and implementation status | `docs/roadmap/` | Proposed, accepted, deferred, or rejected work; implementation status, sequencing, and task breakdowns. | Implemented behavior reference and architectural decision rationale. |
+| Release-note history | `docs/releases/` | One checked-in summary per source release under the procedure; the note at its immutable tag is the release record. | Current commands, behavior, contracts, and compatibility definitions. |
+| Complete copyable artifacts | `examples/` | Maintained configuration, inputs, and other copyable or runnable files. | Field-by-field reference, command reference, prose explanation. |

-Documents that do not exist are required only when the corresponding interface
-or responsibility exists. Do not create placeholder API, consumer, integration,
-or operations documents for behavior the application does not have.
+Create supporting documents for existing interfaces and responsibilities when
+substantive content is available.

 ## Boundary Rules

 ### Orientation

-The README owns product orientation. The developer guide routes contributors.
-Architecture owns normative structure. Internal overview owns the current
-concrete component map. These documents may link to one another but should not
-maintain parallel package or behavior descriptions.
+Link among orientation, architecture, and internal documents; maintain each
+package or behavior description in its canonical owner.

 ### Commands, Configuration, And Operations

@@ -126,18 +111,23 @@ other contracts.

 ### Releases

-The [release policy](release.md) owns requirements and invariants; the
-[repository procedure](../release.md) owns the commands that satisfy them.
-Release notes are
-historical summaries, not current-state contract owners: the checked-in note at
-an immutable tag records that release, while current canonical documentation
-must change with the behavior it describes. Do not use a release procedure or
-note to weaken policy, redefine current contracts, or defer documentation updates.
+The release policy defines requirements and invariants that every release must
+satisfy. The repository-specific release procedure defines the commands and
+workflow maintainers use to satisfy that policy. Release notes record history
+at immutable tags. Maintain current behavior in its canonical documentation,
+update it with the corresponding behavior changes, and keep release procedures
+consistent with adopted policy.
+
+### Project Licensing And Upstream Attribution
+
+README and release documents link to the canonical licensing and attribution
+materials under the [OSS policy](oss.md). The release procedure owns URL
+construction and publication mechanics.

 ### Contracts And Implementation

 Integration and API documents define externally observable shapes and
-semantics. Internal documents explain how Notarius implements or consumes those
+semantics. Internal documents explain how this application implements or consumes those
 contracts. Internal docs may name a field, file, or protocol to identify a
 dependency, but must link to its canonical contract for the definition.

--- a/docs/policy/meta.md
+++ b/docs/policy/meta.md
@@ -0,0 +1,27 @@
+# Policy Set Provenance
+
+**Base Policy Version:** 1.0
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/meta.md
+
+## Origin And Local Authority
+
+This repository's policy set is adapted from
+[Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy).
+The adopted local policies govern work in this repository. Upstream revisions
+become local policy through deliberate adoption, preserving local decisions.
+Each policy's `Upstream Source` identifies its adopted baseline.
+
+## Adoption And Updates
+
+For policy adoption, upstream revision reviews, and updates, consult the
+[upstream adoption and update guide](https://gitea.maximumdirect.net/eric/policy/src/branch/main/docs/adoption.md).
+That guide and the reference example collection are maintained upstream and
+accessed through links. Keep discovery links pointed at the current upstream
+project and guide; keep adopted-source and example links pinned to commits.
+
+The local [developer guide](../development.md) routes tasks to applicable
+policies. Formal credit and licensing notices for the copied policy material
+belong in the local [attribution document](../oss/attribution.md).
--- a/docs/policy/oss.md
+++ b/docs/policy/oss.md
@@ -0,0 +1,218 @@
+# Open Source Licensing And Attribution Policy
+
+**Base Policy Version:** 1.8
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/oss.md
+
+## Purpose And Scope
+
+This policy defines project licensing conventions and a repeatable House Format
+for upstream attribution and license notices. It covers the project's own code
+and upstream components incorporated into or distributed with the application
+or library, including relevant transitive dependencies and copied code,
+documentation, or assets.
+Determine treatment from the component's terms and actual use.
+
+Consulting development guidance or using tooling alone does not require an
+attribution entry. Copying or adapting documentation for inclusion in the
+repository is different: preserve its applicable attribution and license terms.
+A material's role as development guidance does not exempt copied documents.
+Apply any express permissions for attribution-free reuse of example formatting.
+
+The baseline is a publicly available source repository with releases published
+alongside it. The format is independent of language, forge, and build system.
+It does not require attribution for every development tool, establish license
+compatibility, or resolve every obligation arising from use or distribution.
+
+## Canonical Locations
+
+The [documentation policy](documentation.md) assigns ownership:
+
+- `COPYRIGHT`: project name, copyright statements, SPDX expression, grant,
+  warranty disclaimer, and third-party statement.
+- `LICENSE` contains the complete, unmodified project license text, including
+  incorporated companion text. Dependency attribution does not relicense the project.
+- `docs/oss/attribution.md`: canonical component entries.
+- `docs/oss/licenses/`: complete, verbatim standard and applicable companion texts.
+
+Use recognizable license filenames, such as `Apache-2.0.txt` or `LGPL-3.0.txt`.
+A shared standard text may serve multiple entries. Keep explanations outside
+license texts and preserve distinct versions and exceptions.
+
+## Upstream Reference Examples
+
+Use the commit-pinned upstream examples to create actual project notices.
+Retain their links and keep the example collection upstream; keep applicable
+license texts locally as specified above.
+
+## Project Licensing
+
+Notarius's selected application grant is `GPL-3.0-or-later`, recorded in
+[COPYRIGHT](../../COPYRIGHT).
+
+Unless the author specifies otherwise, use **GPL version 3 or later**
+(`GPL-3.0-or-later`) for applications and **LGPL version 3 or later**
+(`LGPL-3.0-or-later`) for libraries. An author's explicit choice takes precedence:
+for example, a one-off script may use MIT. Such a choice requires no exception
+rationale, additional approval, or compensating controls under this policy.
+
+These defaults guide new license selection. Adopting this policy does not
+relicense existing code or override third-party terms. Preserve an existing
+license unless the author deliberately changes it. For mixed-purpose projects,
+follow the author's selected scope rather than inferring different licenses for
+individual packages.
+
+Use the upstream [application COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/application/COPYRIGHT)
+or [library COPYRIGHT example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/library/COPYRIGHT)
+to create the project’s root `COPYRIGHT` file.
+Use verified project names, contribution years, and copyright holders.
+For another selected license, adapt the grant, SPDX expression, disclaimer, and
+text references together to reflect the author's selected grant.
+
+For GPLv3 projects, copy the complete GPLv3 text into `LICENSE`. For LGPLv3
+projects, place the complete LGPLv3 text followed by the complete GPLv3 text in
+`LICENSE`; the LGPL incorporates the GPL terms. Keep the texts unmodified and
+place project-specific statements in `COPYRIGHT`. For the default grants, the
+grant and SPDX expression in `COPYRIGHT` must expressly identify `or-later`;
+follow the author’s choice if a different grant is selected.
+
+For other licenses, provide their complete text and any required project-specific
+fields; the standard reference collection remains unchanged. Keep `COPYRIGHT`,
+`LICENSE`, SPDX expressions, and README descriptions consistent with the actual
+grant. This convention introduces no blanket requirement for per-file headers;
+preserve notices or add them where the applicable terms require them.
+
+Identify separately licensed documentation or assets in the project grant, with
+links to their attribution and license information. An application's default
+code license does not override the terms of incorporated documentation.
+
+## Upstream Attribution House Format
+
+Begin `docs/oss/attribution.md` with `# Open Source Attribution Notices`,
+followed directly by component entries. These comprise the complete document.
+
+Each entry presents these five fields in order, with blank lines between them:
+
+1. **Project name** as a level-two heading. An optional identification paragraph
+   may follow, such as `Selected module: MODULE at VERSION.` with the module and
+   version in backticks. For copied documentation, a concise `Material:` sentence
+   may identify the affected files and whether they were adapted or copied
+   without modification. A factual qualifier such as `(transitive dependency)`
+   is permitted. Limit optional identification prose to factual component and
+   material scope.
+2. **Upstream copyright statement or statements**, preserving their wording.
+   Put multiple statements in separate paragraphs. Include this field when the
+   selected upstream source supplies an applicable statement; otherwise, omit it.
+3. **SPDX license identifier or expression**, when applicable, using
+   `SPDX-License-Identifier: EXPRESSION`.
+4. **License and notice links**, beginning `License and notices:`, separated
+   by ` | `, and ending with a period. Label local standard texts by license
+   name, such as `MIT` or `Apache 2.0`. Label upstream files by their actual
+   filenames, such as `COPYRIGHT`, `LICENSE`, `NOTICE`, or `PATENTS`.
+5. **Source repository link**, rendered exactly as `[Source](COMMIT_URL).`.
+
+Use the upstream [attribution example](https://gitea.maximumdirect.net/eric/policy/src/commit/a469273adda336625f96b9d769ea27b33999f146/examples/licensing/attribution.md)
+to create the project’s `docs/oss/attribution.md`.
+The example illustrates omitted fields and multiple copyrights and licenses.
+Replace the uppercase placeholders and illustrative URLs with actual component
+information. Local license links are relative to the destination
+`docs/oss/attribution.md`; copy the applicable texts into its `licenses/`
+directory. Do not copy example entries for components the project does not use.
+
+These are five fields, not a line limit. Omit the SPDX field when no applicable
+identifier exists; identify nonstandard terms through the linked text. Preserve
+licensing alternatives and exceptions, and record a selected option when
+relevant through the factual license identification. Do not invent an identifier
+or silently resolve an unsettled licensing choice.
+
+Keep entries factual. Do not add agent-authored explanations of license
+expressions, file-level license scope, research performed, retained source
+notices, or compliance conclusions. Avoid filler such as "none is invented
+here" and embellished link labels such as "upstream LICENSE", "additional
+patent grant", or "at the imported commit". Preserve actual required upstream
+content; this rule excludes editorial additions, not required notices. Policy
+interpretation and exception reasoning belong in the adopted OSS policy or an
+appropriate decision record, not the attribution document.
+
+## License Texts And Upstream Links
+
+Link standard license texts to their local copies. Link project-specific
+notices to their upstream copies. Every upstream repository or notice link must
+identify the exact commit corresponding to the
+imported version, including the selected source revision for copied material.
+
+Classify material according to its contents. An upstream `LICENSE`,
+`COPYING`, or similar file may contain project-specific notices or exceptions
+in addition to standard wording. Link both the local standard text and the
+commit-specific upstream file when needed. Make companion license texts directly
+reachable from the entry.
+
+For project-specific license and attribution material, this policy accepts
+direct links to the applicable upstream texts as satisfying reproduction,
+inclusion, or copy requirements. This is the adopted house interpretation.
+Agents must apply it without adding local-copy requirements or seeking repeated
+approval solely because a license uses those terms.
+
+This interpretation concerns notice reproduction. Concrete obligations such as
+marking modified files or supplying corresponding source receive their own
+applicable treatment. Preserve required notices already present in incorporated
+source files; the central attribution entry does not authorize stripping them.
+
+## Discoverability
+
+End the project's README with two friendly statements linking to its actual
+grant in `COPYRIGHT` and the attribution document. For example, for a project
+with the stated license:
+
+```markdown
+PROJECT_NAME is licensed under the [LGPL v3.0 or later](COPYRIGHT).
+
+[Open Source attribution notices](docs/oss/attribution.md) are available.
+```
+
+Each new checked-in release document and its hosted download page must end
+with links whose visible text is `COPYRIGHT | LICENSE | ATTRIBUTION`. Use absolute
+URLs to those files at the release's immutable tag or corresponding immutable source
+revision so the links work in both locations. This release navigation is distinct
+from upstream component links, which must use the imported commit.
+
+Reuse the checked-in release document as the hosted release body where supported.
+The release procedure owns concrete URLs and publication mechanics for delivering
+the links through the selected channel. Do not maintain duplicate notice lists.
+These conventions do not by themselves require separate downloadable license
+assets, source bundles, or a different binary package format.
+
+For Notarius, the [release runbook](../release.md) owns the concrete source-only
+publication process and release navigation.
+
+## Maintenance And Exceptions
+
+Update project licensing statements together when the author changes the grant
+or its scope. Update upstream notices in the change that adds, removes, upgrades,
+copies, or changes the distribution of a relevant component. Check the selected source's license
+and notices rather than assuming they are unchanged. Update affected entries,
+commit links, and texts; retain historical versions through Git.
+
+Check affected statements, faithful standard-text copies, and link destinations
+as part of ordinary change review. For a future release tag, check intended file
+paths against the candidate source; the tag need not resolve remotely before
+publication. Do not add publication-time network checks, CI polling, recurring
+legal sign-offs, mandatory scanners, or a full software bill of materials merely
+to implement this policy.
+
+Use the House Format routinely. Raise an exception only for a concrete obligation
+or unresolved rights question it does not address, including any arising from a
+particular distribution channel. Record the issue and selected treatment in the
+adopted OSS policy or an appropriate decision record. Attribution entries
+contain the resulting factual identification and required material, without
+repeating that reasoning. Resolve the issue before the affected use or
+distribution without reopening settled choices.
+Common ownership of projects is neither required nor a blanket exception.
+
+Apply the formatting convention prospectively. Do not rewrite published tags,
+notes, binaries, or checksums to retrofit it. Address actual omissions deliberately
+under the applicable terms and the [release correction policy](release.md#immutability-and-failure-recovery).
+Ordinary attribution maintenance and release links are preparation work, not new
+release approval gates.
--- a/docs/policy/release.md
+++ b/docs/policy/release.md
@@ -1,13 +1,10 @@
 # Release Policy

-**Base Policy Version:** 1.1
+**Base Policy Version:** 1.4

-**Last Updated**: 2026-09-25
+**Last Updated**: 2026-09-28

-**Upstream Source:** `policy` commit `45591a79004c6811950f14dca554f6ff69b7f58e`.
-
-Notarius adaptations: source-only delivery, lightweight tags, branch-before-tag
-publication, no prereleases, and the justified native command check below.
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/release.md

 ## Purpose

@@ -74,22 +71,26 @@ source tree. Use the complete version tag as the filename and begin with a
 title containing the product name and that exact version.

 Include a short summary and any relevant compatibility impact or upgrade
-instructions. Keep the note proportionate to the change. Fixed sections and
-explicit no-action boilerplate are not required. Existing historical notes
-need not be rewritten to adopt this format.
+instructions. Choose sections suited to the release and keep the note
+proportionate to the change.

 Keep exact current contracts in their canonical documents and update affected
 documentation with the behavior change. Link to those documents from the note
-where useful. A release note must not substitute for current documentation.
+where useful.
+
+Include the release footer defined by the [OSS policy](oss.md#discoverability)
+in each new release document. The [release procedure](../release.md) defines
+its concrete immutable-tag URLs. Notarius has no hosted download page; preparing
+these links with the note does not add a network check or approval gate.
+
 Do not create retrospective notes for the pre-procedure v0.1.0, v0.2.0, or
 v0.3.0 tags.

-Version selection, release-note content, and retirement of completed roadmaps
-are preparation responsibilities, not separate human approval gates. Preserve
-planned and deferred work and repair affected links when retiring roadmaps.
-Ordinary change review covers unintended files, credentials, and private data;
-do not repeat it as a release-specific sign-off. Ignored local files are not
-prohibited merely because they exist: they are not included in the tagged source.
+Handle version selection, release-note content, and retirement of completed
+roadmaps during preparation. Preserve planned and deferred work and repair
+affected links when retiring roadmaps. Reuse ordinary change review for
+unintended files, credentials, and private data. Scope release-content review
+to the tagged source.

 ## Candidate Validation

@@ -193,9 +194,8 @@ identify:
 1. prerequisites, primary branch, and authoritative remote;
 2. version and release-note preparation;
 3. one publication command with its selected local checks and automated guards;
-4. declared deliverables, required build targets, and automation responsibilities;
-5. the successful-push completion point and separately reported delivery status;
-   and
+4. source-only delivery, required build targets, and automation responsibilities;
+5. the successful-push completion point; and
 6. failure handling and ambiguous-push recovery.

 Use copyable commands where practical. Keep optional diagnostics and consumer
--- a/docs/policy/testing.md
+++ b/docs/policy/testing.md
@@ -1,19 +1,16 @@
 # Testing Policy

-**Base Policy Version:** 1.1
+**Base Policy Version:** 1.3

-**Last Updated**: 2026-09-25
+**Last Updated**: 2026-09-28

-**Upstream Source:** `policy` commit `45591a79004c6811950f14dca554f6ff69b7f58e`.
-
-Adopted without substantive deviations; Notarius's established contracts remain
-subject to [Agent Policy](agents.md).
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/testing.md

 ## Purpose

 Our tests exist to make **incorrect changes expensive and correct changes cheap**.

-We do not optimize for test count, line coverage, exhaustive isolation, or the fewest possible tests. We optimize for sufficient confidence in important behavior while imposing as little unnecessary friction as possible on future development.
+We optimize for sufficient confidence in important behavior while minimizing friction on future development.

 ## Every test has a cost

@@ -27,9 +24,9 @@ Evaluate that tradeoff at two levels:
 1. **Per test:** What realistic defect does this test detect, how consequential would that defect be, and is that protection worth the test's lifetime cost?
 2. **Across the suite:** Does this collection provide materially more confidence than a smaller, simpler suite would?

-Some friction is intentional. Tests should make dangerous changes—such as breaking compatibility, corrupting data, violating security boundaries, or reintroducing subtle bugs—require deliberate review. They should not make ordinary internal changes needlessly expensive.
+Some friction is intentional. Tests should make dangerous changes—such as breaking compatibility, corrupting data, violating security boundaries, or reintroducing subtle bugs—require deliberate review. Keep ordinary internal changes inexpensive.

-The cost of a test is not a reason to omit testing by default. Do not cite maintenance cost abstractly. When omitting a plausible test, be able to state why the protected failure is low-risk, already covered, obvious, reversible, or cheaper to detect elsewhere. For consequential, subtle, or difficult-to-observe behavior, the presumption should favor testing.
+Evaluate maintenance cost against the specific failure being protected. When omitting a plausible test, be able to state why the protected failure is low-risk, already covered, obvious, reversible, or cheaper to detect elsewhere. For consequential, subtle, or difficult-to-observe behavior, the presumption should favor testing.

 ## Default testing style

@@ -61,7 +58,7 @@ To the extent the following features are present in the application, prioritize
 6. Previously observed or plausible regressions.
 7. Representative integration and end-to-end workflows.

-A package-level contract is behavior relied upon by another package or major collaborator, not every observable detail of a package implementation.
+A package-level contract comprises behavior relied upon by another package or major collaborator.

 Choose tests for requested behavior and established contracts. Tests must not
 introduce new restrictions, guarantees, or threat scenarios merely because they
@@ -80,7 +77,8 @@ Do not add tests merely because a function, branch, or line exists. Do not add a

 ## Choose the right test boundary

-Test through the narrowest stable boundary that expresses the behavior clearly.
+Choose the narrowest stable boundary that expresses the behavior clearly and
+provides durable confidence with minimal incidental coupling.

 This is often the package API, but it may instead be:

@@ -88,22 +86,15 @@ This is often the package API, but it may instead be:
 - a package-level operation when several internal collaborators jointly produce the behavior; or
 - a larger integration boundary when correctness emerges from interaction with a real dependency.

-Do not force all behavior through oversized end-to-end tests. Do not test every private helper merely because it exists. Choose the boundary that gives durable confidence with the least incidental coupling.
-
 ## Test behavior, not implementation

-A test should protect a decision, contract, or invariant. A test must not memorialize the current implementation.
+A test should protect a selected decision, contract, or invariant.

-A test is suspect when its main purpose is to detect that someone:
+A test is suspect when it primarily detects changes to private constants or
+helpers, equivalent operation ordering, incidental formatting, equivalent
+algorithms, or internal structure that preserves behavior.

- changed an internal constant;
- renamed or split a private helper;
- reordered equivalent internal operations;
- changed incidental formatting;
- replaced one correct algorithm with another; or
- refactored internal object structure without changing behavior.
-
-Refactoring should normally require no test edits unless the refactored structure is itself part of the contract.
+Behavioral tests should normally remain stable through internal refactoring that preserves the contract.

 ## Expected effects of different changes

@@ -120,7 +111,7 @@ A test failing is not the same as a test needing to be edited. Many tests may co

 ## Separate mechanism from policy

-Configurable thresholds and defaults must not be duplicated throughout the test suite.
+Derive expectations from test-controlled configuration and relationships.

 For this example, assume the selected contract rejects a request to start more
 processes than a configured limit. Do not encode its production default indirectly:
@@ -156,18 +147,18 @@ limit solely to reproduce this example.

 The production default should be tested exactly only when its literal value is itself a public, operational, safety, protocol, or compatibility requirement.

-Apply the same rule to limits, timeouts, capacities, retry counts, and ranges: test relationships and behavior, not duplicated literals.
+Apply the same rule to limits, timeouts, capacities, retry counts, and ranges: test relationships and behavior.

 For established concurrency limits, distinguish these behaviors where the contract requires them:

 1. **Configuration handling:** values are accepted or rejected according to the selected contract.
 2. **Runtime enforcement:** observed peak concurrency never exceeds the configured limit.

-Use a test-controlled limit and measure the behavior relative to that limit. Do not merely assert today's default value.
+Use a test-controlled limit and measure the behavior relative to that limit.

-## Avoid semantic duplication across layers
+## Assign each behavior a test owner

-Each behavior should have a clear test owner. Where these layers exist:
+Where these layers exist, assign ownership as follows:

 - Parser tests own parsing cases.
 - Validator tests own validation rules.
@@ -177,7 +168,7 @@ Each behavior should have a clear test owner. Where these layers exist:
 - CLI tests own argument and configuration mapping.
 - End-to-end tests prove that representative assembled workflows work.

-Higher-level tests should not repeat every lower-level case. A single intentional policy change should not require unrelated edits across many test files.
+Give each layer its distinct responsibility and keep expectation updates localized to the contract being changed.

 ## Use test doubles deliberately

@@ -198,12 +189,9 @@ Mocks are appropriate when the contract includes facts such as:
 - an expensive API is called no more than once; or
 - a security audit event is emitted.

-Do not use mocks merely to isolate every object or reproduce the implementation's call graph.
-
 ## Go-specific guidance

-Select techniques according to the behavior and risk being tested. The following
-are options, not a checklist that every package or application must satisfy:
+Select techniques by behavior and risk:

 - table-driven tests for meaningful behavioral categories and boundaries;
 - `t.TempDir()` for real filesystem behavior;
@@ -213,19 +201,17 @@ are options, not a checklist that every package or application must satisfy:
 - integration tests where correctness depends on component interaction; and
 - a small number of representative end-to-end tests when assembled workflows expose meaningful risks not adequately covered at narrower boundaries.

-Avoid exact error-string assertions unless the wording is itself contractual. Prefer `errors.Is`, `errors.As`, typed errors, or structured error fields.
+Prefer `errors.Is`, `errors.As`, typed errors, or structured error fields. Use exact error-wording assertions only when the wording is contractual.

-At CLI boundaries, prefer exit classifications, structured output, and the smallest stable semantic fragment needed to identify the error. Do not snapshot complete diagnostic wording unless it is contractual.
+At CLI boundaries, prefer exit classifications, structured output, and the smallest stable semantic fragment needed to identify the error. Use complete diagnostic snapshots only when the wording is contractual.

 Golden-file updates must require an explicit local flag. CI must not update golden files automatically, and reviewers must inspect the semantic diff before accepting an update.

-Keep tests readable and direct. Test helpers and fixture frameworks must earn their own maintenance cost; do not build elaborate test infrastructure for small or isolated needs.
+Keep tests readable and direct. Size test helpers and fixture frameworks to the maintenance benefit they provide.

 ## Coverage

-Coverage is a diagnostic, not a target.
-
-Use it to find untested critical branches and unexpectedly weak packages. Do not write low-value tests solely to increase a percentage, and do not infer test quality from coverage alone.
+Use coverage to locate untested critical branches and unexpectedly weak packages. Evaluate test quality through meaningful behavioral protection and choose coverage according to risk.

 Pure domain logic will often warrant higher coverage than CLI wiring or external adapters. Uneven coverage is acceptable when it reflects risk.

@@ -233,33 +219,30 @@ Pure domain logic will often warrant higher coverage than CLI wiring or external

 A bug fix should normally include a regression test that fails before the fix and passes afterward.

-Retain the test when the defect could realistically recur and its consequences justify the ongoing cost. Prefer the narrowest durable test of the violated contract or invariant; do not preserve accidental implementation details from the original bug.
+Retain the test when the defect could realistically recur and its consequences justify the ongoing cost. Prefer the narrowest durable test of the violated contract or invariant.

-Not every historical bug requires a permanent test. If the underlying design has made recurrence impossible, the test has become redundant, or a stronger invariant test now subsumes it, remove or consolidate it.
+Remove or consolidate a test when the underlying design has made recurrence impossible, its protection is redundant, or a stronger invariant test subsumes it.

 ## Deleting or rewriting tests

-Tests are maintained code, not permanent historical artifacts.
-
-Delete or rewrite a test when its maintenance cost exceeds the confidence it provides.
+Delete or rewrite tests when maintenance cost exceeds their continuing
+protective value.

 Strong candidates include tests that:

 - require updates after harmless internal changes;
- directly assert private constants without protecting a real contract;
- duplicate the same policy across several layers;
+- assert incidental private constants or snapshot large amounts of incidental output;
 - verify mock choreography rather than outcomes;
- snapshot large amounts of incidental output;
- test trivial private helpers already exercised through stable package behavior;
- protect risks already covered more effectively elsewhere;
+- duplicate policy across layers, retest trivial helpers covered by package
+  behavior, or protect risks covered more effectively elsewhere;
 - are flaky, misleading, obsolete, or disproportionately expensive to diagnose; or
 - no longer correspond to a plausible failure mode.

-Several brittle tests may encode one genuine requirement. Replace them with one durable behavior-level or invariant test rather than preserving all of them.
+Several brittle tests may encode one genuine requirement. Consolidate them into one durable behavior-level or invariant test.

 ## Reviewing a proposed test

-Use the following questions when the value, boundary, or durability of a proposed test is not self-evident. Significant test additions should be reviewable against them, but written answers are not required for every routine test.
+Use the following questions when a proposed test needs closer evaluation. Significant test additions should be reviewable against them; written answers are optional for routine tests.

 1. Which requested behavior or established contract does it protect, and what realistic defect would violate it?
 2. How likely and consequential is that defect, and is it already protected elsewhere?
@@ -273,10 +256,9 @@ A test suite is sufficient when:

 - important requested behavior and established contracts are protected against realistic, consequential failures;
 - boundaries and component interactions have coverage where they introduce meaningful risks not protected elsewhere;
- failures provide useful signal rather than redundant noise;
- legitimate internal changes usually do not require test edits; and
+- failures provide useful, distinct signals;
+- tests usually remain stable through legitimate internal changes; and
 - additional tests would mostly repeat existing protection or preserve inconsequential implementation details.

-Sufficiency is a risk judgment, not a coverage percentage, test count, or required
-mix of testing techniques. Reassess it as the application, its users, and the
-consequences of failure evolve.
+Reassess sufficiency as the application, its users, and the consequences of
+failure evolve.
--- a/docs/release.md
+++ b/docs/release.md
@@ -22,6 +22,15 @@ required. Update current documentation with behavior changes; retire only
 completed roadmaps and preserve planned/deferred work. Commit the candidate on
 `main` after ordinary change review. There is no separate release sign-off.

+End each new release note with this footer, replacing `<version>` with the
+selected tag. Check that `COPYRIGHT`, `LICENSE`, and `docs/oss/attribution.md`
+exist in the candidate source before publication; the future tag need not
+resolve remotely during preparation.
+
+```markdown
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/notarius/src/tag/<version>/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/notarius/src/tag/<version>/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/notarius/src/tag/<version>/docs/oss/attribution.md)
+```
+
 ## Publish

 Run one command from the repository with the actual selected version:
--- a/docs/releases/v0.8.1.md
+++ b/docs/releases/v0.8.1.md
@@ -0,0 +1,23 @@
+# Notarius v0.8.1
+
+This patch release refreshes ConfigKit and PromptKit and makes the project's
+licensing, policy provenance, and upstream attribution easier to find.
+
+## Changes
+
+- Update ConfigKit to v0.4.2 and PromptKit to v0.11.2. These upstream patches
+  update release tooling and policy or licensing documentation without changing
+  the Notarius integration APIs or configured profile settings.
+- Refresh the PromptKit built-in profile-source checkpoint identity for the
+  selected dependency version. Existing checkpoints with the previous identity
+  are not reused; source-keyed chunk plans and published output are unaffected.
+- Align the repository policies with their pinned upstream source, add canonical
+  third-party attribution, and distinguish the GPL-3.0-or-later application grant
+  from the CC-BY-SA-4.0 terms for copied or adapted policy material. The root
+  GPL license text has been brought into the house-standard form without
+  changing the application grant.
+
+Notarius's CLI, configuration schema, subprocess receipt, and durable artifact
+formats have no intentional changes in this release.
+
+[COPYRIGHT](https://gitea.maximumdirect.net/eric/notarius/src/tag/v0.8.1/COPYRIGHT) | [LICENSE](https://gitea.maximumdirect.net/eric/notarius/src/tag/v0.8.1/LICENSE) | [ATTRIBUTION](https://gitea.maximumdirect.net/eric/notarius/src/tag/v0.8.1/docs/oss/attribution.md)
--- a/docs/roadmap/archive/implementation.md
+++ b/docs/roadmap/archive/implementation.md
@@ -0,0 +1,322 @@
+# Policy Alignment Implementation Plan
+
+## Purpose And Execution Contract
+
+Implement [Standard Repository Policy Alignment](policy.md). That feature
+roadmap owns the target policy choices and justified Notarius exceptions; this
+document owns implementation order. It replaces the completed kit-upgrade plan,
+not the implementation or contracts delivered by that earlier work.
+
+Each numbered stage is one bounded prompt for a gpt-5.6-terra coding agent.
+Complete stages in order. Inspect the worktree before each stage, preserve
+unrelated work, validate the resulting documentation, and commit the coherent
+stage under agent policy. Report changed files, checks, and any concrete blocker.
+Do not push, tag, publish, or retire unrelated roadmaps.
+
+This is a documentation/policy migration. Do not change application code,
+dependency pins, tests, release scripts, runtime contracts, or release gates.
+No production credentials or model calls are needed.
+
+## Fixed Sources And Adoption Rules
+
+Use upstream full commit
+`d84a38ebab26f048cafbe59a2246700c35d29843` throughout.
+Begin with its
+[adoption guide](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/adoption.md).
+Read applicable local policies through `docs/development.md`; when revising a
+policy, also read the upstream counterpart and affected cross-policy provisions.
+Do not reconstruct historical adoption baselines.
+
+Retrieve pinned files through public URLs or `git show` against that exact
+commit in an available checkout. Do not use an unverified sibling working tree
+or silently select newer upstream content. An unavailable source is a concrete
+blocker to copying it accurately, not a reason to invent its text.
+
+For every adopted policy:
+
+- Copy upstream wording verbatim except for required template removal and the
+  agreed, substantive project-specific customizations in the feature roadmap.
+- Retain its upstream Base Policy Version; set Last Updated to the actual date
+  the local document is adopted, not the review date by habit.
+- Add Upstream Source pointing to its own file at the full selected commit:
+  `https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/FILE.md`.
+- Remove the entire Base Policy Template section and perform its instructions.
+  Keep upstream generic rules outside it, including commit-pinned example links.
+- Explain substantive local exceptions briefly where they apply, or retain an
+  existing rationale/ADR link. Do not create an exception registry or preserve
+  stylistic paraphrases merely because they already exist.
+
+Current public project and adoption-guide links are discovery links; they may
+follow main. Source, example, and attribution links stay commit-pinned. Preserve
+accurate preexisting example pins supplied by the selected OSS template.
+Metadata must reflect only documents actually adopted by the current stage.
+The transition may temporarily contain mixed versions without claiming otherwise.
+
+## Stage 1 — Establish Provenance And Copied-Policy Licensing
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Establish the self-contained adoption and licensing foundation.
+One prompt limited to two short policies and their actual notice materials.
+
+**Read:** Selected upstream `docs/policy/meta.md` (1.0),
+`docs/policy/oss.md` (1.8), `COPYRIGHT`,
+`examples/licensing/policy-attribution.md`, and the adoption guide;
+local `COPYRIGHT`, `LICENSE`, and the feature roadmap.
+
+**Files:** Create `docs/policy/meta.md`, `docs/policy/oss.md`,
+`docs/oss/attribution.md`, and
+`docs/oss/licenses/CC-BY-SA-4.0.txt`; update `COPYRIGHT`.
+
+1. Adopt meta and OSS using the fixed-source rules. Keep public discovery URLs
+   in meta and link to the existing local developer guide and new attribution.
+   Point project-specific OSS context to Notarius's grant and release runbook;
+   do not import generic example projects.
+2. Create attribution with `# Open Source Attribution Notices` followed by
+   the canonical policy entry. Replace all three UPSTREAM_COMMIT placeholders.
+   Initially identify the two newly adopted policy files as adapted material.
+   Later stages expand this statement as their material is actually adopted;
+   do not imply that the older five files have already been refreshed.
+3. Copy the complete CC BY-SA 4.0 standard text from the pinned reference asset.
+   Preserve the canonical copyright/SPDX/notices/source arrangement and its
+   modification indication. Do not add research or compliance prose.
+4. Add a distinct scope statement to COPYRIGHT: policy material adapted from
+   Standard Repository Policies remains CC-BY-SA-4.0, with attribution defining
+   the affected material. Keep the existing GPL-3.0-or-later application grant,
+   warranty disclaimer, and third-party statement; leave root LICENSE unchanged.
+5. Do not create placeholder dependency entries. Dependency inventory is assigned
+   to Stages 4–5, and remains tracked here rather than asserted complete.
+
+**Acceptance:** Both policies have correct versions, date, file-specific source
+links, and no template-only section. All new relative links resolve. Attribution
+describes this stage's actual material, and code licensing is unchanged.
+
+**Validation:** Compare copied policy bodies and license text to the pinned
+sources; inspect deliberate substitutions. Run `git diff --check` and review
+the COPYRIGHT diff. No Go tests are needed.
+
+## Stage 2 — Standardize General Policies And Selective Orientation
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Adopt the general rules and their reading workflow. One prompt:
+three largely verbatim policy updates plus small orientation edits.
+
+**Read:** Local agent/testing/documentation policies; pinned upstream versions
+1.3, 1.3, and 1.11 respectively; upstream `agents/AGENTS.md` and the adoption
+guide's Policy Reading Guide; local `AGENTS.md` and `docs/development.md`.
+
+**Files:** Update `docs/policy/agents.md`, `testing.md`,
+`documentation.md`, root `AGENTS.md`, `docs/development.md`, and
+`docs/oss/attribution.md`.
+
+1. Adopt agent and testing substantive wording without local paraphrases.
+   Remove the redundant agent preamble, additional generic contract-preservation
+   prose, and ADR-0017 illustration. Its decision remains in architecture/ADR;
+   this is not permission to change it.
+2. Adopt documentation wording and ownership rows. Customize the consumer row
+   for existing subprocess guidance, not a hypothetical public Go API.
+   Omit the inapplicable HTTP contract row; preserve applicable CLI/config/
+   operations/integration/internal ownership. Remove the local duplicate
+   implementation-details-versus-policy section.
+3. Base root AGENTS.md on upstream `agents/AGENTS.md`, not upstream root
+   AGENTS.md. Preserve applicable existing instructions. Require orientation
+   through the developer guide and agent policy, but not full-suite reading.
+4. Add the adoption guide's seven-row selective Policy Reading Guide and its
+   selection/reuse/scope-expansion rules to docs/development.md. Retain existing
+   subsystem navigation and validation guidance; remove redundant competing
+   policy-trigger rows from the old table rather than creating two authorities.
+5. Expand the attribution material statement to identify the newly refreshed
+   policy files, adapted AGENTS.md, and copied policy-reading-guide portion of
+   docs/development.md. Do not license the unrelated remainder as copied policy.
+   Ensure the COPYRIGHT scope statement covers these identified portions.
+
+**Acceptance:** General rules match upstream, except required documentation
+ownership customization. All seven policy triggers are available; existing
+subsystem links still work. Reading is selective and public discovery is reachable.
+No test changes or stricter testing/commit requirements were introduced.
+
+**Validation:** Diff each policy against its pinned source, inspect AGENTS and
+developer-guide navigation, check attribution scope and relative links, and run
+`git diff --check`. Search affected files for leftover template instructions.
+
+## Stage 3 — Align Architecture And Release Policies Without Contract Changes
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Complete the customized policies and release navigation. One prompt
+focused on preserving existing decisions rather than redesigning them.
+
+**Read:** Local architecture and release policies, docs/release.md, relevant
+linked ADRs; pinned upstream architecture 1.3 and release 1.4. Use
+docs/internal/overview.md and existing canonical contracts only where needed to
+resolve an ownership question.
+
+**Files:** Update `docs/policy/architecture.md`, `docs/policy/release.md`,
+`docs/release.md`, and `docs/oss/attribution.md`.
+
+1. Adopt upstream general architecture ownership/approach guidance. Replace its
+   application-specific template guidance with Notarius's existing decisions.
+   Preserve the feature roadmap's enumerated pipeline, module, assets, domain,
+   identity, validation/retry, scheduling, configuration/provenance, state,
+   secret-handling, permissions, platform, and distribution contracts.
+   Keep existing application-specific sections unless an edit is necessary for
+   the adopted structure; do not turn this into a broad architecture rewrite.
+2. Adopt release wording with narrow project customizations: source only,
+   lightweight tags, main/origin, branch-before-tag, no prereleases, and no
+   hosted/asynchronous deliverables. Keep the native CLI/version check and
+   GOWORK=off rationale. Preserve the historical no-retrospective-notes decision.
+   Retain unchanged generic requirements verbatim.
+3. Add the OSS footer rule for new notes. Update the runbook with a copyable
+   three-link COPYRIGHT | LICENSE | ATTRIBUTION footer using absolute
+   `https://gitea.maximumdirect.net/eric/notarius/src/tag/<version>/...` paths.
+   Explain substitution of the selected release tag and local path checking.
+   Do not require a future tag to resolve or change publication scripts.
+4. Expand policy attribution to the complete adopted docs/policy set, retaining
+   the AGENTS/developer-guide scope from Stage 2 and any relevant adaptation
+   indications. All seven per-document source links now identify this adoption.
+
+**Acceptance:** Existing architecture and release choices are unchanged and their
+local reasons remain clear. Upstream generic wording is used where applicable.
+There are no new gates, platforms, artifacts, retrospective notes, or ADR edits.
+
+**Validation:** Review policy diffs specifically for added/removed requirements,
+check runbook agreement and affected links, and run `git diff --check`.
+Do not run a release/publication command. No runtime tests are warranted.
+
+## Stage 4 — Attribute The Kit Dependencies And Catalogs
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Add the first bounded group of component notices: ConfigKit,
+PromptKit, and their two backend catalogs. One prompt for four related projects.
+
+**Read:** Adopted OSS policy; go.mod/go.sum, resolved build dependency metadata;
+exact selected module COPYRIGHT/LICENSE/NOTICE/attribution files and VCS metadata.
+The reviewed pins are ConfigKit v0.4.1, PromptKit v0.11.1, and both catalog
+modules v2.20260926.0; verify the actual selected versions before writing.
+
+**Files:** Update `docs/oss/attribution.md`; add applicable texts under
+`docs/oss/licenses/`.
+
+1. Use read-only discovery such as `GOWORK=off go list -m -json all`,
+   `GOWORK=off go list -deps ./cmd/notarius`, and selected module contents.
+   Dependency acquisition may populate the module cache but must not change
+   dependency pins or introduce a local replace directive.
+2. Establish each selected version's exact source commit from module/VCS
+   metadata; peel annotated tags to commits. Do not substitute a tag object ID,
+   main-branch head, assumed sibling HEAD, or version tag in attribution URLs.
+3. Add factual House Format entries with supplied copyright statements,
+   applicable SPDX expressions, local standard-text links, required upstream
+   notice links, and exact-commit Source links. Preserve alternatives and
+   exceptions; determine scope from contents rather than filenames.
+4. Include LGPLv3 and its GPLv3 companion for the kit grants, and MIT for the
+   catalogs where confirmed by the pinned sources. Reuse shared local standard
+   texts; leave root project LICENSE unchanged.
+5. Inspect upstream dependency inventories for leads, but do not copy them
+   wholesale or treat them as substitutes for Notarius's own inclusion scope.
+   Hand remaining selected third-party components to Stage 5 through the stage
+   report, not editorial prose in attribution.
+
+**Acceptance:** These four components have verified source/notice links and
+complete applicable local texts. No dependency changes, guessed notices, or
+new distribution obligations were invented.
+
+**Validation:** Check exact revision correspondence, upstream filenames, every
+new local license link, and byte fidelity of standard texts. Run
+`git diff --check`; confirm go.mod/go.sum are unchanged. Report discovery
+commands and evidence; do not add a persistent inventory tool or audit artifact.
+
+## Stage 5 — Complete Attribution And Connect Reader Navigation
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Finish remaining incorporated-component coverage and canonical
+navigation. One prompt for the remaining small dependency set and doc links.
+
+**Read:** Adopted OSS policy, remaining selected module/source notices,
+README.md, integration guides, and repository evidence of copied code/assets.
+Start with jsonschema/v6 v6.0.2, x/text v0.40.0, yaml.v3 v3.0.1, and yaml/v4
+v4.0.0-rc.6, then resolve any additional actual incorporation revealed by
+Stage 4. A go.sum entry alone is not proof of incorporation.
+
+**Files:** Update `docs/oss/attribution.md`, applicable
+`docs/oss/licenses/*`, `README.md`,
+`docs/integrations/pkg-configkit.md`, and
+`docs/integrations/pkg-promptkit.md`.
+
+1. Inspect direct/transitive incorporation and copied material separately.
+   Apply the same exact-revision, factual-entry, and faithful-text rules as
+   Stage 4. Include relevant components, not every tool used in development.
+   Do not add generic entries with unresolved versions or copyrights.
+2. Use the OSS format for omitted copyright/SPDX fields where the source
+   supplies no applicable value. Preserve required project-specific notices.
+   Raise only a concrete unresolved obligation or rights issue; do not seek
+   blanket approval for the already selected linked-notice arrangement.
+3. End README with the prescribed GPL-v3-or-later COPYRIGHT link and the
+   Open Source attribution notices link. Do not imply that every incorporated
+   component or document has the application's license.
+4. Replace competing license/notice paragraphs in both integration guides with
+   concise links to the relevant canonical attribution anchors. Keep dependency
+   pins, behavior, compatibility, and public API links in the guides.
+5. Keep the attribution document to its title and factual component entries.
+   Do not include the inventory research, legal conclusions, or completion logs.
+   Do not copy unused upstream examples or standard licenses.
+
+**Acceptance:** Attribution covers the verified relevant components and copied
+policy material, with only applicable texts. README and integration links point
+to the canonical inventory; no user-visible API or dependency settings change.
+
+**Validation:** Review coverage against resolved dependencies and inspected
+copied-material evidence, validate affected relative/source links and text
+fidelity, and run `git diff --check`. No Go suite, scanner, or SBOM is required
+solely for documentation changes.
+
+## Stage 6 — Verify The Complete Adoption
+
+**Status:** Complete (2026-09-28).
+
+**Goal:** Perform the cross-document check and correct scoped documentation
+defects. One prompt; no fresh feature work or automated policy-sync system.
+
+**Read:** The feature roadmap; the seven resulting policies and their pinned
+sources; AGENTS.md, developer guide, COPYRIGHT, README, attribution/license
+materials, release runbook, and affected integration links.
+
+**Work and acceptance:**
+
+1. Compare all seven policies directly against the selected revision. Classify
+   remaining differences as metadata, template removal, required customization,
+   or a feature-roadmap exception. Replace accidental paraphrases with upstream
+   wording. Preserve established local requirements.
+2. Confirm versions 1.3/1.3/1.11/1.3/1.4/1.0/1.8 for agents, architecture,
+   documentation, testing, release, meta, and OSS respectively. Verify each
+   Upstream Source targets its own file and Last Updated reflects actual work.
+3. Confirm discovery links follow public project/main-guide URLs while adopted
+   source, examples, and component attribution remain accurately commit-pinned.
+   Check no placeholder UPSTREAM_COMMIT, template-only section, or local
+   checkout-dependent reference remains in adopted materials.
+4. Check selective policy routing, local authority, canonical documentation
+   ownership, copied-material scope/modification status, unchanged application
+   grant/root LICENSE, and directly reachable license/companion texts.
+5. Verify source-only publication, selected gates, optional diagnostics,
+   release completion, and prospective-only footer guidance still agree.
+   Do not modify historical notes, accepted ADRs, or scripts to satisfy this check.
+6. Review changed-file scope: only intended policy, notice, and supporting
+   documentation files should have changed. Correct in-scope documentation
+   defects, report unresolved concrete issues, and leave unrelated roadmap
+   retirement and release preparation to an explicit later request.
+
+**Validation:** Run `git diff --check`; inspect file/link destinations and
+compare local standard texts with verified sources. A search for
+`Base Policy Template` or `UPSTREAM_COMMIT` in adopted files should be empty;
+do not confuse explanatory roadmap text with an unfilled adopted template.
+No production tests, new test framework, recurring synchronization gate, or
+release execution is needed.
+
+## Open Questions
+
+None at the agreed baseline. Policy choices and exceptions are settled.
+A newly discovered concrete notice/source or rights issue should be reported
+with evidence and viable treatments rather than resolved by inventing a broader
+requirement. That contingency does not authorize reopening settled policies.
--- a/docs/roadmap/archive/policy.md
+++ b/docs/roadmap/archive/policy.md
@@ -0,0 +1,252 @@
+# Standard Repository Policy Alignment
+
+## Purpose
+
+Bring Notarius's adopted policies into alignment with Standard Repository
+Policies, using identical upstream language wherever a substantive,
+project-specific decision does not require customization. Preserve Notarius's
+application contracts, operator choices, selected code license, and source-only
+release process.
+
+This roadmap defines the agreed target and update scope. It does not itself
+adopt policies, alter runtime behavior, or authorize a release.
+
+## Selected Upstream Revision And Current Baseline
+
+The agreed review, performed on 2026-09-28, uses full upstream commit
+`d84a38ebab26f048cafbe59a2246700c35d29843` of
+[Standard Repository Policies](https://gitea.maximumdirect.net/eric/policy).
+Follow the [adoption and update guide at that revision](https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/adoption.md).
+Use that fixed revision for implementation, not whichever revision is then on
+`main`.
+
+The comparison is between the current Notarius documents and that revision.
+Historical adoption baselines need not be reconstructed or assessed. Introducing
+source metadata records the revision actually incorporated by this update, not
+a claim about previous adoptions.
+
+Notarius currently has five policies, no `meta.md` or `oss.md`, and no
+`docs/oss/` attribution collection. Its current agent entry point and developer
+guide provide orientation but lack the complete selective policy-reading guide.
+The project grant is GPL-3.0-or-later; root `LICENSE` contains the GPLv3 text.
+README licensing navigation and prospective release-footer instructions are
+missing.
+
+Public upstream discovery and attribution are now expressly approved. This
+supersedes the earlier instruction to omit references to the policy source;
+local checkout paths are neither necessary nor appropriate public references.
+
+## Alignment Rules
+
+- Start from the selected upstream wording, not a paraphrase of it. Adopt
+  non-substantive wording changes verbatim.
+- Retain local variations only for substantive, locally significant
+  requirements or decisions. Explain their purpose in the relevant policy
+  section or link to existing rationale; do not add a separate exception registry.
+- Follow each template's adoption instructions and remove its entire
+  `Base Policy Template` section. Replace required project-specific guidance
+  rather than leaving template instructions in an adopted policy.
+- Preserve deliberately selected contracts. Simplifying duplicate wording does
+  not authorize changing architecture, runtime behavior, or release mechanics.
+- Keep local policies authoritative. Upstream changes take effect only through
+  deliberate adoption; no automatic synchronization is introduced.
+
+## Target Policy Set And Justified Customizations
+
+| Local file | Current version | Target version | Required treatment |
+| --- | --- | --- | --- |
+| `docs/policy/agents.md` | 1.1 | 1.3 | Adopt substantive upstream wording verbatim. Remove redundant local preamble and the ADR-0017 illustration; architecture already owns the deployment-permissions decision. No substantive exception is needed. |
+| `docs/policy/architecture.md` | 1.1 | 1.3 | Adopt general purpose, ownership, architectural approach, and constraint-versus-implementation guidance while retaining the application-specific decisions described below. |
+| `docs/policy/testing.md` | 1.1 | 1.3 | Adopt substantive upstream wording verbatim. Existing risk-based testing remains intact; no project-specific exception or test rewrite is needed. |
+| `docs/policy/documentation.md` | 1.3 | 1.11 | Adopt upstream wording and licensing/provenance ownership rows. Customize consumer ownership for subprocess use and omit the inapplicable HTTP-contract row. Remove the duplicate local implementation-details-versus-policy section; agent policy owns that rule. |
+| `docs/policy/release.md` | 1.1 | 1.4 | Adopt upstream wording with the existing source-only choices and selected gates below. Add prospective OSS-footer guidance. |
+| `docs/policy/meta.md` | Absent | 1.0 | Add upstream substantive wording, including public discovery links, local authority, and local attribution navigation. |
+| `docs/policy/oss.md` | Absent | 1.8 | Add upstream substantive wording, commit-pinned example links, and required Notarius context through canonical documents. |
+
+No existing policy remains entirely unchanged: all five need wording and/or
+provenance updates. This does not imply new substantive testing or agent rules.
+
+### Architecture Exceptions
+
+The architecture template expressly requires application-specific content.
+Retain Notarius's fixed stage sequence rather than an arbitrary DAG,
+artifact-family ownership across stages, domain-neutral framework, inward
+dependency direction, external adapter boundaries, and content-only assets
+package. Retain adopted validation/retry, scheduling, identity, evidence,
+configuration, and provenance contracts.
+
+Preserve operator-owned filesystem access policy and the separately adopted
+correctness boundaries, cache/checkpoint eligibility, output/debug lifecycle,
+secret handling, and platform/distribution decisions. These express existing
+product requirements and ADR-backed choices, not stylistic variations.
+Use existing architecture and ADRs as their authority; this migration does not
+authorize strengthening or weakening them.
+
+Keep concrete package inventories and implementation mechanics in their current
+internal-documentation homes. No architecture redesign, new threat model, or
+new abstraction is part of this work.
+
+### Documentation Exceptions
+
+Notarius's consumer interface is primarily a subprocess CLI, not a public Go
+API. Retain `docs/consumers/` ownership for that workflow and its consumer
+responsibilities. Retain integration contracts as the owners of durable receipt
+and artifact shapes. No HTTP service documentation or placeholder API document
+is needed.
+
+Other editorial variations should use upstream language, including the current
+versus future behavior and accepted-ADR rules. Preserve their meaning without
+retaining duplicate local formulations.
+
+### Release Exceptions
+
+Preserve source-only delivery, lightweight tags, `main` on `origin`,
+branch-before-tag publication, and no prereleases. There are no binaries,
+hosted release objects, or asynchronous artifacts to publish or recover.
+Use upstream generic language where applicable, but do not introduce those
+channels or atomic-push requirements.
+
+Retain the native CLI build and injected-version check with `GOWORK=off`:
+it protects the executable entry point and release version, which package tests
+alone do not verify. Preserve its documented rationale and existing optional
+diagnostics. No additional validation gate is warranted.
+
+Retain the decision not to create retrospective notes for v0.1.0, v0.2.0, or
+v0.3.0. Apply new footer formatting prospectively; do not rewrite published
+history to retrofit it.
+
+## Provenance And Selective Reading
+
+Each of the seven policies must retain its actual target `Base Policy Version`,
+set `Last Updated` to its actual local adoption date, and add an
+`Upstream Source` link to its own source file. For example:
+
+```text
+https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/testing.md
+```
+
+Substitute the correct filename for each policy; do not link every header to
+the repository root or adoption guide. Retain provenance through subsequent
+local edits.
+
+Use current public discovery URLs in `meta.md`:
+
+- https://gitea.maximumdirect.net/eric/policy
+- https://gitea.maximumdirect.net/eric/policy/src/branch/main/docs/adoption.md
+
+Discovery links intentionally follow the current project and guide.
+Adopted-source, example, and attribution links identify immutable commits.
+The OSS template already includes commit-pinned example references; retain
+accurate pinned references rather than converting them to branch links.
+
+Adapt upstream `agents/AGENTS.md` into root `AGENTS.md`, preserving applicable
+existing instructions. Direct readers to `docs/development.md`, require agent
+policy before recommending/planning/implementing changes, and explicitly avoid
+reading the whole policy suite by default.
+
+Merge the upstream adoption guide's Policy Reading Guide into
+`docs/development.md`. Include all seven task triggers, especially policy
+updates, dependency/licensing changes, validation selection, and compatibility
+decisions. Preserve focused subsystem navigation without duplicating policy
+triggers across competing tables. Reuse policies already in context, expand
+reading when scope expands, and read affected cross-policy provisions when
+revising a policy.
+
+## Licensing And Attribution Target
+
+### Copied Policy Material
+
+Follow the selected upstream grant and canonical policy-attribution example:
+
+- Create `docs/oss/attribution.md` with the House Format title and insert the
+  Standard Repository Policies entry using the selected full commit for its
+  source, COPYRIGHT, and LICENSE URLs.
+- Identify actual copied/adapted material and modification status. Include
+  `docs/policy/`, the adapted root `AGENTS.md`, and the copied policy-reading
+  guide within `docs/development.md` as applicable. Do not claim unrelated
+  developer documentation was copied or relicense unrelated material.
+- Preserve supplied copyright, license, and disclaimer notices through the
+  specified arrangement; keep the entry factual rather than adding compliance
+  or research commentary.
+- Copy the complete, verbatim `CC-BY-SA-4.0.txt` to `docs/oss/licenses/`.
+- Add the separately licensed policy-material scope to `COPYRIGHT`, pointing
+  to attribution for exact scope and notices. Adapted policy material remains
+  CC-BY-SA-4.0; application code remains GPL-3.0-or-later. Leave root `LICENSE`
+  unchanged.
+
+The upstream licensing-format examples are CC0; using their original formatting
+alone does not require a separate attribution entry. This does not exempt
+copied policy prose from its stated terms.
+
+### Incorporated Dependencies And Assets
+
+Complete the previously planned inventory of relevant direct/transitive
+dependencies and copied code/assets using `go.mod`, resolved build dependencies,
+and exact pinned source contents. Neither direct imports alone nor every
+`go.sum` entry defines the inventory.
+
+Current starting points are ConfigKit v0.4.1, PromptKit v0.11.1, both PromptKit
+backend catalogs v2.20260926.0, jsonschema/v6 v6.0.2, x/text v0.40.0, yaml.v3
+v3.0.1, and yaml/v4 v4.0.0-rc.6. Verify actual incorporation, terms, notices,
+and exact commits; this list is not a pre-approved attribution inventory.
+
+Use the upstream OSS House Format without editorial elaboration. Copy only
+applicable standard and companion license texts, retaining their wording.
+Link component-specific notices and sources at the exact imported commit.
+Apply the upstream house interpretation of linked notices without inventing
+extra local-copy requirements, recurring approvals, or licensing conclusions.
+Handle a concrete uncovered obligation separately if one is discovered.
+
+### Navigation And Canonical Ownership
+
+- End `README.md` with the project-grant and attribution links prescribed by
+  OSS policy, using Notarius's GPL-3.0-or-later grant.
+- Update `docs/release.md` with a copyable prospective
+  `COPYRIGHT | LICENSE | ATTRIBUTION` footer using absolute Notarius URLs at
+  the release tag or corresponding immutable source revision. Check intended
+  local paths before publication; do not require an unpublished tag to resolve.
+- Update `docs/integrations/pkg-configkit.md` and
+  `docs/integrations/pkg-promptkit.md` to link to canonical attribution rather
+  than maintaining competing notice inventories. Keep behavioral/API references
+  in those integration guides.
+
+## Local Materials And Upstream-Only References
+
+Keep the seven adopted policies, adapted agent entry point, project-specific
+developer guide, actual notices, and applicable license texts locally.
+
+Keep the upstream README, root AGENTS.md, contributor guide, adoption guide,
+and example collection upstream. Link to them when appropriate instead of
+copying an additional documentation tree. Do not copy unused license texts,
+example projects, or placeholder documents. Root Notarius `AGENTS.md` is based
+on upstream `agents/AGENTS.md`, not upstream's own contributor instructions.
+
+## Implementation Ownership
+
+[Implementation Plan](implementation.md) owns the ordered work stages and their
+validation. This document owns the target end state, scope, and policy choices.
+
+## Scope Boundaries And Acceptance
+
+- No application code, dependency pins, tests, release scripts, or published
+  history change merely to adopt policy wording.
+- No new ADR, recurring policy-sync job, SBOM, scanner, blanket header sweep,
+  security audit, platform matrix, approval round, or release gate is required.
+- All seven policies use the selected versions and correct file-specific source
+  links, with actual adoption dates and no remaining template-only sections.
+- Non-substantive differences use upstream wording; substantive variations are
+  confined to justified Notarius responsibilities and decisions.
+- Orientation supports selective reading and public upstream discovery without
+  requiring a sibling checkout.
+- Attribution accurately identifies copied material, modifications, selected
+  dependency revisions, notices, and faithful local license texts. Application
+  and policy-material license scopes remain distinct.
+- Canonical navigation works without duplicate notice inventories, nonexistent
+  interface documents, or copied upstream guide/example collections.
+- Validate affected relative and public links, metadata targets, license-text
+  fidelity, and `git diff --check`. Ordinary document review is sufficient;
+  production model runs and new runtime tests are not warranted.
+- Resolve only concrete newly discovered rights or scope issues with the user;
+  do not reopen settled choices through blanket approval requirements.
+
+There are no blocking open design decisions at the agreed review baseline.
--- a/docs/roadmap/archive/remediation.md
+++ b/docs/roadmap/archive/remediation.md
@@ -24,7 +24,8 @@ The original finding below is retained as review context.
 ## Review Scope

 Reviewed implementation commits `31b48d2` through `7ac9d94` against
-[the feature roadmap](upgrade-kit.md) and [the implementation plan](implementation.md).
+[the feature roadmap](upgrade-kit.md) and the completed upgrade work recorded
+in those commits.
 The review covered configuration selection/defaults, production client wiring,
 error translation, execution observation, scheduler/debug propagation, current
 documentation, and tests. No production model calls were made.
--- a/docs/roadmap/archive/upgrade-kit.md
+++ b/docs/roadmap/archive/upgrade-kit.md
@@ -12,9 +12,9 @@ Adopt ConfigKit v0.4.0 and PromptKit v0.11.0 in one coordinated work set:
 Preserve application/framework boundaries and keep the two upgrades as distinct
 implementation workstreams. Neither requires a redesign of pipeline execution.

-This feature roadmap owns the target state and scope. The ordered work and
-stage-specific verification belong to the [implementation plan](implementation.md).
-Neither document authorizes release publication.
+This feature roadmap records the target state and scope. Its original
+implementation plan was completed and later replaced by a new work plan.
+Neither document authorized release publication.

 ## Current Baseline

@@ -249,7 +249,7 @@ new durable telemetry artifact, or add complete cost accounting.
 ### Documentation

 Update current documentation with the implementation, keeping canonical
-ownership under [Documentation Policy](../policy/documentation.md):
+ownership under [Documentation Policy](../../policy/documentation.md):

 - `docs/cli.md`: new flag on every affected command and matching help behavior.
 - `docs/config.md`: overlay terminology, directory layout, precedence, and the
@@ -296,7 +296,7 @@ retries and zero-value opt-out, and the dependency license change. PromptKit's
 catalogs are unchanged from v0.10.0; this upgrade adds no further profile-name
 migration or change to the D&D model defaults. Release preparation,
 tagging, and publication remain a separately requested task under
-[Source Releases](../release.md).
+[Source Releases](../../release.md).

 ## Acceptance And Verification

@@ -333,5 +333,5 @@ tagging, and publication remain a separately requested task under
  and the complete configuration with `--config-overlay development`.

 Use existing behavioral tests where possible, following
-[Testing Policy](../policy/testing.md). No live model calls or production API
+[Testing Policy](../../policy/testing.md). No live model calls or production API
 credentials are needed to validate this migration.
--- a/docs/roadmap/implementation.md
+++ b/docs/roadmap/implementation.md
@@ -1,403 +0,0 @@
-# ConfigKit And PromptKit Upgrade Implementation Plan
-
-## Purpose And Scope
-
-Implement [ConfigKit And PromptKit Upgrades](upgrade-kit.md). That document
-owns the desired behavior and operator migration; this document owns execution
-order. Each numbered stage is one bounded implementation prompt for a
-gpt-5.6-terra coding agent. Complete and validate stages in order.
-
-The inspected baseline pins ConfigKit v0.3.0 and PromptKit v0.10.0. Adopt
-exactly ConfigKit v0.4.0 and PromptKit v0.11.0, not whatever release happens to
-be newest during implementation. The release guides and public APIs are
-available in the sibling checkouts `../ConfigKit` and `../promptkit`; consult
-the target tags or downloaded modules if those checkouts have advanced.
-Build and test Notarius with `GOWORK=off`, without local dependency replacements.
-
-Read `docs/development.md` and all five policies in `docs/policy/` before
-implementation. In particular, simplify machinery without narrowing operator
-choices or elevating incidental details into requirements. Preserve existing
-contracts unless this roadmap expressly changes them. Use graph discovery for
-code, then inspect the relevant source and tests; locations below identify the
-reviewed baseline, not a requirement to preserve private file structure.
-
-## Decisions And Boundaries
-
- Configuration selection becomes `--config-overlay` and `overlays/<name>.yml`,
-  with no legacy alias or fallback. Keep empty, omitted, and `default` selection
-  behavior. Do not rename PromptKit profiles or pipeline/runtime profile types.
- Keep configuration version 5, source-file-relative declarations, CLI override
-  precedence, strict loading, inspection provenance, and redaction.
- Add only the global `promptkit.transient_retries` setting: nonnegative integer,
-  default **2 additional attempts**, explicit zero disables. No arbitrary cap,
-  per-binding setting, new CLI retry flag, or new total-deadline setting.
- PromptKit owns transient HTTP retries and structural repairs; Notarius keeps
-  stage/validator retry budgets and disposition unchanged. The existing shared
-  scheduler retains its completion-scoped permit through upstream waiting.
- Add provider-neutral failure metadata and request-local execution summaries.
-  Do not change domain artifacts, result receipts, prompt content, validators,
-  acceptance policy, or introduce a new telemetry service/artifact.
- Successful retry recovery is ordinary success, not a warning. Debug remains
-  opt-in. Existing token fields keep their meaning; observed usage is separate.
- No release, tag, push, source-license change, or binary packaging is part of
-  these stages. Record upgrade implications in current integration/operator
-  documentation; the eventual release note is a separate release task.
-
-For each stage, inspect the starting worktree, implement code with its focused
-tests and current-behavior documentation, run the listed relevant checks, and
-make one coherent local commit under agent policy. Report checks and any gaps.
-Do not repeat passed checks for unchanged content merely to make a commit.
-
-## Stage 1 — Cut Over Configuration Selection To Overlays
-
-**Status:** Completed 2026-09-25.
-
-**Goal:** Adopt ConfigKit v0.4.0 and finish its narrow operator-facing rename in
-one coherent change. This is one prompt: it is a naming migration, not a new
-configuration engine.
-
-**Inspect:** `internal/core/config/load.go`, `loaded_config.go`, configuration
-document/path/operational tests; `internal/cli/run.go`,
-`configkit_commands.go`, CLI configuration and example contract tests;
-`examples/profiles/development.yml`; upstream v0.4.0 migration guide.
-
-**Work:**
-
-1. Upgrade ConfigKit to v0.4.0 in `go.mod`/`go.sum`. Change `LoadOptions.Profile`
-   to `Overlay` and pass it into `configkit.Options[Document].Overlay`. Rename
-   only helpers, fields, locals, fixtures, and descriptions representing the
-   selected configuration layer.
-2. Replace `--config-profile` with `--config-overlay` for `run`, `config validate`,
-   `config effective`, `config explain`, and `pipelines list`. Update usage,
-   flag parsing, argument classification, explicit-empty handling, and error
-   paths together. Retired flags use normal unknown-flag behavior.
-3. Move `examples/profiles/development.yml` to
-   `examples/overlays/development.yml`; update maintained-example discovery and
-   selected-layer fixtures. Check file-relative paths after moving. Leave
-   `examples/llm-profiles/`, PromptKit profile sources, and ordinary explicit
-   imports alone unless an import actually points at the moved example.
-4. Consume upstream overlay provenance and diagnostic names directly. Do not
-   rebuild composition, implement directory fallback, or translate metadata
-   back to profile vocabulary.
-5. Update `docs/config.md`, `docs/cli.md`, `docs/integrations/pkg-configkit.md`,
-   `docs/internal/configuration.md`, relevant portions of `docs/internal/cli.md`,
-   and `docs/consumers/subprocess.md`. Review README, operations, and other
-   consumer examples for affected invocations. Explain the clean migration and
-   distinction from LLM profiles. Preserve accepted ADR-0018 and release history.
-
-**Acceptance:** All five commands select overlays consistently. Representative
-existing tests cover selected/base/empty/default behavior, overlay and explicit
-override precedence, declaration-relative paths, redacted effective/explain
-output, and source-aware failure labels. Include a selected legacy-only file
-case proving there is no silent fallback. Retain ordinary-import behavior and
-LLM profile coverage; do not duplicate every upstream parser case.
-
-**Validate:** `GOWORK=off go test ./internal/core/config ./internal/cli`,
-`GOWORK=off go mod tidy -diff`, `git diff --check`. Review occurrences of
-`config-profile` and `examples/profiles` in current docs/code semantically;
-historical docs and explicit legacy-rejection tests are not defects.
-
-## Stage 2 — Upgrade The PromptKit Runtime Baseline
-
-**Status:** Completed 2026-09-25.
-
-**Goal:** Adopt the compatible upstream dependency and document its changed
-default before adding Notarius controls. One small prompt.
-
-**Inspect:** `internal/framework/llm/promptkit_client.go`, asset/profile identity
-helpers and tests, `go.mod`, and upstream v0.11.0 release/consumer documentation.
-
-**Work:**
-
-1. Pin PromptKit v0.11.0 and tidy. Keep the Go version and provider catalog
-   selections unless the actual dependency graph requires a change; the target
-   release does not require either. Do not alter embedded D&D model settings.
-2. Update `promptKitBuiltinProfileCatalogID` to the v0.11.0 identity in accordance
-   with the existing checkpoint fingerprint convention. No other cache policy
-   change or blanket invalidation is part of this work.
-3. Update the pinned integration links in `docs/integrations/pkg-promptkit.md`,
-   including the relocated upstream `docs/policy/release.md`. Record the
-   LGPL-3.0-or-later dependency license and reference its license/notices; do not
-   relicense Notarius or invent a new distribution workflow.
-4. Remove the obsolete no-provider-retry-loop statement in `docs/internal/llm.md`.
-   Describe the now-active upstream default and per-attempt timeouts in the
-   appropriate integration/operations sections. Do not yet describe the setting
-   or observations from later stages as implemented.
-
-**Acceptance:** The prepared-execution adapter builds and its existing tests
-pass without prompt/catalog changes. Current documentation acknowledges the
-dependency's default retry behavior and license accurately.
-
-**Validate:** `GOWORK=off go test ./internal/framework/llm ./internal/cli`,
-`GOWORK=off go mod tidy -diff`, `git diff --check`.
-
-## Stage 3 — Wire The Explicit Transient Retry Setting
-
-**Status:** Completed 2026-09-25.
-
-**Goal:** Make retry policy inspectable and configurable through the one shared
-engine. One prompt covering a single vertical configuration slice.
-
-**Inspect:** `internal/core/config/{document,config,load,operational_document,
-loaded_config,validation}.go`, effective-config tests;
-`internal/cli/catalog.go:buildProductionLLMClient`;
-`internal/framework/llm/promptkit_client.go:NewPromptKitClient` and HTTP tests.
-
-**Work:**
-
-1. Add `TransientRetries *int` to `PromptKitDocument` and a resolved integer to
-   `PromptKitConfig`. Supply 2 through both the document default path and the
-   runtime `Default()` path. Preserve explicit zero; never use zero as omission.
-   Include it in document-to-runtime conversion and effective configuration.
-2. Reject negative values through both existing document and direct runtime
-   validation entry points. Follow current source-aware diagnostics; do not
-   impose a new maximum. Keep ConfigKit's existing decoding behavior.
-3. Add `TransientRetries *int` to `PromptKitClientConfig`: nil follows upstream
-   default, non-nil includes explicit zero. Production construction always
-   supplies the resolved configuration value. Pass it into `promptkit.Config`,
-   not per-request options. All calls through the injected shared client thus
-   share the setting without module changes.
-4. Add the setting to `examples/dnd-complete.config.yml` and `docs/config.md`;
-   keep the minimal example minimal. Update configuration/LLM internal guides
-   for the new plumbing and operations for the zero-value opt-out.
-
-**Acceptance/tests:** Demonstrate omitted default, explicit zero, a positive
-override, negative rejection, and effective/explain inspection. Use an existing
-CLI factory test to prove the resolved value reaches construction. Exercise
-built-in generation with a local HTTP server: eligible failure then success,
-disabled retries, exhausted configured count, and a noneligible 400 response.
-An injected `LLMClient` stub does not test built-in HTTP retry wiring. Avoid
-testing the upstream jitter formula or every equivalent HTTP status.
-
-**Validate:** `GOWORK=off go test ./internal/core/config ./internal/cli ./internal/framework/llm`
-and `git diff --check`.
-
-## Stage 4 — Preserve Typed Failure And Exhaustion Metadata
-
-**Status:** Completed 2026-09-25.
-
-**Goal:** Distinguish provider failures without coupling callers to PromptKit.
-One prompt; defer execution observations to the next stage.
-
-**Inspect:** `internal/framework/contracts/errors.go`, adapter error conversion
-in `promptkit_client.go`, redaction helpers, and existing pipeline handling of
-`ErrLLMGeneration`, `ErrLLMCapacityExceeded`, and invalid structured output.
-
-**Work:**
-
-1. Extend the existing application-owned `LLMGenerationError` rather than
-   creating a parallel provider-error hierarchy. Retain `StatusCode()` and
-   `errors.Is(err, ErrLLMGeneration)`. Add application-owned failure-kind,
-   exhaustion, and exhausted-generation attempt metadata/accessors; use uint64
-   for upstream attempt counts. Preserve the existing constructor's callers
-   with sensible unspecified/generation metadata, adding a metadata constructor
-   or private adapter helper as needed.
-2. Define kinds for `transport`, `provider_status`, `malformed_response`, and
-   generic `generation`. Exhaustion is an independent boolean and attempt count,
-   not a replacement kind. Zero attempts means unavailable in this error
-   projection, not proof no request happened. The count comes from
-   `RetryExhaustedError.Attempts()` and covers the exhausted generation, not all
-   repair generations combined.
-3. Use `errors.Is`/`errors.As` on upstream sentinels/types. Keep cancellation and
-   deadline identity first, capacity handling intact, and HTTP status available
-   through an exhaustion wrapper. Do not unwrap application errors to upstream
-   provider objects or classify by prose. Preserve sanitized diagnostic text.
-4. A malformed provider envelope is a generation failure; schema-invalid model
-   content stays `ErrInvalidStructuredOutput`. Do not change outer retry or
-   validator disposition logic. Document classification at the integration and
-   internal LLM boundaries.
-
-**Acceptance/tests:** Adapter tests cover transport, malformed response,
-noneligible status, exhausted eligible status with count/status preserved, and
-cancellation/deadline/capacity regression behavior. Check typed fields and
-identities, not full messages. Existing credential-redaction cases remain valid
-for nested exhaustion diagnostics; use fake secrets only.
-
-**Validate:** `GOWORK=off go test ./internal/framework/contracts ./internal/framework/llm ./internal/framework/pipeline`
-and `git diff --check`.
-
-## Stage 5 — Project Request-Local Execution Observations
-
-**Status:** Completed 2026-09-25.
-
-**Goal:** Return a lightweight terminal summary even when generation fails.
-One prompt focused on contracts and adapter mapping, without persistence changes.
-
-**Inspect:** `internal/framework/contracts/contracts.go`, `CompleteStructured`,
-`responseFromResult`, prepared execution tests, upstream `observations.go` and
-prepared-execution observer documentation.
-
-**Work:**
-
-1. Add an optional `Execution *LLMExecutionSummary` field to
-   `StructuredCompletionResponse` (`execution,omitempty`). Own these DTOs in
-   Notarius contracts; do not alias or serialize upstream event types.
-2. The summary contains uint64 `attempts`, `transient_retries`, `repair_calls`;
-   integer millisecond `capacity_wait_ms`, `generation_ms`, `retry_delay_ms`,
-   `duration_ms`; `outcome`, `failure_kind`, `status_code`, `retries_exhausted`;
-   and `usage`. Usage contains prompt/completion/total/cached/cache-write counts,
-   each with `value`, `known`, `complete` fields. Do not omit these booleans or
-   known-zero values. The summary needs no prompts, response text, endpoints,
-   credentials, raw errors, or new copies of run/profile identifiers.
-3. Map terminal outcome/failure values explicitly to application-owned strings.
-   Preserve the distinctions exposed by v0.11.0 (including canceled, deadline,
-   capacity, invalid output, configuration/load/render failures); unknown future
-   failures map to `other`. Reuse relevant application failure vocabulary from
-   Stage 4, without forcing every execution error into a generation error.
-4. Attach a local observer to the `RunRequest` before `PrepareExecution` freezes
-   it. Retain the `ExecutionFinished` projection only: upstream supplies aggregate
-   counts, durations, and usage. Do not sum attempt events and terminal totals,
-   retain an event log, or reconstruct a second accounting system. Synchronous
-   request-local collection needs no global state or asynchronous queue.
-5. Attach that summary to every subsequent return from `RunPrepared`, including
-   context/capacity/provider failure and post-result decode/validation failure.
-   Preparation failure has no execution event and returns no summary. Preserve
-   upstream execution outcome as such: a later Notarius decode error remains a
-   separate returned error, not a fabricated upstream terminal event.
-6. Keep existing successful-result token and repair fields unchanged. Observed
-   `repair_calls` represents execution activity and is not a renamed legacy
-   `RepairAttempts`. No observation field is a billable-cost guarantee.
-
-**Acceptance/tests:** Success, failed execution, cancellation, and no-observation
-preparation failure retain the right presence. Test known zero versus unknown
-and partial aggregate usage with controlled provider responses. One concurrent
-completion case proves no summary cross-contamination. Check relationships and
-nonnegative durations, not exact timing. Document the DTO and mapping in
-`docs/internal/llm.md`; public dependency semantics stay in pkg-promptkit.
-
-**Validate:** `GOWORK=off go test ./internal/framework/contracts ./internal/framework/llm`
-and `GOWORK=off go test -race ./internal/framework/llm`.
-
-## Stage 6 — Carry Summaries Through Existing Debug Paths
-
-**Status:** Completed 2026-09-25.
-
-**Goal:** Make observations useful to operators without a new output channel.
-One prompt, limited to debug propagation and terminal allowlists.
-
-**Inspect:** `internal/framework/pipeline/debug.go`, its response-content/fallback
-helpers, terminal recording tests, and `debugLLMScope.references`. Trace
-`debugLLMCallReference` through the existing timed stage/terminal envelopes;
-updating only the detailed response file is insufficient. The CLI's separate
-run-summary files do not need a new run-wide accounting mechanism.
-
-**Work:**
-
-1. Project the optional execution summary into existing debug response artifacts
-   and per-call references used by stage/terminal records. Explicitly preserve it
-   when `Debug.Response` or `RunResult` is absent and through content splitting
-   and fallback construction. Keep copies detached if existing clone paths
-   could otherwise share mutable pointers.
-2. Use explicit typed fields as the allowlist for this metadata-only terminal
-   projection. Do not carry raw upstream events, newly copied provider diagnostics, or model
-   content into safe terminal summaries. Preserve established redaction and
-   detailed-trace content boundaries.
-3. Leave warnings, normal console output, receipts, domain artifacts, checkpoint
-   payloads, and no-debug behavior unchanged. No new telemetry file or aggregation
-   of observed token totals into legacy totals.
-4. Update `docs/internal/state.md`/relevant debug internals and `docs/operations.md`
-   to identify where this diagnostic information is available. Link to the
-   canonical explanation rather than repeating every field in consumer docs.
-
-**Acceptance/tests:** Through the real debug wrapper and existing recorder seam,
-verify success and failed/canceled completions retain summaries in response and
-safe terminal records. Verify content splitting/fallback does not discard them,
-and debug disabled writes nothing. Reuse existing redaction tests, adding only
-the new projection assertions. No new warnings result from recovered retries.
-
-**Validate:** `GOWORK=off go test ./internal/framework/pipeline ./internal/cli`,
-`GOWORK=off go test -race ./internal/framework/pipeline`, `git diff --check`.
-
-## Stage 7 — Verify Retry Composition And Finish Operator Guidance
-
-**Status:** Completed 2026-09-25.
-
-**Goal:** Validate the cross-boundary behavior that individual stages cannot
-prove, then reconcile current documentation. One prompt; no generalized retry
-test framework or runtime redesign.
-
-**Inspect:** Existing adapter HTTP fixtures, scheduler cancellation tests,
-pipeline stage retry/debug tests, CLI production tests; current config, LLM,
-operations, and consumer documentation.
-
-**Work and acceptance:**
-
- Add one representative local-HTTP scenario combining a recoverable transient
-  status with structurally invalid generated content followed by a successful
-  repair. Prove transient budgets apply independently per generation and
-  terminal attempt/repair/usage accounting is not doubled. Use small explicit
-  budgets rather than executing the illustrative 18-request worst case.
- Exercise cancellation during provider-directed retry waiting without a long
-  real sleep: signal that the request was received, cancel a context while a
-  long Retry-After is pending, and wait with a bounded test timeout. Preserve
-  cancellation identity and the terminal observation. Do not build a second
-  backoff implementation or test exact random delays.
- Review shared scheduler tests for completion-scoped permit ownership and
-  cancellation/release. Add a focused integration case only where existing
-  coverage does not protect that boundary across the new retry path. Keep
-  upstream backend capacity algorithms upstream.
- Confirm a recovered generation passes through ordinary success without
-  producing process warnings. Preserve existing outer stage retries and semantic
-  feedback. Do not alter limits to hide budget multiplication.
- Finish operations guidance: distinguish transient, structural, and stage/
-  validator budgets; give the 18-attempt single-producer illustration with its
-  assumptions; explain per-attempt timeout versus overall caller cancellation,
-  Retry-After waits, cost/latency implications, incomplete usage accounting, and
-  the outer scheduler holding its permit during waits. No new total deadline or
-  exactly-once guarantee is implied.
- Review all canonical docs changed earlier for consistency. Keep exact fields
-  and defaults in config, flags in CLI, dependency semantics in integrations,
-  mechanism in internals, and operating implications in operations. Keep the
-  migration note about overlays distinct from unchanged LLM profiles. Retain
-  historical ADR/release content; no new ADR is needed for these upgrades.
-
-**Validate:** Run the focused adapter/pipeline/CLI tests and race tests covering
-modified concurrency paths. Review tests for unnecessary upstream duplication
-or exact-prose/change-detector assertions; consolidate rather than multiply them.
-
-## Stage 8 — Final Integration Verification And Handoff
-
-**Status:** Completed 2026-09-25.
-
-**Goal:** Verify the complete upgraded application and documentation against the
-feature roadmap. One final verification prompt; fix only defects within scope.
-
-**Work:** Review all feature acceptance items and staged diffs. Confirm no
-upstream types escaped the LLM boundary, no references to the retired config
-flag remain in current examples/help, no unintended LLM profile rename occurred,
-and no source-only/license/release scope expanded. Check edited relative links.
-Leave the roadmap available for the user's completion review; do not publish a
-release or delete planning documents automatically.
-
-**Validation commands:**
-
-```sh
-GOWORK=off go test ./...
-GOWORK=off go vet ./...
-GOWORK=off go build ./...
-GOWORK=off go mod tidy -diff
-GOWORK=off go test -race ./internal/framework/llm ./internal/framework/pipeline
-GOWORK=off go run ./cmd/notarius config validate --config examples/dnd-minimal.config.yml
-GOWORK=off go run ./cmd/notarius config validate --config examples/dnd-complete.config.yml
-GOWORK=off go run ./cmd/notarius config validate --config examples/dnd-complete.config.yml --config-overlay development
-git diff --check
-```
-
-Reuse already-passed checks for the same unchanged candidate where appropriate.
-The example/CLI tests own maintained examples; the commands above are a one-time
-migration smoke check, not new permanent release gates. No live model calls or
-real API keys are required. Report environment/dependency-access failures
-separately from implementation failures; do not claim blocked checks passed.
-
-**Completion criteria:** Both exact dependency pins are active; overlay migration,
-retry setting, typed errors, observations, debug propagation, tests, examples,
-and current documentation satisfy the feature roadmap. Report commits and
-checks, plus any residual limitation. Future release preparation should explain
-the breaking overlay cutover, retry default/opt-out, and upstream license change
-in a minor-release note, but is not part of this implementation.
-
-## Open Questions
-
-None. The feature roadmap supplies the policy choices needed for implementation.
-The DTO naming and stage boundaries above settle remaining implementation choices
-without adding new product restrictions or compatibility promises.
--- a/go.mod
+++ b/go.mod
@@ -3,8 +3,8 @@ module gitea.maximumdirect.net/eric/notarius
 go 1.25.5

 require (
-	gitea.maximumdirect.net/eric/ConfigKit v0.4.0
-	gitea.maximumdirect.net/eric/promptkit v0.11.0
+	gitea.maximumdirect.net/eric/ConfigKit v0.4.2
+	gitea.maximumdirect.net/eric/promptkit v0.11.2
 	github.com/santhosh-tekuri/jsonschema/v6 v6.0.2
 	gopkg.in/yaml.v3 v3.0.1 // indirect
 )
@@ -12,7 +12,7 @@ require (
 require golang.org/x/text v0.40.0

 require (
-	gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1 // indirect
-	gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0 // indirect
+	gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260926.0 // indirect
+	gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260926.0 // indirect
 	go.yaml.in/yaml/v4 v4.0.0-rc.6 // indirect
 )
--- a/go.sum
+++ b/go.sum
@@ -1,11 +1,11 @@
-gitea.maximumdirect.net/eric/ConfigKit v0.4.0 h1:fo+vKff3zTGeWqJIA38NtT84b6OUP//9ZmBH3lFuKgk=
-gitea.maximumdirect.net/eric/ConfigKit v0.4.0/go.mod h1:tYWpsrbLyu05r8+1MapWp5fN6ZrX9I8hU2xEPedYmYk=
-gitea.maximumdirect.net/eric/promptkit v0.11.0 h1:x7JguOUiInPVXK0GEitjyoRFqqvcuSTjYUvqJ+whtik=
-gitea.maximumdirect.net/eric/promptkit v0.11.0/go.mod h1:0zEBVlJJC+ldDdXazAgybYBXNSe74vwFx5dyOuSos/w=
-gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1 h1:S2/Q/JDE+m8Ca3pDhAjVbfYrdlEhs9blj0STgNopHo0=
-gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260922.1/go.mod h1:a3VBbh9oaGXD6ruxhtwHj+AWW6DY/SSyby1QtMmYSUo=
-gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0 h1:Y0EXc3eh12eKW2NrOviVqdk3oBo6UUjopt1YAa1B3Oc=
-gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260922.0/go.mod h1:mtgD1E0SGm0e/I8Ffhz+AYX7GN7RKUWJXehNFIKHs4Y=
+gitea.maximumdirect.net/eric/ConfigKit v0.4.2 h1:ZMxmv8pOnLtAx2hFTf8Z+pHKUbR89xErkBhwjr4yK24=
+gitea.maximumdirect.net/eric/ConfigKit v0.4.2/go.mod h1:tYWpsrbLyu05r8+1MapWp5fN6ZrX9I8hU2xEPedYmYk=
+gitea.maximumdirect.net/eric/promptkit v0.11.2 h1:2RqI+KtflvSh7vLQaTAQCmMaFQscEA7EPwPazyvXRoY=
+gitea.maximumdirect.net/eric/promptkit v0.11.2/go.mod h1:onm/FBPUKQ8/NSPwTEk26Ut+dVX2iXcq8vEseB+g/0E=
+gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260926.0 h1:wdab+R+lgMZxzYwhbAuCrW7zdSQ1cW9ovBR6UzLmZR4=
+gitea.maximumdirect.net/eric/promptkit-backend-openrouter/v2 v2.20260926.0/go.mod h1:a3VBbh9oaGXD6ruxhtwHj+AWW6DY/SSyby1QtMmYSUo=
+gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260926.0 h1:baCCIB6Ee5t0S4Zc++NTBIPcJEv5UPS6DlSrpZfykwg=
+gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome/v2 v2.20260926.0/go.mod h1:mtgD1E0SGm0e/I8Ffhz+AYX7GN7RKUWJXehNFIKHs4Y=
 github.com/dlclark/regexp2 v1.11.0 h1:G/nrcoOa7ZXlpoa/91N3X7mM3r8eIlMBBJZvsz/mxKI=
 github.com/dlclark/regexp2 v1.11.0/go.mod h1:DHkYz0B9wPfa6wondMfaivmHpzrQ3v9q8cnmRbL6yW8=
 github.com/santhosh-tekuri/jsonschema/v6 v6.0.2 h1:KRzFb2m7YtdldCEkzs6KqmJw4nqEVZGK7IN2kJkjTuQ=
--- a/internal/framework/llm/promptkit_profile_fingerprint.go
+++ b/internal/framework/llm/promptkit_profile_fingerprint.go
@@ -17,7 +17,7 @@ const (
 	promptKitLocalBackendMarker          = "notarius:promptkit-local-backend:v1"
 	// The built-in profile catalog is compiled into this pinned PromptKit
 	// release. Update this identity when the dependency is upgraded.
-	promptKitBuiltinProfileCatalogID = "promptkit:v0.11.0:builtin-profiles"
+	promptKitBuiltinProfileCatalogID = "promptkit:v0.11.2:builtin-profiles"
 )

 func promptKitProfileFingerprint(profileDir, profileFile, fallbackProfileDigest string) (CheckpointFingerprint, error) {
Author	SHA1	Message	Date
Eric Rakestraw	9790579b51	Prepare Notarius v0.8.1 source release	2026-09-28 03:04:04 +00:00
Eric Rakestraw	122f36bc68	Update ConfigKit and PromptKit to their latest patches	2026-09-28 02:31:31 +00:00
Eric Rakestraw	90c68dd725	Verify policy adoption and refine notice scope	2026-09-28 01:47:00 +00:00
Eric Rakestraw	b0085a1c3b	Complete dependency notices and attribution links	2026-09-28 01:43:24 +00:00
Eric Rakestraw	eff69683d2	Attribute selected kits and backend catalogs	2026-09-28 01:38:01 +00:00
Eric Rakestraw	d4feccc456	Align architecture and source release policies	2026-09-28 01:35:01 +00:00
Eric Rakestraw	21c07d4ef0	Align general policies and contributor guidance	2026-09-28 01:32:50 +00:00
Eric Rakestraw	d9f8ff8179	Establish policy provenance and licensing notices	2026-09-28 01:31:08 +00:00
Eric Rakestraw	f6d7c7cef4	Plan the policy alignment work	2026-09-28 01:13:52 +00:00
Eric Rakestraw	ff9b05077c	Update the policy alignment roadmap	2026-09-28 01:10:25 +00:00
Eric Rakestraw	1301c445bb	Update kit dependencies and licensing references	2026-09-26 22:02:41 +00:00
Eric Rakestraw	7a7f12142f	Plan licensing policy and attribution updates	2026-09-26 20:47:11 +00:00
Eric Rakestraw	658de79e96	Fix license name typos in COPYRIGHT	2026-09-26 20:38:50 +00:00