Add operator-facing PromptKit inspection to the roadmap

.woodpecker/release.yml

@@ -1,3 +1,4 @@
+# Advisory validation after source publication, never a release-completion gate.
 when:
   - event: tag
 
@@ -5,29 +6,4 @@ steps:
   - name: validate-release
     image: golang:1.25.5
     commands:
-      - |
-        set -eu
-
-        version="$CI_COMMIT_TAG"
-        release_note="docs/releases/$version.md"
-
-        if ! printf '%s\n' "$version" | grep -E -x 'v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)' >/dev/null; then
-          printf '%s\n' "invalid release tag: $version" >&2
-          exit 1
-        fi
-        if [ ! -s "$release_note" ]; then
-          printf '%s\n' "missing release note: $release_note" >&2
-          exit 1
-        fi
-        if ! grep -F -x "# Notarius $version" "$release_note" >/dev/null; then
-          printf '%s\n' "release note heading does not match $version" >&2
-          exit 1
-        fi
-        for heading in '## Summary' '## Compatibility' '## Upgrade' '## Changes'; do
-          if ! grep -F -x "$heading" "$release_note" >/dev/null; then
-            printf '%s\n' "release note is missing heading: $heading" >&2
-            exit 1
-          fi
-        done
-
-        ./scripts/check-release-source.sh "$version"
+      - ./scripts/check-release-source.sh "$CI_COMMIT_TAG"

AGENTS.md

@@ -1,2 +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.
+
+Read and follow `docs/policy/agents.md` before recommending, planning, or
+implementing repository changes.

COPYRIGHT

@@ -0,0 +1,23 @@
+Notarius
+
+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 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 General Public License for more details.
+
+Third-party code and assets are subject to their respective license terms.

LICENSE

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

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.

assets/dnd/combat-turns/schemas/dnd_combat_turns_llm.v1.json

@@ -16,7 +16,8 @@
             "type": "string"
           },
           "turn_kind": {
-            "type": "string"
+            "type": "string",
+            "enum": ["turn", "reaction", "legendary_action", "lair_action", "other"]
           },
           "source_refs": {
             "type": "array",

assets/dnd/enemy-events/schemas/dnd_enemy_events_llm.v1.json

@@ -13,7 +13,10 @@
         "required": ["name", "kind", "source_refs"],
         "properties": {
           "name": {"type": "string"},
-          "kind": {"type": "string"},
+          "kind": {
+            "type": "string",
+            "enum": ["engaged", "killed", "fled", "captured", "incapacitated"]
+          },
           "source_refs": {
             "type": "array",
             "items": {

assets/dnd/item-occurrences/prompts/instructions.md

@@ -18,12 +18,20 @@ when the transcript explicitly describes it being physically destroyed or
 expended as a non-payment component. Use `transferred` only when possession
 moves between two distinct named party members.
 
-Return both `from` and `to` for every occurrence, using `null` when a holder does not
-apply. For `discovered`, set both holders to `null`. For `acquired`, set `from`
-to `null` and provide `to`; for `lost` and `consumed`, provide `from` and set
-`to` to `null`; and for `transferred`, provide both holders. Use `party` only
-for collective or unresolved party possession, never for either side of a
-transfer. Do not emit a transfer for a gift, sale, or payment outside the party.
+Return both `from` and `to` for every occurrence. Use JSON `null`, not an empty
+string, whenever a holder does not apply. Follow this holder matrix exactly:
+
+| `kind` | required `from` | required `to` |
+| --- | --- | --- |
+| `discovered` | `null` | `null` |
+| `acquired` | `null` | `party` or the named party member gaining possession |
+| `lost` | `party` or the named party member losing possession | `null` |
+| `consumed` | `party` or the named party member consuming the item | `null` |
+| `transferred` | one named party member | a different named party member |
+
+Use `party` only for collective or unresolved party possession, never for
+either side of a transfer. Do not emit a transfer for a gift, sale, or payment
+outside the party.
 
 Ordinary non-depleting use is not an occurrence. Do not infer acquisition from a
 discovery, or discovery from an acquisition: emit both only when each is

assets/dnd/item-occurrences/schemas/dnd_item_occurrences_llm.v1.json

@@ -13,7 +13,10 @@
         "required": ["name", "kind", "quantity", "from", "to", "source_refs"],
         "properties": {
           "name": {"type": "string"},
-          "kind": {"type": "string"},
+          "kind": {
+            "type": "string",
+            "enum": ["discovered", "acquired", "lost", "consumed", "transferred"]
+          },
           "quantity": {"type": ["integer", "null"]},
           "from": {"type": ["string", "null"]},
           "to": {"type": ["string", "null"]},

assets/dnd/item-registry/normalize/prompts/instructions.md

@@ -5,5 +5,5 @@ evidence, similar objects, or a shared owner as sufficient.
 Keep currency denominations and materially different item types separate. Keep
 uncertain aliases separate. Do not infer an item property or uniqueness.
 
-When selecting a canonical display name, choose one supplied candidate name
-that is the clearest established designation.
+Set `canonical_candidate_number` to the supplied candidate number whose label
+is the clearest established designation.

assets/dnd/location-registry/normalize/prompts/instructions.md

@@ -5,4 +5,5 @@ nearby evidence, nested places, or generic labels as sufficient.
 Keep parent and child places separate, as well as similarly named places and
 uncertain aliases.
 
-When selecting a canonical display name, prefer the clearest established name.
+Set `canonical_candidate_number` to the supplied candidate number whose label
+is the clearest established name.

assets/dnd/npc-occurrences/schemas/dnd_npc_occurrences_llm.v1.json

@@ -16,7 +16,8 @@
             "type": "string"
           },
           "kind": {
-            "type": "string"
+            "type": "string",
+            "enum": ["mentioned", "noncombat_presence", "dialogue", "combat_ally", "combat_opponent", "other"]
           },
           "source_refs": {
             "type": "array",

assets/dnd/npc-registry/normalize/prompts/instructions.md

@@ -3,7 +3,8 @@ contextual labels and cited transcript windows. Preserve distinct individuals
 even when their names are similar or their contextual descriptions are
 identical.
 
-When selecting a canonical display name, prefer a complete, stable proper name
+Set `canonical_candidate_number` to the supplied candidate number whose label
+is the preferred canonical display name. Prefer a complete, stable proper name
 over an abbreviation. Prefer an unadorned proper name over that name plus a
 contextual class, role, title, or relationship descriptor unless the transcript
 establishes the descriptor as part of the person's name. A longer display name

assets/dnd/scene-descriptions/prompts/instructions.md

@@ -5,9 +5,7 @@ into multiple scenes or use facts that are not supported by it.
 Return one kind, one concise title, and one concise summary. Choose exactly one
 kind:
 
-- combat: active combat materially organizes the scene, including
-  initiative-like exchanges or sustained hostile action. Planning a fight or
-  discussing a completed fight is not combat by itself.
+- combat: a scene classified as combat under the shared combat policy.
 - narrative: current-session in-world play that is not principally active
   combat, a prior-session recap, or sustained out-of-character session
   discussion. This includes exploration, travel, dialogue, investigation,
@@ -20,15 +18,13 @@ kind:
   play.
 
 Narrative is the default for actual current-session gameplay that does not meet
-another definition. When the accepted chunk is mixed:
+another definition. When the accepted chunk has no substantive active combat:
 
-1. use combat when active combat is a substantive central activity, even with
-   brief setup, rules clarification, or immediate aftermath;
-2. otherwise use recap when recounting a previous session is the chunk's
+1. use recap when recounting a previous session is the chunk's
    primary table purpose;
-3. otherwise use meta when sustained out-of-character session discussion is
+2. otherwise use meta when sustained out-of-character session discussion is
    primary and in-world progression is no more than incidental; and
-4. use narrative for all remaining current-session in-world play.
+3. use narrative for all remaining current-session in-world play.
 
 Brief table talk, dice resolution, rules clarification, jokes, or
 administrative comments do not make a gameplay scene meta. A short recollection

assets/dnd/scene-descriptions/prompts/prompt.yaml

@@ -27,6 +27,8 @@ messages:
     content_file: ./sharedassets/common-dnd-transcript-chunk.md
     cache_control:
       type: ephemeral
+  - role: user
+    content_file: ./sharedassets/common-dnd-scene-combat-policy.md
   - role: user
     content_file: ./instructions.md
     cache_control:

assets/dnd/scene-descriptions/schemas/dnd_scene_descriptions_llm.v1.json

@@ -6,7 +6,8 @@
   "required": ["kind", "title", "summary"],
   "properties": {
     "kind": {
-      "type": "string"
+      "type": "string",
+      "enum": ["combat", "narrative", "recap", "meta"]
     },
     "title": {
       "type": "string"

assets/dnd/scene-descriptions/validate/combat-semantics/prompts/instructions.md

@@ -0,0 +1,8 @@
+Classify only whether substantive active combat occurs in the supplied
+transcript chunk under the shared combat policy. Do not judge the scene title,
+summary, non-combat subtype, scene boundary, or any other aspect of a scene
+description.
+
+Return `combat` when the chunk contains substantive active combat and
+`non_combat` otherwise. Give a concise, transcript-grounded explanation for
+the classification.

assets/dnd/scene-descriptions/validate/combat-semantics/prompts/prompt.yaml

@@ -0,0 +1,23 @@
+id: dnd.scene_descriptions.validate_combat
+version: "v1"
+default_profile: dnd-extraction
+inputs:
+  - name: transcript
+    required: true
+    content_type: application/json
+messages:
+  - role: system
+    content_file: ./sharedassets/common-dnd-system.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-scene-combat-policy.md
+  - role: user
+    content_file: ./instructions.md
+  - role: user
+    content_file: ./sharedassets/common-dnd-transcript-chunk.md
+    cache_control:
+      type: ephemeral
+output:
+  format: json
+  validation_mode: json_schema
+  schema_path: dnd_scene_combat_semantics_llm.v1.json
+  repair_attempts: 1

assets/dnd/scene-descriptions/validate/combat-semantics/schemas/dnd_scene_combat_semantics_llm.v1.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "$id": "notarius.dnd.scene_descriptions.combat_semantics.llm",
+  "type": "object",
+  "additionalProperties": false,
+  "required": ["classification", "explanation"],
+  "properties": {
+    "classification": {
+      "type": "string",
+      "enum": ["combat", "non_combat"]
+    },
+    "explanation": {
+      "type": "string",
+      "minLength": 1,
+      "maxLength": 512
+    }
+  }
+}

assets/dnd/shared/prompts/common-dnd-extraction-evidence.md

@@ -1,6 +1,8 @@
 Transcript units are the only evidence for extracted events and factual claims.
 Every reported factual claim must be supported by cited transcript units. Use
 integer `start_unit_id` and `end_unit_id` values from the transcript.
+Within each range, `start_unit_id` must identify the earlier transcript unit and
+`end_unit_id` the same or a later unit according to transcript order.
 
 When supporting evidence is non-contiguous, use multiple narrow ranges rather
 than a broad range that bridges unrelated conversation.

assets/dnd/shared/prompts/common-dnd-scene-combat-policy.md

@@ -0,0 +1,13 @@
+Use `combat` only when substantive active combat materially organizes the
+scene. Active combat includes initiative or turn exchanges, attacks, combat
+spells, damage, saves, movement, or similarly sustained hostile action.
+
+Do not use `combat` for planning or preparing for a possible fight; threats,
+hostile dialogue, or a tense confrontation; immediate aftermath, looting,
+healing, or discussion of a completed fight; a recap or in-world recollection
+of earlier combat; or out-of-character rules discussion without active
+encounter play.
+
+When a chunk contains substantive active combat alongside brief setup, rules
+clarification, interruption, phase transition, or immediate aftermath, classify
+it as `combat`.

assets/generic/normalize/deduplication/prompts/candidates.md

@@ -1,3 +1,3 @@
-Candidate material:
+Candidate material, including the exact valid candidate-number range:
 
 {{ input "candidates" }}

assets/generic/normalize/deduplication/prompts/protocol.md

@@ -1,7 +1,9 @@
-Use only the positive integer `candidate_id` values supplied in the candidate material.
+Use only the positive integer `candidate_number` values supplied in the candidate material. Valid candidate numbers are exactly the inclusive `first` through `last` values declared in `candidate_number_range`; use the explicit number attached to each candidate.
 
-Return a duplicate group only when the evidence supports that every selected candidate describes the same underlying entity. Each group must contain at least two distinct candidate IDs, and its `canonical_candidate_id` must be one of those IDs. A candidate may appear in at most one group.
+Transcript unit `id` values and evidence `start_unit_id` and `end_unit_id` values identify source positions. They are not candidate numbers and must never be used in `candidate_numbers` or `canonical_candidate_number`.
 
-Omit uncertain matches and candidates that should remain distinct. Do not invent candidates or infer an ID from list position. An empty `duplicate_groups` array is valid.
+Return a duplicate group only when the evidence supports that every selected candidate describes the same underlying entity. Each group must contain at least two distinct candidate numbers, and its `canonical_candidate_number` must be one of those numbers. A candidate may appear in at most one group.
 
-The response must conform exactly to the selected JSON schema. Return IDs only: do not copy candidate names, evidence, transcript text, source identifiers, or source ranges into the response.
+Omit uncertain matches and candidates that should remain distinct. Do not invent candidates or infer a number that is not explicitly supplied. An empty `duplicate_groups` array is valid.
+
+The response must conform exactly to the selected JSON schema. Return candidate numbers only: do not copy candidate names, evidence, transcript text, source identifiers, or source ranges into the response.

assets/generic/normalize/deduplication/schemas/semantic_reconciliation_llm.v1.json

@@ -11,9 +11,9 @@
       "items": {
         "type": "object",
         "additionalProperties": false,
-        "required": ["candidate_ids", "canonical_candidate_id"],
+        "required": ["candidate_numbers", "canonical_candidate_number"],
         "properties": {
-          "candidate_ids": {
+          "candidate_numbers": {
             "type": "array",
             "minItems": 2,
             "items": {
@@ -21,7 +21,7 @@
               "minimum": 1
             }
           },
-          "canonical_candidate_id": {
+          "canonical_candidate_number": {
             "type": "integer",
             "minimum": 1
           }

docs/adr/0015-separate-process-warnings-from-quality-diagnostics.md

@@ -0,0 +1,67 @@
+# ADR-0015: Separate process warnings from quality diagnostics
+
+**Status:** Accepted
+**Date:** 2026-08-27
+
+## Context
+
+Notarius currently represents process degradation, incomplete validation,
+extraction-quality doubt, and routine normalization with one flat warning
+record. That makes ordinary successful runs noisy, loses the framework context
+needed to explain a finding, and gives `warning_count` no stable operational
+meaning. It also permits output encoders to add a warning after the durable
+warning file has already been written.
+
+The application needs one bounded diagnostic model that preserves exact
+occurrence counts while retaining only safe, representative samples. Fresh and
+resumed logical runs must present the same groups. The model must not alter
+validation decisions, retry budgets, rejected-output behavior, or process exit
+policy.
+
+## Decision
+
+Warnings are reserved for a completed run that advanced under an allowed
+process-level degradation or incomplete-work policy. Extraction-quality signals
+are advisories, and routine accepted transformations are observations. A
+non-degraded successful run therefore has zero actionable warnings.
+
+Modules and validators own a diagnostic's disposition, category, reason code,
+scope, and safe message. The framework adds pipeline origin, including stage,
+step, lane, module, validator, and chunk context where applicable. It then
+aggregates deterministically by disposition, category, reason code, and full
+origin. Chunk context remains on representative samples so equivalent findings
+across chunks aggregate together.
+
+Diagnostics carry exact occurrence counts, at most three distinct samples, and
+numeric omitted-sample metadata. Producers and validators are bounded to 64
+local groups. Final actionable warning groups are bounded without truncation;
+the non-warning collection may truncate represented groups while preserving an
+exact total occurrence count and explicit truncation metadata.
+
+The public contracts will be versioned: grouped actionable warnings use
+`notarius.warnings.v2`, grouped advisories and observations use
+`notarius.diagnostics.v1`, and the run receipt uses
+`notarius.run-result.v2`. Successful output encoders return logical files or
+an error; they do not add post-encoding warnings.
+
+## Alternatives considered
+
+- Keep one warning list and filter only CLI output. This would leave durable
+  consumers with the same semantically mixed, unbounded contract.
+- Map reason codes to severity in a central framework registry. This would
+  split module-owned meaning between synchronized policy tables and make new
+  diagnostic meaning implicit.
+- Preserve local omission warning records. They inflate visible group counts
+  and lose exact occurrence semantics.
+- Keep output-encoder warnings. A one-pass encoder cannot include those
+  records consistently in files it has already serialized; a two-phase encoder
+  protocol is deferred until a demonstrated need exists.
+
+## Consequences
+
+The framework gains validated diagnostic primitives, local collection,
+origin-aware aggregation, and versioned durable presentation. Existing warning
+transport remains temporarily while producers migrate. Current architecture,
+operator, integration, and internal documentation will describe the behavior
+only as each implementation step lands; this accepted decision does not claim
+that the migration is complete.

docs/adr/0016-feedback-aware-module-requested-retries.md

@@ -0,0 +1,76 @@
+# ADR-0016: Use feedback-aware module-requested retries
+
+**Status:** Accepted
+**Date:** 2026-08-28
+
+## Context
+
+An LLM-backed module can discover that a structurally valid model response is
+unsafe while translating it into a typed candidate, before the ordinary
+validator chain runs. Semantic registry reconciliation is the first such case:
+the shared core can identify invalid duplicate-group proposals, and typed
+application can reject a domain-incompatible group while preserving a safe
+partial result. Repeating the original request without the rejected response or
+corrective explanation gives the model no information with which to improve.
+
+The existing feedback-aware validation mechanism already establishes the safe
+correction protocol, but module-owned retry directives also carry internal
+reason codes, operator messages, and fallback diagnostics. Those values are not
+model instructions. Some module retry conditions, including exhausted
+structured-output repair, also have no valid exact response to append.
+
+## Decision
+
+An LLM-backed normalizer may attach optional, bounded model-facing correction
+guidance to a module-requested retry. Guidance is a separate contract field; the
+framework never derives it from a reason code, operator message, diagnostic, or
+error. A feedback-capable directive must include the exact model candidate that
+controlled the safe fallback and must use `single_response_v1`.
+
+The artifact-neutral producer-attempt state machine constructs the correction
+from that exact latest response and the supplied guidance. The producer rebuilds
+its complete ordinary request and appends the response as one assistant message
+and the guidance as one user message. Earlier attempts do not accumulate, and
+the attempt consumes the same configured stage retry budget as operational,
+structural, validation, and feedback-free module retries.
+
+A module retry without guidance remains valid and starts a fresh attempt. This
+is the required behavior when no valid model candidate exists, including after
+structured-output repair is exhausted. If feedback is supplied without a valid
+supported candidate, the framework fails the module contract rather than
+retrying blindly or inventing guidance.
+
+After retry exhaustion, the normalizer's safe fallback continues through its
+validator chain. Safe semantic groups may remain applied, unsafe groups remain
+separate, and bounded fallback diagnostics may explain the process degradation.
+Exact responses and correction text remain attempt-local and are excluded from
+ordinary errors, warnings, manifests, receipts, caches, and checkpoints.
+
+This decision extends, rather than supersedes,
+[ADR-0014](0014-feedback-aware-validation-retries.md): both correction sources
+use the same transport-neutral payload, replacement-request semantics, outer
+retry budget, and sensitive-data boundary.
+
+## Alternatives considered
+
+- Continue blind module retries. This preserves a smaller contract but wastes
+  the module's deterministic diagnosis and commonly repeats the same defect.
+- Convert module safety checks into validators. Typed reconciliation must apply
+  only safe proposal groups and retain a fallback before validation; moving
+  artifact-owned translation and application policy into validators would blur
+  stage ownership.
+- Copy the retry reason or operator message into the model request. Those values
+  are written for provenance and humans, can contain opaque internal labels,
+  and do not reliably describe a correct replacement.
+- Require feedback for every module retry. Structural failures may have no
+  valid exact candidate, so this would either prevent useful fresh retries or
+  fabricate prior-response material.
+
+## Consequences
+
+The normalize retry contract and generic producer-attempt directive gain an
+optional correction-guidance field and candidate-pairing validation. Modules
+that use it must provide semantically meaningful bounded prose and an exact
+candidate. Registry reconciliation maintains separate operator and model
+renderers, and policy fingerprints change so checkpoints created under blind
+retry behavior are not reused.

docs/adr/0017-defer-cache-access-policy-to-deployment.md

@@ -0,0 +1,59 @@
+# ADR-0017: Defer cache access policy to the deployment
+
+**Status:** Accepted
+**Date:** 2026-09-11
+
+## Context
+
+Canonical chunk plans and invocation checkpoints are reconstructible cache
+state. They may include source-derived content, so access and retention matter,
+but Notarius cannot determine whether a deployment needs a private cache or a
+cache shared by a trusted group. The current application-enforced `0700` and
+`0600` modes prevent ordinary Unix provisioning from making that choice.
+
+[ADR-0005](0005-cache-canonical-chunk-plans-by-source.md) governs canonical
+chunk-plan reuse, while [ADR-0006](0006-separate-output-cache-and-debug-state.md)
+established the output, cache, and debug separation refined by
+[ADR-0007](0007-separate-checkpoint-recording-from-reuse.md). None of those
+decisions requires Notarius to own exact cache access modes.
+
+## Decision
+
+Deployments own cache access policy through provisioned directories, process
+umask, setgid inheritance, and default ACLs. Notarius requests conventional
+maximum creation modes for cache entries and leaves the kernel to select their
+effective permissions.
+
+Notarius continues to own confined paths, symlink rejection, validation,
+atomic publication, cleanup, and recovery. Those correctness boundaries are
+independent from deciding which accounts may access cache state.
+
+Source-derived cache contents can be sensitive. Operators own their access and
+retention policy, while API credentials remain outside cache payloads under the
+existing secret boundary. Existing cache inode modes are not migrated
+automatically.
+
+This decision does not supersede ADR-0005, ADR-0006, or ADR-0007.
+
+## Alternatives considered
+
+- Continue enforcing private `0700` directory and `0600` file modes. This
+  makes one deployment choice for every operator and prevents trusted-group
+  provisioning.
+- Add configurable Notarius permission modes or a private/group cache setting.
+  This preserves application ownership of a deployment concern and expands the
+  public configuration surface without a durable policy reason.
+- Recursively converge existing cache ownership, modes, or ACLs. This would
+  make upgrades mutate operator-managed state and cannot safely infer an
+  intended policy.
+
+## Consequences
+
+Operators can use a restrictive umask for private cache state or provision a
+setgid/default-ACL cache root for trusted-group access. They must deliberately
+recreate or administratively migrate pre-existing cache trees when their
+existing modes do not match the desired deployment policy.
+
+Notarius does not add user or group management, ACL mutation, permission
+configuration, or recursive cache migration. Output and debug permission
+contracts remain separate from this decision.

docs/adr/0018-adopt-configkit.md

@@ -0,0 +1,53 @@
+# ADR-0018: Adopt ConfigKit for configuration loading
+
+**Status:** Accepted
+**Date:** 2026-09-13
+
+## Context
+
+Notarius's former configuration boundary owned strict YAML parsing, input
+presence bookkeeping, defaults, normalization, environment overlays, and
+configuration inspection. Those general-purpose responsibilities had grown
+alongside application-specific pipeline and module semantics.
+
+ConfigKit v0.3.0 provides strict typed YAML loading, imports, configuration
+profiles, explicit CLI overrides, recorded defaults and normalization, safe
+inspection rendering, and released source-origin APIs. The application needs
+those source records to resolve filesystem paths according to the file that
+supplied a surviving declaration.
+
+## Decision
+
+Notarius will adopt the root public `gitea.maximumdirect.net/eric/ConfigKit`
+package at v0.3.0 for its version 5 configuration contract. ConfigKit owns
+source composition, strict decoding, input presence, metadata, and safe
+effective/explanation rendering. Notarius retains its typed document schema,
+field semantics, runtime conversion, catalog-dependent pipeline resolution,
+PromptKit profile handling, and physical run preparation.
+
+Version 5 is a deliberate breaking file-contract change. It uses canonical
+object module bindings and reference sources, and enables ConfigKit imports
+and configuration profiles. The selected configuration file's canonical
+directory is the base for its declared application paths; ConfigKit's released
+`Resolution.InputInfo` and `Resolution.Source` APIs provide their origins.
+
+`NOTARIUS_CONFIG` remains file discovery, while field-level operational
+environment overlays are retired. Explicit configuration-valued CLI flags are
+represented as ConfigKit overrides; invocation actions remain outside that
+boundary.
+
+## Alternatives considered
+
+- Continue extending the custom YAML loader. This preserves duplicated
+  general-purpose parsing, presence, composition, and inspection machinery.
+- Retain version 4 alongside version 5. This would leave a supported dual
+  configuration boundary and delay removal of the machinery being replaced.
+- Wrap ConfigKit in a compatibility pre-parser. This weakens ConfigKit's
+  strict contract and recreates the application-owned parser complexity.
+
+## Consequences
+
+The released application has one ConfigKit-backed loader and one version 5
+contract. Operator documentation and maintained examples move with the cutover.
+ConfigKit metadata is retained only at the configuration publication boundary;
+its types do not become module or runtime pipeline interfaces.

docs/cli.md

@@ -12,8 +12,8 @@ defined in [Operations](operations.md).
 notarius help
 notarius --version
 notarius run <pipeline-id> --input path/to/source.json [--json] [flags]
-notarius config validate [--config path/to/config.yml] [--pipeline pipeline-id] [--only lane-a,lane-b]
-notarius pipelines list [--config path/to/config.yml] [--json]
+notarius config validate [--config path/to/config.yml] [--config-overlay name] [--pipeline pipeline-id] [--only lane-a,lane-b]
+notarius pipelines list [--config path/to/config.yml] [--config-overlay name] [--json]
 ~~~
 
 Running Notarius without arguments, or with **help**, **--help**, or **-h**,
@@ -42,6 +42,7 @@ pipeline ID and **--input** are required.
 | Flag | Meaning |
 | --- | --- |
 | **--config path** | Use this configuration file. When omitted, configuration discovery applies; see [Configuration](config.md). |
+| **--config-overlay name** | Select a ConfigKit configuration overlay. Empty and **default** select the composed base configuration. |
 | **--input path** | Source input file to process. Required. |
 | **--output-dir path** | Override the configured output root for this run. |
 | **--json** | Write the successful run-result receipt as JSON to standard output. |
@@ -55,8 +56,8 @@ pipeline ID and **--input** are required.
 | **--session-id id** | Override the generated prompt session identifier with a non-empty value for LLM-backed module calls. |
 | **--reasoning-effort value** | Replace the selected PromptKit profile's reasoning effort for every LLM-backed call in this run. The value must be non-empty and the flag may be specified only once. |
 | **--clear-reasoning-effort** | Clear reasoning effort inherited from the selected PromptKit profile for every LLM-backed call in this run. |
-| **--reference selector=path** | Add or replace a file reference binding. Repeatable. |
-| **--without-reference selector** | Remove a configured optional reference binding. Repeatable. |
+| **--reference selector=path** | Add or replace external file reference bindings at pipeline, lane, chunk, or binding scope. Repeatable. |
+| **--without-reference selector** | Remove matching configured external reference bindings. Repeatable. |
 
 **--chunk_cache** accepts only **auto**, **bypass**, or **refresh**.
 **--debug-dir**, **--output-dir**, **--session-id**, and
@@ -81,33 +82,62 @@ guidance.
 
 ### Reference selectors
 
-Use **--reference** only for a reference slot declared by the selected
-configured target. The accepted selector forms are:
+Use **--reference** only for reference slots declared by the selected
+configured targets. Qualification narrows the scope of an override:
 
 | Form | Target |
 | --- | --- |
-| slot=path | The unique selected target that declares slot. |
+| slot=path | Every selected target that declares slot. |
 | chunk.slot=path | The chunker. |
-| merge.slot=path | The unique selected merger that declares slot. |
-| lane.slot=path | The unique extractor, merger, or normalizer in lane that declares slot. |
+| lane.slot=path | Every extractor, merger, or normalizer in lane that declares slot. |
 | lane.extract.slot=path | The extractor in lane. |
 | lane.merge.slot=path | The merger in lane. |
 | lane.normalize.slot=path | The normalizer in lane. |
 
-**--without-reference** uses the same selector forms without =path. Slot
-names, requiredness, and configured bindings are part of the
+Pipeline- and lane-scoped selectors are expected to match multiple targets and
+fail if they match none. A stage-specific selector fails when its lane is not
+selected or its target does not declare the slot. There is no stage-wide
+`merge.slot` shorthand; name the lane when targeting a merger.
+
+CLI bindings override configured external paths. For overlapping CLI
+selectors, a binding-specific or chunk selector overrides a lane selector, and
+a lane selector overrides a pipeline selector. The last occurrence wins at
+equal scope. Binding and unbinding the same concrete target at equal scope is
+an error; a narrower bind or unbind may create an intentional exception to a
+broader action.
+
+**--without-reference** uses the same selector forms without `=path` and
+removes external bindings only. Neither flag replaces or removes a generated
+artifact handoff; an external/generated collision is a resolution error.
+Required slots are checked after all effective changes. CLI reference paths
+are resolved relative to the process working directory, so subprocess and
+service callers should use absolute paths. Slot names, accepted media types,
+size limits, requiredness, and configured generated bindings are part of the
 [configuration contract](config.md).
 
+For example, one shared campaign reference can reach every compatible target,
+with an optional lane-specific exception:
+
+~~~
+notarius run dnd-session \
+  --input /data/transcript.json \
+  --reference party=/data/references/party.txt \
+  --reference npc-registry.party=/data/references/npc-party-context.txt
+~~~
+
 ### Run output
 
 Without **--json**, standard output contains the completed pipeline ID, counts
 of normalized and rejected outputs, and the output directory. A debug-enabled
 run also prints its debug-bundle path to standard output. A successful run with
-warnings reports the warning count to standard error. The published JSON bundle
+actionable process warnings reports their group and occurrence counts to
+standard error. When the selected output module publishes `warnings.json`, the
+summary also reports that durable file's path. Advisory and observation findings
+do not produce a warning line. The published JSON bundle
 is defined by the [JSON output contract](integrations/json-output.md).
 
 With **--json**, successful standard output is exactly one
-`notarius.run-result.v1` JSON document followed by a newline, with no
+`notarius.run-result.v2` JSON document followed by a newline, with no
 human-oriented status or debug-path line. Its fields and compatibility policy
 are defined by the [run-result contract](integrations/run-result.md). A caller
 must check for exit status 0 before decoding this output; a failed write can
@@ -125,10 +155,10 @@ OPENROUTER_API_KEY=your-api-key \
 ## config validate
 
 ~~~
-notarius config validate [--config path/to/config.yml] [--pipeline pipeline-id] [--only lane-a,lane-b]
+notarius config validate [--config path/to/config.yml] [--config-overlay name] [--pipeline pipeline-id] [--only lane-a,lane-b]
 ~~~
 
-This command loads and validates a configuration. With **--pipeline**, it also
+This command loads and validates the selected composed configuration. With **--pipeline**, it also
 resolves that pipeline against the production module catalog. **--only** selects
 lanes during that resolution and requires **--pipeline**.
 
@@ -151,10 +181,32 @@ OPENROUTER_API_KEY=validation-placeholder \
 The placeholder in the second command is sufficient only for offline
 validation; it cannot run a provider-backed pipeline.
 
+## config effective
+
+~~~
+notarius config effective [--config path/to/config.yml] [--config-overlay name]
+~~~
+
+This command writes the selected composed configuration as deterministic,
+redacted YAML. Standard output contains only that YAML: it does not validate a
+pipeline, prepare modules, materialize references, or contact a provider.
+
+## config explain
+
+~~~
+notarius config explain [--config path/to/config.yml] [--config-overlay name] <json-pointer>
+~~~
+
+This command writes ConfigKit's redacted, human-readable explanation for one
+canonical JSON Pointer. Supply `""` explicitly to explain the root. A malformed
+pointer is a syntax error; a well-formed unknown path is a command failure.
+The explanation can describe a value displaced by a selected overlay. Standard
+output contains only the explanation.
+
 ## pipelines list
 
 ~~~
-notarius pipelines list [--config path/to/config.yml] [--json]
+notarius pipelines list [--config path/to/config.yml] [--config-overlay name] [--json]
 ~~~
 
 This command lists configured pipeline IDs in sorted order. By default, it
@@ -171,7 +223,11 @@ go run ./cmd/notarius pipelines list \
 Successful commands write their primary result to standard output. Warnings and
 errors are written to standard error.
 
-For **run --json**, warnings remain on standard error and standard output is a
+Configuration load errors include ConfigKit's field diagnostics and source
+coordinates, followed by a source-ID legend identifying the acquired files or
+source labels. This includes imported files and the selected configuration overlay.
+
+For **run --json**, actionable process warnings remain on standard error and standard output is a
 machine-readable success result only. Syntax and runtime diagnostics remain on
 standard error. Parse the result only after the process exits with status 0.
 
@@ -182,6 +238,6 @@ standard error. Parse the result only after the process exits with status 0.
 | 2 | The command or flag syntax was invalid, including unknown commands, missing required arguments, invalid flag values, or invalid flag combinations. |
 
 The root help spellings are the supported help path. Invoking **--help** on
-**run**, **config validate**, or **pipelines list** is handled by the flag
+**run**, a **config** subcommand, or **pipelines list** is handled by the flag
 parser as a usage error: it writes an error to standard error and exits with
 status 2.

docs/config.md

@@ -1,7 +1,7 @@
 # Configuration
 
 This is the canonical reference for Notarius configuration. Configuration files
-are YAML and must declare version 4. They select pipelines and their modules;
+are YAML and must declare version 5. They select pipelines and their modules;
 the [CLI reference](cli.md) owns invocation syntax, and
 [Operations](operations.md) owns run-state procedures.
 
@@ -19,12 +19,16 @@ The command fails if none of these paths provides a configuration file.
 For configuration values, precedence is:
 
 1. built-in defaults;
-2. the selected YAML file;
-3. supported operational environment variables; and
-4. the CLI run overrides that apply to a command.
+2. composed YAML sources, including imports;
+3. the selected ConfigKit overlay; and
+4. explicitly supplied configuration-valued run flags.
 
-Environment variables do not provide a second configuration schema. They only
-override the fields listed below.
+`--config-overlay` selects a ConfigKit overlay from `overlays/<name>.yml`
+beneath the selected configuration root. Empty and `default` select no overlay.
+`profiles/<name>.yml` is not a fallback location, and `--config-profile` is no
+longer accepted. Configuration overlays are distinct from PromptKit LLM profiles selected by
+`llm_profile` or `--llm-profile`. The retired operational environment variables
+have no effect; `NOTARIUS_CONFIG` remains a source-discovery input.
 
 ## Maintained Examples
 
@@ -33,7 +37,23 @@ override the fields listed below.
 - [Complete D&D configuration](../examples/dnd-complete.config.yml) uses
   ordered steps, all implemented D&D lanes, generated references, state
   settings, bounded LLM concurrency, and the maintained
-  [operator profile](../examples/profiles/dnd-extraction.yml).
+  [LLM profile](../examples/llm-profiles/dnd-extraction.yml) and imports its
+  pipeline from [a fragment](../examples/pipelines/dnd-session.yml).
+
+The complete fragment also defines `dnd-session-development`, which inherits
+the complete pipeline and profile while setting
+`structured_output_repair_attempts: 0`. Select it with:
+
+```sh
+notarius run dnd-session-development \
+  --config /path/to/dnd-complete.config.yml \
+  --input /path/to/transcript.json
+```
+
+See the [CLI reference](cli.md#run) for the full invocation contract. This
+variant disables PromptKit structural repairs without changing configured producer
+retry budgets. When using another profile, operators can instead select
+`dnd-session` and set its `llm_profile` to that profile.
 
 Use these complete files as starting points rather than combining the
 illustrative fragments in this reference.
@@ -46,7 +66,7 @@ other than **version** is optional.
 
 | Field | Type | Default | Rules |
 | --- | --- | --- | --- |
-| **version** | integer | none | Required; must be 4. |
+| **version** | integer or quoted string | none | Required; must be 5. Maintained files use `version: 5`. |
 | **promptkit** | object | none | Profile source and optional local-backend configuration. |
 | **pipelines** | map | empty | Maps pipeline IDs to pipeline definitions. |
 | **concurrency** | object | see below | Global LLM and extraction limits. |
@@ -69,6 +89,68 @@ Built-in defaults are:
 
 An empty cache directory in YAML deliberately selects the corresponding
 per-user root. An explicit empty output or debug directory is invalid.
+Selecting a chunk-plan or checkpoint directory does not configure filesystem
+access policy. Cache permissions come from deployment provisioning, process
+umask, setgid inheritance, and default ACLs; see [Operations](operations.md#cache-provisioning).
+
+Every nonempty relative configured destination or reference path resolves from
+the canonical directory of the file that supplies its surviving declaration.
+This includes imported fragments, selected configuration overlays, and values
+copied through inheritance: the copied value keeps its original declaring
+file. A child-supplied replacement resolves from the child's declaring file.
+Built-in relative destinations use the selected main configuration file's
+directory; explicit `--output-dir` and `--debug-dir` values use the invocation
+working directory. Absolute values remain unchanged.
+
+The root file can use ConfigKit imports to compose disjoint definitions. Imports
+and selected overlays remain under the configuration root; they do not merge or
+append a pipeline's `steps` sequence. An overlay replaces sequences as defined
+by ConfigKit, so changing an individual ordered binding requires supplying the
+whole replacement sequence.
+
+## Sibling Inheritance
+
+ConfigKit v0.5.0 supports native `extends` composition in mappings. A directive
+names exactly one immediate sibling in the same mapping; it is not a path or a
+cross-scope lookup. Imports, the selected overlay, and explicit overrides are
+composed before inheritance, which runs before typed decoding and normal
+Notarius validation. Every definition, including a parent and definitions not
+selected for a run, remains subject to ordinary validation.
+
+Child mappings recursively overlay parent mappings. A child sequence, scalar,
+or null replaces the inherited value. This makes pipeline inheritance useful
+for reusing a complete pipeline while replacing whole ordered lists:
+
+~~~yaml
+pipelines:
+  production:
+    input: {module: seriatim}
+    llm_profile: dnd-extraction
+    # Other complete pipeline settings and ordered steps...
+  development:
+    extends: production
+    structured_output_repair_attempts: 0
+~~~
+
+Pipeline names are siblings within `pipelines`; nested mappings such as named
+artifact lanes also have their own sibling namespace. Step entries are a
+sequence, so a step cannot extend another step. Replacing `steps` or a validator
+chain supplies the complete replacement sequence; entries are not appended or
+merged by identifier.
+
+Inherited values count as explicit input for Notarius's existing
+presence-sensitive rules: zero, false, and empty-list overrides stay explicit
+instead of restoring a default. Null also replaces the inherited value, but
+each field's ordinary type and validation rules still apply; null is not
+universally valid. Omitting `extends` preserves a relationship supplied by a
+lower-priority source, while `extends: null` cancels that relationship. It
+does not independently clear other inherited fields.
+
+`extends` is now a reserved key in every input mapping, including dynamic
+module options and named maps. Existing ordinary data or entry names using that
+key must be renamed along with any consumer that reads them. Configuration
+overlays, pipeline inheritance, and PromptKit profile `base_profile`
+inheritance are separate mechanisms.
 
 ## PromptKit Profiles
 
@@ -76,11 +158,12 @@ The optional **promptkit** object selects one source of profile definitions and
 may register one conventional local OpenAI-compatible backend:
 
 ~~~yaml
-version: 4
+version: 5
 
 promptkit:
   profile_dir: ./profiles
   # profile_file: ./profiles.yml
+  transient_retries: 2
   local_backend:
     endpoint: http://localhost:8000/v1
     concurrency_limit: 2
@@ -90,21 +173,23 @@ promptkit:
 | --- | --- | --- |
 | **profile_dir** | string | Non-empty directory containing profile files. |
 | **profile_file** | string | Non-empty profile file. |
+| **transient_retries** | integer | Non-negative additional built-in HTTP attempts for eligible transient provider failures; defaults to 2. Set 0 to disable these retries. |
 | **local_backend** | object | Optional registration for the conventional PromptKit backend ID **local**. |
 | **local_backend.endpoint** | string | Required when **local_backend** is present; absolute HTTP or HTTPS URL with a host. |
 | **local_backend.concurrency_limit** | integer | Optional non-negative limit; defaults to 0. |
 
-Set at most one of **profile_dir** and **profile_file**. Relative values use
-the process working directory, not the configuration file's directory. The
-complete example's `./examples/profiles/dnd-extraction.yml` value is therefore
-valid when Notarius is launched from the repository root; use an absolute path
-for services and containers.
+Set at most one of **profile_dir** and **profile_file**. Every nonempty relative
+configured filesystem path is resolved from the canonical directory of the
+file that supplies it. The complete example's
+`./llm-profiles/dnd-extraction.yml` value therefore resolves beside that example.
+Use absolute paths for services and containers when their deployment layout is
+not configuration-relative.
 
 An operator source is optional. For a requested ID, PromptKit checks the
 configured operator source first, then Notarius's embedded fallback profiles,
 then its own built-in catalog. A matching profile is complete: it replaces a
 lower-precedence definition rather than merging with it. The maintained
-[`dnd-extraction` operator profile](../examples/profiles/dnd-extraction.yml)
+[`dnd-extraction` LLM profile](../examples/llm-profiles/dnd-extraction.yml)
 is a secret-free deployment artifact; production, development, and local
 deployments can each provide a complete definition with that same workload ID.
 Use workload-oriented IDs for new profiles instead of model names.
@@ -147,30 +232,15 @@ requiring credential values. It rejects absent, malformed, or incompatible
 profiles before a run prepares modules. Credential availability is checked only
 when a generation is prepared.
 
-## Migrating Version 3 Configuration
+## Version 5 Migration
 
-Version 3 files are not decoded or rewritten. Change **version: 3** to
-**version: 4** and rename the top-level **scriptorium:** section to
-**promptkit:**. Version 4 decoding is strict, so a remaining **scriptorium**
-field is rejected as unknown.
-
-## Operational Environment Variables
-
-These variables are applied after YAML values:
-
-| Variable | Overrides | Rules |
-| --- | --- | --- |
-| **NOTARIUS_TOTAL_LLM_CONCURRENCY** | **concurrency.total_llm** | Integer. |
-| **NOTARIUS_STAGE_WORKERS_EXTRACT** | **concurrency.stage_workers.extract** | Integer. |
-| **NOTARIUS_OUTPUT_DIR** | **output.directory** | Non-empty path. |
-| **NOTARIUS_CACHE_CHUNK_PLANS_MODE** | **cache.chunk_plans.mode** | **auto**, **bypass**, or **refresh**. |
-| **NOTARIUS_CACHE_CHUNK_PLANS_DIR** | **cache.chunk_plans.directory** | Non-empty path. |
-| **NOTARIUS_CACHE_CHECKPOINTS_DIR** | **cache.checkpoints.directory** | Non-empty path. |
-| **NOTARIUS_DEBUG_DIR** | **debug.directory** | Non-empty path. |
-
-Integer values are trimmed then parsed as base-10 integers. Directory and
-output values reject NUL characters. **NOTARIUS_CONFIG** participates only in
-configuration discovery.
+Version 3 and version 4 files are rejected and are not rewritten at load time.
+Use `version: 5`, rename the former `scriptorium` section to `promptkit`, and
+convert every module binding to an object containing `module`. Convert every
+external reference to `{path: ...}` and move any lane-level references to the
+corresponding extraction binding. Put durable operational values in YAML or
+use the documented explicit run flags; the former field-level environment
+variables are not read.
 
 ## Concurrency, Output, Cache, And Debug
 
@@ -195,11 +265,14 @@ debug:
 **concurrency.total_llm** must be greater than zero. The only supported
 **concurrency.stage_workers** key is **extract**; its value must be from 1
 through **total_llm**. When omitted, it is recalculated from the effective
-**total_llm** after YAML and environment precedence.
+**total_llm** after imports, overlay selection, and explicit ConfigKit
+overrides.
 
 **cache.chunk_plans.mode** accepts **auto**, **bypass**, or **refresh**.
 **cache.checkpoints.enabled** is a boolean. The CLI can override the output
 directory and chunk-plan mode for one run; see [CLI reference](cli.md#run).
+Cache directory fields select only locations; Notarius has no cache permission
+field or operational environment override.
 
 ## Pipelines
 
@@ -209,14 +282,20 @@ Each **pipelines** entry has a unique, non-empty ID and the following shape:
 pipelines:
   dnd-session:
     llm_profile: dnd-extraction
-    input: seriatim
-    chunk: generic
-    output: json
+    input:
+      module: seriatim
+    chunk:
+      module: generic
+    output:
+      module: json
     artifacts:
       spells:
-        extract: dnd/spells
-        merge: appendorder
-        normalize: dnd/spells
+        extract:
+          module: dnd/spells
+        merge:
+          module: appendorder
+        normalize:
+          module: dnd/spells
 ~~~
 
 | Field | Type | Default | Rules |
@@ -286,19 +365,20 @@ A lane has these fields:
 | **extract** | module binding | none | Required. |
 | **merge** | module binding | **appendorder** | Optional. |
 | **normalize** | module binding | **noop** | Optional. |
-| **references** | map | none | Supported compatibility alias for **extract.references**. |
+| **references** | map | none | Not supported at lane scope; place references on the eligible binding. |
 | **validators** | list | none | Non-empty lane-level lists are rejected. Set validator overrides on a binding instead. |
 
-The lane-level **references** alias remains accepted. When the alias and
-**extract.references** bind the same slot, **extract.references** wins. Use
-the binding-local form in new configurations.
+Lane-level **references** are not supported. Put a lane extraction reference
+under **extract.references**.
 
 ## Module Bindings And Validators
 
-Use a module key directly when no other binding fields are needed:
+Every module and validator binding uses an object, even when it has no fields
+beyond its module key:
 
 ~~~yaml
-input: seriatim
+input:
+  module: seriatim
 ~~~
 
 Use an object for fields:
@@ -309,7 +389,8 @@ extract:
   llm_profile: dnd-extraction
   retries: 2
   references:
-    spell_catalog: ./dnd-spell-catalog.json
+    spell_catalog:
+      path: ./dnd-spell-catalog.json
 ~~~
 
 | Binding field | Type | Default | Rules |
@@ -381,18 +462,20 @@ When enabled, it publishes the selected source-unit excerpt defined by the
 
 ## References And Ordered Handoffs
 
-Reference maps bind named slots that the selected target declares. A scalar is
-an external path. Pipeline-level maps accept only external paths; step-local
-and binding-local maps may also select a normalized artifact from an earlier
-step:
+Reference maps bind named slots that the selected target declares. An external
+reference is an object with `path`. Pipeline-level maps accept only external
+paths; step-local and binding-local maps may also select a normalized artifact
+from an earlier step:
 
 ~~~yaml
 steps:
   - id: describe-session
     artifacts:
       npc-registry:
-        extract: dnd/npc-registry
-        normalize: dnd/npc-registry
+        extract:
+          module: dnd/npc-registry
+        normalize:
+          module: dnd/npc-registry
   - id: extract-events
     references:
       npc_registry:
@@ -401,8 +484,10 @@ steps:
           lane: npc-registry
     artifacts:
       spells:
-        extract: dnd/spells
-        normalize: dnd/spells
+        extract:
+          module: dnd/spells
+        normalize:
+          module: dnd/spells
 ~~~
 
 An artifact selector contains only **step** and **lane**. The producer must be
@@ -411,10 +496,16 @@ slot. A generated binding supplies one accepted normalized artifact; it does
 not name a file. A configured generated dependency remains required even when
 that consumer slot is otherwise optional.
 
-Pipeline references are defaults. A matching step-local or binding-local
-external path overrides a pipeline default. Required slots must be bound after
-these configuration values and any CLI reference overrides are applied.
-Reference paths in YAML are resolved relative to the configuration file.
+Pipeline references are configuration defaults. A matching step-local or
+binding-local external path overrides a pipeline default. CLI reference
+bindings are then operational overrides of configured external paths; their
+pipeline, lane, and binding scopes and precedence are defined by the
+[CLI reference](cli.md#reference-selectors). A CLI file reference cannot
+replace a configured generated artifact handoff. Required slots must be bound
+after configuration and CLI reference actions are applied. A YAML reference
+path resolves from the file that supplies its surviving declaration, including
+an imported fragment or selected overlay. CLI reference paths resolve relative
+to the process working directory.
 
 ### D&D Reference Slots
 
@@ -504,11 +595,33 @@ Available validator keys are:
 | Item occurrences | **extract/dnd/item-occurrences/shape**, **extract/dnd/item-occurrences/registry**, **extract/dnd/item-occurrences/source_refs**, **extract/dnd/item-occurrences/source_relatedness**, **normalize/dnd/item-occurrences/invariants** |
 | Item registry | **extract/dnd/item-registry/shape**, **extract/dnd/item-registry/source_refs**, **extract/dnd/item-registry/source_relatedness**, **normalize/dnd/item-registry/identity** |
 | NPC occurrences | **extract/dnd/npc-occurrences/shape**, **extract/dnd/npc-occurrences/registry**, **extract/dnd/npc-occurrences/source_refs**, **extract/dnd/npc-occurrences/source_relatedness**, **normalize/dnd/npc-occurrences/invariants** |
-| Scene descriptions | **extract/dnd/scene-descriptions/shape**, **extract/dnd/scene-descriptions/source_refs**, **extract/dnd/scene-descriptions/source_relatedness**, **normalize/dnd/scene-descriptions/invariants** |
+| Scene descriptions | **extract/dnd/scene-descriptions/shape**, **extract/dnd/scene-descriptions/source_refs**, **extract/dnd/scene-descriptions/source_relatedness**, **extract/dnd/scene-descriptions/combat_semantics** (LLM-backed, opt-in), **normalize/dnd/scene-descriptions/invariants** |
 | Enemy events | **extract/dnd/enemy-events/shape**, **extract/dnd/enemy-events/engagements**, **extract/dnd/enemy-events/source_refs**, **extract/dnd/enemy-events/source_relatedness**, **normalize/dnd/enemy-events/invariants** |
 | Location registry | **extract/dnd/location-registry/shape**, **extract/dnd/location-registry/source_refs**, **extract/dnd/location-registry/source_relatedness**, **normalize/dnd/location-registry/identity** |
 | Location occurrences | **extract/dnd/location-occurrences/shape**, **extract/dnd/location-occurrences/registry**, **extract/dnd/location-occurrences/source_refs**, **extract/dnd/location-occurrences/source_relatedness**, **normalize/dnd/location-occurrences/invariants** |
 
+`extract/dnd/scene-descriptions/combat_semantics` is not in a production default chain. To opt in, replace the scene extractor validator chain with the current ordered chain plus the semantic validator last, and set a positive producer retry budget if a rejection should request a corrected scene:
+
+~~~yaml
+extract:
+  module: dnd/scene-descriptions
+  retries: 1
+  validators:
+    - module: generic/valid_json
+    - module: extract/dnd/scene-descriptions/shape
+    - module: extract/dnd/scene-descriptions/source_refs
+    - module: generic/valid_json_schema
+    - module: extract/dnd/scene-descriptions/source_relatedness
+    - module: extract/dnd/scene-descriptions/combat_semantics
+      retries: 1
+~~~
+
+An override replaces, rather than extends, the default chain. See [Module Bindings And Validators](#module-bindings-and-validators) for binding, profile, repair, retry, and failure-policy rules.
+
+The validator retry shown above permits one additional execution against the
+same scene candidate when the LLM-backed validator itself fails; it is separate
+from both the extractor's producer retry and PromptKit structural repair.
+
 When no override is configured, production D&D bindings use the following
 ordered chains. Each row lists extract then normalize; spell chains are the
 same at both stages.
@@ -541,7 +654,16 @@ go run ./cmd/notarius config validate \
 ~~~
 
 Configuration validation rejects invalid YAML, unsupported fields, invalid
-defaults or environment overrides, incompatible module keys, unknown options,
+defaults or explicit CLI overrides, incompatible module keys, unknown options,
 invalid reference bindings, missing required reference slots, invalid validator
 overrides, and incompatible generated artifact handoffs. Use
 [pipelines list](cli.md#pipelines-list) to inspect configured IDs.
+
+## Inspection
+
+Use [config effective](cli.md#config-effective) to write the selected composed
+configuration as deterministic, redacted YAML. Use
+[config explain](cli.md#config-explain) with a canonical JSON Pointer to inspect
+the effective or historical provenance for one path, including a value displaced
+by a selected overlay. Neither command resolves a pipeline, prepares modules,
+materializes references, or requires provider credentials.

docs/consumers/dnd-pipeline.md

@@ -23,14 +23,14 @@ A deployment must provide its own PromptKit profile and campaign reference
 files. Use absolute paths for service and subprocess deployments. In
 particular, observe these different resolution rules:
 
-- reference paths in YAML are resolved relative to the Notarius configuration
-  file; and
-- `promptkit.profile_file` is resolved relative to the Notarius process working
-  directory.
+- reference and PromptKit profile paths in YAML are resolved relative to the
+  file that supplies their surviving declaration;
+- reference paths passed with `--reference` are resolved relative to the
+  Notarius process working directory.
 
 Do not copy the repository example's relative profile path into a deployment
-without also controlling that working directory. The complete path and profile
-rules are defined in [Configuration](../config.md).
+without preserving its configuration-relative layout. The complete path and
+profile rules are defined in [Configuration](../config.md).
 
 Preflight the deployed configuration before processing sessions and whenever
 it changes:
@@ -73,9 +73,21 @@ notarius run dnd-session \
   --config /absolute/path/to/notarius.yml \
   --input /absolute/path/to/transcripts/final.trimmed.json \
   --output-dir /absolute/path/to/notarius-output \
+  --reference party=/absolute/path/to/references/party.txt \
+  --reference players=/absolute/path/to/references/players.txt \
+  --reference glossary=/absolute/path/to/references/glossary.txt \
+  --reference spell_catalog=/absolute/path/to/references/spells.json \
   --json
 ```
 
+Each unqualified reference is pipeline-scoped: Notarius supplies it to every
+selected D&D target that declares the slot. A deployment may omit an optional
+reference it does not maintain, and may use the lane- or binding-qualified
+forms from the [CLI reference](../cli.md#reference-selectors) for an exceptional
+override. The registry, scene-description, combat-turn, and NPC-occurrence
+references declared between ordered steps in the complete configuration are
+generated artifacts. Do not pass those handoffs on the CLI.
+
 The caller should:
 
 - capture stdout and stderr separately;
@@ -92,7 +104,7 @@ stream and exit-status contract.
 ## Discover The Published Bundle
 
 Decode the successful stdout document as a supported run-result schema. For
-the current contract, `schema_version` is `notarius.run-result.v1`. Tolerate
+the current contract, `schema_version` is `notarius.run-result.v2`. Tolerate
 unknown fields allowed by that version, but reject an unsupported schema
 version.
 
@@ -145,7 +157,8 @@ The JSON encoder always publishes these bundle-management files:
 | `index.json` | Discovery document for lane and pipeline-wide artifacts. |
 | `manifest.json` | Run provenance and result summaries. |
 | `rejected.json` | Rejected pipeline outputs. |
-| `warnings.json` | Accepted-output and run warnings. |
+| `warnings.json` | Actionable process-degradation warnings. |
+| `diagnostics.json` | Advisory and observation findings for accepted artifacts. |
 
 The complete configuration also requests two pipeline-wide artifacts:
 

docs/consumers/subprocess.md

@@ -15,9 +15,12 @@ configured lane inventory, and downstream acceptance checklist, see
 Optionally preflight a selected configuration and pipeline before work starts:
 
 ```sh
-notarius config validate --config /path/to/notarius.yml --pipeline pipeline-id
+notarius config validate --config /path/to/notarius.yml --config-overlay production --pipeline pipeline-id
 ```
 
+Omit `--config-overlay` when the composed base configuration is the intended
+selection; it is independent from any `--llm-profile` run override.
+
 Invoke the run with explicit paths and machine-readable output. Capture
 standard output and standard error separately; do not combine them before
 processing the result.
@@ -25,19 +28,43 @@ processing the result.
 ```sh
 notarius run pipeline-id \
   --config /path/to/notarius.yml \
+  --config-overlay production \
   --input /path/to/source.json \
   --output-dir /path/to/output-root \
   --json
 ```
 
 Use absolute paths for supplied input, configuration, output-root, and
-reference files. Notarius generates a stable prompt session for the resolved
-input module and exact input bytes. Pass **--session-id** only when intentionally
-grouping different invocations under a different session. Supply credentials
-through Notarius's documented configuration and environment mechanisms, never
-as command-line arguments or generated secret-bearing configuration. In
-particular, a session identifier is provider-visible and is not a credential
-mechanism.
+reference files. Pass each external reference as its own argument-vector pair;
+do not construct and invoke a shell command. An unqualified reference selector
+supplies that file to every compatible selected target. Lane and stage
+qualification are available for exceptional overrides, while generated
+same-run references remain part of configured pipeline composition. The
+[CLI reference](../cli.md#reference-selectors) owns the exact selector and
+precedence contract.
+
+The maintained D&D subprocess workflow uses this facility for campaign context:
+
+```sh
+notarius run dnd-session \
+  --config /absolute/path/to/notarius.yml \
+  --input /absolute/path/to/transcripts/final.trimmed.json \
+  --output-dir /absolute/path/to/notarius-output \
+  --reference party=/absolute/path/to/references/party.txt \
+  --reference players=/absolute/path/to/references/players.txt \
+  --reference glossary=/absolute/path/to/references/glossary.txt \
+  --reference spell_catalog=/absolute/path/to/references/spells.json \
+  --json
+```
+
+Only pass the external references available to and desired by the deployment.
+Notarius generates a stable prompt session for the resolved input module and
+exact input bytes; reference changes do not change it. Pass **--session-id**
+only when intentionally grouping different invocations under a different
+session. Supply credentials through Notarius's documented configuration and
+environment mechanisms, never as command-line arguments or generated
+secret-bearing configuration. In particular, a session identifier is
+provider-visible and is not a credential mechanism.
 
 Wait for the process before interpreting standard output. Only an exit status
 of 0 permits decoding the receipt. On a nonzero exit, retain standard error for
@@ -79,7 +106,7 @@ silently treated as fully reviewed by the caller.
 ## Preserve Provenance And Handle Data Carefully
 
 Keep the receipt with the published `manifest.json`, and retain
-`rejected.json` and `warnings.json` when review or later provenance requires
+`rejected.json`, `warnings.json`, and `diagnostics.json` when review or later provenance requires
 them. Treat the input, output bundle, cache, debug bundle, and captured process
 logs as potentially sensitive data. Apply the caller's access controls and
 retention policy, and avoid copying secrets into arguments, logs, or

docs/development.md

@@ -4,19 +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. |
@@ -25,7 +47,7 @@ implemented component map.
 | 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 verification | [Source Releases](release.md) and [Documentation Policy](policy/documentation.md) | The release procedure owns maintainer guards and immutable-tag recovery; the policy assigns release-note ownership. |
+| 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

docs/integrations/json-output.md

@@ -9,7 +9,7 @@ Output configuration, including chunk-map and evidence-context publication, belo
 ## Bundle Layout
 
 All paths below are logical, relative, slash-separated bundle paths. The
-encoder always emits the first four JSON files below and adds lane or
+encoder always emits the first five JSON files below and adds lane or
 pipeline-wide artifact files when their corresponding artifacts are available:
 
 A subprocess caller first obtains the physical bundle root from the
@@ -21,7 +21,8 @@ root for the logical discovery described here.
 | `index.json` | Entry point that names the other published files and lane payloads. |
 | `manifest.json` | Run provenance and result summaries. |
 | `rejected.json` | Rejected pipeline outputs. |
-| `warnings.json` | Accepted-output and run warnings. |
+| `warnings.json` | Actionable process-degradation warnings. |
+| `diagnostics.json` | Accepted-artifact quality advisories and normalization observations. |
 | `lanes/<safe-lane-id>.json` | One normalized artifact payload for each lane. |
 | `chunk-map.json` | Optional accepted chunk map, when its export is enabled and available. |
 | `evidence-context.json` | Optional selected source-unit excerpt, when evidence publication is enabled. |
@@ -39,7 +40,8 @@ normalized lanes has this valid minimal index:
   "manifest_file": "manifest.json",
   "output_files": [],
   "rejected_file": "rejected.json",
-  "warnings_file": "warnings.json"
+  "warnings_file": "warnings.json",
+  "diagnostics_file": "diagnostics.json"
 }
 ```
 
@@ -49,6 +51,7 @@ normalized lanes has this valid minimal index:
 | `output_files` | Yes | Lane descriptors sorted by `lane_id`. |
 | `rejected_file` | Yes | Always `rejected.json`. |
 | `warnings_file` | Yes | Always `warnings.json`. |
+| `diagnostics_file` | Yes | Always `diagnostics.json`. |
 | `chunk_map` | No | Descriptor for the pipeline-wide `chunk-map.json`; never a lane descriptor. |
 | `evidence_context` | No | Descriptor for the pipeline-wide `evidence-context.json`; never a lane descriptor. |
 
@@ -132,7 +135,7 @@ These values describe observed execution; they are not a backend-registration
 interface. Entries that differ by backend or effective reasoning remain
 distinct even when their profile, provider, and model are otherwise equal.
 
-## Rejections And Warnings
+## Rejections, Warnings, And Diagnostics
 
 `rejected.json` is always an object with a `rejected` array. Each entry has
 required `stage` and `message`; `step_id`, `lane_id`, `module_key`, `chunk_id`,
@@ -142,9 +145,47 @@ contain the bounded `validation` summary described above; the existing singular
 validator and reason fields remain the first configured rejection for
 compatibility.
 
-`warnings.json` is always an object with a `warnings` array. Each warning has
-`reason_code` and `message`; `scope` is optional. Both arrays are empty when
-there is nothing to report.
+`warnings.json` is always the `notarius.warnings.v2` envelope:
+
+```json
+{
+  "schema_version": "notarius.warnings.v2",
+  "group_count": 0,
+  "occurrence_count": 0,
+  "groups": []
+}
+```
+
+It contains only process warnings. `group_count` is exact, and
+`occurrence_count` is the exact sum of its group occurrence counts.
+
+`diagnostics.json` is always the `notarius.diagnostics.v1` envelope:
+
+```json
+{
+  "schema_version": "notarius.diagnostics.v1",
+  "group_count": 0,
+  "occurrence_count": 0,
+  "truncated": false,
+  "unrepresented_occurrence_count": 0,
+  "groups": []
+}
+```
+
+It contains only advisory and observation groups. `group_count` counts groups
+represented in `groups`; `occurrence_count` includes both represented and
+unrepresented occurrences. When `truncated` is true,
+`unrepresented_occurrence_count` is the exact number omitted from group
+representation.
+
+Each group has `disposition`, `category`, `reason_code`, framework-owned
+`origin`, exact `occurrence_count`, bounded `samples`, and
+`omitted_sample_count`. Samples carry safe `scope` and `message`, plus a chunk
+ID and zero-based chunk index when applicable. A group retains at most three
+distinct samples. The framework fails rather than truncating actionable
+warnings beyond 128 groups; it represents at most 256 advisory/observation
+groups and records further occurrences through the diagnostic truncation
+fields above.
 
 ## Compatibility
 

docs/integrations/pkg-configkit.md

@@ -0,0 +1,19 @@
+# ConfigKit Integration
+
+Notarius uses the public root package
+[`gitea.maximumdirect.net/eric/ConfigKit`](https://gitea.maximumdirect.net/eric/ConfigKit)
+at v0.5.0 for version 5 configuration acquisition, imports, overlays, explicit
+overrides, native sibling inheritance, diagnostics, and safe inspection
+rendering. ConfigKit composes source precedence and inheritance before typed
+decoding; Notarius does not perform a second inheritance merge.
+
+Notarius owns the typed document, domain defaults and validation, runtime
+conversion, catalog-dependent pipeline resolution, source-aware configured
+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. See the pinned upstream [v0.5.0 release notes](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/dc09959cca4e105f49ec316c6d4ba585bd2340bd/docs/releases/v0.5.0.md)
+and [configuration contract](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/dc09959cca4e105f49ec316c6d4ba585bd2340bd/docs/config.md).
+
+See the canonical [ConfigKit attribution](../oss/attribution.md#configkit) for
+its license and notices.

docs/integrations/pkg-promptkit.md

@@ -1,11 +1,11 @@
 # PromptKit Integration
 
 Notarius pins
-[`gitea.maximumdirect.net/eric/promptkit` v0.9.0](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.9.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.9.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.9.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.9.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
@@ -53,7 +53,7 @@ Notarius sends one stable effective session through PromptKit's direct session
 field, which is authoritative for provider session behavior. It also retains
 the same value as the `session_id` prompt variable for maintained prompt
 compatibility. The generated identifier is 76 ASCII characters, within
-PromptKit v0.9.0's 256-code-point session limit. Session IDs are non-secret
+PromptKit's 256-code-point session limit. Session IDs are non-secret
 correlation identifiers and may be exposed to providers and provider
 observability. The CLI contract owns generation and override behavior.
 
@@ -71,7 +71,15 @@ endpoint-only profiles have no such backend limit. The adapter translates
 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, and leaves retries to the calling pipeline stage.
+error type. PromptKit's built-in client retries eligible transient HTTP failures
+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
+`LLMGenerationError`, retaining a safe failure kind, HTTP status when present,
+and retry-exhaustion attempt count. Transport, malformed successful envelopes,
+provider statuses, and generic generation failures remain distinct without
+exposing PromptKit error values to Notarius callers.
 
 ## Profile Sources And Compatibility
 
@@ -86,16 +94,16 @@ 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.9.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.
 
-PromptKit v0.9.0 accepts only the `developer`, `system`, `user`, and
+PromptKit accepts only the `developer`, `system`, `user`, and
 `assistant` text-chat roles after normalizing case and surrounding whitespace.
 Maintained Notarius prompt definitions use only `system` and `user`.
 
-For application-owned semantic correction, Notarius uses PromptKit v0.9.0's
+For application-owned semantic correction, Notarius uses PromptKit's
 `RunRequest.AppendedMessages` after the ordinary rendered prompt. It supplies
 exactly two messages in order: the latest validated producer response with
 role `assistant`, then deterministic validation guidance with role `user`.
@@ -112,12 +120,28 @@ and terminal summaries retain only safe counts, digests, identities, and usage;
 complete appended messages remain limited to the explicitly requested detailed
 debug trace.
 
-PromptKit now obtains its maintained OpenRouter and Rakestrawhome backend and
+PromptKit obtains its maintained OpenRouter and Rakestrawhome backend and
 profile catalogs from independently versioned transitive modules. Notarius
 does not import or register either catalog; PromptKit retains catalog source,
 identity, precedence, credential, and capacity ownership.
 
-Notarius supports this boundary against PromptKit v0.9.0. Its fallback source,
+External catalog profile names and settings can change between dependency
+releases, including removal without aliases. Review directly selected IDs and
+inherited `base_profile` values when upgrading. An application-owned alias that
+inherits an external profile does not freeze that profile's settings.
+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.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
+`dnd-extraction` fallback already follows this model and does not inherit an
+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.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,
@@ -146,3 +170,9 @@ profile/configuration contracts against the upstream documentation. Maintained
 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.
+
+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).

docs/integrations/run-result.md

@@ -9,18 +9,22 @@ Command syntax, streams, and exit statuses are defined in the
 
 ## Schema
 
-The current schema version is `notarius.run-result.v1`.
+The current schema version is `notarius.run-result.v2`.
 
 | Field | Required | Meaning |
 | --- | --- | --- |
-| `schema_version` | Yes | Exactly `notarius.run-result.v1`. |
+| `schema_version` | Yes | Exactly `notarius.run-result.v2`. |
 | `run_id` | Yes | The finalized Notarius run identifier. |
 | `pipeline_id` | Yes | The effective pipeline identifier. |
 | `output_directory` | Yes | Absolute path to the published, run-specific output bundle. |
 | `index_file` | For the production JSON output | Logical path `index.json`; omitted for other output modules. |
 | `normalized_output_count` | Yes | Number of final normalized outputs. |
 | `rejected_output_count` | Yes | Number of recorded rejected outputs. |
-| `warning_count` | Yes | Number of final run warnings. |
+| `warning_group_count` | Yes | Exact number of actionable warning groups. |
+| `warning_occurrence_count` | Yes | Exact occurrences represented by actionable warning groups. |
+| `diagnostic_group_count` | Yes | Number of represented advisory and observation groups. |
+| `diagnostic_occurrence_count` | Yes | Advisory and observation occurrences, including unrepresented occurrences. |
+| `diagnostics_truncated` | Yes | Whether advisory/observation group representation was truncated. |
 | `validation_status` | Yes | The final run manifest validation status. |
 | `validation_summaries` | No | Bounded per-producer validation outcomes; present when producer work ran. |
 | `debug_directory` | No | Absolute path to the run-specific debug bundle when requested debug capture completed. |
@@ -34,14 +38,18 @@ means one or more otherwise accepted results advanced under validator-failure
 
 ```json
 {
-  "schema_version": "notarius.run-result.v1",
+  "schema_version": "notarius.run-result.v2",
   "run_id": "run-1770000000000000000-0123456789abcdef0123456789abcdef",
   "pipeline_id": "dnd-session",
   "output_directory": "/work/results/run-1770000000000000000-0123456789abcdef0123456789abcdef",
   "index_file": "index.json",
   "normalized_output_count": 6,
   "rejected_output_count": 2,
-  "warning_count": 1,
+  "warning_group_count": 1,
+  "warning_occurrence_count": 2,
+  "diagnostic_group_count": 3,
+  "diagnostic_occurrence_count": 5,
+  "diagnostics_truncated": false,
   "validation_status": "incomplete",
   "validation_summaries": [
     {

docs/internal/cli.md

@@ -25,7 +25,8 @@ preparation, and runner mechanics after their inputs are supplied.
 ## Dispatch And Configuration Handoff
 
 The root dispatcher handles help, version reporting, configuration validation,
-pipeline listing, and a pipeline run. Version reporting resolves build
+effective-configuration inspection, explanation inspection, pipeline listing,
+and a pipeline run. Version reporting resolves build
 information through `internal/buildinfo` before production composition, so the
 diagnostic remains available without configuration or runtime collaborators.
 The public syntax, streams, exit classes, and version semantics are defined by
@@ -33,14 +34,15 @@ the [CLI reference](../cli.md). Other root commands normalize injectable
 options before dispatch so that a missing production dependency fails as a
 command error rather than reaching execution.
 
-Commands that need configuration use one shared loader. The CLI discovers the
-file, parses it through **internal/core/config**, starts from defaults, applies
-the file and supported environment overrides, and then validates it for the
-command. The configured discovery and precedence contract is in
+Commands that need configuration use one shared ConfigKit-backed loader. The
+CLI discovers the file, passes the requested overlay and only explicit
+configuration-valued run overrides, and receives a **LoadedConfig**. The
+configured discovery and precedence contract is in
 [Configuration](../config.md), while the loading and resolution mechanics are
 in [Configuration Internals](configuration.md).
 
-Configuration validation without a selected pipeline checks structural
+`config effective` and `config explain` only render the loaded ConfigKit view;
+they do not resolve pipelines or construct providers. Configuration validation without a selected pipeline checks structural
 configuration only. Validation with a selected pipeline also builds the
 effective catalog, resolves the pipeline, and verifies every explicit effective
 PromptKit profile. Selected LLM-backed input, chunk, lane, output, and validator
@@ -84,8 +86,7 @@ field.
 After parsing and validating a run invocation, the CLI performs this ordered
 handoff:
 
-1. load and validate configuration, then apply command-level operational
-   overrides;
+1. load and validate configuration with ConfigKit command overrides;
 2. create and validate a safe run identity, then allocate a debug bundle only
    when requested;
 3. build the effective catalog, resolve requested reference changes, resolve
@@ -115,6 +116,16 @@ to checkpoint identity and `pipeline.RunInput`. The public flag and stability
 contract are defined by the [CLI reference](../cli.md#run); framework and LLM
 packages only transport the supplied value.
 
+The CLI also owns the scope grammar for reference flags. It enumerates the
+selected chunk and lane targets from registered module specifications, expands
+pipeline- and lane-scoped actions into exact stage-and-lane bindings, and
+resolves overlapping bind and unbind actions by specificity before calling
+configuration resolution. The generic pipeline therefore receives only exact
+`ReferenceBinding` and `ReferenceUnbind` values and has no knowledge of CLI
+selector syntax. Configuration resolution retains ownership of configured
+external/generated conflicts, required slots, and module compatibility; file
+materialization still occurs afterward.
+
 For `run --json`, the CLI constructs and encodes its private run-result receipt
 after a successful runner result is available, before it publishes logical
 output files. It writes the prepared receipt to standard output only after
@@ -166,8 +177,9 @@ is discoverable.
 - **internal/cli/production_contract_test.go** covers registrar composition,
   production catalog contents, assets, and representative configuration
   validation.
-- **internal/cli/reference_contract_test.go** covers CLI reference overrides,
-  origin separation, and materialization boundaries.
+- **internal/cli/reference_contract_test.go** covers scoped CLI reference
+  expansion, specificity, bind/unbind conflicts, generated-reference
+  protection, origin separation, and materialization boundaries.
 - **internal/cli/state_hardening_test.go** covers safe run identity, state
   roots, and failure ordering.
 

docs/internal/configuration.md

@@ -8,17 +8,17 @@ either interface.
 
 ## Boundary
 
-The configuration package turns a selected YAML file and supported environment
-values into a validated, independently owned configuration. It then resolves a
+The configuration package turns a selected ConfigKit-composed YAML document
+into a validated, independently owned configuration. It then resolves a
 requested pipeline against a module catalog before the framework prepares or
 runs anything.
 
 | Boundary | Inputs | Outputs | Does not own |
 | --- | --- | --- | --- |
-| Loading | Selected file path and environment lookup | Parsed file model and a populated **Config** | Choosing the file path or reporting a command result. |
+| Loading | Selected file path, overlay, overrides, and invocation directory | **LoadedConfig** with ConfigKit inspection metadata and a populated **Config** | Choosing the file path or reporting a command result. |
 | Validation | **Config** | Structural configuration errors with pipeline, lane, or binding context | Module availability, capabilities, or construction. |
 | Resolution | Valid **Config**, selected pipeline and lanes, runtime reference changes, LLM override, and module catalog | **EffectiveConfig** with a **ResolvedPipeline** | Materializing reference bytes, preparing modules, execution, or filesystem state. |
-| Summary | **Config** or **EffectiveConfig** | Detached redacted payload suitable for debug summaries | Redacting arbitrary process state or provider traffic. |
+| Inspection | **LoadedConfig** and an optional JSON Pointer | Redacted effective YAML or explanation text | Pipeline selection, module preparation, or provider work. |
 
 The CLI discovers a configuration file, invokes this package, and supplies the
 result to the framework. Configuration never reads an input file, constructs a
@@ -28,23 +28,26 @@ at their respective [CLI](cli.md), [pipeline](pipeline.md), and
 
 ## Loading And Validation
 
-The CLI loads configuration in this order:
-
-1. parse the selected YAML file strictly into the file model;
-2. start from **Default**;
-3. apply the file model; and
-4. apply the supported environment overrides.
-
-This establishes the public precedence order without giving environment input a
-second file schema. Loading and application reject malformed YAML, unsupported
-file versions, unknown fields, invalid values, and identifiers that are empty
-or collide after whitespace normalization. The file application also makes the
-effective extraction-worker default follow the effective LLM limit. A present
-PromptKit local-backend object requires and trims its endpoint, defaults its
-omitted concurrency limit to zero, and is copied so the parsed file model
-cannot alias the populated **Config**. A pipeline `llm_profile` is
-presence-aware: omission remains empty, while a present blank value is
-rejected and a non-empty file value is trimmed before it reaches **Config**.
+ConfigKit composes the selected root, imports, optional selected overlay, and
+explicit CLI overrides in precedence order, then expands native sibling
+inheritance before typed decoding. The document definition supplies typed
+defaults and structural validation; Notarius's recorded resolution changes
+normalize configured paths after decode. Path normalization follows the source
+of the surviving value, including a value copied through inheritance, rather
+than the inheritance directive's location. Inherited input remains explicit
+for presence-sensitive behavior, including zero, false, and empty values;
+existing field validation still governs whether the resulting values are valid.
+ConfigKit's inspection history retains inheritance transfers alongside later
+normalization, and effective configuration renders the normalized values used
+by runtime conversion. The private typed document consumes the directive, so
+no upstream inheritance type or unresolved directive reaches runtime pipeline
+or module contracts. See [Configuration](../config.md#sibling-inheritance)
+for the operator syntax and field rules. Only
+`NOTARIUS_CONFIG` participates in discovery; retired field-level environment
+variables do not participate in loading. Version 5 decoding rejects scalar
+module bindings and scalar external references. ConfigKit retains redacted,
+historical inspection metadata while **LoadedConfig** keeps that implementation
+detail private behind effective and explanation writers.
 
 **Config.Validate** checks configuration-only invariants before resolution. It
 rejects incompatible profile sources, invalid state-surface values, unsupported
@@ -52,18 +55,21 @@ concurrency settings, malformed bindings and references, invalid retries, and
 invalid pipeline, step, or lane structure. PromptKit local-backend validation
 accepts only an absolute HTTP or HTTPS endpoint with a host and no user
 information, query, or fragment, and rejects a negative local concurrency
-limit. Its errors retain the closest known pipeline, lane, and binding context.
+limit. It also rejects a negative `promptkit.transient_retries` value; decoded
+omission resolves to two, while explicit zero remains a distinct opt-out. Its
+errors retain the closest known pipeline, lane, and binding context.
 It deliberately does not require modules to be registered: that requires a
 catalog and belongs to resolution.
 
 The exact user-selectable values and validation rules are defined in
-[Configuration](../config.md). Keep additions to the file model, an
-environment override, its validation, and that reference in the same change.
+[Configuration](../config.md). Keep document schema, source-aware normalization,
+runtime conversion, and that reference aligned in the same change.
 
 ## Effective Resolution
 
-**Config.Resolve** first recomputes derived concurrency defaults and validates
-the configuration. It normalizes the requested pipeline ID, copies the selected
+**Config.Resolve** derives an absent extraction-worker value in an owned copy
+and validates the configuration. A programmatically supplied worker value is
+always explicit. It normalizes the requested pipeline ID, copies the selected
 profile, and passes the non-empty command-level LLM profile override, requested
 lane selection, and reference changes to the framework resolver.
 
@@ -110,43 +116,39 @@ bytes, a debug payload, or all runtime state. The CLI records it as invocation
 provenance before execution; cache and checkpoint identity have additional
 owners in [Run State Internals](state.md).
 
-Configuration summaries must use **Redacted**, **RedactedSummaryPayload**, or
-**RedactedResolvedPipelinePayload**, never a direct configuration marshal.
-Those methods copy every binding and nested option container, replace values
-whose key is credential-shaped with **[REDACTED]**, and omit materialized
-reference content while retaining safe binding and reference provenance. The
-payload must not alias the source configuration or resolved pipeline.
-PromptKit's local endpoint and concurrency limit are preserved as non-secret
-configuration metadata in the independently owned summary; the object contains
-no credential value. This redaction is deliberately narrow: it protects
-configuration summaries and does not authorize recording arbitrary environment
-values or provider requests.
+Configuration publication uses ConfigKit's redacted effective YAML. Resolved
+pipeline publication uses **RedactedResolvedPipelinePayload**, which copies
+bindings and nested option containers, replaces credential-shaped values with
+**[REDACTED]**, and omits materialized reference content while retaining safe
+provenance. This redaction is deliberately narrow and does not authorize
+recording arbitrary environment values or provider requests.
 
 ## Invariants To Preserve
 
-- Defaults, YAML values, and environment values are applied in one direction;
-  later sources may override only their supported operational settings.
+- ConfigKit composition applies defaults, imports, an optional overlay, and
+  explicit overrides in one direction with retained origin metadata.
 - A configuration is structurally valid before it is resolved, and a resolved
   pipeline is compatible with the supplied catalog before preparation begins.
 - Whitespace-normalized identifiers are unique wherever they identify a
   pipeline, step, lane, worker, or reference slot.
-- Resolution and summary generation return detached data. Redaction must cover
-  every configured and resolved binding, including nested validator bindings.
+- Runtime conversion and resolved-pipeline publication return detached data.
+- The resolved PromptKit transient-retry budget is always passed to the shared
+  built-in client; document presence preserves an explicit zero.
 - The resolved digest changes when resolved composition changes and never
   includes itself.
 
 ## Focused Tests
 
-- **internal/core/config/file_config_contract_test.go** covers strict file
-  parsing, normalization, file application, and structural rejection.
-- **internal/core/config/env_contract_test.go** covers supported operational
-  overrides and their precedence.
+- **internal/core/config/document_test.go** and
+  **operational_document_test.go** cover ConfigKit document loading,
+  normalization, imports, overlays, and overrides.
 - **internal/core/config/validation_contract_test.go** covers configuration
   invariants and contextual failures.
 - **internal/core/config/effective_config_contract_test.go** covers defaults,
   selections, overrides, resolution context, digest changes, and ownership.
-- **internal/core/config/redaction_test.go** covers recursive credential
-  redaction, reference-content exclusion, and non-aliasing payloads.
+- **internal/core/config/loaded_config_test.go** covers safe effective and
+  explanation rendering; **redaction_test.go** covers resolved-pipeline
+  redaction and reference-content exclusion.
 
 Run **go test ./internal/core/config** after changing this boundary. Changes to
 the handoff or resolved-composition semantics also need the focused framework

docs/internal/dnd.md

@@ -29,13 +29,17 @@ The D&D registrar registers the family’s artifact codecs, extractors, typed
 append-order mergers, normalizers, validators, prompt assets, fallback LLM
 profile asset, and default validator chains. Each extractor and normalizer has
 a stable module spec, explicit execution class, strict option decoding, and a
-typed builder. Scene chunking, every extractor, and NPC, location, and item-registry
-normalization are registered as `llm_backed`; the remaining current D&D mergers
-and normalizers are `deterministic`. The metadata is available to catalog inspection and
-resolved-pipeline debug data and determines which selected bindings inherit the
-pipeline profile. The registry normalizers use `single_response_v1`, forwarding
-corrections to their reconciliation completion and retaining the accepted raw
-proposal only as an owned model candidate. Configuration remains the canonical owner of the exact keys,
+typed builder. Scene chunking, every extractor, and NPC, location, and
+item-registry normalization are registered as `llm_backed`; the remaining
+current D&D mergers and normalizers are `deterministic`. The metadata is
+available to catalog inspection and resolved-pipeline debug data and determines
+which selected bindings inherit the pipeline profile. The registry normalizers
+use `single_response_v1`, forwarding corrections to their reconciliation
+completion and retaining the accepted raw proposal only as an owned model
+candidate. When deterministic proposal safety or typed application rejects a
+group, they provide separate model-facing prose for a corrective module retry;
+internal issue categories, reason codes, and operator messages remain
+diagnostic-only. Configuration remains the canonical owner of the exact keys,
 profile precedence, and validator order.
 
 Private structured-LLM response schemas are deliberately minimal. They reject
@@ -117,14 +121,27 @@ presentation, and final ephemeral generic transcript windows. These orders and
 cache controls are prompt behavior; change them only through the owning
 manifest and prompt declaration.
 
+NPC, item, and location registry reconciliation translate shared proposal
+safety categories into bounded prose that references only the response-local
+duplicate-group ordinals and candidate handles. Item reconciliation appends its
+typed rule that currency may be consolidated only with aliases of the same
+denomination and never with non-currency items. The next normalize attempt
+receives that prose with the exact defective proposal under the shared
+replacement-request protocol. Structurally invalid output has no valid proposal
+candidate and receives a fresh feedback-free attempt instead. If the stage
+budget is exhausted, safe groups stay applied, unsafe groups stay separate, and
+one fallback warning summarizes the final defect without raw model content.
+
 ## Evidence, Candidates, And Normalization
 
 The current transcript is the only durable evidence source. Extractors assign
-the current source identity, preserve candidate evidence ranges for validators,
-and canonically order or remove exact duplicate ranges without asking the
-model to repair semantic errors. Campaign context and generated artifacts may
-ground names or control routing, but they never establish evidence for a D&D
-result.
+the current source identity and losslessly order any reversed range whose two
+endpoints resolve in that source, using transcript position rather than numeric
+unit-ID order. They then canonically order ranges and remove exact duplicates.
+This routine canonicalization does not request a retry or emit a warning.
+Unresolvable or wrong-source ranges remain unchanged for validators to reject.
+Campaign context and generated artifacts may ground names or control routing,
+but they never establish evidence for a D&D result.
 
 Default chains keep responsibilities separate: structural validators assess the
 candidate, source-reference validators resolve cited ranges against the current
@@ -134,22 +151,119 @@ relatedness validators report advisory evidence concerns. The configured order
 is documented in
 [Configuration](../config.md#production-validator-keys-and-default-chains).
 
-Every D&D rejection describes the correction in transcript-grounded domain
-terms, using contextual names, artifact fields, and source segment ranges when
-useful. The guidance must not ask the model to reproduce durable entity IDs,
-hashes, validator module keys, or reason codes. Those identifiers remain in
-ordinary validation provenance; only the actionable semantic guidance is
-eligible for the correction prompt.
+The optional `extract/dnd/scene-descriptions/combat_semantics` validator is the
+D&D family's LLM-backed review of only combat versus non-combat classification.
+It selects the shared combat-policy prompt fragment and asks the model to
+classify the current chunk independently as `combat` or `non_combat` without
+receiving the proposed scene kind. Deterministic code compares that
+classification with the proposed kind and either approves it or produces the
+appropriate correction guidance. This keeps every schema-valid classification
+interpretable and avoids anchoring the reviewer on the producer's answer. It
+does not assess titles, summaries, non-combat subtype, or scene boundaries;
+deferred boundary-coherence review remains separate. It is opt-in;
+[Configuration](../config.md) owns selection and retry/failure behavior.
+
+### Combat-semantics provider evaluation
+
+The human-reviewed corpus at
+`internal/modules/dnd/validate/scenedescriptions/combat_semantics/testdata/evaluation_cases.json`
+owns the proposed kind, expected combat classification, and reviewer rationale
+for each synthetic case. Its package test validates the fixture contract only.
+Provider evaluation remains an explicit maintainer operation and must not be
+added to the default offline test suite.
+
+Use the following protocol before proposing default-chain inclusion:
+
+1. Record the Notarius commit, prompt and schema fingerprints, provider, model,
+   profile settings, reasoning effort, structural-repair setting, number of
+   repetitions, and evaluation date before collecting results. Do not revise
+   expected classifications merely to agree with provider output; a substantive
+   corpus correction requires independent human review.
+2. Exercise the production validator construction and prompt assets from an
+   explicitly invoked, disposable evaluation driver or test in the validator
+   package. For each corpus case, construct transcript source units from the
+   listed IDs and text, assign matching per-unit source references, and use
+   `source.MaterializeChunkPlan` with one range spanning those units. Construct
+   exactly one scene whose ID and source range match that chunk and whose kind
+   is the case's `proposed_kind`; title and summary may use fixed placeholders
+   because the validator neither receives nor evaluates them. Invoke the typed
+   validator at extract stage through the production registry and scheduled LLM
+   client. Do not commit provider credentials, generated source material, or an
+   always-on live test.
+3. Compare the model classification with `expected_classification`, then verify
+   that its deterministic comparison with `proposed_kind` yields the expected
+   approval or rejection direction.
+   Record an unexpected approval of an expected rejection as a false
+   acceptance, an unexpected rejection of an expected approval as a false
+   rejection, and any validator execution failure separately from semantic
+   accuracy. Retain per-case results so repeated trials and systematic failure
+   modes remain visible.
+4. Evaluate producer correction separately with representative complete
+   scene-description runs configured as shown in
+   [Configuration](../config.md#production-validator-keys-and-default-chains).
+   For every initial semantic rejection, record whether the next producer
+   attempt returns the requested combat status and is approved. Do not count a
+   PromptKit structural repair as a producer-correction attempt.
+5. Run the correction evaluation with debug capture enabled and without reused
+   extraction checkpoints. Record added validator and producer calls, elapsed
+   latency, and cumulative prompt, completion, cached, and total token usage
+   from the debug attempt records. Compare these values with an otherwise
+   identical run whose scene-description chain omits the semantic validator.
+
+The default-chain review must consider classification error, false acceptance,
+false rejection, execution failure, producer-correction success, added calls,
+latency, and token use together. A structurally successful provider run alone
+is not evidence that the validator should become a default.
+
+Every producer-correctable D&D rejection describes all currently detectable
+corrections in transcript-grounded domain terms, using contextual names,
+model-owned artifact fields, and source segment ranges when useful. Validators
+collect independent record defects in one pass so one retry does not merely
+reveal the next issue. Shared D&D diagnostic helpers keep repeated rules and
+record descriptions stable, de-duplicated, and bounded; each artifact family
+continues to own the semantic rule and its prose.
+
+Operator diagnostics and model guidance are separate products of the same
+assessment. Operator messages may use typed paths, reason details, and opaque
+application identities. Correction guidance must not copy those messages or
+ask the model to reproduce durable entity IDs, hashes, validator module keys,
+reason codes, or Go field paths. A registry-normalization rejection instead
+speaks in terms of the duplicate-group proposal response the normalizer can
+actually revise. Normalization-only deterministic invariants retain useful
+operator detail but do not imply that a model controls derived ordering or
+identity. Only bounded actionable semantic guidance is eligible for a
+correction prompt.
+
+Private LLM schemas use simple enums for closed categorical fields when the
+provider-compatible shape can express the rule directly. Deterministic typed
+validators retain the same checks as defense in depth and for non-LLM
+producers. Private schemas keep every property required and avoid optional
+properties, `uniqueItems`, and conditional cross-field logic.
+
+Item-occurrence shape validation groups repeated holder mistakes by occurrence
+kind and gives the producer the required JSON null/non-null relationship. It
+identifies affected records by contextual item name and cited transcript range,
+never by the deterministically attached durable item ID. Holder mistakes remain
+semantic rejections rather than silent rewrites because changing a holder can
+also change the meaning of the occurrence kind.
 
 Enemy-event extraction additionally rejects a second `engaged` observation for
 the same comparison identity within one scene-scoped result. Normalization may
 combine results from distinct scenes, so it intentionally does not apply that
 rule. Configuration owns the exact validator key and chain position.
 
+Extraction source-reference validators share one full-span chunk-containment
+policy. After ordinary reference validity succeeds, the policy resolves both
+endpoints through document order and requires every source unit in the
+inclusive range to be present in the current chunk. It does not assume numeric
+unit-ID ordering, mutate input, or weaken wrong-source and unresolved-reference
+validation. Scene descriptions remain separate because their validator owns an
+exact one-scene range contract rather than general extraction containment.
+
 Normalizers are deterministic for spells, combat turns, item occurrences, NPC
 occurrences, scene descriptions, enemy events, and location occurrences. They
 canonicalize display values and evidence, use source-document order for stable
-output, and issue bounded warnings for changes or collapsed duplicates. NPC,
+output, and emit bounded normalization observations for changes or collapsed duplicates. NPC,
 item, and location registry normalizers are intentional exceptions: each first
 produces a deterministic candidate set, then may use a bounded structured-LLM
 proposal to reconcile identity groups.
@@ -158,13 +272,16 @@ proposal to reconcile identity groups.
 
 The three registry normalizers instantiate the domain-neutral
 `internal/framework/semanticreconcile` engine with default bounds. Each
-eligible candidate receives a contiguous, one-based `candidate_id` for that
-request. The model sees that handle, the candidate label and source-free
-evidence ranges, plus bounded transcript windows; it returns only duplicate
+eligible candidate receives a contiguous, one-based `candidate_number` for that
+request, and candidate material declares the exact inclusive range. The model
+sees that handle, the candidate label and source-free evidence ranges, plus
+bounded transcript windows; it returns only duplicate
 groups of supplied handles and one supplied canonical handle per group. It
 never returns names, evidence, durable IDs, or replacement records. Identical
 labels and evidence remain independently selectable because their handles are
-distinct.
+distinct. Transcript unit `id` values and evidence `start_unit_id` and
+`end_unit_id` values are source positions in a separate namespace and are
+never valid candidate numbers.
 
 The generic core owns the mandatory handle protocol, candidate and transcript
 presentation, the private response schema, source-reference validation,

docs/internal/llm.md

@@ -216,6 +216,19 @@ than output-validation failures. Apart from documented context, capacity, and
 invalid-output categories, provider error values and types do not cross the
 adapter error chain; callers receive only a credential-redacted diagnostic.
 
+`LLMGenerationError` preserves the provider-neutral failure kind (`transport`,
+`provider_status`, `malformed_response`, or generic `generation`) and any HTTP
+status. When PromptKit exhausts an eligible transient-status retry budget, it
+also records that exhaustion and the attempts in that generation. Those fields
+do not include repair generations, and zero attempts means unavailable rather
+than proof that no request was sent.
+
+Every execution that reaches PromptKit returns an optional request-local
+`execution` summary. It contains only terminal aggregate attempts, retry and
+repair counts, durations, outcome and failure classification, status, and
+presence-aware token usage. Preparation failures have no summary; later local
+decode failures retain the upstream terminal summary without changing it.
+
 When PromptKit rejects backend admission before generation, the adapter maps
 `promptkit.ErrCapacityExceeded` to
 `contracts.ErrLLMCapacityExceeded`, retaining prompt context and a redacted
@@ -247,21 +260,29 @@ redaction boundary.
 Structural repair does not replace pipeline retry behavior: a binding's
 configured retry count reruns its complete stage attempt after an operational
 or structural error, module-requested retry, or actionable semantic rejection.
-The pipeline owns attempt lifecycle, validation chains, and retry diagnostics;
-see [Pipeline Internals](pipeline.md#validation-retries-and-output) and the
+An actionable module-requested retry and a validator rejection both use the
+same correction payload when the producer exposes an exact latest response;
+feedback-free module retries reconstruct the ordinary request without appended
+messages. The pipeline owns attempt lifecycle, validation chains, and retry
+diagnostics; see
+[Pipeline Internals](pipeline.md#validation-retries-and-output) and the
 [binding reference](../config.md#module-bindings-and-validators).
 
 ## Timeout Ownership
 
 The caller context remains the outer cancellation authority. PromptKit applies
-a positive effective generation timeout as an inner request deadline; an
-explicit zero disables only that generation deadline. The HTTP client timeout
-is a separate transport-wide cap. Notarius forwards the caller context and
-does not install another timeout wrapper around PromptKit.
+a positive effective generation timeout as an inner request deadline for each
+built-in generation attempt; an explicit zero disables only that generation
+deadline. The HTTP client timeout is a separate transport-wide cap. Notarius
+forwards the caller context and does not install another timeout wrapper around
+PromptKit.
 
-The selected PromptKit profile owns generation settings. Notarius binding
-retries remain outside the adapter and repeat the complete module operation
-and validation chain. PromptKit does not add a provider retry loop.
+The selected PromptKit profile owns generation settings. The resolved global
+`promptkit.transient_retries` configuration is passed to the shared PromptKit
+engine and controls additional built-in attempts for eligible transient HTTP
+failures in one generation. It defaults to two; explicit zero disables those
+attempts. Notarius binding retries remain outside the adapter and repeat the
+complete module operation and validation chain.
 Operator-facing behavior is summarized in
 [Operations](../operations.md#operational-limits), and the pinned upstream
 contract is identified in

docs/internal/modules.md

@@ -95,19 +95,24 @@ source-backed artifact-family normalizer projects its deterministic records
 into contextual candidates and owned typed record envelopes, supplies its
 chosen prompt identity and resolved LLM profile, and constructs an engine with
 explicit limits. The core filters invalid evidence, assigns contiguous
-request-local integer handles, renders bounded candidate and transcript
-materials, invokes the structured-completion boundary, and assesses the
-returned duplicate groups into a stable non-overlapping plan.
+one-based request-local candidate numbers, renders bounded candidate and
+transcript materials, invokes the structured-completion boundary, and assesses
+the returned duplicate groups into a stable non-overlapping plan. Candidate
+material declares the exact inclusive number range for the request. Transcript
+unit IDs and evidence range endpoints remain source positions in a separate
+namespace and are never valid candidate numbers.
 
 The normalizer then applies that plan through a typed `ApplicationPolicy`. The
 core preserves ungrouped records, contribution order, and provenance while the
 artifact family owns group guards, field and evidence consolidation, durable
-ID derivation, retry and fallback presentation, warnings, and postconditions.
-Request-local handles do not enter the typed value or durable artifact. Fewer
-than two eligible candidates skips model invocation; exceeding a candidate or
-combined-material bound preserves the deterministic result under the family's
-fallback policy. Provider, transport, cancellation, and context-construction
-failures remain execution errors.
+ID derivation, retry and fallback presentation, classified diagnostics, and
+postconditions.
+These candidate numbers are the concrete private representation of ADR-0013's
+request-local handles; they do not enter the typed value or durable artifact.
+Fewer than two eligible candidates skips model invocation; exceeding a
+candidate or combined-material bound preserves the deterministic result under
+the family's fallback policy. Provider, transport, cancellation, and
+context-construction failures remain execution errors.
 
 When the engine actually makes a proposal call, its typed result carries the
 owned exact proposal response under the same correction contract as other
@@ -115,6 +120,16 @@ eligible producers. Deterministic skip, limit, and fallback outcomes carry no
 model candidate, so a later rejection applies terminal policy without spending
 an ineffective semantic retry.
 
+When proposal assessment or typed group application rejects a structurally
+valid group, the normalizer may return its safe partial value with a
+module-requested retry. A feedback-capable directive supplies bounded
+model-facing correction guidance separately from operator diagnostics and
+retains the exact proposal response as its candidate. The shared stage retry
+mechanism appends that response and guidance to a fresh complete request. A
+structurally invalid completion has no valid candidate and therefore requests a
+feedback-free fresh attempt. On exhaustion, only the final safe fallback and
+its bounded process diagnostic advance to validation.
+
 The core supplies a conservative generic prompt and the single private
 response schema. A domain prompt may substitute its semantic instructions but
 mounts the core-owned protocol and candidate/transcript presentation assets.

docs/internal/overview.md

@@ -26,7 +26,7 @@ physical state roots.
 | --- | --- | --- |
 | Executable and command boundary | **cmd/notarius**, **internal/cli** | Process entry, command dispatch, configuration discovery, production composition, runtime collaborator setup, durable file placement, and user-facing reporting. |
 | Build information | **internal/buildinfo** | Resolves a stable linked release tag or build metadata for the diagnostic root version command. |
-| Configuration | **internal/core/config** | Defaults, strict YAML parsing, environment overrides, structural validation, effective resolution, redaction, and resolved-composition summaries. |
+| Configuration | **internal/core/config** | ConfigKit document definition, source-aware normalization, runtime conversion, structural validation, safe inspection, effective resolution, and resolved-composition redaction. |
 | Generic models | **internal/core/source**, **internal/core/artifacts**, **internal/framework/contracts** | Source documents and chunks, manifests and provenance, plus typed artifact, reference, validation, output, and structured-completion contracts. |
 | Pipeline framework | **internal/framework/pipeline** | Registries, profile and reference resolution, typed preparation, validation, retry coordination, ordered execution, handoff, and result assembly. |
 | LLM and prompt runtime | **internal/framework/llm**, **internal/framework/promptfs** | Provider-neutral structured completions, scheduling, profile recording, prompt assets, schema registration, and credential-shaped-value redaction. |

docs/internal/pipeline.md

@@ -12,7 +12,7 @@ own durable output shapes. Concrete production extensions are covered by
 The pipeline framework accepts a resolved composition, registries, shared
 dependencies, input bytes, a supplied prompt session, and state/debug
 collaborators. It returns logical output files, normalized artifacts, recorded
-rejections and warnings, manifest provenance, and checkpoint decisions. The
+rejections, grouped diagnostics, manifest provenance, and checkpoint decisions. The
 CLI owns process arguments, configuration discovery, session resolution,
 physical roots, and placement of returned output files.
 
@@ -52,7 +52,7 @@ consumers do not repeat profile inheritance or configuration resolution.
 Each LLM request receives its own copy of that resolved value. PromptKit spends
 it only for structural correction inside one completion; the runner's binding
 retry policy remains the separate outer budget for complete stage attempts.
-Configuration resolution supplies the selected profile and catalog; see
+Configuration resolution supplies the selected overlay and catalog; see
 [Configuration Internals](configuration.md).
 
 External reference materialization happens before preparation. The materializer
@@ -97,6 +97,13 @@ codec, checks its complete schema and media identity, and records a content
 digest plus bounded producer provenance. A missing, ambiguous, invalid, or
 incompatible producer prevents the consumer step from starting.
 
+Resolution receives only exact stage-and-lane operational reference overrides.
+The CLI may offer broader pipeline- or lane-scoped selectors, but expands and
+arbitrates those before entering the framework. External overrides are applied
+after configured external defaults and local bindings. They cannot coexist
+with a generated binding for the same target and slot, and external unbinds do
+not remove generated handoffs.
+
 ## Execution And Ordering
 
 The runner validates its input, installs no-op state collaborators when none
@@ -150,34 +157,41 @@ oversized aggregate is a framework contract error; guidance is never inferred
 or truncated.
 
 The runner applies the binding's retry policy around a stage operation and its
-complete validation chain. It preserves warnings only from the final accepted
-or rejected attempt, plus one fixed warning per validator whose execution
+complete validation chain. It preserves terminal diagnostics only from the final accepted
+or rejected attempt, plus one fixed validation-incomplete warning per validator whose execution
 budget was exhausted under `warn_continue`. Cancellation stops retries.
 Normalizer-specific retry directives consume this same budget and validate any
-final safe fallback through the normalizer chain.
+final safe fallback through the normalizer chain. A directive may carry bounded
+correction guidance only when it also exposes the exact latest
+`single_response_v1` candidate. The state machine then uses the same replacement
+request shape as validator correction. A directive without guidance clears any
+prior correction and starts a fresh attempt, which preserves structural retry
+behavior when no valid response exists.
 
 The artifact-neutral producer-attempt state machine owns that shared budget,
 attempt provenance, semantic-correction material, and terminal-policy
 selection. It accepts producer and complete-validation closures, so artifact
 materialization, cache handling, checkpoints, and debug output stay at the
 operation boundary. It distinguishes operational, structural, module-requested,
-and semantic retries. A semantic retry is available only for a valid latest
-`single_response_v1` candidate; a deterministic or no-model rejection instead
-settles the semantic policy immediately. Structural-output errors alone use the
-structural policy, and validation failure without rejection settles the
-validator-failure policy without regenerating the producer.
+and validator-semantic retries. Model feedback from either semantic source is
+available only for a valid latest `single_response_v1` candidate. A
+deterministic or no-model validator rejection instead settles the semantic
+policy immediately, while a feedback-free module directive remains an ordinary
+fresh retry. Structural-output errors alone use the structural policy, and
+validation failure without rejection settles the validator-failure policy
+without regenerating the producer.
 
 Chunk planning uses this state machine for generated plans. A rejected or
 validation-incomplete automatic cache hit is not model material and therefore
 falls through to a fresh initial generation at producer attempt one; it neither
 receives a correction, consumes retry budget, promotes cached-candidate
-warnings, nor overwrites the stored record. An incomplete cache validation
+diagnostics, nor overwrites the stored record. An incomplete cache validation
 under `fail_run` terminates instead. Only a newly generated, completely
 validated plan is published to the chunk-plan store. Rejected plans never
 advance, and validation-incomplete plans remain unpublishable.
 
 After terminal lane work, the runner assembles manifest provenance, normalized
-artifacts, rejections, warnings, and an optional accepted chunk map. When an
+artifacts, rejections, final grouped diagnostics, and an optional accepted chunk map. When an
 output policy selected evidence lanes, it decodes accepted serialized normalize
 outputs through their registered codecs and invokes the prepared typed
 projectors. Rejected or absent lanes contribute nothing. This reconstruction is
@@ -224,6 +238,8 @@ Debug recording is attempt-scoped and application-owned. A failure to persist
 required debug data is a framework error. State roots, persistence, reason-code
 meanings, resume, and cleanup are intentionally owned by
 [Run State Internals](state.md) and [Operations](../operations.md).
+Extract-validator trace scopes include the current chunk ordinal so concurrent
+chunks cannot overwrite one another's validator attempts or LLM artifacts.
 
 ## Invariants To Preserve
 

docs/internal/state.md

@@ -1,5 +1,9 @@
 # Run State Internals
 
+LLM debug response artifacts and their safe per-call references retain an
+optional terminal execution summary when one is available. This metadata is
+diagnostic only and does not change receipts, checkpoints, or aggregate usage.
+
 This document describes the implementation collaborators behind output, cache,
 and debug state. User-visible fields belong in [Configuration](../config.md),
 and physical layout, retention, recovery, reason codes, and cleanup belong in
@@ -32,11 +36,18 @@ owned by the [Accepted Chunk Map contract](../integrations/chunk-map.md).
 
 `internal/framework/chunkplan` owns source-addressed plan storage, validation,
 and atomic publication. Its store is constructed only when the selected mode is
-not `bypass`.
+not `bypass`. It preserves rooted entry checks while creating new cache roots
+and source-digest directories with requested mode `0777`, then creates an
+atomic temporary file through rooted `O_CREATE|O_EXCL` with requested mode
+`0666` before sync and rename.
 
 `internal/framework/checkpoint` owns checkpoint identity, manifests, payload
 codecs, loader, and recorder. The CLI constructs a recorder whenever checkpoint
 recording is enabled and constructs a loader only for a `--resume` invocation.
+The recorder writes manifest and payload JSON through
+`fileio.WriteJSONWithProcessPermissions`, whose confined atomic writer creates
+new directories with requested mode `0777` and temporary files with requested
+mode `0666` before publication.
 Identity incorporates explicit stable semantic fingerprints collected from
 prepared modules and validators in addition to configuration, input,
 references, runtime overrides, observed LLM profiles, and the LLM runtime's
@@ -64,12 +75,13 @@ Ordinary resume loads extract, merge, and normalize checkpoints progressively
 and may execute later lane stages after an earlier cache miss. Selective
 recomputation instead asks the loader for the required producer's accepted
 normalize artifact. That lookup reuses the existing normalize files, requires
-workspace schema v3 plus an exact non-empty invocation identity, and deliberately
+workspace schema v4 plus an exact non-empty invocation identity, and deliberately
 does not require extract or merge checkpoint files or dependency fingerprints.
 The runner performs canonical codec and producer-provenance validation before
 cloning the artifact into normal step output. Success restores only stored
-normalize warnings and emits one normalize decision; failure retains the files,
-records the decision, and stops without executing the producer or consumer.
+normalize diagnostics and emits one normalize decision; failure retains the
+files, records the decision, and stops without executing the producer or
+consumer.
 
 The loader assigns a typed category and reason code at each validation site;
 diagnostic prose is not classified after the fact. The runner then applies
@@ -85,7 +97,10 @@ and debug-summary JSON.
 canonical operator-facing reason-code reference.
 
 `internal/core/fileio` provides confined atomic file writes used by state
-collaborators. The chunk-plan store retains its stronger entry validation.
+collaborators. Its exact-mode writer remains available to output and debug
+callers; its process-permission writer is used by checkpoints. The chunk-plan
+store retains its stronger rooted entry validation. [Operations](../operations.md#cache-provisioning)
+owns cache mode and provisioning guidance.
 
 The CLI constructs selective-recomputation policy from resolved generated
 artifact dependencies. It forces the selected step and transitive consumers,
@@ -97,7 +112,7 @@ owns the operator workflow and stable reason-code meanings.
 
 `internal/core/debugbundle` allocates an explicitly requested per-run bundle
 with `summary/` and `trace/` roots. `SummaryWriter` persists redacted command,
-resolution, run, warning, and failure artifacts. `internal/framework/debug`
+resolution, run, final grouped diagnostic, and failure artifacts. `internal/framework/debug`
 implements the pipeline-facing trace recorder under the trace root.
 
 The CLI allocates a bundle before pipeline resolution and treats requested

docs/operations.md

@@ -50,11 +50,45 @@ directory selects a per-user root:
 
 The field definitions and configuration examples are in [Configuration](config.md).
 On supported Unix systems, output directories and files are created with
-requested modes **0755** and **0644**. Chunk-plan, checkpoint, and debug
-directories and files use **0700** and **0600**. The operating system's umask
-may impose stricter output modes. Cache and debug roots may contain sensitive
-source-derived data, so provision them for one trusted account or service. An
-output bundle can also contain source content when its JSON output enables
+requested modes **0755** and **0644**; debug directories and files use
+**0700** and **0600**. The operating system's umask may impose stricter output
+or debug modes. Chunk-plan and checkpoint caches instead request maximum modes
+of **0777** for new directories and **0666** for new files, including atomic
+temporary files. The kernel applies the service's umask and applicable default
+ACLs when those entries are created.
+
+## Cache Provisioning
+
+Cache locations select where Notarius writes, not who can access them. A
+private service can use a restrictive umask:
+
+~~~sh
+umask 0077
+notarius run example --config /etc/notarius/config.yml --input /srv/input.txt
+~~~
+
+A trusted-group deployment can provision a setgid cache root and use a
+group-oriented umask (or an equivalent default ACL):
+
+~~~sh
+install -d -m 2770 -g notarius-operators /srv/notarius/chunk-plans /srv/notarius/checkpoints
+umask 0007
+notarius run example --config /etc/notarius/config.yml --input /srv/input.txt
+~~~
+
+Setgid and default ACLs control inherited group ownership and access policy;
+Notarius does not copy a parent directory's literal mode bits. Cache state is
+reconstructible but can contain source-derived data, so operators own its
+access and retention policy. Existing cache inodes retain their prior modes
+after an upgrade. Recreate a cache beneath correctly provisioned parents, or
+stop writers and perform a deliberate administrative migration when a
+whole-tree change is required.
+
+Cache publication remains atomic and stored records remain validated. Those
+guarantees do not add cross-process locking or transactional coordination for
+simultaneous writers to one checkpoint identity.
+
+Output bundles can also contain source content when JSON output enables
 evidence publication. Apply an appropriate umask and output-root access policy
 before enabling that option; the requested output modes alone may not be
 suitable for transcript-bearing bundles.
@@ -81,7 +115,7 @@ precedence rules are owned by [Configuration](config.md#promptkit-profiles).
 Use a profile source owned by the service account, keep it readable only by
 the intended operator, and supply provider credentials through the service
 environment—not in the Notarius configuration or profile YAML. The maintained
-[operator profile](../examples/profiles/dnd-extraction.yml) is secret-free and
+[LLM profile](../examples/llm-profiles/dnd-extraction.yml) is secret-free and
 can be copied as a format starting point. Validate a deployment without a
 provider call or credentials:
 
@@ -92,11 +126,11 @@ notarius config validate --config /etc/notarius/config.yml --pipeline dnd-sessio
 An unset optional `api_key_env` reaches the provider without authorization and
 may receive a 401 or 403 response.
 
-Profile paths are currently resolved from the process working directory, not
-from the configuration file. The complete example's
-`./examples/profiles/dnd-extraction.yml` path is valid for a repository-root
-invocation only. Use absolute paths such as
-`/etc/notarius/profiles/dnd-extraction.yml` for services and containers.
+Configured PromptKit profile paths resolve from the file that supplies their
+surviving declaration. The complete example's
+`./llm-profiles/dnd-extraction.yml` path is therefore relative to that example.
+Use absolute paths such as `/etc/notarius/profiles/dnd-extraction.yml` for
+services and containers when that is clearer for the deployment.
 
 ## Run Lifecycle
 
@@ -105,19 +139,40 @@ and resolves configuration before module preparation and source parsing. It
 then performs any permitted cache lookup, executes the pipeline, and publishes
 logical output files only after a successful runner result.
 
-On success, the command reports the output bundle path. A warning-bearing run
-still succeeds and reports its warning count on standard error. Errors and
+On success, the command reports the output bundle path. A run with actionable
+process warnings still succeeds and reports warning-group and occurrence counts
+on standard error; advisory and observation findings do not produce a warning
+line. Errors and
 their exit classes are defined in the [CLI reference](cli.md#output-streams-and-exit-statuses).
 
 ## Validation Retries And Terminal Outcomes
 
+When debug recording is enabled, per-call response artifacts include the
+terminal execution summary for retry, repair, timing, and presence-aware usage
+diagnosis. Normal output, receipts, and warnings do not aggregate or publish
+this diagnostic metadata.
+
 Each producer binding has one outer **retries** budget. It covers complete
 producer attempts for operational failures, invalid structured output,
 normalizer fallback retry, and semantic correction. It is independent from
-PromptKit's structural-repair calls inside one completion and from an
-LLM-backed validator's own retry budget. A semantic correction rebuilds the
-ordinary producer request and supplies only the latest rejected model response
-plus aggregated validator guidance; it is not a conversation replay.
+PromptKit's structural-repair calls inside one completion, its configured
+`promptkit.transient_retries` built-in HTTP attempts, and an LLM-backed
+validator's own retry budget. The transient setting defaults to two additional
+attempts for eligible provider statuses; set it explicitly to zero when an
+operator needs one HTTP attempt per generation. A semantic correction rebuilds
+the ordinary producer request and supplies only the latest rejected model
+response plus aggregated validator guidance; it is not a conversation replay.
+
+These budgets multiply only by their declared scopes. With two outer producer
+retries, two transient retries, and one structural repair, a single producer
+can issue up to 18 HTTP attempts: three producer attempts, each with an initial
+generation and one repair generation, each allowing three HTTP attempts. This
+is an illustration, not a total-deadline or exactly-once guarantee. Every
+built-in HTTP attempt has its own generation timeout; caller cancellation
+remains the overall authority and interrupts Retry-After waiting. The shared
+Notarius scheduler keeps its permit through those waits, so retry budgets can
+increase latency and provider cost. Observed usage can remain incomplete when
+providers omit accounting fields.
 
 After the applicable budgets are exhausted, the resolved
 [`validation_policy`](config.md#pipelines) determines the result. Structural
@@ -127,13 +182,14 @@ validator execution failure normally uses `warn_continue`, which keeps an
 otherwise accepted result in the current run with `incomplete` validation
 provenance. It emits one bounded warning for every validator whose execution
 budget was exhausted. A corrected result that later passes validation does not
-retain abandoned-attempt warnings.
+retain diagnostics from abandoned attempts.
 
 Treat a successful process exit as a completed run, not as proof that every
 candidate was fully validated. Inspect the receipt's `validation_status`,
-`validation_summaries`, rejection count, and warning count when an orchestrator
-requires complete validation. The durable fields and their meanings are owned
-by the [run-result receipt](integrations/run-result.md) and
+`validation_summaries`, rejection count, and warning group and occurrence
+counts when an orchestrator requires complete validation. The durable fields
+and their meanings are owned by the
+[run-result receipt](integrations/run-result.md) and
 [published JSON output contract](integrations/json-output.md).
 
 ## Output Bundles
@@ -271,8 +327,9 @@ Only a [debug-enabled run](cli.md#run) creates a bundle:
   trace/
 ~~~
 
-The summary contains redacted invocation and resolution information plus run,
-warning, checkpoint, chunk-plan, and terminal reporting artifacts. Attempt
+The summary contains redacted invocation and resolution information, including
+`effective-config.yml` and the separately redacted resolved pipeline, plus run,
+final grouped diagnostic, checkpoint, chunk-plan, and terminal reporting artifacts. Attempt
 terminal records contain bounded attempt kinds, validator outcomes, policy,
 decision, PromptKit repair count, and usage; they do not contain assistant
 responses or complete correction messages. The trace contains allowlisted
@@ -281,7 +338,8 @@ content. Neither surface is a cache input. Do not treat a debug bundle as safe
 to share merely because its configuration summary is redacted. Invocation
 metadata omits reasoning effort when it is inherited, records the replacement
 value when one is supplied, and records an empty value when inherited reasoning
-was explicitly cleared.
+was explicitly cleared. It records `config_overlay` only when a non-base
+configuration overlay was selected.
 
 Notarius never creates debug state without an explicit request and never
 automatically deletes a requested bundle. If allocation succeeds, the command
@@ -313,7 +371,9 @@ 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
-structural output repair happens within one structured-completion call. Its
+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
 selected binding, then the pipeline, then the prompt declaration; see
 [module bindings](config.md#module-bindings-and-validators). This is distinct
@@ -321,19 +381,20 @@ from Notarius binding **retries**, which rerun the complete module operation
 and validation chain and do not consume or replenish the structural-repair
 limit. The maintained production prompts declare one repair attempt, paid only
 after a structural failure. One structured completion with repair budget **R**
-makes at most **R + 1** serial provider calls. If one stage attempt performs
-**C** structured completions, a binding with **retries: N** has a maximum of
-**(N + 1) * C * (R + 1)** provider calls; LLM-backed validators have their own
-corresponding invocation counts and budgets. This is an upper bound, not a
-promise that every call reaches a provider.
+contains at most **R + 1** serial generations. Each generation can now contain
+more than one provider call when PromptKit retries an eligible transient
+failure. LLM-backed validators have their own corresponding invocation and
+repair budgets. These are bounds on attempted work, not a promise that every
+call reaches a provider.
 
 Timeouts are layered. Caller cancellation is the outer authority. A positive
-effective generation timeout adds an inner request deadline, while zero
-disables only that generation deadline. The HTTP client timeout remains a
-transport-wide cap. Notarius does not add another timeout around PromptKit.
-Repairs are serial within the same caller context, so their worst-case latency
-and cost follow the provider-call bound above; provision run deadlines and
-provider budgets accordingly. Credentials remain optional unless the selected
+effective generation timeout adds an inner request deadline to each built-in
+generation attempt, while zero disables only that generation deadline. The HTTP
+client timeout remains a transport-wide cap. Notarius does not add another
+timeout around PromptKit. Retries and repairs are serial within the same caller
+context, so their worst-case latency and cost can exceed the structural-repair
+bound above; provision run deadlines and provider budgets accordingly.
+Credentials remain optional unless the selected
 PromptKit profile requires one, in which case preparation fails before a
 provider call when its configured credential is unavailable.
 The pinned upstream boundary and profile-format links are in

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.5.0`.
+
+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/dc09959cca4e105f49ec316c6d4ba585bd2340bd/COPYRIGHT) |
+[LICENSE](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/dc09959cca4e105f49ec316c6d4ba585bd2340bd/LICENSE).
+
+[Source](https://gitea.maximumdirect.net/eric/ConfigKit/src/commit/dc09959cca4e105f49ec316c6d4ba585bd2340bd).
+
+## 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).

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.

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.

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.

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>.

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.

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.

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.

docs/policy/agents.md

@@ -0,0 +1,79 @@
+# Agent Policy
+
+**Base Policy Version:** 1.3
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/agents.md
+
+## Purpose
+
+Agents must read and follow these rules.
+
+## Implementation Discipline
+
+**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.
+
+**Keep implementation machinery proportionate.** Use straightforward,
+idiomatic code and introduce only the machinery needed to support the requested
+behavior and flexibility. Optimize for conceptual simplicity and
+maintainability, not for the fewest lines, fewest options, or narrowest product
+surface.
+
+**Do not invent restrictions.** Do not reject, prohibit, constrain, cap,
+harden, or otherwise narrow behavior unless required by the user, an explicit
+repository contract, or an unavoidable correctness constraint. Preserve
+operator and caller choice where policy has not been established. If an
+additional restriction appears advisable, present it as a decision rather than
+silently implementing it.
+
+**Do not invent guarantees.** Do not strengthen public contracts, guarantees,
+or invariants beyond those expressly requested by the user.
+
+**Use the standard library.** For example: in almost every case, the best
+approach to copying files is to use the standard library. Writing custom code to
+implement power-loss protection at the application level, or to guard against
+bad actors with privileged and concurrent access to the host's filesystem,
+is wasteful, unnecessary, and not idiomatic. Stick to the simple, standard, and
+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.
+
+## Git Commit Policy
+
+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.
+Complete the appropriate validation before committing. If work is incomplete or
+validation is blocked, report that state accurately.
+
+Before committing:
+
+1. Run `git status --short` and review the relevant diff, including any staged
+   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. 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.
+
+If the unit cannot be safely separated from pre-existing work, leave it uncommitted
+and explain the overlap rather than silently including that work. If a commit
+fails, preserve the changes and report the failure; do not bypass hooks.
+
+Default commit authorization does not authorize pushing, publishing, amending,
+resetting, reverting, or rewriting history. Those actions require a separate user
+instruction. Do not use `git commit -a` or `git commit --no-verify` to bypass the
+staging and validation discipline above.

docs/policy/architecture.md

@@ -1,10 +1,46 @@
-# Architecture
+# Architecture Policy
 
-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/).
+**Base Policy Version:** 1.3
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/architecture.md
+
+## Purpose And Ownership
+
+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.
+
+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
 
@@ -38,6 +74,8 @@ Notarius is contract-first without being abstraction-heavy. Interfaces and
 extension points should protect demonstrated boundaries. New abstraction is not
 itself an architectural goal.
 
+Implementation discipline is owned by [Agent Policy](agents.md).
+
 ## Layers And Dependency Direction
 
 The application boundary is the composition root and may depend on concrete
@@ -146,8 +184,9 @@ lanes, validators, and LLM profile: the canonical source digest selects the
 plan, while the current run still applies its configured chunk validators to
 the materialized chunks.
 
-The framework owns orchestration and handoff provenance. Modules return logical
-results and warnings; they do not own CLI reporting, physical output, cache, or
+The framework owns orchestration, origin enrichment, aggregation, and handoff
+provenance. Modules return logical results and classified diagnostics; they do
+not own CLI reporting, physical output, cache, or
 debug roots, durable file placement, or checkpoint and debug lifecycle.
 
 After pipeline-wide chunking, extraction uses bounded framework concurrency.
@@ -159,17 +198,26 @@ may overlap. The framework must not create unbounded goroutines per lane or
 chunk.
 
 Completion timing does not choose public ordering or errors. The coordinator
-orders accepted artifacts, warnings, rejections, checkpoint events, and
+orders accepted artifacts, grouped diagnostics, rejections, checkpoint events, and
 framework errors by stable pipeline scope. Rejections do not cancel unrelated
 work. A framework error cancels derived work, prevents undispatched work from
 starting, waits for started work, and prevents output encoding.
 
+Warnings are process-only signals: configuration degradation, approved fallback,
+or incomplete configured validation. Quality uncertainty and grounding findings
+are advisories; successful canonicalization and cleanup are observations.
+Modules choose that semantic classification, while the framework attaches
+origin, aggregates groups, enforces bounds, and presents final collections.
+An ordinary successful run therefore has zero warnings. See
+[ADR-0015](../adr/0015-separate-process-warnings-from-quality-diagnostics.md)
+for the decision rationale.
+
 ## Validation
 
 Validation is a framework-managed boundary around outputs from chunk, extract,
 merge, and normalize stages. Validators receive immutable stage output and
-make an explicit whole-output decision: approve, approve with warnings,
-reject, fail, or skip when a runtime prerequisite is unavailable.
+make an explicit whole-output decision: approve, reject, fail, or skip when a
+runtime prerequisite is unavailable.
 
 Typed artifact validators receive the domain value directly. Chunk validators
 receive source-zone chunks, while serialized validators receive immutable
@@ -191,6 +239,13 @@ they are not model instructions. The framework constructs model-facing retry
 text only from the semantic guidance and fails the contract rather than
 inventing or truncating missing guidance.
 
+An LLM-backed module may also request a feedback-aware retry when its own
+deterministic translation or typed safety policy rejects a structurally valid
+model response. It must supply model-facing guidance separately from its
+reason code, operator message, and fallback diagnostics, together with the
+exact `single_response_v1` candidate. A feedback-free module retry remains
+valid when no exact candidate exists.
+
 Default validator chains are production composition policy and are registered
 centrally by stage and module. Configuration may replace a stage-local default,
 including with an explicitly empty chain. Configured validator order is
@@ -212,12 +267,14 @@ the two budgets must remain separate.
 
 An LLM-backed producer can participate in semantic correction only when it
 declares `single_response_v1` and returns the exact one response that directly
-controlled its candidate. On an actionable rejection, the framework rebuilds
-the ordinary request and appends only the latest defective response as an
-`assistant` message plus one aggregated `user` correction message. This is a
-fresh replacement request, not a growing conversation. The retry budgets,
-terminal policy, and sensitive-data rationale are recorded in
-[ADR-0014](../adr/0014-feedback-aware-validation-retries.md).
+controlled its candidate. On an actionable validator rejection or
+feedback-capable module retry, the framework rebuilds the ordinary request and
+appends only the latest defective response as an `assistant` message plus one
+aggregated `user` correction message. This is a fresh replacement request, not
+a growing conversation. The retry budgets, terminal policy, and sensitive-data
+rationale are recorded in
+[ADR-0014](../adr/0014-feedback-aware-validation-retries.md) and
+[ADR-0016](../adr/0016-feedback-aware-module-requested-retries.md).
 
 When a model selects an application entity, callers must supply a contextual
 selection and deterministically attach the opaque application identity whenever
@@ -242,9 +299,11 @@ beneath this mandatory application-wide scheduler.
 
 ## Configuration And Provenance
 
-Configuration loading, precedence, defaults, environment overrides, redaction,
-and validation are centralized. Named pipeline definitions make structural
-composition explicit and discoverable. Operational overrides are permitted
+Configuration loading, precedence, defaults, redaction, and validation are
+centralized through the ConfigKit-backed boundary. `NOTARIUS_CONFIG` is limited
+to discovery; field-level environment overlays are not configuration input.
+Named pipeline definitions make structural composition explicit and discoverable.
+Explicit command overrides are permitted
 when they do not obscure the configured pipeline structure.
 
 Run preparation fails before stage execution when statically discoverable
@@ -256,8 +315,30 @@ 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.
+Host access policy belongs to the deployment; hypothetical privileged actors
+concurrently changing the filesystem do not justify new application defenses
+without an explicit decision. This scope statement does not remove the adopted
+correctness boundaries below or claim excluded scenarios cannot occur. Follow
+[Agent Policy](agents.md) when a new threat or guarantee needs a decision.
+
 Notarius exposes three filesystem surfaces with independent roots and
 lifecycle:
 
@@ -274,6 +355,15 @@ an invocation that explicitly requests resume. Debug is never a cache input and
 is never created without an explicit request. Pipeline modules receive
 collaborator interfaces and never physical roots.
 
+Deployments own cache access policy. Cache writers request conventional maximum
+creation modes and let the process umask, setgid inheritance, and default ACLs
+determine effective access. Notarius owns the separate safety boundary:
+confined paths, symlink rejection, atomic publication, validation, and
+recovery. It does not chmod, chown, chgrp, or migrate cache entries to impose
+an application policy. This rule applies to chunk-plan and checkpoint cache
+only; output and debug retain their separate contracts. [Operations](../operations.md)
+owns deployment provisioning and retention guidance.
+
 Only accepted, completely validated producer output is reusable checkpoint or
 chunk-plan state. Rejected, structurally invalid, and validation-incomplete
 results cannot become cache or checkpoint inputs, even when a
@@ -304,8 +394,9 @@ best-effort development and compilation environment, while Windows is
 unsupported. Notarius distributes source releases only: an immutable source
 tag and its checked-in release note identify a release. The project does not
 publish executable binaries, archives, installers, container images,
-checksums, signatures, or package-manager entries. Maintainer release commands
-and tag guards belong to [Source Releases](../release.md).
+checksums, signatures, or package-manager entries. [Release Policy](release.md)
+owns publication requirements and completion; maintainer commands and guards
+belong to [Source Releases](../release.md).
 
 ## Architectural Non-Goals
 

docs/policy/documentation.md

@@ -1,9 +1,15 @@
 # Documentation Policy
 
+**Base Policy Version:** 1.11
+
+**Last Updated**: 2026-09-28
+
+**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
@@ -12,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
@@ -24,24 +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.
 
-ADRs are the narrow exception: an ADR 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.
+Architectural constraints may govern future changes. Describe current structure
+from implemented behavior.
+
+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.
@@ -57,37 +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. |
-| Current application architecture | `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. |
-| 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. |
-| Source release procedure | `docs/release.md` | Maintainer release selection, candidate validation, tagging, publication guards, verification, and immutable-tag recovery. | Product installation summary, CLI version semantics, historical release summaries, CI implementation detail. |
-| 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, if a public package or API is introduced | `docs/consumers/` | Task-oriented use of the public interface, minimal client examples, and consumer responsibilities. | HTTP 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
 
@@ -99,16 +111,23 @@ other contracts.
 
 ### Releases
 
-`docs/release.md` owns the source-release procedure. 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 note to defer
-or replace current 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.
 

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).

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.

docs/policy/release.md

@@ -0,0 +1,204 @@
+# Release Policy
+
+**Base Policy Version:** 1.4
+
+**Last Updated**: 2026-09-28
+
+**Upstream Source**: https://gitea.maximumdirect.net/eric/policy/src/commit/d84a38ebab26f048cafbe59a2246700c35d29843/docs/policy/release.md
+
+## Purpose
+
+This policy defines a proportionate workflow for validating and publishing an
+intended source revision under a fresh version. Releases should require little
+routine intervention, avoid repeated work, and preserve published contents.
+
+The repository-specific commands belong in `docs/release.md`. Historical release
+summaries belong in `docs/releases/`. The procedure must agree with the adopted
+policy and link to it rather than introduce additional release requirements.
+
+## Release Model And Completion
+
+A source release identifies one exact committed source revision through an
+immutable version tag and a version-matched, checked-in release note. The
+primary release branch is `main` and the authoritative remote is `origin`.
+Tags are lightweight. Publish the candidate to `main` before pushing its tag.
+
+A successful push of the intended tag, with its source commit available on the
+authoritative primary branch, completes the release. Notarius uses
+branch-before-tag publication; it does not require an atomic push.
+
+Release commands must finish at successful publication. They must not wait for
+or poll CI, require successful CI status, inspect downloadable artifacts, or
+check consumer installation or Go module availability as completion gates.
+A failed or ambiguous push requires resolving the authoritative remote state
+before declaring success or retrying; successful pushes do not require a
+separate remote read-back gate.
+
+Notarius publishes source only: no binaries, archives, images, packages,
+checksums, signatures, or Gitea release objects. Tag CI may provide advisory
+validation but publishes no deliverables and is not a completion gate.
+
+## Versioning And Compatibility
+
+Stable releases use Semantic Versioning in the form `vMAJOR.MINOR.PATCH`, with
+no leading zeroes. Notarius does not support prereleases.
+
+The selected version must be unused locally and on the authoritative remote.
+Do not require queries to every configured remote or publication service.
+A version known to have already been published must not be reused, even if the
+normal guards do not inspect that channel. Adding a distribution channel
+requires a deliberate update to the policy and procedure where needed.
+
+For releases at or after `v1.0.0`:
+
+- a major release may make intentional incompatible changes;
+- a minor release may add backward-compatible behavior; and
+- a patch release may make backward-compatible fixes.
+
+Before `v1.0.0`, a minor release may change a documented public, operational,
+configuration, data, integration, or compatibility contract when the release
+note explains the impact and required consumer action. A patch release must
+not intentionally break those contracts within its minor line.
+
+Additional compatibility promises and deliberate exceptions belong in the
+adopted policy or canonical contract documentation. Release notes explain
+changes; they do not redefine current compatibility contracts.
+
+## Release Documentation And Preparation
+
+Every new release must include `docs/releases/<version>.md` in the tagged
+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. 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.
+
+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.
+
+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
+
+Provide one publication command that validates the final committed candidate,
+checks publication state, and publishes the intended refs. A validation-only
+mode or command may be provided for diagnosis, but must not be a required step
+before publication repeats the same checks.
+
+Run the complete deterministic, offline default test suite once for the final
+candidate, following the [testing policy](testing.md). For repositories that
+publish builds, verify the required build targets. Select those targets for
+the application's actual support commitments; native testing on each platform
+and access to particular hardware are not default release prerequisites.
+
+Additional gates must address a concrete risk that the existing checks do not
+adequately cover. Do not automatically require linting, race testing, module
+hygiene audits, documentation audits, credential scans, example validation, or
+expanded platform matrices solely because they are possible. Retain such
+checks when their distinct protection justifies their cost. A one-time migration
+check must not silently become a permanent release requirement.
+
+Release tests must not require real credentials, mutable application services,
+paid APIs, provider probes, or inference calls. The procedure may describe dependency
+preparation separately from offline validation.
+
+Avoid duplicate validation across release phases. Successful checks for the
+same final candidate need not be repeated solely to satisfy another phase;
+any reuse must clearly apply to that exact candidate. Persistent validation
+caches are not required. If the candidate changes, validate the new candidate.
+Cheap publication-state checks may be repeated immediately before pushing
+because local or remote state may have changed during validation.
+
+Automate mechanical guards. Human review gates are strongly disfavored: add one
+only through an explicit project-specific policy decision explaining the
+concrete risk and why ordinary change review or automation is insufficient.
+Do not add routine confirmations for checks the command can perform itself.
+
+### Notarius Gate Selection
+
+Run the default offline Go suite once and build the native `cmd/notarius` with
+release version injection, checking its `--version` output. The command check
+protects the actual executable entry point and linker-supplied version, which
+package tests alone do not verify. Build products are temporary, not published.
+Use `GOWORK=off` so a sibling checkout cannot substitute for declared dependencies.
+
+Race tests, standalone vet, formatting/whitespace checks, module tidy audits,
+standalone example validation, and Linux/Darwin cross-builds remain useful
+change-specific development checks, not mandatory release gates. Default tests
+already cover maintained examples. Source-only publication does not require a
+binary distribution matrix. No new platform or hardware prerequisites are added.
+
+## Publication Guards
+
+Automate the checks needed to publish the intended source under a fresh version:
+
+- the version has the adopted format and is unused locally and on the
+  authoritative remote;
+- the worktree and index are clean on the primary release branch;
+- the source being published is the exact candidate that passed validation,
+  including its matching release note;
+- the branch push advances authoritative `main` to the candidate without
+  discarding remote history, before the tag is published; and
+- the tag identifies the validated candidate and only the intended refs are
+  published.
+
+Fetch the authoritative branch and tag state as needed for these checks.
+Do not force branch or tag updates to bypass a failed guard. Publish explicit
+refs rather than all local tags. Do not require CI success, publication-service
+availability checks, or a separate manual confirmation for each guard.
+
+## Immutability And Failure Recovery
+
+Published version tags and published contents are immutable. Do not move,
+overwrite, recreate, or delete a published tag, or replace a published artifact,
+checksum, signature, provenance statement, or release note under that version.
+The checked-in note at the immutable tag is that release's historical record.
+
+If validation fails before publication, correct and commit the candidate and
+rerun the publication command. If a push fails or its outcome is ambiguous,
+inspect the authoritative remote before retrying. Remove an unpublished local
+tag only after confirming it was never published or used by a release channel.
+An unavailable remote leaves publication status unknown; do not overwrite a tag
+to resolve uncertainty.
+
+Transient network, authentication, CI, or consumer-availability failures do not
+by themselves require a new version. Advisory CI or optional installation checks
+may be retried against the same immutable tag. Notarius has no asynchronous
+artifact delivery to recover.
+
+A defect requiring changes to published source or contents requires a corrected
+commit, a new semantically appropriate version, a matching release note, and
+the release procedure again. Leave the original release intact. A channel's
+yank, deprecation, or advisory mechanism may warn consumers away from a defective
+release without replacing its contents or reusing its version.
+
+## Repository Release Procedure
+
+Maintain `docs/release.md` as a short, executable maintainer runbook. It must
+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. 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
+verification clearly optional. The procedure must not turn preparation work,
+ordinary change review, or post-publication investigation into additional
+release gates.

docs/policy/testing.md

@@ -1,39 +1,32 @@
 # Testing Policy
 
+**Base Policy Version:** 1.3
+
+**Last Updated**: 2026-09-28
+
+**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
 
-Testing is not an unqualified good. Every test imposes both an immediate cost and a continuing lifetime cost.
-
-A test must be:
-
-- written and reviewed;
-- understood by future maintainers and coding agents;
-- executed in local and CI workflows;
-- diagnosed when it fails;
-- updated when legitimate behavior changes;
-- maintained as fixtures, APIs, and dependencies evolve; and
-- removed or rewritten when it becomes redundant, brittle, misleading, or obsolete.
-
-Tests also create cognitive and architectural friction. They can constrain refactoring, duplicate policy, slow feedback loops, add noise to failures, and cause harmless implementation changes to require unrelated edits across the suite.
+Every test has an immediate and continuing cost: writing, review, execution,
+diagnosis, fixture maintenance, and updates when legitimate behavior changes.
+Tests can also constrain refactoring, duplicate policy, and add failure noise.
 
 A test is warranted only when the confidence it provides justifies these costs.
-
-Apply this cost-benefit analysis at two levels:
+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?
 
-The preferred test suite is a **lean suite that provides sufficient confidence in the risks that matter, without redundant or low-value tests**. We seek sufficient confidence with the least unnecessary testing friction, not the fewest possible tests.
+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.
 
-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.
-
-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
 
@@ -55,7 +48,7 @@ Control clocks, randomness, environment variables, and other process-global or m
 
 ## What deserves tests
 
-Prioritize tests for:
+To the extent the following features are present in the application, prioritize tests for:
 
 1. Public and package-level contracts.
 2. Domain rules and important invariants.
@@ -65,15 +58,27 @@ Prioritize tests for:
 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.
 
-For behavior involving **data integrity, destructive operations, compatibility, security, concurrency, idempotency, or recovery**, presume that durable tests are required unless the behavior is already credibly protected at another layer.
+Choose tests for requested behavior and established contracts. Tests must not
+introduce new restrictions, guarantees, or threat scenarios merely because they
+could be asserted. Follow the [agent policy](agents.md) when deciding whether a
+behavior belongs to the contract; current implementation behavior alone is not
+sufficient authority.
+
+For established behavior involving **data integrity, destructive operations,
+compatibility, security, concurrency, idempotency, or recovery**, favor durable
+tests for realistic failures whose consequences warrant protection. Identify
+the failure and the existing contract it would violate. These categories call
+for attention, not an automatic test inventory or permission to strengthen the
+application's guarantees. Account for protection already provided at other layers.
 
 Do not add tests merely because a function, branch, or line exists. Do not add a test when the same meaningful risk is already adequately protected elsewhere.
 
 ## 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:
 
@@ -81,28 +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—not memorialize the current implementation.
+A test should protect a selected decision, contract, or invariant.
 
-Before adding or retaining a test, ask:
+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.
 
-> What realistic defect would this test catch?
-
-A test is suspect when its main purpose is to detect that someone:
-
-- 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.
-
-A test can be factually correct and still have negative value. Accurately describing current behavior is not enough; the protected behavior must be important enough to justify the future friction.
+Behavioral tests should normally remain stable through internal refactoring that preserves the contract.
 
 ## Expected effects of different changes
 
@@ -119,12 +111,13 @@ 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 example, do not encode an internal concurrency limit indirectly:
+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:
 
 ```go
-// Production policy:
+// Production default:
 const maxConcurrency = 4
 
 // Brittle test:
@@ -142,25 +135,30 @@ require.NoError(t, runner.Start(limit))
 require.ErrorIs(t, runner.Start(limit+1), ErrTooMuchConcurrency)
 ```
 
-The test should prove:
+For this selected contract, the test should prove:
 
 - the configured limit is accepted; and
 - one beyond the configured limit is rejected.
 
+Rejection is not a general requirement for concurrency control. If the selected
+contract queues excess work or limits active workers while accepting larger
+batches, test that behavior instead. Do not add rejection or a configurable
+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 concurrency limits, test both kinds of behavior when relevant:
+For established concurrency limits, distinguish these behaviors where the contract requires them:
 
-1. **Configuration enforcement:** invalid or excessive requested values are handled correctly.
+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, assign ownership as follows:
 
 - Parser tests own parsing cases.
 - Validator tests own validation rules.
@@ -170,9 +168,7 @@ Each behavior should have a clear test owner.
 - 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.
-
-Tests that are individually reasonable may still be collectively redundant. Evaluate the marginal value of each additional test in light of the protection already provided by the rest of the suite.
+Give each layer its distinct responsibility and keep expectation updates localized to the contract being changed.
 
 ## Use test doubles deliberately
 
@@ -193,104 +189,76 @@ 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
 
-Use:
+Select techniques by behavior and risk:
 
 - table-driven tests for meaningful behavioral categories and boundaries;
 - `t.TempDir()` for real filesystem behavior;
 - `httptest.Server` for realistic HTTP interactions;
-- fuzz tests for parsers, normalization, path handling, and broad input spaces;
+- fuzz tests when exploring broad input spaces, such as parsers or path handling, adds useful protection beyond representative cases;
 - golden files only when the complete output is intentionally stable;
 - integration tests where correctness depends on component interaction; and
-- a small number of representative end-to-end tests.
+- 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.
 
-Increasing coverage is valuable only when the newly covered behavior protects a meaningful risk at an acceptable cost.
-
 ## Regression tests
 
 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.
-
-Deleting a low-value test can improve the quality of the suite by reducing noise, maintenance burden, and friction around legitimate change.
+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. What realistic defect would it catch?
-2. How likely is that defect?
-3. How consequential would it be?
-4. Is the behavior already protected elsewhere?
-5. At which layer should this behavior be owned?
-6. Does the test assert a durable contract or an incidental implementation detail?
-7. Could the implementation be refactored without changing the behavior and without editing this test?
-8. What should cause this test to fail?
-9. What legitimate changes should not cause this test to fail?
-10. What ongoing maintenance, execution, and diagnostic cost will the test impose?
-11. Is there a smaller or more direct test that protects the same risk?
-
-Do not add the test when its expected lifetime cost exceeds its expected protective value.
-
-When deciding not to test plausible behavior, record or be able to explain why the risk is low, already protected, obvious, reversible, or cheaper to detect elsewhere.
+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?
+3. What is the narrowest stable boundary that can test it clearly?
+4. Would a correct internal refactor or a change to an incidental default require test edits?
+5. Does its confidence justify its maintenance, execution, and diagnostic cost, or would a smaller test suffice?
 
 ## Definition of sufficient
 
 A test suite is sufficient when:
 
-- important contracts and invariants are protected;
-- meaningful boundaries and failure modes are exercised;
-- realistic and consequential regressions are credibly protected against silent recurrence;
-- behavior involving data integrity, destructive operations, compatibility, security, concurrency, idempotency, and recovery is credibly protected;
-- important external boundaries have realistic integration coverage;
-- representative complete workflows are tested;
-- failures provide useful signal rather than redundant noise;
-- legitimate internal changes usually do not require test edits; and
+- 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, 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 or test count. Reassess it as the application, its users, and the consequences of failure evolve.
-
-The governing rule is:
-
-> Test heavily where failure is consequential, subtle, or difficult to detect after the fact. Test lightly where failure is obvious, reversible, and inexpensive—and retain no test whose lifetime cost exceeds the confidence it provides.
+Reassess sufficiency as the application, its users, and the consequences of
+failure evolve.

docs/release.md

@@ -1,164 +1,93 @@
 # Source Releases
 
-This procedure is for maintainers publishing Notarius source releases. A
-release is an immutable lightweight `vMAJOR.MINOR.PATCH` tag on `main` together
-with its checked-in `docs/releases/<tag>.md` note. Tag CI validates that source
-candidate after publication; it does not publish or repair a release.
+This is the executable runbook for [Release Policy](policy/release.md).
+Notarius publishes an immutable lightweight tag and its checked-in release note,
+not binaries or Gitea release objects. Linux is supported; macOS is best-effort
+for development, and Windows is unsupported. `main` on `origin` is authoritative.
 
-Notarius publishes no binaries, archives, checksums, signatures, containers,
-package-manager entries, or Gitea release objects. Windows is not supported.
-Do not create retrospective notes for the pre-procedure `v0.1.0`, `v0.2.0`, or
-`v0.3.0` tags.
+## Prepare
 
-## Select And Describe The Release
+Use Git, a POSIX shell, and Go 1.25.5 or newer. Configure ordinary Git credentials
+for `origin` and private-module access without putting secrets in the repository.
+Prepare dependencies before offline validation where necessary:
 
-Choose an unused stable semantic version in the form `vMAJOR.MINOR.PATCH`.
-Prereleases are not supported. Before `v1.0.0`, a minor release may change a
-documented CLI, configuration, durable artifact, integration, or operating
-contract when its note explains the impact and required operator action. A
-patch release must not intentionally break those documented contracts within
-its minor line.
+```sh
+GOWORK=off GOPRIVATE=gitea.maximumdirect.net go mod download
+```
 
-Create the version-matched note as part of the candidate. Every new note uses
-this structure, with concise, truthful content in each section:
+Choose an unused stable version under the policy's compatibility rules. Add
+`docs/releases/<version>.md`, starting with `# Notarius <version>`, with a concise
+summary and relevant compatibility/upgrade information. No fixed section list is
+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
-# Notarius vMAJOR.MINOR.PATCH
-
-This release ...
-
-## Summary
-
-## Compatibility
-
-## Upgrade
-
-## Changes
+[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)
 ```
 
-The note is a historical summary. Link to current canonical documentation for
-exact behavior, and update that documentation in the candidate rather than
-using the note as a substitute.
+## Publish
 
-## Prepare The Candidate
-
-Set the selected release version and disable Go workspace use for every
-candidate command:
+Run one command from the repository with the actual selected version:
 
 ```sh
-RELEASE_VERSION=vMAJOR.MINOR.PATCH
-export RELEASE_VERSION GOWORK=off
+./scripts/release.sh vMAJOR.MINOR.PATCH
 ```
 
-Run the shared source-candidate checks from the repository. They cover module
-hygiene, tests, race tests, vet, builds, formatting, whitespace, maintained
-configuration validation, and the Linux and Darwin command-build matrix:
+The command checks version availability on `origin`, branch and worktree state,
+and the matching note. It runs the complete offline default test suite once and
+a native CLI build/version check with `GOWORK=off`. The
+[gate rationale](policy/release.md#notarius-gate-selection) explains the selected
+checks. It then rechecks candidate and publication state, pushes the exact
+candidate to `main` without force, creates a lightweight tag, and pushes only
+that tag. It neither rewrites history nor publishes other local tags.
+
+A successful tag push completes the source release. The command does not wait
+for CI or verify consumer installation/module availability. Tag CI is advisory
+validation only; there are no asynchronous deliverables to await.
+
+## Failure And Recovery
+
+Before publication, correct failed checks, commit any changes, and rerun the
+command. If the candidate changes during validation, validation must run again
+on the new candidate. A failed branch push publishes no tag.
+
+On a failed or ambiguous push, the command queries the affected remote ref. If
+a tag push reports failure but the intended lightweight tag is confirmed on the
+remote, publication succeeded. Otherwise it stops and reports failure or unknown
+status, leaving any local tag intact for inspection. Do not blindly rerun, force
+push, or delete a possibly published tag.
+
+Inspect authoritative state before retrying:
 
 ```sh
-./scripts/check-release-source.sh "$RELEASE_VERSION"
+git ls-remote origin refs/heads/main refs/tags/vMAJOR.MINOR.PATCH
+git rev-parse vMAJOR.MINOR.PATCH
 ```
 
-Before committing, manually follow every changed local Markdown link and
-review the candidate for unintended files, generated output, credentials, or
-other unrelated changes. Commit the release note and all affected current
-documentation, then run the shared checker against that exact candidate. Push
-the candidate commit to `main` only after it succeeds. Record the exact commit
-only after that push:
+If the intended tag exists remotely, leave it immutable. If it is absent and
+you have confirmed that the local tag was never published or used by a release
+channel, remove only that unpublished local tag, then rerun the command. A
+failed remote query is not proof of absence. Network/authentication failures
+alone do not require a new version. A defect requiring changes to published
+source requires a new semantically appropriate version and matching note.
 
-```sh
-RELEASE_COMMIT=$(git rev-parse 'HEAD^{commit}')
-export RELEASE_COMMIT
-```
+## Optional Diagnostics
 
-For private-module installation, configure standard `GOPRIVATE` matching this
-module and ordinary Git authentication for the hosting service before running
-the verification below. The exact authentication mechanism belongs to the
-maintainer environment; never record credentials or environment dumps in a
-release note, command history, or repository file.
+`./scripts/check-release-source.sh <version>` runs validation without publication.
+It is useful for diagnosis, but is not a required preliminary step that must
+repeat the publication command's checks.
 
-## Guard And Publish The Tag
+Race tests, vet, module hygiene, formatting, example checks, and cross-builds may
+be run when relevant to a change; they are not additional release gates. The
+development guide and testing policy govern change-specific verification.
 
-Fetch current remote references, then run this guard without editing the
-candidate. It requires `main`, a clean worktree and index, disabled workspace
-use, a stable release version, the recorded and pushed commit, a matching note,
-and unused local and remote tags:
-
-```sh
-git fetch origin main --tags
-
-if ! printf '%s\n' "$RELEASE_VERSION" |
-  grep -E -x 'v(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)\.(0|[1-9][0-9]*)' >/dev/null
-then
-  printf '%s\n' "invalid release version: $RELEASE_VERSION" >&2
-  exit 1
-fi
-test "$GOWORK" = off
-test "$(git branch --show-current)" = main
-test -z "$(git status --porcelain)"
-test "$RELEASE_COMMIT" = "$(git rev-parse 'HEAD^{commit}')"
-test "$RELEASE_COMMIT" = "$(git rev-parse 'origin/main^{commit}')"
-test -s "docs/releases/$RELEASE_VERSION.md"
-grep -F -x "# Notarius $RELEASE_VERSION" "docs/releases/$RELEASE_VERSION.md"
-for heading in '## Summary' '## Compatibility' '## Upgrade' '## Changes'; do
-  grep -F -x "$heading" "docs/releases/$RELEASE_VERSION.md"
-done
-if git rev-parse -q --verify "refs/tags/$RELEASE_VERSION" >/dev/null; then
-  printf '%s\n' "local tag already exists: $RELEASE_VERSION" >&2
-  exit 1
-fi
-if git ls-remote --exit-code --tags origin "refs/tags/$RELEASE_VERSION" >/dev/null 2>&1; then
-  printf '%s\n' "remote tag already exists: $RELEASE_VERSION" >&2
-  exit 1
-fi
-```
-
-Create an explicitly lightweight tag against the guarded commit, verify its
-target, and push only that tag ref:
-
-```sh
-git -c tag.gpgSign=false tag "$RELEASE_VERSION" "$RELEASE_COMMIT"
-test "$(git cat-file -t "$RELEASE_VERSION")" = commit
-test "$(git rev-parse "$RELEASE_VERSION^{commit}")" = "$RELEASE_COMMIT"
-git push origin "refs/tags/$RELEASE_VERSION:refs/tags/$RELEASE_VERSION"
-```
-
-Never use `git push --tags`, move a published tag, or delete a published tag.
-
-## Verify The Published Release
-
-Confirm that the remote tag still points at the guarded commit and that the
-note is available from the tagged tree:
-
-```sh
-REMOTE_TAG_COMMIT=$(git ls-remote origin "refs/tags/$RELEASE_VERSION" | awk '{print $1}')
-test "$REMOTE_TAG_COMMIT" = "$RELEASE_COMMIT"
-git show "$RELEASE_VERSION:docs/releases/$RELEASE_VERSION.md" >/dev/null
-```
-
-Verify a fresh source installation and its diagnostic version. The temporary
-directory confines the installed command to this check:
-
-```sh
-release_verification_dir=$(mktemp -d)
-trap 'rm -rf "$release_verification_dir"' 0 HUP INT TERM
-mkdir -p "$release_verification_dir/bin"
-GOWORK=off GOBIN="$release_verification_dir/bin" go install \
-  "gitea.maximumdirect.net/eric/notarius/cmd/notarius@$RELEASE_VERSION"
-test "$("$release_verification_dir/bin/notarius" --version)" = "notarius $RELEASE_VERSION"
-```
-
-An exact fresh checkout and `GOWORK=off go build ./cmd/notarius` is an
-equivalent source verification when local installation policy requires it.
-`notarius --version` is diagnostic only; downstream compatibility remains
-defined by the published receipt and artifact contracts.
-
-## Failure And Correction Policy
-
-If candidate validation fails before publication, fix the candidate on `main`,
-rerun the shared checker, and repeat the guards. An unpublished local tag may
-be deleted after inspection.
-
-If the remote tag or tag CI reveals a defect, leave the published tag intact.
-Fix the defect on `main`, choose a new patch version, write a new matching
-note, and repeat this procedure. Do not weaken tag immutability or add release
-assets as a workaround.
+A fresh source install or exact-tag checkout/build may be used to investigate
+consumer availability after release. Such checks are optional and do not delay
+or reverse release completion. `notarius --version` is diagnostic; subprocess
+compatibility is defined by the receipt and artifact contracts.

docs/releases/v0.5.0.md

@@ -0,0 +1,85 @@
+# Notarius v0.5.0
+
+This release separates actionable process warnings from extraction-quality
+advisories and routine normalization observations, giving operators a quiet
+warning channel without discarding durable diagnostic detail.
+
+## Summary
+
+Notarius now carries one validated, origin-aware diagnostic contract from
+producers and validators through retries, reusable state, output publication,
+debug summaries, run receipts, and CLI presentation. Warnings are reserved for
+process degradation or incomplete configured work. Data-quality findings are
+advisories, and successful deterministic cleanup is recorded as observations.
+An ordinary successful run therefore reports zero warnings while retaining
+bounded diagnostic provenance for later review.
+
+The framework aggregates findings deterministically by their stable identity
+and complete pipeline origin, preserves exact occurrence counts, and retains
+bounded representative samples. Warning groups fail rather than truncate;
+advisory and observation representation is bounded with explicit truncation
+metadata and exact unrepresented-occurrence counts.
+
+## Compatibility
+
+- `warnings.json` now uses the incompatible grouped
+  `notarius.warnings.v2` envelope and contains process warnings only. Consumers
+  of the former flat warning payload must migrate to the current
+  [JSON output contract](../integrations/json-output.md).
+- The new `diagnostics.json` file uses `notarius.diagnostics.v1` and contains
+  advisory and observation groups. Production `index.json` files always expose
+  both `warnings_file` and `diagnostics_file`.
+- The machine-readable run receipt is now `notarius.run-result.v2`. It replaces
+  `warning_count` with exact warning group and occurrence counts and adds
+  advisory/observation group, occurrence, and truncation fields. See the
+  current [run-result receipt](../integrations/run-result.md).
+- Custom output modules must return their complete logical file set or an
+  error. The former `OutputResult.Warnings` field has been removed; an output
+  module cannot report a warning after serializing its output.
+- Reusable state now uses `notarius.workspace.v4` and chunk-plan records use
+  `notarius.chunk-plan.v3` so they can preserve structured diagnostics. Older
+  pre-release reusable state is not reused under these contracts; start with
+  clean state when deterministic continuity with an older workspace is not
+  required.
+- Validation acceptance, semantic retry budgets, rejection policy, and D&D
+  artifact schema identities are unchanged by this release.
+
+## Upgrade
+
+1. Update subprocess consumers to require `notarius.run-result.v2` and read
+   `warning_group_count`, `warning_occurrence_count`,
+   `diagnostic_group_count`, `diagnostic_occurrence_count`, and
+   `diagnostics_truncated`.
+2. Update output-bundle consumers to decode `notarius.warnings.v2`, discover
+   `diagnostics.json` through `index.json`, and treat diagnostics as review
+   information rather than process warnings.
+3. Update any custom output module for the removal of
+   `OutputResult.Warnings`; return an error when encoding cannot complete.
+4. Clear pre-release reusable state before the first upgraded production run
+   when deterministic continuity with an older workspace is not required.
+5. Run `notarius config validate --config <path> --pipeline <id>` and perform
+   one representative run before promoting the release in an automated
+   pipeline.
+
+## Changes
+
+- Added validated diagnostic dispositions, categories, origins, stable reason
+  codes, exact occurrence counts, and bounded representative samples.
+- Added deterministic run-level aggregation with separate limits for
+  actionable warning groups and advisory/observation groups.
+- Reclassified D&D source-relatedness and unresolved-identity findings as
+  data-quality advisories and routine normalization changes as observations.
+- Preserved structured diagnostics across producer retries, validation,
+  generated-reference handoff, checkpoints, chunk-plan reuse, and debug
+  summaries while discarding superseded-attempt findings.
+- Added grouped `warnings.json`, a new grouped `diagnostics.json`, and the
+  corresponding production index entries.
+- Upgraded the machine-readable run receipt and human CLI summary to report
+  exact warning and diagnostic counts without allowing advisory volume to
+  create warning output.
+- Removed post-encoding output warnings and hardened diagnostic validation,
+  overflow handling, aggregate memory bounds, and warning-file path
+  presentation.
+- Documented diagnostic ownership, classification, operator interpretation,
+  durable contracts, and architectural invariants in ADR-0015 and the
+  canonical CLI, operations, integration, and internal documentation.

docs/releases/v0.6.0.md

@@ -0,0 +1,84 @@
+# Notarius v0.6.0
+
+This release improves the reliability and ergonomics of unattended,
+subprocess-driven D&D extraction pipelines.
+
+## Summary
+
+Notarius now gives models more precise, semantically useful correction guidance
+when deterministic or model-backed validation rejects an otherwise structured
+candidate. Semantic reconciliation retries identify candidates with compact,
+request-local numbers, preserve valid candidates when a proposal cannot be
+repaired, and report bounded process warnings when reconciliation is
+incomplete. D&D extraction also canonicalizes safely resolvable reversed source
+ranges and applies more consistent schema, prompt, and validator constraints,
+improving successful operation with smaller models without weakening evidence
+validation.
+
+An optional LLM-backed combat-semantics validator can review whether scene
+descriptions correctly consolidate combat and apply the `combat` kind. For
+subprocess callers, command-line references now follow the pipeline-scoped
+configuration model: a shared reference can be supplied once and automatically
+reach every compatible selected target, while lane- and binding-specific forms
+remain available for exceptions.
+
+## Compatibility
+
+- The meaning of an unqualified `--reference slot=path` or
+  `--without-reference slot` selector has changed. It now applies to every
+  selected pipeline target that declares the slot instead of requiring exactly
+  one matching target. Review callers that relied on ambiguity rejection or a
+  unique implicit target; the current selector contract is documented in the
+  [CLI reference](../cli.md).
+- The stage-wide `merge.slot` CLI reference shorthand has been removed. Use
+  `lane.merge.slot` for an exact merge binding, `lane.slot` for all compatible
+  bindings in one lane, or an unqualified `slot` for pipeline scope.
+- Command-line file references cannot replace, remove, or coexist with a
+  generated artifact handoff for the same concrete target and slot. Resolution
+  reports the conflict so the caller can narrow or remove the selector.
+- The private LLM-facing semantic-reconciliation contract now uses contiguous
+  `candidate_number` values rather than application identities. This is not a
+  durable or operator-configurable contract and requires no operator action.
+- Durable D&D artifact schemas, the `notarius.run-result.v2` receipt,
+  `notarius.warnings.v2`, and `notarius.diagnostics.v1` are unchanged from
+  `v0.5.0`.
+
+## Upgrade
+
+1. Update subprocess commands to provide shared inputs once with
+   `--reference slot=path`, and convert any stage-wide `merge.slot` selector to
+   an explicit supported scope. The [subprocess consumer guide](../consumers/subprocess.md)
+   and [complete D&D consumer guide](../consumers/dnd-pipeline.md) show the
+   current invocation pattern.
+2. Review CLI reference overrides that overlap generated same-run references;
+   narrow or remove an external selector rather than attempting to replace the
+   generated handoff.
+3. Run `notarius config validate --config <path> --pipeline <id>` for every
+   deployed pipeline configuration.
+4. Optionally add
+   `extract/dnd/scene-descriptions/combat_semantics` to the scene-description
+   validator chain where the deployment wants LLM-backed combat-scene review;
+   see the [configuration reference](../config.md).
+5. Perform a representative run with the deployed model profile and inspect
+   the machine-readable receipt, warnings, and diagnostics before promotion.
+
+## Changes
+
+- Added feedback-aware, module-requested retry support for normalizers while
+  keeping retry budgets bounded and preserving attempt diagnostics.
+- Reworked semantic reconciliation around compact, contiguous candidate
+  numbers, explicit namespace guidance, complete proposal validation, and
+  model-facing retry feedback that omits opaque internal identities.
+- Preserved candidates separately when an exhausted semantic proposal cannot
+  be safely applied, with a bounded process warning describing the fallback.
+- Canonicalized safely resolvable reversed D&D source-reference endpoints
+  before deterministic coverage validation and clarified the shared evidence
+  prompt.
+- Improved D&D schemas, prompts, and validators with closed-value constraints,
+  contextual correction guidance, shared source-range coverage logic, and
+  clearer item-holder transition rules.
+- Added the optional D&D scene-description combat-semantics validator, shared
+  combat policy assets, evaluation fixtures, and retry-path coverage.
+- Made unqualified CLI references pipeline-scoped, added hierarchical lane and
+  exact-binding selectors, defined deterministic override precedence, and
+  documented first-class subprocess use.

docs/releases/v0.7.0.md

@@ -0,0 +1,88 @@
+# Notarius v0.7.0
+
+This release simplifies configuration management with ConfigKit and makes
+cache access permissions a deployment responsibility.
+
+## Summary
+
+Notarius adopts ConfigKit v0.3.0 for strict configuration loading, imports,
+configuration profiles, provenance, and redacted inspection. Operators can
+compose whole pipeline definitions from separate files and select development
+overlays without duplicating the base configuration.
+
+Configured relative filesystem paths now resolve against their declaring
+files, including imported definitions and profile replacements. The effective
+configuration and its explanation reflect the paths used at runtime.
+
+## Compatibility
+
+- Configuration version 5 replaces version 4; there is no compatibility loader.
+  Numeric `version: 5` is the canonical spelling; quoted `"5"` also works.
+- Module and validator bindings require objects with `module:`; external
+  references require objects with `path:`. Lane-level reference aliases are
+  removed; use binding-local references instead.
+- Strict ConfigKit YAML parsing rejects aliases, merge keys, and unsupported
+  scalar forms. See the [configuration reference](../config.md) for the
+  complete contract and migration guidance.
+- The seven operational environment overrides are removed:
+  `NOTARIUS_TOTAL_LLM_CONCURRENCY`, `NOTARIUS_STAGE_WORKERS_EXTRACT`,
+  `NOTARIUS_OUTPUT_DIR`, `NOTARIUS_CACHE_CHUNK_PLANS_MODE`,
+  `NOTARIUS_CACHE_CHUNK_PLANS_DIR`, `NOTARIUS_CACHE_CHECKPOINTS_DIR`, and
+  `NOTARIUS_DEBUG_DIR`. `NOTARIUS_CONFIG` still selects the configuration
+  file; PromptKit credential environment variables remain supported.
+- Configured relative reference, PromptKit profile, output, cache, and debug
+  paths use the canonical declaring file's directory. Built-in relative
+  defaults use the main configuration directory. CLI-relative paths still use
+  the invocation directory; absolute paths are unchanged.
+- Requested debug bundles now contain `effective-config.yml` instead of
+  `effective-config.json`. Inspection output is redacted and is not promised
+  to be reloadable configuration.
+- Chunk-plan and checkpoint cache writers respect deployment permissions
+  through ordinary creation modes, umask, setgid inheritance, and default ACLs;
+  they no longer impose private permissions. Existing entries are not chmodded
+  or migrated. Output and debug access contracts are unchanged.
+- Durable extraction artifact schemas and subprocess receipt formats are
+  unchanged by this release.
+
+## Upgrade
+
+1. Migrate deployed configurations to version 5 using the
+   [configuration migration guide](../config.md#version-5-migration). Expand
+   shorthand bindings and references, and move retired environment settings
+   into YAML or supported CLI overrides.
+2. Review relative paths, particularly output/cache/debug directories and
+   PromptKit profile sources. Use absolute paths when preserving an existing
+   deployment location is important.
+3. Review deployment access settings for cache directories. Provision umask,
+   groups, and ACLs as appropriate; Notarius does not choose the installation's
+   access policy. See [Operations](../operations.md).
+4. Use `config validate --config <path> --pipeline <id>` for each pipeline,
+   including selected configuration profiles. Inspect resolved settings with
+   `config effective` and their provenance with `config explain`; see the
+   [CLI reference](../cli.md).
+5. Update any debug-bundle tooling that consumes the former effective JSON
+   file. Subprocess callers may optionally select an overlay through
+   `--config-profile`; this is separate from PromptKit's `--llm-profile`.
+
+The maintained [minimal](../../examples/dnd-minimal.config.yml) and
+[complete](../../examples/dnd-complete.config.yml) D&D examples demonstrate
+self-contained configuration and composed pipelines with a development profile.
+Build from the source tag using the [source-release procedure](../release.md).
+
+## Changes
+
+- Replaced custom YAML parsing and environment-overlay machinery with a
+  ConfigKit-backed typed document boundary and detached runtime conversion.
+- Added imports, configuration profiles, source-aware normalization, safe
+  effective/explanation commands, and source-file legends for load errors.
+- Preserved explicit zeroes and empty validator overrides at supported stages,
+  rejected invalid reference branches before conversion, and retained
+  whitespace normalization for worker identifiers.
+- Corrected normalization recording for ordered steps and validator sequences,
+  with regression coverage for runtime values and provenance.
+- Accepted ConfigKit's integer representation at module-option boundaries
+  through checked shared conversion.
+- Updated examples, configuration and subprocess guidance, and debug rendering.
+- Reworked cache creation to respect deployment-selected permissions while
+  retaining confined paths, symlink rejection, atomic publication, validation,
+  and recovery.

docs/releases/v0.7.1.md

@@ -0,0 +1,44 @@
+# Notarius v0.7.1
+
+This release updates the prompt engine and its provider catalogs while retaining
+Notarius's application-owned D&D defaults and subprocess contracts.
+
+## Summary
+
+- Upgrade PromptKit from v0.9.0 to v0.10.0 and adopt its selected provider catalogs.
+- Refresh the profile-source checkpoint identity for the updated catalog.
+- Document profile ownership and upstream catalog compatibility.
+
+## Compatibility
+
+Notarius's CLI, configuration schema, durable artifact formats, and subprocess
+receipt are unchanged. The `dnd-extraction` fallback retains its explicit model
+and settings; the upgrade does not switch it to an upstream default profile.
+
+Upstream catalog selections require review: `deepseek-3-2`, `deepseek-4-flash`,
+and `deepseek-4-pro` are no longer present. Operators selecting or inheriting
+those profiles must supply a complete operator-owned definition or select an
+available profile. `deepseek-flash-latest` and `deepseek-pro-latest` are not
+equivalent aliases and need not preserve previous settings. See the
+[PromptKit integration contract](../integrations/pkg-promptkit.md#profile-sources-and-compatibility).
+
+Existing checkpoints with the previous profile-source identity are not reused.
+Source-keyed chunk plans and existing output artifacts are unaffected.
+
+## Upgrade
+
+Review selected LLM profile IDs and inherited bases before rebuilding from this
+tag. No Notarius configuration migration is required for the maintained examples
+or application-owned D&D defaults. For controlled model settings, use a complete
+[operator profile](../config.md#promptkit-profiles), rather than inheriting a
+volatile catalog entry. Follow the [source release procedure](../release.md)
+for source installation and verification.
+
+## Changes
+
+- PromptKit v0.10.0 preserves the public engine API and adds two opt-in maintained
+  profile names; Notarius continues using its existing adapter and defaults.
+- The dependency graph selects OpenRouter catalog v2.20260922.1 and Rakestrawhome
+  catalog v2.20260922.0.
+- Profile checkpoint fingerprinting and current integration documentation now
+  identify the updated engine.

docs/releases/v0.8.0.md

@@ -0,0 +1,31 @@
+# Notarius v0.8.0
+
+This release upgrades ConfigKit and PromptKit and makes provider retry behavior
+explicit, inspectable, and available in debug diagnostics.
+
+## Compatibility
+
+Configuration selection now uses `--config-overlay` and
+`overlays/<name>.yml`. The retired `--config-profile` flag and
+`profiles/<name>.yml` lookup are no longer accepted. PromptKit LLM profiles are
+unchanged.
+
+`promptkit.transient_retries` defaults to two additional eligible transient
+HTTP attempts per generation. Set it to `0` to disable built-in transient
+retries. Existing pipeline and validator retry settings remain separate.
+
+## Upgrade
+
+Move selected configuration files from `profiles/` to `overlays/` and replace
+every `--config-profile` invocation with `--config-overlay`. Review retry and
+timeout budgets before deployment, especially where providers charge per
+attempt. See [Configuration](../config.md), [Operations](../operations.md), and
+the [PromptKit integration contract](../integrations/pkg-promptkit.md).
+
+## Changes
+
+- Upgrade ConfigKit to v0.4.0 and PromptKit to v0.11.0.
+- Add application-owned generation failure and request-local execution-summary
+  metadata, including retry exhaustion details.
+- Record execution summaries in existing debug response artifacts and safe
+  per-call references.

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)

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.

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.

docs/roadmap/archive/remediation.md

@@ -0,0 +1,124 @@
+# Kit Upgrade Review Remediation
+
+## Resolution
+
+Completed 2026-09-26. No production changes were needed.
+
+- `internal/framework/llm/promptkit_observation_test.go` now covers retries in
+  both initial and repair generations, aggregate versus legacy accounting,
+  unknown/known-zero/partial usage, retry-wait cancellation, exhausted execution,
+  preparation failure, and overlapping request isolation.
+- `internal/framework/pipeline/debug_execution_test.go` exercises the real
+  scheduled client and debug wrapper together. It verifies returned and persisted
+  summaries for provider errors and cancellation without a body, split debug and
+  fallback content, terminal references, and explicit usage-presence JSON fields.
+- Temporary regression probes confirmed that discarding failed responses in the
+  scheduler and collapsing usage presence into known zero cause the new tests
+  to fail. Those probes were reverted.
+- Focused LLM/pipeline tests, their race-enabled suites, and
+  `GOWORK=off go test ./...` passed. Existing no-debug and redaction coverage was
+  retained. Runtime budgets, scheduler policy, and output contracts are unchanged.
+
+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 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.
+
+The implemented architecture is consistent with the intended design: ConfigKit
+v0.4.0 owns composition and overlay provenance behind the configuration boundary;
+PromptKit v0.11.0 owns transient retries and structural repairs behind the LLM
+adapter. Notarius retains stage retry/disposition policy, completion-scoped
+scheduling, application-owned error/observation types, and opt-in debug output.
+No new runtime defect or unrequested restriction was established in this review.
+
+## Finding 1 — Complete The Missing Retry And Observation Verification
+
+**Priority:** Medium. This is a verification gap, not a demonstrated runtime
+failure. Stages 5–7 are marked complete, but their consequential cross-boundary
+acceptance tests were not implemented.
+
+### Evidence And Risk
+
+- `internal/framework/llm/promptkit_client_test.go:58` adds only a successful,
+  single-attempt observation assertion with positive prompt-token usage. It
+  does not exercise absent versus partial/known-zero usage, failed/canceled
+  execution summaries, preparation failure, or concurrent request isolation.
+- `TestPromptKitClientAppliesConfiguredBuiltInTransientRetries` covers basic
+  status recovery, explicit zero, exhaustion, and a noneligible status. It
+  discards the response, so does not protect terminal accounting. There is no
+  combined transient-retry/structural-repair scenario or cancellation while
+  waiting on Retry-After.
+- `internal/framework/llm/scheduled_client.go:40` now preserves a response when
+  the inner call fails. No corresponding test protects that behavior. Returning
+  an empty response again would silently remove precisely the failed-call
+  observations this feature is intended to retain.
+- `internal/framework/pipeline/debug.go:267` and `:277` add execution summaries
+  to response artifacts and call references, plus fallback/content-splitting
+  propagation. Neither the debug nor terminal-debug tests were extended to
+  exercise these fields. Passing existing tests does not prove that failed-call
+  metadata reaches persisted records.
+
+These are Notarius-owned integration risks, not a request to re-test PromptKit's
+backoff algorithm. Losing failed-call observations or misrepresenting incomplete
+usage would be difficult to detect in ordinary successful runs. A focused set
+of behavioral tests is justified under the testing policy.
+
+### Required Remediation
+
+Use existing test assets, local HTTP fixtures, scheduler wrappers, and debug
+recorders. Combine related assertions; no fixed test count or new test framework
+is required.
+
+1. Add an adapter scenario with a transient failure, a structurally invalid
+   completion, and a successful repair. Exercise retries in both generations
+   with small explicit budgets, and assert terminal attempts/retries/repair
+   counts without double-counting. Use controlled usage fields to distinguish
+   known zero, unknown, and partial aggregate usage. Preserve legacy usage
+   semantics independently.
+2. Cover failed and canceled completions, including cancellation during a
+   Retry-After wait. Verify caller cancellation identity, bounded completion,
+   and retained execution metadata. Use signaling and a generous bounded test
+   timeout, not exact sleep durations or jitter assertions. Cover a preparation
+   failure with no execution summary. Add a small concurrent-call check for
+   request-local summary isolation, which race tests alone do not prove.
+3. Exercise an error response through the real scheduled client and existing
+   debug wrapper/recorder seams. Assert that the summary reaches response
+   artifacts and terminal call references even without a provider response
+   body. Cover the content-splitting/fallback path with a representative response.
+   Reuse existing no-debug and redaction tests rather than duplicating their
+   whole inventories. Keep new summary assertions metadata-only.
+
+Retain existing scheduler policy, stage/validator budgets, cancellation
+disposition, warning semantics, and debug opt-in behavior. Do not introduce a
+total deadline, new retry caps, telemetry artifacts, or live API requirements
+to make these tests easier. Fix production code only if these checks reveal a
+violation of the already selected behavior.
+
+**Acceptance:** The added tests fail if failed responses lose their execution
+summary at an adapter/wrapper boundary, usage presence is collapsed into zero,
+or retry/repair totals are double-counted. They pass with the intended behavior
+and provide evidence for the previously unverified stage acceptance criteria.
+
+**Validation:** Run focused LLM/pipeline tests, race-enabled tests for those
+packages, and `GOWORK=off go test ./...`. No production credentials are needed.
+
+## Checks Completed During Review
+
+- `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`
+- CLI configuration validation for the minimal and complete examples, including
+  the complete example with `--config-overlay development`.
+- `git diff --check`
+
+All passed. Existing green tests do not substitute for the missing behavioral
+coverage above. Temporary diagnostic test material used during review was
+removed; no application code was changed.

docs/roadmap/archive/upgrade-kit.md

@@ -0,0 +1,337 @@
+# ConfigKit And PromptKit Upgrades
+
+## Purpose
+
+Adopt ConfigKit v0.4.0 and PromptKit v0.11.0 in one coordinated work set:
+
+- Consistently call ConfigKit's selected configuration layer an **overlay**,
+  distinct from PromptKit LLM profiles.
+- Adopt configurable transient HTTP retries, provider-neutral failure
+  classifications, and execution observations from PromptKit.
+
+Preserve application/framework boundaries and keep the two upgrades as distinct
+implementation workstreams. Neither requires a redesign of pipeline execution.
+
+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
+
+The reviewed baseline is Notarius v0.7.1 (`53d9284`):
+
+- `go.mod` pins ConfigKit v0.3.0 and PromptKit v0.10.0.
+- `internal/core/config/load.go` passes `LoadOptions.Profile` into
+  `configkit.Options[Document].Profile`.
+- `--config-profile` selects `profiles/<name>.yml` beneath the configuration
+  root for `run`, `config validate`, `config effective`, `config explain`, and
+  `pipelines list`.
+- The maintained selected-layer example is
+  `examples/profiles/development.yml`; configuration and CLI tests create
+  equivalent directories and exercise selection and inspection.
+- ConfigKit owns composition and inspection metadata. Notarius owns its
+  version 5 document, defaults, validation, source-relative path resolution,
+  runtime conversion, and CLI discovery.
+
+A dependency-only trial against v0.4.0 fails to compile at `load.go:33` because
+`configkit.Options.Profile` no longer exists. The review found no direct
+Notarius references to `LayerProfile`, `CodeProfile*`, or `LoadSecretsDir`.
+
+An isolated dependency-only trial against PromptKit v0.11.0 passes the complete
+Notarius test suite and `go vet ./...`. That proves baseline compatibility, not
+adoption of the new controls or observations. The current adapter does not
+configure transient retries or attach an execution observer. It classifies
+generation errors broadly and records successful-result usage and structural
+repair counts. The outer scheduler holds a permit for the whole completion.
+
+## Upstream Changes
+
+### ConfigKit v0.4.0
+
+The [ConfigKit v0.4.0 release guide](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.4.0/docs/releases/v0.4.0.md)
+defines four breaking naming changes:
+
+| Surface | Previous | Target |
+| --- | --- | --- |
+| Selection API | `Options.Profile` | `Options.Overlay` |
+| Selected file | `profiles/<name>.yml` | `overlays/<name>.yml` |
+| Provenance layer | `LayerProfile` / `profile` | `LayerOverlay` / `overlay` |
+| Diagnostic identifiers | `CodeProfile*` / `profile.*` | `CodeOverlay*` / `overlay.*` |
+
+There are no legacy aliases or directory fallback. Explicit imports from a
+directory named `profiles` remain valid ordinary imports. Merge rules,
+precedence, lifecycle, source-origin APIs, minimum Go version, and YAML parser
+dependency are unchanged.
+
+The intervening v0.3.1 release makes the opt-in `LoadSecretsDir` API ignore
+dot-prefixed entries. Notarius does not use this API; adding secrets-directory
+bootstrap is outside this work.
+
+### PromptKit v0.11.0
+
+The [PromptKit v0.11.0 release guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.11.0/docs/releases/v0.11.0.md)
+introduces additive runtime APIs and one changed default:
+
+- Built-in generation defaults to two additional transient HTTP attempts for
+  statuses 429, 500, 502, 503, and 504. Engine and request controls can override
+  the count, including zero. Injected `LLMClient` implementations are not
+  automatically replayed; a custom HTTP client on the built-in path still is.
+- Backoff is cancellable and honors valid provider `Retry-After` timing.
+  Generation and HTTP timeouts apply per attempt; the caller context bounds
+  the whole operation. Transport failures, malformed responses, other HTTP
+  statuses, and invalid generated content are not transient-retry candidates.
+- `RunRequest.Observer` reports lifecycle metadata, attempts, waits, outcomes,
+  and presence-aware usage, including work before a failed execution. It works
+  with prepared execution; preparation itself emits no execution events.
+- `ErrTransport`, `ErrMalformedResponse`, `ErrRetriesExhausted`, and
+  `RetryExhaustedError` support typed classification without parsing error text.
+- The license changes to LGPL-3.0-or-later. Catalog selections and the minimum
+  Go version are unchanged from v0.10.0.
+
+## Target End State
+
+### Dependency And Ownership
+
+Pin ConfigKit v0.4.0 and PromptKit v0.11.0 and tidy the dependency graph.
+Continue using only ConfigKit's
+public root API behind `internal/core/config`. No compatibility parser,
+application-owned composition engine, or new configuration abstraction is
+needed. PromptKit remains behind `internal/framework/llm`; its types must not
+leak into domain modules or pipeline contracts. Retain the existing prepared
+execution path, profile choices, and D&D model settings.
+
+### Consistent Overlay Selection
+
+- Replace the configuration-selection CLI flag with `--config-overlay` on all
+  commands that currently accept `--config-profile`.
+- Rename application-owned fields, variables, helpers, help text, and test
+  descriptions that specifically represent this selection to overlay terms.
+- Pass the selection through `configkit.Options.Overlay`.
+- Select files only from `overlays/<name>.yml`, following ConfigKit's contract.
+- Preserve empty and `default` selection as the composed base configuration
+  without a selected overlay.
+- Use a clean cutover: no old CLI alias, directory fallback, automatic file
+  moves, or custom migration machinery. Normal unknown-flag handling is
+  sufficient for the retired flag; explain migration in documentation.
+
+This rename is deliberately narrow. Preserve `llm_profile`, `--llm-profile`,
+`promptkit.profile_dir`, `promptkit.profile_file`, `base_profile`, embedded
+`dnd-extraction` profiles, and `examples/llm-profiles/`. Other application
+concepts named `Profile`, including pipeline/runtime types, must not be renamed
+merely because they share the word.
+
+### Preserved Behavior
+
+Retain configuration version 5, with the additive retry setting described below.
+Preserve existing defaults other than the explicitly adopted transient retry policy,
+imports, overlay merge behavior (including sequence replacement), explicit CLI
+override precedence, strict decoding, domain validation, and secret redaction.
+Do not add new restrictions or relax existing explicit contracts as part of the
+rename.
+
+Relative paths continue to resolve from the file supplying the surviving
+declaration, including overlay files. Invocation-relative CLI paths and
+main-file-relative built-in defaults retain their current behavior.
+
+Effective configuration, explanations, and configuration-load diagnostics use
+the new upstream overlay provenance and diagnostic vocabulary. Preserve source
+file labels and actionable error context; do not translate the new metadata
+back into legacy profile terminology.
+
+Pipeline stage order, semantic acceptance, LLM selection, domain artifact
+schemas, and subprocess result receipts remain unchanged. No blanket checkpoint
+invalidation is added merely for the ConfigKit rename. Update the existing
+PromptKit-version identity used by checkpoint fingerprinting with its dependency
+pin, following the current adapter convention; no cache redesign is needed.
+
+### Transient Retry Policy
+
+Expose `promptkit.transient_retries` as a nonnegative integer setting with a
+Notarius default of **2 additional attempts**. Explicit zero disables transient
+retries. Apply the resolved setting to the shared PromptKit engine so modules,
+normalizers, validators, and semantic correction calls receive the same policy.
+Include the effective value in configuration inspection. Do not impose an
+arbitrary application maximum or add per-binding controls in this work set.
+
+Maintain three separate budgets and owners:
+
+| Budget | Owner | Repeated work |
+| --- | --- | --- |
+| Transient retries | PromptKit | The same generation request after eligible HTTP failures |
+| Structural repairs | PromptKit | A corrective generation for invalid structured output |
+| Producer/validator retries | Notarius | The configured stage or validator operation, with semantic feedback where applicable |
+
+Do not silently reduce, repurpose, or remove existing stage/validator budgets.
+Each structural repair generation receives its own transient budget. For a
+single-completion producer, two additional stage attempts, one structural
+repair, and two transient retries permit up to 18 HTTP attempts, excluding any
+separate validator calls. Document this multiplication and the possibility of
+additional cost; retries do not imply exactly-once provider execution.
+
+Preserve caller cancellation throughout generation and waiting. Do not describe
+a profile's generation timeout as a total completion deadline: provider
+`Retry-After` can extend waits beyond local backoff, and each HTTP attempt has
+its own timeout. A new total-deadline configuration surface is outside this
+upgrade; accurately document the current controls and limitations.
+
+Retain Notarius's completion-scoped scheduler permit during upstream backoff.
+PromptKit releases its active backend permit during that wait, but this does
+not release the outer Notarius permit. This remains bounded and correct; do
+not add an attempt-level scheduler redesign.
+
+### Provider-Neutral Failure Diagnostics
+
+Translate the new typed errors into application-owned classifications for
+transport failures and malformed provider responses. Represent transient retry
+exhaustion separately from its underlying failure/status, retaining the actual
+attempt count where available. Preserve existing HTTP-status reporting,
+capacity classification, cancellation, deadline handling, and redaction.
+
+Do not turn a malformed provider envelope into a semantic rejection or confuse
+it with a structurally invalid model response. Do not expose PromptKit error
+types across the adapter boundary or parse prose to recover classifications.
+Existing stage disposition policies continue to decide what happens after a
+completion fails; this work does not redesign those policies.
+
+### Execution Observations
+
+Attach a request-local observer through the existing prepared-execution path.
+Translate selected metadata into Notarius-owned completion/debug summaries:
+
+- dispatched attempt, transient retry, and structural repair-call counts;
+- capacity-wait, generation, retry-delay, and total execution durations;
+- terminal outcome, failure classification, HTTP status, and exhaustion state;
+- observed token counts with explicit known/complete indicators.
+
+Retain available summaries on failed completions, including cancellation, rather
+than discarding them with the absent `RunResult`. Preparation failures have no
+execution observation; do not fabricate one. Keep existing successful-result
+usage fields and their meanings unchanged. Observation totals are separate
+presence-aware metadata, not a second set of tokens to add to existing usage.
+Unknown counts are not known zero; partial totals are not a billing ledger.
+
+Use lightweight per-request accumulation with no unbounded event history or
+asynchronous queue. Callbacks are synchronous: avoid blocking I/O or acquisition
+of scheduler resources inside them, and isolate concurrent requests. Persist
+the projection through the existing opt-in debug path, including safe terminal
+summaries where applicable. Do not serialize upstream event structs directly;
+their JSON layout is not a public contract. Allowlist metadata and preserve
+existing identifier/content handling and redaction boundaries.
+
+Successful transient recovery is ordinary success, not a warning. This work
+does not add routine console messages, change the warning policy, introduce a
+new durable telemetry artifact, or add complete cost accounting.
+
+## Required Changes
+
+### Code And Examples
+
+- Update `go.mod` and `go.sum` and the configuration loader/options boundary.
+- Update CLI selection plumbing in `internal/cli/run.go` and
+  `configkit_commands.go`, including usage, flag parsing, argument classification,
+  explicit empty-value handling, and error paths.
+- Move the maintained example to `examples/overlays/development.yml` and update
+  example discovery and related fixtures. Inspect relative paths when moving
+  files; do not assume all occurrences of `profiles` are configuration overlays.
+- Update affected configuration and CLI tests, particularly document paths,
+  operational defaults, safe inspection, command selection, diagnostic source
+  labels, run contracts, and maintained-example coverage.
+- Add the retry setting through the typed configuration document, defaults,
+  validation, runtime conversion, and CLI client-construction boundary. Update
+  the complete example to demonstrate it without adding unnecessary settings
+  to the minimal example.
+- Update the PromptKit adapter's engine construction, request observation,
+  error conversion, and checkpoint version identity. Extend transport-neutral
+  response/debug contracts only with the application-owned metadata needed.
+- Carry observations through the pipeline debug wrapper and safe terminal
+  reporting without double-counting usage or losing failed-call summaries.
+
+### Documentation
+
+Update current documentation with the implementation, keeping canonical
+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
+  explicit distinction from LLM profiles; transient retry setting and default.
+- `docs/integrations/pkg-configkit.md`: pinned release and supported upstream
+  naming/inspection contract.
+- `docs/internal/configuration.md` and relevant CLI internals: new selection
+  terminology and unchanged boundaries.
+- `docs/consumers/subprocess.md` and any other current callers/examples: updated
+  invocation syntax. Review operations and README references where applicable.
+- `docs/integrations/pkg-promptkit.md`: updated pin, typed errors, observer
+  support, and retry contract. Refresh pinned upstream links, including its
+  relocated release-policy document.
+- `docs/internal/llm.md` and relevant pipeline/debug internals: observation
+  projection, failure handling, scheduler interaction, and separate retry
+  budgets. Remove the obsolete claim that PromptKit has no provider retry loop.
+- `docs/operations.md`: latency/cost implications, timeout limits, opt-in debug
+  evidence, and how to disable transient retries.
+
+Preserve historical release notes and the accepted text of ADR-0018. Its
+ConfigKit ownership decision remains valid; a terminology migration alone does
+not require a new ADR or supersession. Current documentation must not portray
+the old dependency pin as the current supported version.
+
+Record PromptKit's LGPL-3.0-or-later change in the integration documentation and
+eventual release note. Review its notices and distribution implications within
+Notarius's source-only release model. Do not silently relicense Notarius, copy
+upstream release policy into this repository, or introduce binary packaging.
+Any future binary distribution needs its own license-compliance review.
+
+## Operator Migration And Release Impact
+
+This work belongs in the next **minor** Notarius release, not a patch, because
+both the documented selected-file layout and CLI syntax change.
+
+Operators move selected configuration files from `profiles/` to `overlays/`
+and replace `--config-profile` with `--config-overlay` in scripts, service
+definitions, and subprocess callers. Preserve unrelated PromptKit profile
+directories and explicit imports. Review relative paths and explicit imports
+that refer to moved files. No YAML body version migration is required.
+
+The eventual release note must explain this cutover, the newly enabled transient
+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).
+
+## Acceptance And Verification
+
+- Notarius builds against ConfigKit v0.4.0 and PromptKit v0.11.0 without
+  compatibility shims.
+- All five affected commands use the new flag; non-default overlay selection,
+  omitted selection, empty selection, and `default` retain their intended
+  behavior. The old flag is not accepted.
+- Selected overlays load from the new directory. A legacy-only selected file
+  does not silently load; ordinary explicit imports remain supported.
+- Representative tests demonstrate overlay precedence, CLI overrides,
+  declaration-relative paths, redacted inspection, and source-aware failures.
+- Maintained examples validate, including the development overlay. LLM profile
+  loading and defaults remain unaffected.
+- Tests prove the default transient retry policy, explicit zero, configured
+  counts, and negative-value rejection through the relevant configuration and
+  adapter boundaries. Use local HTTP test servers for eligible/noneligible
+  statuses, exhaustion, cancellation, and interaction with structural repair;
+  an injected LLM fake alone does not exercise built-in HTTP retries.
+- Provider-neutral errors preserve underlying status and cancellation identity
+  without leaking credentials or upstream types.
+- Observations are available for success and failure, preserve unknown versus
+  known-zero usage, avoid aggregate double-counting, and stay isolated under
+  concurrent completions. Successful retry recovery emits no warning.
+- Representative scheduler/repair/retry checks preserve bounded execution and
+  cancellation; use existing coverage where it already proves the contract.
+- Current documentation, help text, examples, and tests agree. Searches for old
+  vocabulary are reviewed semantically, excluding intentional historical and
+  LLM-profile references rather than enforcing a blanket text ban.
+- Run focused `go test ./internal/core/config ./internal/cli ./internal/framework/llm ./internal/framework/pipeline`, followed by
+  `go test ./...`, `go vet ./...`, `go build ./...`, `go mod tidy -diff`, and
+  `git diff --check`, with `GOWORK=off`. Run race-enabled tests for the modified
+  adapter, scheduler, and observation integration. Validate both maintained configurations
+  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
+credentials are needed to validate this migration.

docs/roadmap/archive/warning-signal-and-presentation-audit.md

@@ -0,0 +1,648 @@
+# Warning Signal And Presentation Audit
+
+## Executive Assessment
+
+Notarius warning execution is mechanically stronger than its operator-facing
+presentation. Terminal-attempt promotion, stable ordering after concurrent
+work, checkpoint replay, validation summaries, and debug retention are all
+substantially correct. The audit found no general duplicate-append defect in
+the extract, merge, or normalize handoffs and no leakage of abandoned-attempt
+warnings into a successful result.
+
+The warning channel itself is not coherent. One flat `contracts.Warning` type
+currently represents at least four materially different concepts:
+
+- actionable degradation or incomplete validation;
+- heuristic data-quality doubt;
+- successful but potentially reviewable fallback; and
+- routine canonicalization, ordering, and deduplication observations.
+
+That conflation is the primary reason successful runs produce a count that is
+large but operationally weak. The maintained complete D&D example demonstrates
+the problem without a live provider: an approved run with no rejected outputs
+published 12 warning records, all from three advisory relatedness checks. An
+operator separately reported a successful complete D&D run with 10 outputs,
+one rejection, and 85 warnings. The production bundle for that run was not
+available in this environment, so its reason-code distribution could not be
+measured.
+
+The current implementation also has four correctness or robustness gaps:
+
+1. warning records lose stage, step, lane, module, validator, and chunk
+   provenance when promoted, which makes safe aggregation and diagnosis
+   impossible from `warnings.json` alone;
+2. there is no framework-level validation or aggregate bound, and the NPC- and
+   spell-relatedness validators bypass the D&D warning limiter entirely;
+3. warnings returned by an output encoder are added after `warnings.json` has
+   already been encoded, so the receipt, stderr, debug bundle, and published
+   warning file can disagree; and
+4. a skipped validator contributes to `incomplete` validation but does not
+   receive the warning generated for an exhausted validator failure.
+
+The recommended end state is a structured diagnostic contract with explicit
+disposition, category, origin, occurrence count, and bounded samples. Warnings
+are reserved for process-level degradation or incompleteness. LLM-judged or
+deterministically inferred extraction-quality signals are advisories, never
+warnings, and routine normalization observations remain inspectable without
+being reported as top-level warnings. An ordinary successful run in which all
+configured work completes normally should therefore report zero warnings. This
+is an architectural and durable-contract change, not merely revised CLI prose.
+
+## Evidence And Limits
+
+The audit used:
+
+- a complete static search of production `contracts.Warning` constructors,
+  reason-code constants, result fields, and promotion sites under `internal/`;
+- call-path inspection through producer attempts, validators, lane
+  coordination, chunk-plan reuse, checkpoints, output encoding, debug output,
+  CLI presentation, and run-result construction;
+- the maintained complete and minimal D&D examples with offline fake LLMs;
+- focused deterministic tests for warning bounds, semantic-reconciliation
+  fallback, `warn_continue`, semantic retries, terminal rejection, concurrency
+  ordering, and checkpoint reuse; and
+- the operator-provided observation of an 85-warning complete D&D run.
+
+No provider-backed production run was attempted because this environment has
+no API key. Consequently, the audit can establish warning mechanics, possible
+multiplicity, synthetic volume, and obvious heuristic limitations, but cannot
+estimate production frequency or the real false-positive rate of individual
+D&D advisories. Those measurements are not required to choose the recommended
+architecture; they are required before strengthening any heuristic advisory
+into a rejection or setting a numerical production acceptance target.
+
+## Complete Warning-Producer Inventory
+
+### Framework And Generic Boundaries
+
+| Producer | Reason code | Trigger and consequence | Multiplicity and bound | Current surfaces and coverage |
+| --- | --- | --- | --- | --- |
+| Reference materialization in `internal/framework/pipeline/references.go` | `empty_reference` | A bound external reference is a valid, accepted media type but contains zero bytes. The prompt may receive materially incomplete context. | One per empty bound file; finite by configuration but no shared run-level cap. | Enters `RunInput.Warnings`; reference tests protect contextual scope. |
+| Producer-attempt policy in `internal/framework/pipeline/producer_attempts.go` | `validator_execution_incomplete` | An applicable validator exhausted its execution budget and `warn_continue` accepted the otherwise valid candidate. | One per failed validator on each terminal candidate. An extract chain can multiply this by chunks and lanes. There is no global cap. | Durable warning, receipt count, stderr, debug, and validation summary. `TestWarnContinueRecordsOneWarningForEachExhaustedValidator` covers failures. |
+| Chunk, extract, merge, normalize, and output module result contracts | Module-defined | A module may return arbitrary warnings with its successful candidate. | No contract validation, message limit, per-result cap, or global cap. Current production modules are inventoried below. | Terminal-attempt filtering and concurrency ordering are well tested. |
+| Production JSON output encoder | None | The encoder copies incoming warnings into `warnings.json`; it does not currently create warnings. | Same count as its input. | JSON encoder and assembled-pipeline tests compare the incoming run warnings with the published file. |
+| Output encoder result contract | Module-defined | Any output encoder may return warnings discovered during encoding. | Unbounded by contract. No production encoder currently exercises this capability. | Appended to final `RunOutput` only after logical files were encoded; this is the cross-surface defect described in AUD-WARN-004. |
+
+Input adapters and production mergers do not currently have independent
+warning producers. Chunk-plan and checkpoint decisions are structured manifest
+or debug provenance rather than warnings. Cancellation and hard persistence,
+reference, parsing, serialization, and provider failures remain errors.
+
+### D&D Extraction Gates
+
+| Producer | Reason code | Trigger and consequence | Multiplicity and bound |
+| --- | --- | --- | --- |
+| `dnd/combat-turns` extractor | `scene_classification_unavailable` | The chunk has no exact matching scene-description classification. The extractor returns an empty accepted result and skips the LLM, so combat-turn output may be incomplete. | At most one per chunk for this lane. |
+| `dnd/enemy-events` extractor | `scene_classification_unavailable` | The same missing or mismatched scene gate causes accepted empty enemy-event output. | At most one per chunk for this lane. |
+
+An exact non-combat classification produces an intentional empty result without
+a warning. An exact combat classification proceeds normally. The two producers
+share a code and operator consequence but use different messages; their module
+origins are not retained in the final warning record.
+
+### D&D Source-Relatedness Validators
+
+All ten relatedness validators are deterministic advisories: they approve the
+candidate and warn when contextual prose or an entity name is not lexically
+present in cited text. Shape and source-reference failures are deliberately
+left to blocking validators earlier in the chain. The same relatedness
+validator is registered in both the extract and normalize default chain for
+each artifact family in `internal/modules/dnd/register/chains.go`.
+
+| Artifact family | Warning reason | Per-record trigger | Local bound | Omission reason |
+| --- | --- | --- | --- | --- |
+| Combat turns | `combat_turn_not_near_source` | Actor token sequence absent | 20 per validator invocation | `combat_turn_relatedness_warnings_omitted` |
+| Enemy events | `enemy_event_not_near_source` | Subject token sequence absent | 20 | `enemy_event_relatedness_warnings_omitted` |
+| Item occurrences | `item_occurrence_source_unrelated` | Item name token sequence absent | 20 | `item_occurrence_relatedness_warnings_omitted` |
+| Item registry | `item_not_near_source` | Item name token sequence absent | 20 | `item_relatedness_warnings_omitted` |
+| Location occurrences | `location_occurrence_not_near_source` | Location name token sequence absent | 20 | `location_occurrence_relatedness_warnings_omitted` |
+| Location registry | `location_not_near_source` | Location name token sequence absent | 20 | `location_relatedness_warnings_omitted` |
+| NPC occurrences | `npc_occurrence_not_near_source` | NPC name token sequence absent | 20 | `npc_occurrence_relatedness_warnings_omitted` |
+| NPC registry | `npc_not_near_source` | NPC name token sequence absent | **Unbounded** | None |
+| Scene descriptions | `scene_description_not_near_source` | No significant title or summary token appears; up to two findings per scene | 20 | `scene_description_relatedness_warnings_omitted` |
+| Spells | `spell_not_near_source` | Spell-name token sequence absent | **Unbounded** | None |
+
+The eight limiter-generated omission records are presentation artifacts, not
+new source-relatedness conditions. They occupy a warning slot and make list
+length differ from the actual occurrence count.
+
+### D&D Normalizers
+
+Every production D&D normalizer bounds its returned warning slice to 20 through
+`internal/modules/dnd/shared/diagnostics`, including a final omission record
+when needed. Registry semantic retries reserve space for their fallback
+warning. The following table is complete by semantically distinct condition;
+codes listed together are parallel artifact-family variants.
+
+| Condition | Reason codes | Result impact | Current classification assessment |
+| --- | --- | --- | --- |
+| Display or field whitespace/name canonicalization | `npc_fields_normalized`, `item_fields_normalized`, `location_fields_normalized`, `spell_name_canonicalized`, `combat_actor_canonicalized`, `enemy_event_name_canonicalized`, `item_occurrence_name_canonicalized`, `location_occurrence_name_canonicalized`, `scene_description_prose_normalized` | Deterministic successful mutation. The item-occurrence code can also describe `from`/`to` whitespace, not only the item name. | Routine observation. |
+| Durable ID recomputation | `npc_id_recomputed`, `item_id_recomputed`, `location_id_recomputed` | Restores the deterministic name-derived ID. | Routine observation; invalid identity is separately rejected by default chains. |
+| Source-reference sorting or deduplication | `source_references_normalized` | Sorts and removes exact duplicate references while deliberately preserving invalid references for their validators. | Routine observation. Shared code is useful but ambiguous without producer origin. |
+| Canonical record ordering | `combat_turns_reordered`, `enemy_events_reordered`, `item_occurrences_reordered`, `location_occurrences_reordered`, `npc_occurrences_reordered`, `scene_description_order_normalized` | Deterministic order changes only. | Routine observation. |
+| Exact or approved semantic duplicate consolidation | `duplicate_npc_collapsed`, `duplicate_item_collapsed`, `duplicate_location_collapsed`, `duplicate_spell_cast_collapsed`, `duplicate_combat_turn_collapsed`, `duplicate_enemy_event_collapsed`, `duplicate_item_occurrence_collapsed`, `duplicate_location_occurrence_collapsed`, `duplicate_npc_occurrence_collapsed`, `scene_description_duplicate_collapsed` | Removes duplicate records and preserves or combines canonical evidence according to the artifact policy. Registry codes cover both exact and accepted semantic consolidation. | Durable normalization observation; not normally operator-actionable. |
+| Unresolved external membership | `spell_name_unresolved`, `item_occurrence_unknown_item_id`, `location_occurrence_unknown_location_id` | The value is preserved but is not grounded in the effective catalog or registry. Default chains normally reject the same condition before normalization; it remains reachable with validator overrides or defensive direct use. | Actionable data-quality warning. |
+| Unsafe currency consolidation proposal | `item_semantic_proposal_invalid` | The proposed group is rejected and all records are preserved because denominations or currency/non-currency members are incompatible. The same code is also used internally as a retry reason. | Advisory about model proposal quality; no accepted-data loss. The control and diagnostic meanings should be separated. |
+| Semantic reconciliation unavailable or exhausted | `npc_semantic_reconciliation_exhausted`, `item_semantic_reconciliation_exhausted`, `location_semantic_reconciliation_exhausted` | The safe deterministic result is accepted, but possible semantic duplicates remain. | Actionable fallback warning. |
+| Local warning truncation | `npc_normalization_warnings_omitted`, `item_normalization_warnings_omitted`, `location_normalization_warnings_omitted`, `spell_normalization_warnings_omitted`, `combat_turn_normalization_warnings_omitted`, `enemy_event_normalization_warnings_omitted`, `item_occurrence_normalization_warnings_omitted`, `location_occurrence_normalization_warnings_omitted`, `npc_occurrence_normalization_warnings_omitted`, `scene_description_normalization_warnings_omitted` | Reports that individual records were omitted from presentation. | Group metadata, not an independent warning. |
+
+No production D&D normalization warning exposes raw model responses,
+correction guidance, or provider errors. Most dynamic names are quoted and
+truncated by the shared helper. That local discipline is not enforced by the
+generic warning contract, and the spell relatedness message does not use the
+shared truncation helper.
+
+## Warning Propagation And Surface Map
+
+```text
+external-reference warnings -----------------------------+
+                                                           |
+module candidate warnings -> validation chain warnings     |
+             |                      |                       |
+             +---- producer-attempt terminal policy -------+
+                                  |                        |
+                   accepted / terminal rejection only      |
+                                  |                        |
+              chunk or lane result in canonical order      |
+                                  |                        |
+       checkpoint record/replay and ordered step merge     |
+                                  |                        |
+                            RunOutput.Warnings <------------+
+                                  |
+                   OutputRequest -> output encoder
+                                  |             |
+                         warnings.json     OutputResult.Warnings
+                                                |
+                              appended to final RunOutput only
+                                  |
+                 receipt, stderr, final debug warning summary
+```
+
+### Attempts And Validation
+
+- `runProducerAttempts` promotes only the terminal accepted or terminal
+  rejected candidate's module and completed-validator warnings. Operational,
+  structural, semantic, and module-directed attempts that are superseded are
+  retained in attempt debug artifacts but not in the final collection.
+- A module-directed semantic-reconciliation retry adds its fallback warning
+  only when no retry remains. Earlier attempt warnings are discarded.
+- On `warn_continue`, warnings from the otherwise accepted candidate and
+  completed approved or rejected validators are retained. One fixed,
+  non-sensitive `validator_execution_incomplete` warning is added for every
+  failed validator. Skipped validators affect the validation summary and final
+  `incomplete` status but do not receive such a warning.
+- A semantic terminal rejection retains only warnings from that rejected
+  attempt. Structural rejection after producer failure cannot retain a
+  candidate warning because no valid candidate result exists.
+
+These behaviors are protected by the producer-attempt, extract-handoff,
+rejection-warning, normalize-retry, and attempt-debug tests. They are the right
+foundation for the redesign and should not be replaced with early-exit or
+all-attempt accumulation.
+
+### Concurrency And Ordering
+
+Extract jobs are dispatched chunk-first and lane-second. Results are stored by
+chunk index, finalized in ascending chunk order, and lane continuations are
+merged into a slice indexed by configured lane order. Pipeline steps run in
+configured order. The resulting public order is therefore:
+
+1. pre-run reference warnings;
+2. chunk-stage warnings;
+3. step order;
+4. configured lane order within each step;
+5. chunk order within extract;
+6. merge warnings; then
+7. normalize warnings; followed by any output-result warnings.
+
+`TestRunnerBoundsExtractJobsAndStabilizesReverseCompletion` exercises warning
+order under reversed completion. No completion-order leak was found.
+
+### Chunk Plans And Checkpoints
+
+- A reusable chunk plan stores producer warnings only. Current validators run
+  again, and their current warnings are appended. Warnings from a cached plan
+  candidate that fails current validation are discarded before regeneration.
+- Accepted extract, merge, and normalize checkpoints store the terminal
+  warnings for their stage. Reuse loads and appends those warnings once at the
+  same logical handoff. Tests compare fresh and resumed warning collections and
+  preserve their order.
+- Validation-incomplete accepted outputs are not reusable, preventing a later
+  run from silently treating incomplete validation as complete.
+- Required accepted-normalize hydration replays that normalize checkpoint's
+  warnings; checkpoint decisions separately expose that reuse occurred.
+
+The recommended redesign should keep fresh and resumed logical diagnostics
+equivalent. Whether a result was reused belongs in checkpoint provenance, not
+in the diagnostic grouping key; adding a `reused` distinction would fragment
+groups and make equivalent runs present differently.
+
+### Terminal Surfaces
+
+| Surface | Current content | Audience | Audit result |
+| --- | --- | --- | --- |
+| `RunOutput.Warnings` | Flat final slice | Framework and CLI | Canonical in-memory list, but lacks origin and bounds. |
+| Published `warnings.json` | Object containing the warnings passed into the output encoder | Durable consumers | Exact for the production JSON encoder unless the encoder itself returns warnings. |
+| `index.json` | Path to `warnings.json` | Durable consumers | Stable discovery path; no separate diagnostic-detail path. |
+| Run-result v1 | `warning_count = len(final RunOutput.Warnings)` | Subprocess callers | Count only; no group/occurrence distinction. |
+| Human stderr | `run completed with N warning(s)` | Operators | Count only and no direct detail path. Successful exit remains zero. |
+| Manifest | Validation and rejection summaries, no warning collection | Durable provenance | Correctly avoids duplicating the flat list. |
+| Debug summary `warnings.json` | Raw final warning array | Operators/developers | Includes final output-result warnings and can therefore differ from published `warnings.json`. |
+| Debug run report | Final warning count | Operators/developers | Same final slice length as receipt and stderr. |
+| Attempt/stage debug | Candidate-local warning detail and origin in path/envelope | Forensics | Sufficient to diagnose provenance, but debug capture is optional and is not a durable consumer contract. |
+
+## Empirical Measurements
+
+### Offline And Synthetic Runs
+
+| Scenario | Result | What it establishes |
+| --- | --- | --- |
+| Maintained complete D&D config and transcript with the repository's offline fake LLM | Approved, 10 normalized outputs, 0 rejected outputs, 12 warnings; receipt, stderr, and published file all reported 12 | An ordinary structurally successful workflow can be noisy without fallback or incomplete validation. |
+| Same complete run, grouped after publication | Three reason codes, seven exact `(reason, scope, message)` tuples, maximum exact-tuple repetition of three | The flat count materially overstates distinct operator conditions. Scope resets within chunks and does not identify origin. |
+| Maintained focused scene-description workflow | Approved, one normalized output, 0 warnings | The warning channel can be quiet when synthetic model text is lexically grounded. |
+| Generic warning publication contract | One warning reaches successful stderr, durable output, and debug summary | The ordinary pre-output path is consistent. |
+| NPC semantic-reconciliation candidate-limit fallback | No LLM call, all records preserved, one exhaustion warning, total warnings no greater than 20 | Fallback is bounded and materially different from routine normalization. |
+| `warn_continue` with two failed validators and one skipped validator | Validation status contains all three incomplete validators; warning slice contains two execution-incomplete records | Current warning count does not describe all incomplete validation. |
+| Retrying extract candidate | Two producer attempts; only the accepted attempt's one warning is final | Retry does not amplify abandoned warnings. |
+| Terminal semantic rejection | Only the final rejected attempt's operation and validator warnings are final | Rejection diagnostics are retained without retaining superseded warnings. |
+| Fresh versus reused extract checkpoint | Warning collections are deeply equal | Checkpoint replay does not itself amplify warnings. |
+| Spell normalizer with 21 unresolved entries | 20 records: 19 samples plus one omission record saying two additional warnings were omitted | `warning_count` is neither exact occurrence count nor distinct-condition count. |
+
+The focused audit tests passed in `internal/cli`,
+`internal/framework/pipeline`, the NPC-registry and spell normalizers, and all
+D&D packages.
+
+### Bounded Sample Review
+
+The complete offline D&D run produced:
+
+| Reason | Count | Sample | Review |
+| --- | ---: | --- | --- |
+| `location_not_near_source` | 4 | `Moon Gate` was absent from cited text | Correctly identifies deliberately unsupported fake output. Three records shared the same exact tuple because chunk and stage origin were lost. |
+| `location_occurrence_not_near_source` | 4 | A `Moon Gate` visit was absent from cited text | Correctly identifies the same unsupported registry-driven occurrence, but repeats the same operator concern across extraction and normalization. |
+| `scene_description_not_near_source` | 4 | A title or summary had no significant exact token in cited text | Mixed value. Generic `session scene` prose is ungrounded, while `Arrival` versus transcript `arrive` illustrates an expected lexical false positive. |
+
+This fake workflow is an integration fixture, not a model-quality benchmark.
+It nonetheless proves that the checks carry useful evidence while being too
+imprecise and repetitive to serve as one-warning-per-record operator alerts.
+
+### Production Evidence Still Needed
+
+The reported 85-warning run establishes that high volume occurs in practice,
+but the following remain unknown:
+
+- dominant production reason codes and stage/lane sources;
+- unique group count versus repeated occurrence count;
+- false-positive rate for each relatedness family;
+- how much volume comes from normalization observations versus advisories;
+- whether fresh and resumed production runs remain equivalent; and
+- a defensible numerical acceptance target.
+
+If further data is worthwhile, the operator can supply the v1 receipt,
+`warnings.json`, and manifest validation summaries without supplying transcript
+or lane artifacts. An initial privacy-preserving report should group by reason
+code and normalized scope family, count exact repeated tuples, and omit message
+text. Reviewing heuristic precision requires a separately approved bounded
+sample with its cited source context.
+
+## Classification Of Current Conditions
+
+| Target disposition | Current families | Result impact | Operator action | Durable placement |
+| --- | --- | --- | --- | --- |
+| **Warning** | Empty reference; validator failure or skip accepted under `warn_continue`; unavailable required scene classification; exhausted semantic reconciliation | A configured process completed under an allowed degraded or incomplete policy rather than completing normally | Correct reference/configuration, inspect provider/validator, or rerun | Actionable `warnings.json`, receipt summary, stderr summary, debug |
+| **Advisory** | Source-relatedness heuristics; unresolved spell or registry membership; guarded invalid semantic proposal; any future LLM-judged uncertainty or extraction-quality signal | Uncertain data quality or poor model proposal, but accepted data is structurally valid and deterministic guards prevented unsafe mutation | Optional model/source review; no routine action for every record | Durable diagnostic detail and debug; never a top-level warning |
+| **Observation** | Whitespace/name/ID/source-reference canonicalization; canonical ordering; exact and approved semantic duplicate consolidation | Successful intended normalization | None under normal operation | Durable bounded normalization diagnostics or debug; no stderr warning |
+| **Not a diagnostic** | Rejection, invalid structure, cancellation, persistence error, provider failure under fail-run policy | Candidate or run did not complete according to policy | Inspect rejection/error and retry or correct input/configuration | Existing rejection, validation summary, error, and debug contracts |
+
+Exact and semantic duplicate consolidation should remain distinguishable in
+category or reason metadata even though both are observations. Semantic
+reconciliation exhaustion remains a warning because a capability was not
+applied; successful approved consolidation is an observation because it is the
+normalizer's intended work.
+
+## Ranked Findings
+
+### AUD-WARN-001 — The Flat Warning Type Destroys Signal Quality
+
+- **Priority:** High operator impact; high implementation leverage.
+- **Evidence:** `contracts.Warning` has only scope, reason, and message. Routine
+  normalizer changes, heuristic doubt, fallback, and incomplete validation all
+  enter the same slice and the same CLI count. The offline complete run's 12
+  records were all advisories; the operator observed 85 records in a successful
+  real run.
+- **Impact:** Operators cannot tell whether a warning requires a rerun, a
+  configuration repair, optional review, or no action. Repeated routine output
+  trains them to ignore the channel.
+- **Recommendation:** Replace the flat semantic contract with explicit
+  `warning`, `advisory`, and `observation` dispositions plus a small category
+  vocabulary. Do not infer disposition from message text or require every
+  downstream consumer to maintain a reason-code policy table.
+
+### AUD-WARN-002 — Warning Records Lose The Origin Needed For Diagnosis And Aggregation
+
+- **Priority:** High correctness and usability impact.
+- **Evidence:** The runner knows stage, step, lane, module, validator, chunk ID,
+  and chunk index at promotion time, but `terminalWarnings` flattens module and
+  validator records into `[]contracts.Warning`. Per-chunk scopes such as
+  `locations[0]` and `occurrences[0]` then repeat without identifying their
+  chunk or producer. `source_references_normalized` is intentionally shared
+  across families and is therefore especially ambiguous.
+- **Impact:** `warnings.json` cannot answer which stage or module produced a
+  record. Message- or scope-based deduplication would merge unrelated findings
+  or retain accidental duplicates.
+- **Recommendation:** Keep module findings free of framework context, then have
+  the framework add a structured origin envelope before promotion. Validator
+  findings must retain validator identity instead of passing through
+  `validationReport.Warnings()` as a flat slice.
+
+### AUD-WARN-003 — Warning Volume Is Not End-To-End Bounded Or Validated
+
+- **Priority:** High robustness impact; medium immediate likelihood.
+- **Evidence:** D&D's `LimitWarnings` caps most individual producers at 20, but
+  NPC- and spell-relatedness return one warning per record without the helper.
+  Every extract validator is invoked per chunk, all ten relatedness checks run
+  again after normalization, and there is no run-level collector. The generic
+  contract validates neither disposition nor reason/message size, UTF-8,
+  blankness, or total records.
+- **Impact:** Warning memory and output grow with chunks, lanes, configured
+  validators, and record counts. Local omission records lose exact occurrence
+  semantics while still incrementing `warning_count`.
+- **Recommendation:** Add a generic bounded diagnostic collector that preserves
+  exact occurrence counts and bounded samples. Validate all diagnostic fields
+  at the module/framework boundary. Immediately bring NPC and spell
+  relatedness under the existing cap if the full redesign is staged.
+
+### AUD-WARN-004 — Output Encoder Warnings Make Durable Surfaces Disagree
+
+- **Priority:** Medium current impact; high contract correctness risk.
+- **Evidence:** `Runner.Run` passes existing warnings to `encoder.Encode`, then
+  the production encoder serializes `warnings.json`. Only after encoding does
+  the runner append `OutputResult.Warnings`. The receipt, stderr, debug summary,
+  and debug run report see the final slice; the already-created published file
+  cannot. No production encoder currently returns a warning, so ordinary JSON
+  runs do not trigger the defect.
+- **Impact:** A valid output-module implementation can violate the documented
+  claim that `warning_count` describes the published warning collection.
+- **Recommendation:** Remove successful output warnings from the output-module
+  contract unless a demonstrated use case requires them; encoding failures
+  should be errors and optional encoder observations should be debug data. A
+  two-phase finalize API is the viable but more complex alternative.
+
+### AUD-WARN-005 — Validation Skips Are Incomplete But Not Warned
+
+- **Priority:** Medium operator/correctness impact.
+- **Evidence:** `firstIncompleteValidation` treats failed and skipped validators
+  alike, and validation summaries include both. `incompleteValidationWarnings`
+  emits records only for `validationFailed`. The focused test demonstrates
+  three incomplete validators but two warnings.
+- **Impact:** A successful run can have `validation_status: incomplete` while
+  its warning count understates or even omits the affected validators. A caller
+  that checks only warnings receives a weaker signal than the manifest and
+  receipt status.
+- **Recommendation:** Produce one aggregated incomplete-validation warning
+  group whose occurrences cover both failure and skip, while retaining typed
+  outcome and safe reason metadata in the validation summary. Do not expose
+  provider errors or arbitrary skip prose in model or operator messages.
+
+### AUD-WARN-006 — Relatedness Checks Are Useful But Repetitive And Lexically Weak
+
+- **Priority:** Medium operator impact; low acceptance-policy urgency.
+- **Evidence:** Every family runs the advisory in both extract and normalize
+  chains. The complete fixture contains exact repeated tuples, and the checks
+  rely on exact normalized token sequences or a minimal significant-token
+  overlap. Reason naming drifts between `*_not_near_source` and
+  `*_source_unrelated`.
+- **Impact:** The checks can catch unsupported entities, but aliases, pronouns,
+  inflection, and generic scene prose create predictable false positives. Flat
+  per-record presentation magnifies them.
+- **Recommendation:** Retain the validators and their stage-local execution,
+  but classify and aggregate them as advisories. Normalize reason-code naming
+  when the diagnostic contract changes. Do not strengthen them into rejection
+  rules without a human-reviewed production evaluation.
+
+### AUD-WARN-007 — `warning_count` Has No Stable Operational Meaning
+
+- **Priority:** High downstream-contract impact.
+- **Evidence:** The receipt and CLI use `len(output.Warnings)`. One list element
+  can be an omission summary representing several hidden occurrences; repeated
+  records can represent the same condition; and skipped validators can be
+  absent. A 21-occurrence spell test produces a list length of 20.
+- **Impact:** The value is neither an exact occurrence count nor a distinct
+  warning-group count. Consumers cannot set policy or present a trustworthy
+  summary from it.
+- **Recommendation:** Introduce explicit warning-group and warning-occurrence
+  counts in a versioned receipt. Do not silently redefine the v1 field.
+
+## Recommended Target Contract And Presentation Model
+
+### Diagnostic Model
+
+Use one validated internal diagnostic model with these concepts:
+
+- **disposition:** `warning`, `advisory`, or `observation`;
+- **category:** a small enum such as `configuration`, `degradation`,
+  `validation_incomplete`, `data_quality`, `fallback`, or `normalization`;
+- **reason code:** stable semantic identity owned by the producer;
+- **origin:** framework-added phase/stage, step ID, lane ID, module key,
+  validator name, chunk ID, and chunk index when applicable;
+- **occurrence count:** exact number of matching findings;
+- **samples:** a small deterministic list of bounded scope/message pairs; and
+- **omitted sample count:** `occurrence_count - len(samples)`, represented as
+  metadata rather than another diagnostic record.
+
+Errors and rejected outputs must not become diagnostic dispositions. A warning
+means that the run completed under policy despite a process-level degradation
+or incomplete configured operation. Advisory and observation dispositions can
+describe accepted artifact quality and transformation provenance, but no
+LLM-judged extraction-quality signal may be promoted to a warning. Validation
+status remains authoritative for approval, rejection, and incomplete
+validation.
+
+### Aggregation
+
+The framework runner should own aggregation after it enriches findings with
+origin and before public output construction. Modules and validators retain
+semantic ownership of disposition, category, reason, scope, and message; they
+must not own CLI or file presentation.
+
+The default stable key should be:
+
+```text
+disposition + category + reason_code
++ phase/stage + step_id + lane_id + module_key + validator_name
+```
+
+Chunk, record scope, and message text belong in samples and must not be part of
+the group key. This groups repeated per-chunk findings without merging the same
+code across distinct producers or pipeline locations. Group order should be
+the first occurrence in the runner's existing canonical order; sample order
+should follow the same order. A final canonical sort by the complete origin key
+is also viable, but completion timing must never choose either order.
+
+Aggregation must be incremental and bounded. Producers should use a shared
+collector that counts every occurrence while retaining only bounded samples;
+the framework then merges producer groups without reconstructing counts from
+omission prose. A global maximum group count is also required, with overflow
+represented by structured aggregate metadata and with actionable groups given
+priority over lower dispositions.
+
+### Durable Files
+
+Keep one canonical home for each class:
+
+- `warnings.json` should contain versioned, grouped actionable warnings only;
+- a new `diagnostics.json` should contain versioned advisory and observation
+  groups only, avoiding duplication of warning groups;
+- `index.json` should link both files;
+- `rejected.json` and manifest validation summaries should retain their current
+  separate responsibilities; and
+- debug bundles should retain candidate-attempt detail plus the final grouped
+  projections.
+
+This is preferable to keeping all detail in `warnings.json` and filtering only
+the CLI: downstream consumers would otherwise continue to receive a semantically
+mixed warning contract, and routine observations would still dominate the
+durable file.
+
+### CLI And Receipt
+
+For a successful human run with actionable warnings, print a concise summary
+such as:
+
+```text
+notarius: run completed with 2 warning groups (7 occurrences); details=/.../warnings.json
+```
+
+Advisories and observations should not produce the warning line. Their durable
+path remains discoverable through `index.json`; a concise non-warning count can
+be added to the ordinary success line only if operator testing shows value. An
+ordinary successful run with no process degradation should write nothing to
+the warning stream even when it publishes quality advisories or normalization
+observations.
+
+Create `notarius.run-result.v2` rather than redefining v1. It should expose at
+least:
+
+- `warning_group_count`;
+- `warning_occurrence_count`; and
+- `diagnostic_group_count` for non-warning durable groups.
+
+The receipt should continue to expose validation status, validation summaries,
+and rejected-output count independently. Process exit behavior should not
+change as part of warning presentation reform.
+
+### Checkpoint Semantics
+
+Store the structured terminal diagnostic groups with accepted checkpoints and
+replay them exactly once at their logical stage. Fresh and reused runs should
+produce the same public groups and counts. Checkpoint events and debug records,
+not diagnostic identity, should disclose whether computation was reused.
+
+### Output Encoder Boundary
+
+Prefer removing `OutputResult.Warnings`. A successful output encoder should
+either return the complete logical files or fail. If future encoders genuinely
+need to produce durable post-encoding warnings, introduce an explicit
+two-phase prepare/finalize contract so those warnings can be included in the
+same published collection. Do not retain the current self-inconsistent
+one-pass capability.
+
+## Resolution Of Required Design Questions
+
+| Question | Recommendation | Viable alternative and tradeoff |
+| --- | --- | --- |
+| Explicit severity/disposition or external reason mapping? | Put validated disposition and category in the contract. | A central reason-code registry avoids payload fields but makes new modules depend on a second synchronized policy table and leaves downstream meaning implicit. |
+| Keep all detail in `warnings.json` or separate it? | Separate grouped actionable warnings from grouped advisories/observations in `diagnostics.json`. | Keep the flat durable list and aggregate only CLI output; simpler migration, but it preserves the noisy downstream contract and ambiguous count. |
+| Who owns aggregation? | Framework runner/coordinator after origin enrichment. | Output module aggregation keeps framework types smaller but duplicates policy across encoders and cannot repair missing validator origin. |
+| Stable aggregation key? | Disposition, category, reason code, and full producer origin; exclude chunk/scope/message. | Explicit producer-supplied grouping keys offer flexibility but add another identity that can drift from reason codes. Message-template grouping is brittle and unsafe. |
+| Samples and omissions? | Exact occurrence count plus deterministic bounded samples and numeric omitted-sample count. | Omission warning records preserve the current representation but inflate group counts and require prose parsing. |
+| `warning_count` semantics? | Version receipt and replace ambiguity with group and occurrence counts. | Keep v1 count as published record length and add optional fields; compatible, but two competing warning counts remain easy to misuse. |
+| Which normalization changes remain warnings? | Only exhausted process fallback. Unresolved membership is a data-quality advisory; successful canonicalization, reordering, ID repair, source-ref dedupe, and duplicate consolidation are observations. | Treat unresolved membership or semantic duplicate consolidation as warnings because they affect grounding or cardinality; more conservative, but it violates the process-only warning rule and reports accepted artifact quality as an operational failure. |
+| Source-relatedness disposition? | Grouped advisory by default; preserve current approve behavior. | Retain warning disposition or make rejection configurable. Rejection requires production precision evidence; current lexical rules are not strong enough. |
+| Checkpoint-loaded warnings? | Present the same logical groups as fresh execution and use checkpoint events for reuse provenance. | Mark groups as replayed; aids forensics but fragments aggregation and makes semantically equivalent runs differ. |
+| ADR and schema versions? | Add an ADR and version the run receipt and diagnostic files. | Treat the work as CLI-only presentation and avoid an ADR; insufficient because module contracts, output files, checkpoint payloads, and downstream fields change. |
+
+## Compatibility, Documentation, And ADR Implications
+
+The target alters public and internal contracts enough to require a new ADR.
+It should record:
+
+- the distinction among warnings, advisories, observations, rejections, and
+  errors;
+- the invariant that warnings are process-level signals, LLM-judged extraction
+  quality is never a warning, and ordinary non-degraded success has zero
+  warnings;
+- module semantic ownership versus framework origin/aggregation ownership;
+- bounded group and sample semantics;
+- fresh/checkpoint equivalence; and
+- the output-encoder decision.
+
+Implementation should introduce `notarius.run-result.v2`. The grouped warning
+and diagnostic envelopes should each carry their own schema version. Because
+the content of `warnings.json` changes incompatibly from a flat array wrapper
+to groups, release notes and the published JSON integration contract must call
+out the migration. `index.json` gains the diagnostic file path.
+
+Canonical documentation updates belong in:
+
+- `docs/cli.md` for stderr presentation only;
+- `docs/operations.md` for operator review and debug workflow;
+- `docs/integrations/json-output.md` for warning and diagnostic file schemas;
+- `docs/integrations/run-result.md` for v2 fields and compatibility;
+- `docs/consumers/subprocess.md` and `docs/consumers/dnd-pipeline.md` for
+  downstream policy checks;
+- `docs/internal/pipeline.md` for promotion, aggregation, retry, and checkpoint
+  mechanics;
+- `docs/internal/modules.md` and `docs/internal/dnd.md` for producer rules and
+  the D&D classification matrix; and
+- `docs/policy/architecture.md` for the durable ownership invariant after the
+  ADR is accepted and implemented.
+
+No configuration knob is required for the first implementation. A fixed,
+well-documented taxonomy is easier to reason about than per-reason display
+overrides. Configurable escalation or suppression can be considered only after
+production review demonstrates a concrete operator need.
+
+## Test Coverage Assessment
+
+Existing coverage worth preserving includes:
+
+- accepted-attempt and terminal-rejection warning promotion;
+- validator failure retry exhaustion and `warn_continue`;
+- module semantic retry fallback;
+- deterministic warning order under concurrent lane completion;
+- chunk-plan invalidation and discarded-cache warning behavior;
+- fresh/checkpoint warning equivalence;
+- local D&D warning caps and safe dynamic-message quoting;
+- JSON warning-file publication; and
+- CLI stderr, debug, and receipt counts.
+
+Material gaps are:
+
+- no bound test for NPC- or spell-relatedness warnings;
+- no generic warning-field or result-size validation;
+- no test for output encoder warnings versus published `warnings.json`;
+- no operator-level aggregation or bounded-sample tests;
+- no fresh/resume test for grouped counts because groups do not yet exist; and
+- no production evaluation of advisory precision.
+
+Tests should protect the semantic relationships: exact occurrence counts,
+bounded samples, deterministic group order, actionable-only warning
+presentation, and cross-surface equality. They should not assert one exact
+warning count for every complete D&D run or treat message wording as a public
+API unless the wording itself enforces a security boundary.
+
+## Audit Conclusion
+
+The application is in a good position for warning reform. Its retry,
+validation, checkpoint, and concurrency mechanics provide reliable points at
+which to attach structured diagnostics. The most valuable change is not to
+suppress individual reason codes; it is to replace the semantically flat,
+origin-free collection with bounded typed groups and to reserve the word
+“warning” for conditions that merit operator attention.
+
+Provider-backed runs would improve prioritization and help tune the D&D
+advisories, but they are not necessary to conclude that routine normalization
+and heuristic doubt should not dominate stderr or the durable warning
+contract. They should be gathered before changing heuristic acceptance policy
+or adopting a numerical production warning-volume target.

docs/roadmap/configkit.md

@@ -0,0 +1,229 @@
+# ConfigKit 0.5 And Configuration Inheritance
+
+## Purpose
+
+Adopt ConfigKit v0.5.0 and make its sibling inheritance useful and supported in
+Notarius configuration, particularly for deriving development or testing
+pipelines from a complete D&D pipeline without duplicating the pipeline body.
+
+ConfigKit owns source composition and inheritance. Notarius continues to own
+typed configuration, domain defaults and validation, pipeline resolution, and
+execution. This work does not introduce a second configuration-merging engine.
+
+The [implementation plan](implementation.md) owns the ordered work and
+validation sequence. Release preparation and publication remain separate.
+
+## Reviewed Baseline
+
+Reviewed on 2026-10-03. Notarius pins ConfigKit v0.4.2 and uses its ordinary
+`Load` API in `internal/core/config/load.go`. Configuration version 5 supports
+imports, selected configuration overlays, explicit command overrides, recorded
+normalization, and redacted effective/explain output. Runtime configuration is
+detached from the ConfigKit inspection snapshot.
+
+Named pipelines and artifact lanes are mappings; pipeline `steps` and validator
+chains are sequences. The complete example imports
+`examples/pipelines/dnd-session.yml`, while the existing development overlay
+changes operational settings. Relative configured paths are resolved from the
+file supplying their surviving declaration. The current path resolver uses
+ConfigKit origin/source metadata and host filesystem paths.
+
+Target ConfigKit v0.5.0 at full source commit
+`dc09959cca4e105f49ec316c6d4ba585bd2340bd`. Consult the pinned
+[release guide](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.5.0/docs/releases/v0.5.0.md)
+and [configuration contract](https://gitea.maximumdirect.net/eric/ConfigKit/src/tag/v0.5.0/docs/config.md).
+The release adds inheritance, layered loading, filesystem-backed sources,
+mapping sources, and passive resource contexts. Its Go requirement and YAML
+dependency are unchanged. The upgrade has not yet been trialed against
+Notarius's test suite at this review baseline.
+
+## Target End State
+
+### Native Sibling Inheritance
+
+Operators can define a named pipeline with `extends: parent-pipeline` and
+override only the settings that differ. The parent remains an ordinary named,
+valid pipeline; no abstract-template flag, template registry, or special
+validation exemption is introduced. Derived pipelines use the existing run,
+listing, validation, effective-configuration, and explanation commands.
+
+Use ConfigKit's native semantics without restricting inheritance to pipelines
+or implementing a Notarius-specific subset:
+
+- `extends` selects one exact key among the mapping's immediate siblings.
+  It is not a path, cross-scope lookup, or multiple-parent expression.
+- Source precedence is assembled before inheritance, and inheritance runs
+  before typed decoding and application resolution. Inherited input is explicit
+  for presence-sensitive defaults, including zero, false, empty, and null.
+- Child mappings recursively overlay parent mappings; sequences, scalars,
+  and null replace inherited values. Existing typed/domain validation still
+  determines whether the resulting value is valid.
+- Omitting `extends` retains a lower-priority relationship; `extends: null`
+  cancels the relationship, not arbitrary inherited fields independently.
+- Root and sequence-element mappings have no sibling namespace for their own
+  string relationship. Nested mappings may have one. In particular, individual
+  entries of the `steps` sequence cannot extend other step entries.
+- ConfigKit rejects missing/non-mapping parents, invalid directive types, and
+  cycles, and resolves effective relationships even in unselected entries.
+- Parent definitions receive normal typed decoding and Notarius validation.
+  Inheritance is not a way to hide invalid partial pipeline definitions.
+- Inherited nested relationships resolve at their destination according to
+  ConfigKit's rules; do not pre-expand or reinterpret them in Notarius.
+
+Names are matched by ConfigKit before Notarius's existing identifier trimming.
+Document exact-key lookup rather than introducing pre-inheritance name rewriting.
+
+The principal documented workflow is whole-pipeline reuse. Inheritance does not
+append steps, merge sequences by `id`, or allow a child to override one list
+element without supplying a replacement list. The same applies to validator
+chains. Do not disguise this boundary through custom list-merging code.
+
+### Paths, Provenance, And Runtime Boundaries
+
+An inherited relative reference or resource path remains relative to its
+original declaring file, not the child's file or the invocation directory.
+Imported parents, overlays, and nested inheritance must retain that behavior.
+Direct child declarations use their own source context. Built-in relative
+destinations and CLI-supplied paths keep their existing bases.
+
+Review `documentPathBase` and related original-path/normalization handling
+against the new origin metadata. Make narrowly required corrections if needed;
+do not assume that successful typed decoding proves correct path resolution.
+Effective output must agree with the runtime paths, and explanations must retain
+the upstream derivation evidence through recorded Notarius normalization.
+
+Keep the ConfigKit boundary private: no upstream inheritance objects or
+unresolved directives reach runtime pipeline/module types. ConfigKit expands
+relationships once during loading. Notarius's existing binding-profile,
+validation-policy, and module-default resolution still operate on the resulting
+configuration; they are not replaced with generic sibling inheritance.
+
+Configuration overlays, pipeline inheritance, and PromptKit `base_profile`
+inheritance remain distinct mechanisms. The latter still belongs to PromptKit.
+
+### Compatibility And Upgrade Policy
+
+Keep Notarius configuration `version: 5`. The typed runtime shape is unchanged;
+the new capability belongs to configuration composition. No new CLI flag or
+inheritance opt-in setting is needed or available upstream.
+
+The significant compatibility change is that `extends` becomes a reserved key
+in every input mapping, including dynamic module-option maps and named maps.
+It is consumed before typed decoding, so it can no longer be ordinary data or
+an ordinary entry name there. Audit maintained configuration/fixtures for such
+usage and document that affected operator configurations must rename the key
+or identifier and any associated consumer field. Do not silently strip, alias,
+or bypass the directive to preserve an incompatible interpretation.
+
+Configurations without that collision should retain their existing meaning.
+Preserve discovery, import rules, overlay selection, explicit CLI override
+precedence, strict decoding, redaction, defaults, and validation. Existing
+configuration-stage inheritance does not alter the fixed execution pipeline,
+artifact contracts, warning policy, or checkpoint identity design.
+
+The eventual Notarius release should be a new minor version, explaining both
+the feature and the newly reserved input key. Release preparation/publication
+is separate from this work; no exact release number is selected here.
+
+## Required Work
+
+### Dependency And Configuration Integration
+
+Upgrade `go.mod` and `go.sum` to the exact target. Keep PromptKit and unrelated
+dependencies unchanged unless dependency resolution demonstrably requires it.
+Continue using ordinary `configkit.Load`, the existing typed defaults factory,
+and source-aware resolution/validation callbacks.
+
+Inspect the load, operational-document, path, conversion, inspection, and CLI
+boundaries. Add only integration adjustments demonstrated necessary by the
+upstream change. There should be no `Extends` field added to Notarius runtime
+types and no homegrown inheritance algorithm.
+
+Update ConfigKit's factual attribution version and COPYRIGHT/LICENSE/source
+links to the target commit after inspecting its actual notices. Preserve the
+selected project grant and reuse unchanged local license texts.
+
+### Maintained Example
+
+Extend the complete example's imported pipeline definitions with a small
+`dnd-session-development` sibling deriving from `dnd-session`, demonstrating a
+pipeline-level setting override such as a smaller structural-repair budget.
+Use already supported values and existing profile sources so the example
+validates without an invented model/profile dependency. Explain that
+`llm_profile` is another useful override when the operator supplies that profile.
+
+Retain the runnable parent, minimal example, and existing operational overlay.
+Do not duplicate the complete steps list or add a third standalone configuration
+merely to demonstrate inheritance. Update example-loading/listing expectations
+for the additional pipeline, checking inherited behavior rather than snapshots
+of incidental formatting or total line counts.
+
+### Canonical Documentation
+
+- `docs/config.md`: own syntax, composition order, exact sibling lookup,
+  replacement/null semantics, path bases, reserved-key migration, and limits
+  on step/validator-list composition. Link to the maintained example and pinned
+  upstream rules rather than duplicating the entire upstream manual.
+- `docs/internal/configuration.md`: describe expansion before typed decoding,
+  presence and source-aware normalization, and the unchanged runtime boundary.
+- `docs/integrations/pkg-configkit.md`: update the supported version, public
+  contract links, and integration scope.
+- `docs/oss/attribution.md`: update the dependency's verified source/notice links.
+- `docs/cli.md` and consumer guides: update only where navigation or examples
+  benefit from showing selection of the derived pipeline. Do not invent new
+  invocation syntax or duplicate the configuration reference.
+
+The existing ConfigKit architecture decision remains applicable. No new ADR is
+required solely for consuming the library's composition feature; do not rewrite
+an accepted ADR or turn new private implementation details into invariants.
+
+## Verification And Acceptance
+
+Use focused Notarius boundary tests, not a duplicate of ConfigKit's full suite:
+
+- Existing maintained configurations continue loading and resolving.
+- A derived pipeline retains its own identifier and inherits the complete
+  parent pipeline while applying its explicit overrides.
+- Imports and selected overlays participate in composition before inheritance;
+  explicit CLI overrides keep their documented precedence.
+- Representative zero/false/null inputs exercise existing presence-sensitive
+  defaulting or validation correctly; null is not universally valid merely
+  because inheritance can represent it.
+- Replacing a steps or validator sequence does not concatenate or merge it.
+- References inherited from a parent in another file retain their declaring
+  directory, while child-supplied replacements use the child's directory.
+- Effective and explanation output remain redacted and expose useful source
+  and inheritance information after application normalization.
+- Representative invalid inheritance produces ConfigKit load diagnostics through
+  the normal Notarius CLI error path, without a parallel validation engine.
+- Maintained examples and their imported fragments validate offline without
+  credentials or provider calls.
+
+Configuration and CLI boundary coverage should protect document/path/operational,
+effective/explanation, and maintained-example behavior. Framework-resolution
+coverage is appropriate where a distinct handoff risk requires it. Acceptance
+includes the offline default suite, vet, and build with `GOWORK=off`, dependency
+tidiness, and documentation diff/link checks appropriate to the changes. The
+implementation plan owns their sequencing; these checks are not additional
+permanent release gates.
+
+## Deferred Capabilities And Non-Goals
+
+- Do not adopt `LoadLayered` or add a new underlay precedence tier now. Existing
+  imports, overlays, and typed defaults remain the loading model. Bundled
+  pipeline presets or site-wide default layers need a separate operator-facing
+  design if selected later.
+- Do not move Go defaults into embedded YAML or mapping sources solely because
+  v0.5.0 provides those APIs.
+- Do not generalize references to arbitrary `fs.FS` resources in this work.
+  `SourceContext` may be used if it materially helps the required path behavior,
+  but its filesystem access rules must not silently replace Notarius's existing
+  host-path contract or introduce new path restrictions.
+- No abstract templates, multiple inheritance, list-element composition,
+  new template schema, new pipeline scheduler, or extra configuration knobs.
+- No opt-in gate or Notarius-only prohibition on other valid native inheritance
+  locations; use upstream semantics and existing domain validation.
+
+There are no significant open design decisions at this baseline. Implementation
+should verify the new metadata behavior and correct concrete integration gaps
+without broadening the agreed feature scope.

docs/roadmap/future.md

@@ -10,77 +10,13 @@ not as committed release dates.
 PromptKit now owns structural output repair within one completion. Notarius
 owns stage candidates, validator chains, semantic rejection policy, bounded
 feedback-aware stage retries, validation provenance, and reusable-state
-eligibility. The remaining near-term work applies those completed foundations
-to domain review and operator-facing diagnostics.
+eligibility, and the separation of actionable process warnings from quality
+diagnostics. The remaining near-term work applies those completed foundations
+to domain review and empirical evaluation.
 
-### D&D Combat Scene Semantic Validation
-
-- Add an optional production LLM-backed D&D validator that determines whether
-  proposed scene boundaries and classifications represent substantive active
-  combat correctly. Its central quality goal is that active combat is kept in
-  coherent scenes classified as `combat`, rather than split incorrectly or
-  hidden inside scenes classified as `narrative`, `recap`, or `meta`.
-- Resolve the validator's exact target before implementation. The current
-  `dnd/scenes` chunker owns only complete, gap-free source ranges, while the
-  per-chunk `dnd/scene-descriptions` extractor owns the `combat`, `narrative`,
-  `recap`, and `meta` classification. The preferred initial placement is
-  therefore an extract-stage validator for `dnd/scene-descriptions`, where it
-  can compare one proposed kind with the corresponding transcript chunk.
-- Consider a chunk-stage LLM validator only for a distinct boundary-coherence
-  question that can be answered from the complete transcript and proposed
-  range map, such as whether one continuous combat was fragmented across
-  inappropriate scene boundaries. Do not duplicate the same classification
-  judgment at both stages. Moving classification into chunk-plan annotations
-  would change the deliberately minimal, annotation-free chunk contract and
-  requires an explicit architecture review before it is selected.
-- Validate both false negatives and false positives: a non-combat kind must not
-  omit substantive active combat, and a combat kind must be supported by such
-  combat. Keep the existing deterministic downstream rule that combat-turn
-  extraction runs only for an exact `combat` scene classification; semantic
-  review improves the upstream classification but does not replace that gate.
-- Run the semantic validator through PromptKit, use a minimal required-field
-  structured response schema, and let PromptKit repair structural validator
-  output within its bounded budget. A contract-invalid final validator response
-  is a validator execution failure, not a semantic rejection and not a reason
-  to recursively validate the validator.
-- Evaluate the prompt and decision policy against a small human-reviewed set
-  containing combat setup, active turns, interruptions, multi-phase encounters,
-  brief rules discussion, aftermath, recalled combat, and false-positive
-  hostile dialogue. Measure false acceptance, false rejection, retry success,
-  added calls, latency, and token cost before placing it in the production
-  default chain.
-- An ADR is not required if classification remains owned by
-  `dnd/scene-descriptions` and the validator follows the generic validation ADR.
-  Create or supersede an ADR if the work transfers scene classification into
-  the chunker or otherwise changes stage ownership or the durable chunk-plan
-  contract.
-
-### Warning Signal And Presentation Reform
-
-- Audit every warning producer and representative successful runs. Ordinary
-  success producing dozens of warnings is a failed operator experience: the
-  volume obscures actionable problems and trains operators to ignore the
-  warning channel.
-- Define a small warning taxonomy that distinguishes actionable degradation,
-  incomplete validation, lossy fallback, and data-quality risk from routine
-  normalization observations or informational diagnostics. Preserve detailed
-  traceability in debug or manifest data without promoting every observation
-  to a top-level CLI warning.
-- Consider stable deduplication and aggregation by scope and reason code,
-  bounded samples plus omitted counts, and a concise CLI summary with a path to
-  detailed diagnostics. Do not suppress genuine validator execution failures
-  merely to reduce the count.
-- Decide which warnings affect process status, rejection summaries, durable run
-  receipts, or only debug output. Ensure warning ordering and aggregation are
-  deterministic across concurrent execution.
-- Establish a representative warning-volume acceptance target and human review
-  workflow before changing individual producers piecemeal. The intended result
-  is not zero warnings; it is a small set in which every surfaced warning merits
-  operator attention.
-- This work does not require an ADR unless it changes validation acceptance,
-  failure, or durable contract semantics. CLI presentation and diagnostic
-  taxonomy otherwise belong in a feature roadmap followed by updates to their
-  canonical configuration, operations, integration, and internal documents.
+Near-term reliability work should now be selected from the concrete evaluation
+and extension opportunities below. The retry, validation, and subprocess
+foundations described above are implemented current behavior.
 
 ## Near-Term D&D Pipeline
 

docs/roadmap/implementation.md

@@ -0,0 +1,528 @@
+# ConfigKit Inheritance Implementation Plan
+
+## Purpose And Scope
+
+Implement [ConfigKit 0.5 And Configuration Inheritance](configkit.md). That
+feature roadmap owns the intended behavior and policy choices. This document
+owns the ordered implementation work. Each numbered stage is one prompt for a
+Luna coding agent; complete its acceptance criteria before starting the next.
+
+The starting baseline pins ConfigKit v0.4.2 and PromptKit v0.11.2, uses ordinary
+`configkit.Load`, and accepts Notarius configuration version 5. Upgrade only
+ConfigKit to v0.5.0, source commit
+`dc09959cca4e105f49ec316c6d4ba585bd2340bd`. The release tag is annotated: use
+`git rev-parse 'v0.5.0^{commit}'` when verifying the source commit in a checkout.
+
+The implementation adds supported native configuration inheritance and a
+maintained example. It does not require changing pipeline execution, artifact
+schemas, or release tooling. Release preparation and publication remain a
+separate task; this feature belongs in a future minor release.
+
+## Working Instructions For Every Stage
+
+- Read `docs/development.md`, `docs/policy/agents.md`, and the feature roadmap.
+  Use the development guide to select additional applicable policies, including
+  architecture, testing, documentation, and OSS for the changes being made.
+- Inspect the named code and tests before editing. Prefer the repository's
+  code knowledge graph for code discovery. Inspect the pinned upstream release
+  and public API when an integration detail needs confirmation; do not assume
+  a sibling checkout's current branch equals the released version.
+- Keep ordinary `configkit.Load`, typed defaults, and the existing private
+  configuration boundary. ConfigKit handles `extends` before decoding; add no
+  `Extends` field, second merge pass, application template registry, or opt-in
+  flag. Accept valid native inheritance locations under existing domain rules.
+- Make production changes only where a concrete integration failure requires
+  them. A stage may consist of focused tests and documentation when the
+  existing adapter already behaves correctly. Fix a regression rather than
+  weakening an established expectation to accommodate the upgrade.
+- Test Notarius's boundary with the real ConfigKit dependency and small,
+  deterministic fixtures. Reuse existing helpers and coverage; do not replicate
+  ConfigKit's complete test matrix, add diagnostic snapshots, or assert
+  incidental output formatting. Keep the default suite offline and independent
+  of credentials and model calls.
+- Use `GOWORK=off` for Go commands so a sibling checkout cannot substitute for
+  the pinned modules. Update canonical documentation as each behavior lands.
+  Review the diff, run the stage's checks, and commit the coherent result under
+  the agent policy. Record any unresolved failure in the handoff rather than
+  marking that stage complete. Do not push or publish a release as part of this
+  plan.
+
+## Stage 1 — Upgrade The Dependency And Its Notices
+
+> Completion: complete.
+
+Goal: establish the released dependency baseline without redesigning the
+configuration adapter.
+
+Inspect:
+
+- `go.mod`, `go.sum`, and `internal/core/config/load.go`.
+- `docs/integrations/pkg-configkit.md` and the ConfigKit entry in
+  `docs/oss/attribution.md`.
+- ConfigKit's pinned `docs/releases/v0.5.0.md`, `go.mod`, `COPYRIGHT`, and
+  `LICENSE`; consult the sibling checkout with `git show v0.5.0:<path>`.
+
+Work:
+
+1. Run `GOWORK=off go get gitea.maximumdirect.net/eric/ConfigKit@v0.5.0`, then
+   `GOWORK=off go mod tidy`. Review the selected dependency graph. Retain
+   PromptKit v0.11.2 and unrelated pins unless module resolution requires a
+   change; explain any such change in the handoff.
+2. Search maintained configuration, fixtures, YAML tags, and documentation for
+   ordinary uses of the key or entry name `extends`. For example, use
+   `rg -n '\bextends\b' examples internal docs assets`. Classify any matches:
+   new inheritance instructions are valid; ordinary field/key uses collide
+   with the new reserved directive. Rename actual maintained collisions and
+   their consumers together, without an alias or bypass. Do not rename the
+   unrelated PromptKit `base_profile` setting.
+3. Run focused existing tests. Address compile/API compatibility failures with
+   the smallest necessary adapter changes. Native inheritance needs no
+   registration or load option.
+4. Update the integration document's pin and brief description to v0.5.0;
+   replace the v0.4.2 patch-only explanation with the new composition boundary.
+   Link to pinned upstream release/configuration documentation.
+5. Update only ConfigKit's attribution version and exact source/notice links
+   to the target commit, preserving the verified copyright and
+   `LGPL-3.0-or-later` expression. Reuse the existing LGPL/GPL texts when
+   unchanged. Do not refresh unrelated component attribution or policies.
+
+Acceptance criteria:
+
+- The declared and selected ConfigKit module is v0.5.0, without a workspace or
+  local `replace` dependency.
+- Existing configuration and CLI tests pass; maintained ordinary `extends`
+  collisions, if any, have been resolved explicitly.
+- Integration and attribution documents agree with the actual dependency and
+  imported source commit. The adapter still uses ordinary `Load`.
+
+Validation:
+
+```sh
+GOWORK=off go list -m gitea.maximumdirect.net/eric/ConfigKit
+GOWORK=off go test ./internal/core/config ./internal/cli
+git diff --check
+```
+
+Prompt size: one dependency upgrade, its notices, and demonstrated compatibility
+adjustments. Leave new inheritance coverage to the following stages.
+
+## Stage 2 — Prove Pipeline Composition And Runtime Conversion
+
+> Completion: complete.
+
+Goal: establish whole-pipeline reuse through the real configuration boundary.
+
+Inspect `load.go`, `document.go`, `loaded_config.go`, `pipeline_document.go`,
+`document_test.go`, `pipeline_document_test.go`, and
+`effective_config_contract_test.go` under `internal/core/config`. Reuse the
+existing test catalog for runtime resolution.
+
+Work:
+
+1. Add focused loading coverage in `internal/core/config/inheritance_test.go`.
+   Define a valid parent pipeline and a child with `extends: parent` plus a
+   pipeline-level override. Assert the inherited input, bindings, and ordered
+   steps survive conversion, while the child retains its own pipeline ID and
+   the parent keeps its own settings.
+   Keep the fixture small rather than copying the complete D&D example.
+2. Resolve the resulting child with the existing catalog. Assert its selected
+   ID and overridden setting reach the resolved pipeline. Use the catalog's
+   registered module keys and avoid generated-reference requirements in this
+   small fixture; the full generated-reference handoff is covered in Stage 7.
+   Reuse existing resolution tests for unrelated defaults and digests.
+3. Add one replacement case: the child supplies a complete different `steps`
+   list. Assert replacement and ordering, with no parent steps appended or
+   merged by ID. Both resulting pipelines must satisfy ordinary validation.
+4. Add one native nested-mapping case using sibling artifact lanes in an
+   `artifacts` mapping: a child lane inherits a valid parent lane and overrides
+   a binding value. This proves that Notarius does not limit inheritance to
+   pipeline mappings. Other upstream-supported mapping shapes need no custom
+   permission mechanism.
+5. In `docs/config.md`, add the canonical inheritance explanation: exact
+   immediate-sibling lookup, one parent, source composition before expansion,
+   recursive mapping combination, sequence/scalar/null replacement, normal
+   validation of parent and child, and all effective relationships being
+   resolved. State that step-sequence entries cannot extend each other.
+   Include a small illustrative pipeline snippet and the reserved `extends`
+   migration note. Distinguish configuration overlays and PromptKit profiles.
+
+Acceptance criteria:
+
+- Loading and resolving a child yields an ordinary independently identified
+  pipeline with the expected inherited composition and explicit override.
+- Replacement lists retain only the child list, in its configured order.
+- Valid nested artifact-lane inheritance works through native ConfigKit
+  behavior without extra runtime types or application merging.
+- Configuration version remains 5 and the user reference describes the
+  implemented syntax and reserved-key compatibility impact.
+
+Validation:
+
+```sh
+GOWORK=off go test ./internal/core/config
+git diff --check
+```
+
+Prompt size: small composition fixtures, runtime handoff, and one canonical
+syntax section. Presence-sensitive cases belong to Stage 3.
+
+## Stage 3 — Preserve Presence And Existing Domain Validation
+
+> Completion: complete.
+
+Goal: ensure inherited input remains explicit through Notarius normalization,
+defaulting, and validator-chain conversion.
+
+Inspect `operational_document.go`, `pipeline_document.go`,
+`document_normalizer.go`, `loaded_config.go`, and their existing presence tests.
+Extend `inheritance_test.go` rather than adding a parallel fixture framework.
+
+Work:
+
+1. Cover inherited `structured_output_repair_attempts: 0`: it remains a
+   populated zero override after loading and resolution, rather than reverting
+   to a pipeline or prompt default. Also cover a child explicitly overriding a
+   nonzero parent budget with zero.
+2. Cover an inherited supported `validators: []` on a chunk or extraction
+   binding. Its runtime override retains `Set=true` and an empty chain. Cover
+   a child replacing a nonempty parent chain with `[]`; do not concatenate it
+   or reinstall default validators because the child list is empty.
+3. Cover an inherited false module-option value, such as
+   `output.options.evidence_context.enabled: false`, remaining false in runtime
+   configuration. Inspect the decoded document's input metadata to establish
+   explicit presence where needed, rather than relying on truthiness.
+4. Cover inherited or child-supplied null for a field already rejected when
+   explicit, such as `structured_output_repair_attempts`. Require the existing
+   contextual load failure. Inheritance's support for null does not make that
+   field nullable. Reuse existing direct-input null coverage.
+5. Use a small overlay fixture to demonstrate the sequencing: an overlay that
+   changes the parent before expansion changes the child's inherited value;
+   a child's own explicit replacement wins over the parent's value. Verify
+   `extends: null` cancellation using a child with its own valid input binding,
+   and verify omission of the directive in an overlay preserves the base
+   relationship. An explicit override record for the parent value must be
+   reflected in an inheriting child as well.
+6. If any integration defect appears, correct Notarius's existing presence or
+   conversion handling, using ConfigKit's metadata. Add no application
+   inheritance evaluator. Refine `docs/config.md` to explain explicit
+   zero/false/empty/null and cancellation without promising universal validity.
+
+Acceptance criteria:
+
+- Inherited and direct replacements retain their existing explicit-value
+  semantics, including zero repair budgets and empty validator overrides.
+- Existing null restrictions are neither relaxed nor expanded.
+- Overlay/explicit-override composition precedes inheritance, and cancellation
+  behaves as described by the pinned upstream contract.
+
+Validation:
+
+```sh
+GOWORK=off go test ./internal/core/config
+git diff --check
+```
+
+Prompt size: presence and precedence at one package boundary. This stage does
+not change defaults or add CLI flags for arbitrary configuration overrides.
+
+## Stage 4 — Verify Declaration-Relative Paths Through Inheritance
+
+> Completion: complete.
+
+Goal: keep inherited resource paths anchored to the original declaration.
+
+Inspect `document_paths.go`, `document_paths_test.go`, the original-path map in
+`pipeline_document.go`, and sequence mutation recording in
+`document_normalizer.go`. Consult ConfigKit's public `InputInfo`, `Origin`, and
+`Source` contracts at v0.5.0.
+
+Work:
+
+1. Extend real-file tests using `t.TempDir()`: import parent and child pipeline
+   definitions from different subdirectories beneath one configuration root.
+   Give the parent pipeline a relative external reference and one reference
+   inside an inherited ordered step. Assert both inherited paths resolve from
+   the parent's file; a direct child reference replacement resolves from the
+   child's file. Reference files may be minimal public fixture data.
+2. Add an overlay replacement case where the parent reference is declared by
+   the overlay and subsequently inherited. Its base must be the overlay's
+   directory. A nested reference-mapping inheritance case must preserve its
+   original contributor when copied into a derived pipeline.
+3. Combine one inherited path case with whitespace-normalized pipeline or
+   reference keys. The existing `originalPath` mechanism must still find the
+   input's origin. ConfigKit exact sibling matching happens before Notarius
+   trims names; do not pre-normalize the inheritance lookup.
+4. Include a legitimate `../` reference, retaining the current host-path
+   behavior. Reuse existing coverage for built-in destination bases, explicit
+   CLI destination bases, absolute paths, and empty cache roots unless the
+   upgrade reveals a distinct regression.
+5. Fix `documentPathBase` or related origin handling only if these tests expose
+   a failure. Query the surviving value's contributor, not the `extends`
+   control location or an arbitrary sibling. Keep the existing host-path
+   resolution model; do not replace it with resource opening through
+   `ResourceContext.FS`, which could introduce containment restrictions.
+6. Clarify inherited declaring-file behavior in `docs/config.md`. Update the
+   loading/path explanation in `docs/internal/configuration.md` to reflect
+   expansion before decoding and source-aware recorded normalization.
+
+Acceptance criteria:
+
+- Imported, nested, and overlaid inherited paths use the file supplying the
+  surviving value; direct child replacements use their own declaring file.
+- Normalized identifiers and inherited ordered-step references retain correct
+  bases without unrecorded sequence mutation failures.
+- Existing path access and destination policies are preserved. No new path
+  containment, existence, or resource-format restriction is introduced.
+
+Validation:
+
+```sh
+GOWORK=off go test ./internal/core/config
+git diff --check
+```
+
+Prompt size: one path-resolution seam and focused real-file regressions.
+Inspection rendering is checked separately in Stage 5.
+
+## Stage 5 — Preserve Inspection, Derivation, And Ownership
+
+> Completion: complete.
+
+Goal: prove inherited configuration remains correctly inspectable after
+Notarius's recorded normalization and runtime conversion.
+
+Inspect `loaded_config.go`, `loaded_config_test.go`, `document_normalizer.go`,
+`redaction_test.go`, and the new inherited path fixtures. Review upstream
+metadata/history APIs rather than inventing a new provenance format.
+
+Work:
+
+1. Through `LoadedConfig.WriteEffective`, check a derived pipeline's expanded
+   values and resolved reference paths agree with its runtime configuration.
+   Verify consumed `extends` directives are absent from the effective typed
+   configuration. Assert selected values/paths, not the full YAML document.
+2. Through `WriteExplanation`, inspect one inherited scalar and one inherited
+   path that Notarius normalizes. Assert useful parent/source and inheritance
+   evidence remains available alongside the final normalization result.
+   Use structured upstream metadata within the configuration package for
+   precise provenance checks, and minimal stable fragments for rendered text.
+   Do not require a new Notarius renderer or exact diagnostic wording.
+3. Add a synthetic credential-shaped option to a parent and inherit it into a
+   child. Verify effective and explanation views redact its value, including
+   inherited/displaced history where present. Use only fake secret strings and
+   the existing sensitivity predicate; add no new credential rules.
+4. Extend the existing ownership test: mutating a child's runtime nested map
+   must not mutate the parent's runtime map or the frozen inspection snapshot.
+   Retain the `RuntimeConfig()` detached-copy behavior without a new cloning
+   mechanism unless the test demonstrates a conversion defect.
+5. Update `docs/internal/configuration.md` to describe inherited explicit input,
+   retained derivation, normalization, and the detached runtime boundary. Repair
+   any affected stale loading terminology, such as calling a configuration
+   overlay a profile. Link to `docs/config.md` for syntax and field rules.
+
+Acceptance criteria:
+
+- Effective paths agree with runtime paths; explanations retain useful source
+  and transfer evidence after normalization.
+- Existing redaction applies to inherited values and history.
+- Parent, child, returned copies, and inspection snapshots have the established
+  ownership behavior. Upstream inspection types stay private to configuration.
+
+Validation:
+
+```sh
+GOWORK=off go test ./internal/core/config
+git diff --check
+```
+
+Prompt size: configuration inspection and ownership, with focused tests and its
+internal documentation.
+
+## Stage 6 — Exercise CLI Selection And Failure Reporting
+
+> Completion: complete.
+
+Goal: make derived pipelines first-class through the existing commands and
+preserve the normal load-error path for invalid inheritance.
+
+Inspect `internal/cli/configkit_commands_test.go`, `command_contract_test.go`,
+and the configuration command/load helpers. Use the existing injected catalog
+and fake collaborators; do not construct providers or make LLM calls.
+
+Work:
+
+1. Add a small valid parent/child fixture. Exercise `pipelines list` and
+   `config validate --pipeline child`; assert the child can be selected by its
+   own ID and listing remains sorted. Reuse existing command rendering tests
+   rather than duplicating every output mode.
+2. Exercise `config effective` and `config explain` for that child to prove CLI
+   wiring reaches the safe upstream inspection views. Assert successful status
+   and relevant inherited evidence, not a whole-output snapshot.
+3. Add representative invalid load cases for a missing parent, a cycle, and an
+   invalid directive type. Keep one invalid relationship in an unselected
+   pipeline to prove selecting a different valid pipeline cannot hide it.
+   Assert runtime-error status, no success output, and meaningful safe
+   configuration diagnostics. Reuse package-level diagnostics for more detailed
+   path checks; ConfigKit owns the full malformed-directive matrix.
+4. Check exact-key behavior with a whitespace-bearing parent name: the matching
+   declaration works and existing identifier normalization follows expansion.
+   A mismatch should produce the upstream missing-parent failure. No automatic
+   trimming, aliases, or application-specific inheritance restrictions are
+   added.
+5. Change production CLI code only if these tests expose a wiring defect.
+   `docs/cli.md` may gain a short link to configuration inheritance where useful,
+   but commands and flags remain the same.
+
+Acceptance criteria:
+
+- Derived pipelines use the ordinary selection, listing, validation, and
+  inspection commands.
+- Invalid relationships reach the existing load-error reporting path, even
+  when their entries are not selected for execution.
+- Read-only command tests require neither credentials nor provider work.
+
+Validation:
+
+```sh
+GOWORK=off go test ./internal/cli ./internal/core/config
+git diff --check
+```
+
+Prompt size: command-boundary behavior and representative error propagation.
+
+## Stage 7 — Publish And Test The Development Pipeline Example
+
+> Completion: complete.
+
+Goal: give operators one complete, runnable demonstration without duplicating
+the full pipeline.
+
+Inspect `examples/dnd-complete.config.yml`,
+`examples/pipelines/dnd-session.yml`, `examples/overlays/development.yml`,
+`internal/cli/example_contract_test.go`, and `maintainedExampleFiles` in
+`internal/cli/production_contract_test.go`.
+
+Work:
+
+1. Add this sibling to `examples/pipelines/dnd-session.yml`:
+
+   ```yaml
+   dnd-session-development:
+     extends: dnd-session
+     structured_output_repair_attempts: 0
+   ```
+
+   Keep it beneath `pipelines`, beside the complete parent. Explain with a short
+   comment that this development variant disables PromptKit structural repairs
+   while inheriting the steps and configured producer-stage retry budgets.
+   It uses the parent's existing `dnd-extraction` profile.
+2. Update the complete example's expected pipeline IDs to include the child in
+   sorted order. Keep the minimal example and existing operational overlay.
+   Do not add a third standalone configuration or duplicate the parent's steps.
+3. Extend maintained-example coverage to load, resolve, and materialize external
+   references for both complete-example pipelines. Compare the child to the
+   parent for step/lane composition and generated-reference bindings, and assert
+   the selected zero structural-repair setting reaches eligible resolved
+   bindings. Do not assert equal pipeline digests: their IDs/settings differ.
+4. Update `TestMaintainedExamplesValidateEffectiveProfilesOffline` to validate
+   every expected pipeline in each maintained example, including the new child,
+   with credentials absent. Retain the existing two-root-example inventory.
+5. Update `docs/config.md`'s maintained-example guidance to show selection of the
+   variant and explain that operators may instead override `llm_profile` when
+   supplying another profile. Link to the inherited fragment. Add only a short
+   configuration link in `docs/consumers/dnd-pipeline.md` if useful; keep its
+   complete parent workflow and artifact instructions intact.
+
+Acceptance criteria:
+
+- The existing complete root imports both valid pipelines, and the derived
+  pipeline contains only the relationship and its intentional override.
+- Both variants resolve and validate offline using the maintained profile,
+  external references, generated bindings, and full module catalog.
+- Maintained examples and navigation accurately explain the variant without
+  confusing it with the operational overlay or PromptKit profile inheritance.
+
+Validation:
+
+```sh
+GOWORK=off go test ./internal/cli -run 'TestMaintained'
+GOWORK=off go test ./internal/core/config ./internal/cli
+git diff --check
+```
+
+Prompt size: one example fragment, its existing test inventory, and focused
+operator guidance. No full live extraction run is needed.
+
+## Stage 8 — Consolidate Documentation And Verify The Complete Upgrade
+
+> Completion: complete.
+
+Goal: finish with an internally consistent, validated upgrade ready for review.
+
+Inspect all changed files, `docs/config.md`,
+`docs/internal/configuration.md`, `docs/integrations/pkg-configkit.md`,
+`docs/oss/attribution.md`, and affected CLI/consumer navigation. Compare against
+the feature roadmap's acceptance criteria.
+
+Work:
+
+1. Confirm canonical ownership: configuration defines syntax/precedence/path
+   rules; internals explain the adapter; integration documentation identifies
+   the supported upstream contract; attribution records the imported version
+   and notices. Remove duplicate definitions introduced during earlier stages.
+2. Check the documentation covers the reserved key in every input mapping,
+   exact sibling naming, normal validation of all definitions, replacement of
+   step/validator sequences, source-relative inherited paths, explicit values,
+   and cancellation. Do not describe deferred `LoadLayered`, filesystem source,
+   mapping source, or underlay workflows as available Notarius features.
+3. Search for stale ConfigKit v0.4.2/current-pin claims in active documentation
+   and dependency files, ordinary reserved-key collisions, and confusing profile
+   terminology. Leave historical releases and archived roadmaps intact. Verify
+   relative document links locally and pinned external links where accessible;
+   no new documentation-checking tool or recurring network gate is required.
+4. Run the full offline default suite, vet, and native build. Build to a
+   `mktemp -d` destination so no binary is left in the repository. Run
+   `GOWORK=off go mod tidy -diff`; an unexpected diff must be resolved and
+   reviewed rather than accepted silently.
+5. Review the final implementation for unintended restrictions or guarantees:
+   no new schema version, inheritance whitelist, abstract-template exemption,
+   custom list merge, host-path restriction, configuration source tier,
+   additional CLI knobs, or upstream types leaking into runtime contracts.
+6. Report the implemented behavior, successful checks, and any concrete gaps.
+   Keep roadmap retirement and release publication for a later request.
+
+Acceptance criteria:
+
+- Every required outcome in `configkit.md` is implemented and covered at the
+  appropriate boundary, with no unexplained scope expansion.
+- Maintained examples and canonical documents agree with the selected module
+  and observed loading behavior. Dependency metadata is tidy.
+- Full offline tests, vet, build, and relevant diff/link checks pass. Any
+  unavailable optional external-link verification is reported accurately.
+
+Validation:
+
+```sh
+GOWORK=off go test ./...
+GOWORK=off go vet ./...
+build_dir=$(mktemp -d)
+GOWORK=off go build -o "$build_dir/notarius" ./cmd/notarius
+GOWORK=off go mod tidy -diff
+git diff --check
+git status --short
+```
+
+These are development checks for this upgrade, not additional permanent release
+gates. Do not repeat successful checks for unchanged content solely to satisfy
+another handoff step; rerun the affected checks after any correction.
+
+Prompt size: final review, small documentation consolidation, and aggregate
+verification. A newly discovered substantial defect must be reported with its
+evidence and required follow-up rather than folded into an unrelated refactor.
+
+## Open Questions
+
+None at this baseline. The dependency target, native inheritance semantics,
+path policy, example override, documentation owners, and deferred features are
+specified. Whether an adapter needs a small correction is determined by the
+integration tests above, rather than a new product-policy decision.

docs/roadmap/promptkit.md

@@ -0,0 +1,409 @@
+# PromptKit 0.12 Configuration Migration
+
+## Purpose
+
+Adopt PromptKit v0.12.0 after the completed ConfigKit upgrade, replacing the
+removed configuration APIs and asset formats with PromptKit's ConfigKit-backed
+configuration boundary. Make the new composition, inheritance, presence, and
+captured-configuration capabilities useful without introducing a second loader
+or changing Notarius's domain extraction and pipeline acceptance policies.
+
+This is a feature roadmap, not an execution sequence. The operator-source and
+native-overlay decisions were accepted on 2026-10-04 and are incorporated below.
+A separate implementation plan will define the execution sequence. Release
+preparation and publication are separate work.
+
+## Reviewed Baseline
+
+Reviewed on 2026-10-04 against Notarius commit
+`af62b3b`, with ConfigKit v0.5.0 and PromptKit v0.11.2 selected in `go.mod`.
+The remote PromptKit v0.12.0 tag resolves to full source commit
+`4b8169da286917fde7875425bb32b799b12c6af3`, matching the sibling checkout.
+Primary upstream references are the
+[release guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.12.0/docs/releases/v0.12.0.md),
+[consumer migration guide](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.12.0/docs/consumers/pkg-promptkit.md#migrate-from-the-previous-configuration-api),
+and [format reference](https://gitea.maximumdirect.net/eric/promptkit/src/tag/v0.12.0/docs/formats.md).
+These were reviewed in the local checkout; the remote tag was verified directly.
+
+The current integration has these migration-sensitive boundaries:
+
+- `internal/framework/llm/asset_registry.go` flattens module-owned prompt,
+  schema, and fallback-profile filesystems and constructs `WithPromptFS`,
+  `WithSchemaFS`, and `WithFallbackProfileFS` options.
+- `promptkit_profiles.go` shares profile-source construction between the
+  execution client and credential-free explicit-profile inspection. It uses
+  `Config.ProfileDir`, `WithProfileFile`, and the backend registration option.
+  The inspection engine supplies `PromptDir: "."` without preparing a prompt.
+- `promptkit_client.go` constructs the engine and uses prepared execution,
+  semantic correction messages, structural repair overrides, observations,
+  direct sessions, reasoning overrides, and provider-neutral error adaptation.
+- `promptkit_profile_fingerprint.go` combines a pinned catalog marker with
+  reread operator profile files and fallback asset bytes. The optional local
+  endpoint contributes a separate identity; local concurrency is excluded.
+- Embedded prompt definitions throughout `assets/dnd/` and
+  `assets/generic/normalize/deduplication/` use top-level `id` and `version`.
+  `assets/dnd/profiles/dnd-extraction.yaml` and the maintained deployment file
+  `examples/llm-profiles/dnd-extraction.yml` use top-level `id`.
+- The public profile contract says a matching operator profile completely
+  replaces a fallback or catalog profile. It documents `base_profile`
+  inheritance. These claims do not match v0.12.0's native semantics.
+
+The current focused LLM, CLI, and module-integration tests pass with
+`GOWORK=off`. This establishes the baseline only: no trial dependency upgrade,
+live inference, or production model-quality evaluation has been performed.
+
+## Upstream Changes Relevant To Notarius
+
+PromptKit v0.12.0 is an incompatible configuration/API release:
+
+- `Config.Sources` accepts ordered ConfigKit underlays and an optional main
+  input. Legacy prompt/profile directory fields and configuration-source
+  options are removed. Schema and injected-runtime options remain available.
+- Documents use keyed `backends`, `profiles`, and `prompts` mappings, with a
+  second version mapping beneath each prompt ID. Embedded `id`, `version`, and
+  `base_profile` fields are invalid; profile inheritance uses `extends`.
+- Files within one source group compose strictly, not by filename precedence.
+  Later groups overlay earlier groups recursively. Explicit null, zero,
+  false, and empty values can differ from omission; `{}` does not clear a map.
+- Engine construction validates every final effective definition, including
+  unused definitions, and captures message content and static templates.
+  Ordinary execution and inspection do not reload them. Schemas, request
+  artifacts, credentials, and provider operations retain their runtime timing.
+- `InspectConfiguration` exposes captured presence, sources, diagnostics,
+  explanations, and redacted effective output. These reports are not
+  automatically safe to publish: ordinary prompt/provider content remains data.
+- Maintained catalogs move to `/v3`, both at `v3.20260930.0`.
+  PromptKit and Notarius already share the required ConfigKit v0.5.0 and Go
+  1.25.5 baseline; no additional Go-version upgrade is required by this release.
+
+## Target End State
+
+### One Native Configuration Boundary
+
+PromptKit owns the effective backend/profile/prompt configuration and all
+upstream composition and inheritance. Notarius selects its sources and adapts
+the resulting engine to the existing provider-neutral completion contract.
+ConfigKit and PromptKit types remain inside the LLM adapter's explicit
+integration boundary, not in domain modules or pipeline contracts.
+
+Retain Notarius configuration `version: 5`, `promptkit.profile_file`,
+`promptkit.profile_dir`, their mutual exclusion and declaring-file-relative
+path handling, `transient_retries`, and the optional conventional local backend.
+Do not add replacement Notarius configuration fields merely because the
+upstream constructor has changed. Document the changed external file format.
+
+Use one shared source-construction path for execution and profile preflight.
+The source precedence is:
+
+1. PromptKit's maintained catalog layer, supplied by PromptKit itself.
+2. Registered application prompt and fallback-profile assets.
+3. The explicitly selected operator file or directory.
+4. A programmatic `local` backend contribution when Notarius's
+   `promptkit.local_backend` is configured, so those explicit Notarius values
+   win over conflicting file declarations of those fields.
+
+The existing selected file/directory accepts native combined `profiles`,
+`backends`, and `prompts` documents. Enable explicit ConfigKit imports on these
+operator inputs. Describe the familiar `profile_file` and `profile_dir` fields
+as PromptKit configuration sources whose principal workflow is profile
+selection; do not add a section whitelist or a custom merge language.
+Domain modules remain responsible for interpreting and validating model output,
+even when an operator supplies a prompt overlay.
+
+Inputs within each group use native strict composition. Directory discovery is
+recursive over YAML files and has no hidden per-file priority. No unselected
+directory is scanned. Construct filesystem-backed inputs with usable resource
+contexts so referenced message files retain their declaring-source base.
+Do not combine host profile files with embedded content under a fabricated
+common filesystem root.
+
+Document import layouts that do not accidentally select the same definitions
+through both directory discovery and imports: a file-root import layout is
+often the simplest choice. Use native import/resource rules rather than
+inventing deduplication, filename override order, or broader host access.
+
+Use `FilesystemInputs` for the existing flattened embedded views,
+`DirectoryInputs` or an individual ConfigKit file input for the operator
+source, and `BackendSource` with the presence-aware local-backend helper for
+programmatic backend configuration. Keep schemas on the existing schema
+filesystem boundary. There is no need to deserialize catalog assets, register
+catalog backends individually, or recreate PromptKit inheritance.
+
+Profile preflight does not need dummy prompt directories or synthetic prompts.
+Both construction paths include the same catalog, application prompt/fallback,
+operator, and local-backend layers. This matters for partial operator prompt
+overlays: inspecting a layer without its application base would validate a
+different effective definition. Call `InspectProfile` on the constructed engine
+without preparing a synthetic request. Construction still captures and
+validates the effective prompt definitions; preflight does not resolve
+credential values, prepare request artifacts, or contact providers.
+
+### Keyed Assets Without Prompt Behavior Changes
+
+Every maintained prompt declaration becomes a keyed document of this shape:
+
+```yaml
+prompts:
+  dnd.spells:
+    v1:
+      # Existing definition body, without embedded id/version fields.
+```
+
+Profiles become keyed entries beneath `profiles`. Preserve literal prompt IDs,
+the `v1` version, logical profile IDs, selected response schemas, content paths,
+message order, roles, shared fragment bytes, cache-control metadata, and
+configured structural repair budgets. Do not conflate this migration with
+prompt rewriting, schema changes, or durable artifact version changes.
+
+The application-owned `dnd-extraction` fallback continues to explicitly select
+`openrouter`, `openai/gpt-5.6-luna`, timeout 240, and service tier `flex`, with
+reasoning effort unset. Do not replace that choice with an upstream catalog
+alias or adopt unrelated model defaults. Migrate the maintained operator
+example and relevant inline Go/YAML test fixtures as well as production assets.
+
+Module ownership, ordered asset manifests, scoped mounting, and selected-asset
+hashing remain intact. Check virtual filenames and source-relative
+`content_file` resolution after wrapping definitions; do not move business
+logic into the root `assets` package.
+
+### Presence, Inheritance, And Operator Migration
+
+The adopted policy is native recursive overlay, not a compatibility shim
+for complete-definition replacement. Operators can override only the fields
+they want. Omitted fields retain lower-layer values, and `extends` uses native
+literal sibling-key lookup. Changing a backend or model does not erase
+explicit inherited settings; backend-derived defaults are applied to the
+final backend after inheritance.
+
+Document intentional clearing with `null`, including reasoning/service tier,
+sampling controls, credential lookup, and provider maps where supported.
+Distinguish null from zero/false/blank and from an empty mapping. For example,
+switching an operator's `dnd-extraction` overlay to a local model may also need
+`service_tier: null` to remove the fallback's explicit `flex` setting. Do not
+automatically scrub settings based on model-name heuristics.
+
+Translate `base_profile` to `extends` in maintained examples and explain that
+operators must migrate their external files. Do not retain legacy aliases or
+an alternate parser. Preserve exact PromptKit keys; do not introduce a new
+identifier normalization pass. Update tests that assumed whole replacement
+or selection-time validation deliberately, rather than treating those
+intentional upstream changes as regressions.
+
+Native eager validation applies to final effective values, not independently
+to each superseded contribution. Do not add a source-history audit or raw-layer
+validation that prevents legitimate overrides from repairing lower layers.
+
+### Native Operator Capabilities
+
+Support the capabilities of the unified format directly, without new Notarius
+configuration knobs or model-specific adaptation:
+
+- Custom or multiple backend definitions, including endpoint, credential
+  environment name, provider parameters, concurrency, and queue capacity.
+  Operators may also overlay maintained backend settings, for example changing
+  OpenRouter's admission limit. Backend IDs are configuration keys, not a
+  closed registration list. Notarius's global scheduler still applies.
+- Profile inheritance, partial overrides, and recursive provider-parameter
+  composition. Explicit null suppression and zero/false values follow native
+  field rules. Native sibling inheritance is not limited by a Notarius
+  profiles-only whitelist; prompt/backend mappings follow upstream rules too.
+- File-configured `api_key_required`, with PromptKit's exact credential
+  precedence and runtime checks. In particular, true suppresses a backend's
+  implicit environment source; an explicitly configured profile environment
+  source remains usable. This is an operator choice, not a new mandatory
+  credential policy or a reason to require credentials during preflight.
+- Deployment prompt overlays and declaring-source-relative message files,
+  including imported content. Prompt version selection remains caller-owned;
+  this upgrade does not infer a new module version from file order or add
+  automatic latest-version selection.
+
+The existing `local_backend` object remains a convenient highest-priority
+contribution for that conventional backend. Other backend settings remain
+available through the unified operator source; do not copy every upstream field
+into a parallel Notarius backend schema.
+
+Keep the two maintained top-level configuration examples. Use the complete
+example's existing PromptKit deployment file and small canonical documentation
+snippets to demonstrate native inheritance/partial overrides, custom backend
+configuration, imports, null clearing, and prompt editing without adding a
+large unrelated example suite. Not every capability needs its own runnable
+pipeline.
+
+### Captured Execution And Checkpoint Identity
+
+One engine represents one captured configuration for its lifetime. Editing
+operator definitions or message files requires constructing a new engine;
+there is no watcher or automatic hot reload in this scope. Preserve the normal
+CLI lifecycle without promising that independently constructed preflight and
+execution engines are one transactional filesystem snapshot.
+
+Compute and retain checkpoint identity from the configuration actually
+captured by the execution engine. Do not identify an old captured engine by
+files reread after it was constructed. Identity must account for effective
+profile/backend semantics and the pinned PromptKit/catalog revisions. It must
+also account for operator prompt definitions and their
+captured prompt content, not just `content_file` path strings.
+
+Use public captured inspection and prompt-definition equality values where
+appropriate; do not reach into PromptKit internals. `InspectPrompt.PromptHash`
+includes captured content and is an opaque equality value. Inspection reports
+alone do not embed referenced message-file bodies. Preserve application
+module/schema fingerprints, actual-used profile provenance, and the existing
+exclusion of concurrency-only local settings from semantic checkpoint identity.
+A conservative identity across effective profiles is acceptable; per-selected-
+profile optimization is not a prerequisite for this upgrade.
+
+Raw sources, configuration history, prompt bodies, endpoints, and credential
+values must not be added to ordinary manifests or checkpoint metadata. The
+new inspection API supports both private captured identity and the explicitly
+requested operator reports below. Do not automatically dump reports into run
+output or debug bundles. Hash-only identity is distinct from publishing an
+inspection report, and redaction is not a substitute for covering execution
+semantics.
+
+### Operator-Facing PromptKit Inspection
+
+Provide explicit CLI operations for three complementary views:
+
+- **Effective configuration:** write the captured, ConfigKit-redacted PromptKit
+  configuration, including effective keyed backends, profiles, and prompts.
+  Use `Engine.InspectConfiguration().WriteEffective` rather than reconstructing
+  YAML from Notarius's profile declarations or runtime manifests.
+- **Setting explanation:** explain one canonical JSON Pointer in that captured
+  configuration, including source history, layer overrides, and inheritance.
+  Use the captured inspection's explanation API. Literal IDs containing `/`
+  or `~` use ordinary JSON Pointer escaping, not a dot-path interpretation.
+- **Resolved profile:** inspect one explicit profile ID with `InspectProfile`
+  and present its backend-completed execution settings, including target,
+  effective reasoning/provider controls, credential environment name and
+  requirement, and selected backend identity. Endpoint-only profiles remain
+  identifiable as such. Do not conflate configured profile fields with values
+  derived from backend defaults.
+
+Use the same selected Notarius configuration/overlay, registered application
+assets, operator sources, and local-backend contribution as execution and
+preflight. A report describes the engine captured for that invocation, not a
+live view of a separate running process. Constructing the engine performs
+native definition/content validation, but these commands do not need transcript
+input, execute pipeline stages, prepare requests, resolve credential values,
+admit provider capacity, or contact a model. Required-credential profiles remain
+inspectable when the named environment variable is unset.
+
+Keep existing Notarius `config effective` and `config explain` behavior intact;
+the PromptKit view must be an explicit selection, not a replacement or an
+automatic second document appended to their output. Define the concrete command
+syntax in the implementation plan and maintain it in `docs/cli.md` when it
+lands. Standard output contains the selected report only; ordinary diagnostics
+and failures follow the existing CLI conventions. Unknown paths/profiles and
+invalid pointers must be distinguishable without leaking raw configuration
+through error messages.
+
+Reports are operator-requested application data. Preserve upstream credential
+redaction and Notarius's existing secret-handling boundary; include credential
+variable names, never their values. Configuration explanations can contain
+overridden values and inline prompt/provider content, and effective YAML is not
+a transcript-free or generally sanitized report. Document these properties and
+operator-owned output handling without adding permission enforcement, new
+confirmation gates, automatic report persistence, or blanket content removal.
+
+Effective configuration, backend-completed profile settings, and prepared
+request details are different views. These commands do not render a prompt
+with transcript inputs or return captured message-file bodies merely because
+they appear in the configuration as `content_file` references. Keep complete
+request/response inspection on the existing explicitly requested debug path.
+
+### Existing Execution Policies Remain Unchanged
+
+Preserve prepared execution, the exact latest-response semantic correction
+pair, prompt-prefix caching, direct sessions, reasoning overrides, cancellation,
+the shared scheduler, local/backend admission, observer accounting, error
+classification, and credential redaction. Structural repairs, transient HTTP
+retries, outer producer attempts, and validator execution budgets remain
+separate. The existing one-repair maintained prompt default remains unchanged.
+
+The migration does not change extraction/normalization semantics, warning
+classification, artifact contracts, subprocess receipts, or reusable-state
+eligibility. Construction errors may occur earlier under native eager
+validation; adapt them through the existing safe adapter/CLI error boundary,
+not by exposing arbitrary upstream configuration content.
+
+## Required Work
+
+- Update `go.mod` and `go.sum` to PromptKit v0.12.0 and its selected `/v3`
+  catalogs. Keep ConfigKit v0.5.0 and unrelated dependencies unless module
+  resolution requires a change. Remove obsolete `/v2` requirements after tidy.
+- Replace removed constructor/source/backend APIs in the LLM adapter and
+  shared profile-preflight construction; retain schema and injected-client
+  options. Remove obsolete adapter helpers rather than layering a parallel
+  configuration system beside them.
+- Migrate every registered prompt and fallback profile, the maintained
+  deployment profile, and affected test fixtures to keyed definitions.
+- Adopt the unified source policy, explicit operator imports, presence/null
+  behavior, native operator capabilities, and captured
+  lifetime; replace live-file checkpoint fingerprinting with captured identity.
+- Add explicit effective-configuration, setting-explanation, and resolved-
+  profile CLI inspection using the shared captured-engine construction and
+  public PromptKit inspection APIs. Keep upstream inspection values within
+  the adapter boundary and preserve ordinary Notarius configuration reports.
+- Update behavioral tests at the adapter, CLI preflight, asset registry, and
+  representative assembled-module boundaries. Reuse real ConfigKit/PromptKit
+  loading and offline injected clients or local HTTP fixtures.
+- Update canonical documentation when implementation lands:
+  `docs/config.md` owns selected sources, precedence, profile syntax and
+  migration; `docs/operations.md` owns deployment and reload guidance;
+  `docs/internal/llm.md` owns construction, capture, and checkpoint mechanics;
+  `docs/integrations/pkg-promptkit.md` owns the supported upstream boundary and
+  pinned links; `docs/cli.md` owns the new inspection operations and output/error
+  behavior. Add a short troubleshooting workflow in `docs/operations.md` that
+  links to those references. Revise consumer examples only where affected.
+- Update `docs/oss/attribution.md` for PromptKit and the two `/v3` catalogs,
+  checking their actual notices and exact source commits. PromptKit remains
+  LGPL-3.0-or-later; the catalogs remain MIT at the reviewed revisions. Reuse
+  unchanged standard texts and preserve the project's own license grant.
+
+Native layered overrides change an existing documented operator contract.
+Add a concise Notarius ADR recording the accepted native composition and
+unified-source ownership/compatibility decision rather than duplicating the
+upstream manual. Existing historical ADRs need not be rewritten.
+
+## Verification And Acceptance
+
+Acceptance is behavioral, not an inventory of private helper names:
+
+- All registered D&D and generic prompts construct and prepare with migrated
+  assets, resolving shared/module content in the correct source context.
+  Request identities, message content/order, schemas, and cache controls retain
+  their intended behavior. Do not add exact shared-prefix-length detector tests.
+- Operator overrides, inheritance, explicit zero/null, duplicate definitions
+  within a group, local backend precedence, endpoint-only profiles, and invalid
+  unused final definitions follow the native configuration policy. Cover
+  representative imported combined definitions, custom/backend catalog
+  overlays, partial prompt overlays with their embedded base, and optional
+  versus explicitly required credentials. Credential-free preflight and
+  execution resolve the same source ordering and application definitions.
+- Engine/file mutation tests demonstrate captured settings and content;
+  fingerprints stay tied to that engine and change when a new engine captures
+  different execution-relevant settings or operator prompt content.
+- CLI inspection reports effective values, setting origins, and backend-
+  completed profiles from the same source policy without transcript input,
+  credentials, or provider calls. Cover representative inheritance/null
+  overrides, escaped literal IDs, required-credential inspection with an unset
+  variable, and invalid/unknown selectors. Verify redaction and unchanged
+  ordinary Notarius reports without pinning incidental report formatting.
+- Structural repair, semantic feedback, sessions/reasoning, capacity failure,
+  transient errors, safe diagnostics, and observations retain existing
+  provider-neutral behavior using deterministic boundary tests.
+- Maintained minimal, complete, and inherited development pipelines validate
+  without credentials or provider calls. External legacy profile files receive
+  clear migration guidance, not silent reinterpretation.
+
+Use focused LLM, CLI, and module-integration tests during implementation, then
+`GOWORK=off go test ./...`, `GOWORK=off go vet ./...`, a temporary native build,
+and `GOWORK=off go mod tidy -diff` for this shared-boundary migration. Verify
+selected module versions, attribution links, maintained examples, and stale
+API/format claims. These are migration checks, not new permanent release gates.
+Live provider testing is optional follow-up evidence, not required acceptance.
+
+This work warrants a minor Notarius release because the accepted external
+profile format and override behavior change. Keep Notarius configuration at
+version 5; select the actual release number during separate release preparation.

docs/roadmap/remediation.md

@@ -0,0 +1,108 @@
+# ConfigKit Inheritance Review Remediation
+
+## Review Scope And Overall Result
+
+Reviewed on 2026-10-04, comparing implementation commits `ec99d48` through
+`6450994` with the baseline `9e74df0`, the ConfigKit feature roadmap, and its
+eight-stage implementation plan.
+
+The architecture matches the intended design. ConfigKit v0.5.0 owns source
+composition and native sibling inheritance before decoding. Notarius retains
+its typed defaults, presence-sensitive validation, declaration-relative path
+normalization, detached runtime configuration, catalog-dependent resolution,
+and private redacted inspection boundary. The production configuration adapter
+needed no changes; the work adds the dependency update, integration tests,
+documentation, and the derived development pipeline example.
+
+No production regression or inadvertently strengthened requirement was found.
+In particular, the implementation adds no inheritance whitelist, new schema
+version, custom merging, path-containment rule, template exemption, or release
+gate. The newly reserved `extends` key is the expressly adopted upstream
+compatibility change.
+
+Two follow-ups were identified: a path-test blind spot and an incomplete
+documented command. Completion is recorded under each finding. This document
+records remediation work only; it does not authorize
+unrelated runtime refactoring.
+
+## Finding 1 — Make The Path Fixture Distinguish Declaring Directories
+
+Priority: P2. Category: verification gap.
+
+Status: addressed on 2026-10-04. The fixture now uses distinct parent-, child-,
+and overlay-local paths for the source-base assertions and retains a separate
+`../` reference. `GOWORK=off go test ./internal/core/config` passed. No
+production resolver change was needed.
+
+Evidence: `internal/core/config/inheritance_test.go:338–436`,
+`TestInheritedReferencePathsKeepDeclaringSource`.
+
+The parent, child, and overlay files live in `root/parents`, `root/children`,
+and `root/overlays`. Their resource paths all use `../fixtures/<name>`, and
+the expected paths all point into `root/fixtures`. Resolving one of these
+paths from any of the three directories yields the same result. Thus, choosing
+the child's directory for an inherited step/nested reference, or choosing the
+parent's directory for an overlay replacement, could still pass this test.
+
+`TestInheritedInspectionRetainsOriginsRedactionAndOwnership` does distinguish
+the parent directory for a simple inherited `./shared.txt` reference. It does
+not close the blind spot for the nested, ordered-step, direct-child replacement,
+and overlay cases in the larger path fixture.
+
+Required change:
+
+- Revise the existing path fixture to use directory-distinguishing relative
+  paths for these cases, such as `./shared.txt`, `./step.txt`, and a child-local
+  replacement. Assert inherited paths against the parent's directory, direct
+  replacements against the child's directory, and overlay-supplied paths
+  against the overlay's directory.
+- Retain a separate legitimate `../` example to protect the existing host-path
+  behavior. Avoid making every path converge on one shared sibling directory.
+- Keep this as a focused real-file configuration test. Change production
+  resolution only if the improved assertions expose an actual defect.
+
+Acceptance: choosing a parent, child, or overlay directory incorrectly produces
+a different absolute path and fails the relevant assertion. Nested inheritance,
+inherited ordered-step references, child replacements, and overlay replacements
+still pass with the actual resolver.
+
+Validation: `GOWORK=off go test ./internal/core/config`.
+
+## Finding 2 — Supply Input In The Development Pipeline Command
+
+Priority: P3. Category: documentation accuracy.
+
+Status: addressed on 2026-10-04. The example now supplies the pipeline ID,
+configuration path, and transcript input path, and links to the CLI run
+reference. The flags were checked against that reference, and
+`GOWORK=off go test ./internal/cli` passed without a live model request.
+
+Evidence: `docs/config.md:43–49`, in Maintained Examples.
+
+The new example says to select the development pipeline with
+`notarius run dnd-session-development --config /path/to/dnd-complete.config.yml`.
+The run command requires `--input`. Executing the equivalent command against
+the maintained configuration returns `notarius: run requires --input` with CLI
+exit status 2, before pipeline execution.
+
+Required change: include a transcript input placeholder in the invocation,
+for example `--input /path/to/transcript.json`, and retain the link to the CLI
+reference for the full invocation contract. No CLI behavior change or new test
+framework is needed.
+
+Acceptance: the documented command supplies both required run inputs—the
+pipeline ID and input path—and uses the implemented flag names. Verify against
+the CLI reference and existing parser coverage without a live model request.
+
+## Checks Completed During Review
+
+- `GOWORK=off go test ./...` passed.
+- `GOWORK=off go vet ./...` passed.
+- `GOWORK=off go build` of `./cmd/notarius` to a temporary destination passed.
+- `GOWORK=off go mod tidy -diff` produced no changes.
+- The selected ConfigKit module is v0.5.0; PromptKit remains v0.11.2.
+- The implementation diff passed whitespace checks.
+- The incomplete development invocation was reproduced without provider calls.
+
+These checks describe the review baseline. Subsequent remediation and its
+focused validation are recorded under each finding.

examples/dnd-complete.config.yml

@@ -1,6 +1,10 @@
-version: 4
+version: 5
+configkit:
+  imports:
+    - path: pipelines/dnd-session.yml
 promptkit:
-  profile_file: ./examples/profiles/dnd-extraction.yml
+  profile_file: ./llm-profiles/dnd-extraction.yml
+  transient_retries: 2
 concurrency:
   total_llm: 2
   stage_workers:
@@ -16,145 +20,3 @@ cache:
     directory: ./notarius-cache/checkpoints
 debug:
   directory: ./notarius-debug
-pipelines:
-  dnd-session:
-    llm_profile: dnd-extraction
-    input: seriatim
-    # Stable campaign context is shared by every module that accepts these slots.
-    references:
-      party: ./dnd-party.txt
-      glossary: ./dnd-glossary.txt
-    chunk:
-      module: dnd/scenes
-      retries: 2
-    output:
-      module: json
-      options:
-        include_chunk_map: true
-        evidence_context:
-          enabled: true
-          window_units: 3
-          lanes:
-            - item-occurrences
-            - item-registry
-            - location-registry
-            - location-occurrences
-            - npc-registry
-            - spells
-            - combat-turns
-            - npc-occurrences
-            - enemy-events
-    steps:
-      # Establish session-wide reference artifacts before their consumers.
-      - id: describe-session
-        artifacts:
-          item-registry:
-            extract:
-              module: dnd/item-registry
-              retries: 2
-            merge: appendorder
-            normalize: dnd/item-registry
-          npc-registry:
-            extract:
-              module: dnd/npc-registry
-              retries: 2
-            merge: appendorder
-            normalize:
-              module: dnd/npc-registry
-              retries: 2
-          location-registry:
-            extract:
-              module: dnd/location-registry
-              retries: 2
-            merge: appendorder
-            normalize:
-              module: dnd/location-registry
-              retries: 2
-          scene-descriptions:
-            extract:
-              module: dnd/scene-descriptions
-              retries: 2
-            merge: appendorder
-            normalize: dnd/scene-descriptions
-      - id: extract-events
-        # Accepted registry artifacts and scene-description eligibility artifacts
-        # are supplied in memory to their compatible consumers in this step.
-        references:
-          location_registry:
-            artifact:
-              step: describe-session
-              lane: location-registry
-          npc_registry:
-            artifact:
-              step: describe-session
-              lane: npc-registry
-          scene_descriptions:
-            artifact:
-              step: describe-session
-              lane: scene-descriptions
-          item_registry:
-            artifact:
-              step: describe-session
-              lane: item-registry
-        artifacts:
-          item-occurrences:
-            extract:
-              module: dnd/item-occurrences
-              retries: 2
-            merge: appendorder
-            normalize: dnd/item-occurrences
-          spells:
-            extract:
-              module: dnd/spells
-              retries: 2
-              references:
-                spell_catalog: ./dnd-spell-catalog.json
-            merge: appendorder
-            # Stage-local file references are intentionally bound at each stage.
-            normalize:
-              module: dnd/spells
-              references:
-                spell_catalog: ./dnd-spell-catalog.json
-          combat-turns:
-            extract:
-              module: dnd/combat-turns
-              retries: 2
-            merge: appendorder
-            normalize: dnd/combat-turns
-          npc-occurrences:
-            extract:
-              module: dnd/npc-occurrences
-              retries: 2
-            merge: appendorder
-            normalize: dnd/npc-occurrences
-          location-occurrences:
-            extract:
-              module: dnd/location-occurrences
-              retries: 2
-            merge: appendorder
-            normalize: dnd/location-occurrences
-      - id: track-enemies
-        references:
-          npc_registry:
-            artifact:
-              step: describe-session
-              lane: npc-registry
-          scene_descriptions:
-            artifact:
-              step: describe-session
-              lane: scene-descriptions
-          combat_turns:
-            artifact:
-              step: extract-events
-              lane: combat-turns
-          npc_occurrences:
-            artifact:
-              step: extract-events
-              lane: npc-occurrences
-        artifacts:
-          enemy-events:
-            extract:
-              module: dnd/enemy-events
-              retries: 2
-            merge: appendorder
-            normalize: dnd/enemy-events

examples/dnd-minimal.config.yml

@@ -1,9 +1,12 @@
-version: 4
+version: 5
 pipelines:
   dnd-session:
     llm_profile: dnd-extraction
-    input: seriatim
+    input:
+      module: seriatim
     artifacts:
       spells:
-        extract: dnd/spells
-        normalize: dnd/spells
+        extract:
+          module: dnd/spells
+        normalize:
+          module: dnd/spells

examples/overlays/development.yml

@@ -0,0 +1,8 @@
+# This selects operational settings only; choose a different LLM profile with
+# the pipeline's llm_profile field or the run command's --llm-profile flag.
+concurrency:
+  total_llm: 1
+  stage_workers:
+    extract: 1
+output:
+  directory: ./notarius-output-development

examples/pipelines/dnd-session.yml

@@ -0,0 +1,170 @@
+pipelines:
+  dnd-session:
+    llm_profile: dnd-extraction
+    input:
+      module: seriatim
+    # Stable campaign context is shared by every module that accepts these slots.
+    references:
+      party:
+        path: ../dnd-party.txt
+      glossary:
+        path: ../dnd-glossary.txt
+    chunk:
+      module: dnd/scenes
+      retries: 2
+    output:
+      module: json
+      options:
+        include_chunk_map: true
+        evidence_context:
+          enabled: true
+          window_units: 3
+          lanes:
+            - item-occurrences
+            - item-registry
+            - location-registry
+            - location-occurrences
+            - npc-registry
+            - spells
+            - combat-turns
+            - npc-occurrences
+            - enemy-events
+    steps:
+      # Establish session-wide reference artifacts before their consumers.
+      - id: describe-session
+        artifacts:
+          item-registry:
+            extract:
+              module: dnd/item-registry
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/item-registry
+          npc-registry:
+            extract:
+              module: dnd/npc-registry
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/npc-registry
+              retries: 2
+          location-registry:
+            extract:
+              module: dnd/location-registry
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/location-registry
+              retries: 2
+          scene-descriptions:
+            extract:
+              module: dnd/scene-descriptions
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/scene-descriptions
+      - id: extract-events
+        # Accepted registry artifacts and scene-description eligibility artifacts
+        # are supplied in memory to their compatible consumers in this step.
+        references:
+          location_registry:
+            artifact:
+              step: describe-session
+              lane: location-registry
+          npc_registry:
+            artifact:
+              step: describe-session
+              lane: npc-registry
+          scene_descriptions:
+            artifact:
+              step: describe-session
+              lane: scene-descriptions
+          item_registry:
+            artifact:
+              step: describe-session
+              lane: item-registry
+        artifacts:
+          item-occurrences:
+            extract:
+              module: dnd/item-occurrences
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/item-occurrences
+          spells:
+            extract:
+              module: dnd/spells
+              retries: 2
+              references:
+                spell_catalog:
+                  path: ../dnd-spell-catalog.json
+            merge:
+              module: appendorder
+            # Stage-local file references are intentionally bound at each stage.
+            normalize:
+              module: dnd/spells
+              references:
+                spell_catalog:
+                  path: ../dnd-spell-catalog.json
+          combat-turns:
+            extract:
+              module: dnd/combat-turns
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/combat-turns
+          npc-occurrences:
+            extract:
+              module: dnd/npc-occurrences
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/npc-occurrences
+          location-occurrences:
+            extract:
+              module: dnd/location-occurrences
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/location-occurrences
+      - id: track-enemies
+        references:
+          npc_registry:
+            artifact:
+              step: describe-session
+              lane: npc-registry
+          scene_descriptions:
+            artifact:
+              step: describe-session
+              lane: scene-descriptions
+          combat_turns:
+            artifact:
+              step: extract-events
+              lane: combat-turns
+          npc_occurrences:
+            artifact:
+              step: extract-events
+              lane: npc-occurrences
+        artifacts:
+          enemy-events:
+            extract:
+              module: dnd/enemy-events
+              retries: 2
+            merge:
+              module: appendorder
+            normalize:
+              module: dnd/enemy-events
+
+  # Development variant: disable PromptKit structural repairs while retaining
+  # the inherited steps and configured producer retry budgets.
+  dnd-session-development:
+    extends: dnd-session
+    structured_output_repair_attempts: 0

go.mod

@@ -3,14 +3,16 @@ module gitea.maximumdirect.net/eric/notarius
 go 1.25.5
 
 require (
-	gitea.maximumdirect.net/eric/promptkit v0.9.0
+	gitea.maximumdirect.net/eric/ConfigKit v0.5.0
+	gitea.maximumdirect.net/eric/promptkit v0.11.2
 	github.com/santhosh-tekuri/jsonschema/v6 v6.0.2
-	gopkg.in/yaml.v3 v3.0.1
+	gopkg.in/yaml.v3 v3.0.1 // indirect
 )
 
 require golang.org/x/text v0.40.0
 
 require (
-	gitea.maximumdirect.net/eric/promptkit-backend-openrouter v1.0.0 // indirect
-	gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome v1.0.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
 )

go.sum

@@ -1,13 +1,17 @@
-gitea.maximumdirect.net/eric/promptkit v0.9.0 h1:IpvDRC8L6xRxQ9hpuyKOmMc5b6MeLTKYyx+h1YAjy08=
-gitea.maximumdirect.net/eric/promptkit v0.9.0/go.mod h1:oMJ/WUJImUtwJ5e+6MAGECPYAErAkOaKel0G+3T/b4E=
-gitea.maximumdirect.net/eric/promptkit-backend-openrouter v1.0.0 h1:lc062euk2qseO//D762i3JaFyulDNML3eQQX7DkYTho=
-gitea.maximumdirect.net/eric/promptkit-backend-openrouter v1.0.0/go.mod h1:AIa7kAu2mfrRQgcspe4L+DW51WqgnALQT60lqkEywJI=
-gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome v1.0.0 h1:j9YY7wsTVjzke2kHH4YAzpU0oUpM+x+nXwl1IeS+2eg=
-gitea.maximumdirect.net/eric/promptkit-backend-rakestrawhome v1.0.0/go.mod h1:4RNS+LILDg4JbS4Ts9Lwy1C92wauXJIbeQaalps4Koo=
+gitea.maximumdirect.net/eric/ConfigKit v0.5.0 h1:2KwG10+kApWM3avOoYA+p768xcbHUp7tQ2rqizBNpyg=
+gitea.maximumdirect.net/eric/ConfigKit v0.5.0/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=
 github.com/santhosh-tekuri/jsonschema/v6 v6.0.2/go.mod h1:JXeL+ps8p7/KNMjDQk3TCwPpBy0wYklyWTfbkIzdIFU=
+go.yaml.in/yaml/v4 v4.0.0-rc.6 h1:1h7H1ohdUh93/FyE4YaDa1Zh64K6VVbjF4K6WUxMtH4=
+go.yaml.in/yaml/v4 v4.0.0-rc.6/go.mod h1:aZqd9kCMsGL7AuUv/m/PvWLdg5sjJsZ4oHDEnfPPfY0=
 golang.org/x/text v0.40.0 h1:Ub2Z6/xjgF1WrYQz2nuITOEegKFtiIy+rieRJ5lHZKs=
 golang.org/x/text v0.40.0/go.mod h1:hpnzDAfGV753zIKo+wk3u1bVKCGPbrnF7+7LBF/UHVY=
 gopkg.in/check.v1 v0.0.0-20161208181325-20d25e280405 h1:yhCVgyC4o1eVCa2tZl7eS0r+SDo693bJlVdllGtEeKM=

internal/cli/assembled_spell_pipeline_contract_test.go

@@ -71,28 +71,39 @@ func TestAssembledSpellPipelineNormalizesMergedCasts(t *testing.T) {
 		t.Fatalf("distinct cast = %#v, want separate evidence event", distinct)
 	}
 
-	wantWarningReasons := []string{
+	wantDiagnosticReasons := []string{
 		spellnormalize.ReasonCodeSpellNameCanonicalized,
 		spellnormalize.ReasonCodeSourceReferencesNormalized,
 		spellnormalize.ReasonCodeDuplicateSpellCastCollapsed,
 		"spell_not_near_source",
 	}
-	gotWarningReasons := make([]string, len(output.Warnings))
-	for index, warning := range output.Warnings {
-		gotWarningReasons[index] = warning.ReasonCode
+	gotDiagnosticReasons := make([]string, len(output.Diagnostics.Groups))
+	for index, group := range output.Diagnostics.Groups {
+		gotDiagnosticReasons[index] = group.ReasonCode
 	}
-	if !reflect.DeepEqual(gotWarningReasons, wantWarningReasons) {
-		t.Fatalf("warnings = %#v, want deterministic normalize and validation warnings", output.Warnings)
+	if !reflect.DeepEqual(gotDiagnosticReasons, wantDiagnosticReasons) {
+		t.Fatalf("diagnostics = %#v, want deterministic normalize and validation diagnostics", output.Diagnostics)
 	}
-	if output.Warnings[2].Scope != "spell_casts[0]" || !strings.Contains(output.Warnings[2].Message, "retained input index 0") || !strings.Contains(output.Warnings[2].Message, "removed input indices [1]") {
-		t.Fatalf("duplicate warning = %#v, want retained and removed merged indices", output.Warnings[2])
+	if output.Diagnostics.Groups[2].Samples[0].Scope != "spell_casts[0]" || !strings.Contains(output.Diagnostics.Groups[2].Samples[0].Message, "retained input index 0") || !strings.Contains(output.Diagnostics.Groups[2].Samples[0].Message, "removed input indices [1]") {
+		t.Fatalf("duplicate diagnostic = %#v, want retained and removed merged indices", output.Diagnostics.Groups[2])
 	}
 
 	warningsFile := decodeAssembledOutput[struct {
-		Warnings []contracts.Warning `json:"warnings"`
+		Groups []contracts.DiagnosticGroup `json:"groups"`
 	}](t, output.OutputFiles, "warnings.json")
-	if !reflect.DeepEqual(warningsFile.Warnings, output.Warnings) {
-		t.Fatalf("warnings file = %#v, run warnings = %#v, want manifest output path to preserve warnings", warningsFile.Warnings, output.Warnings)
+	if len(warningsFile.Groups) != 0 {
+		t.Fatalf("warnings file = %#v, want no process warnings for advisory-only diagnostics", warningsFile.Groups)
+	}
+	diagnosticsFile := decodeAssembledOutput[struct {
+		SchemaVersion                string                      `json:"schema_version"`
+		GroupCount                   int                         `json:"group_count"`
+		OccurrenceCount              int                         `json:"occurrence_count"`
+		Truncated                    bool                        `json:"truncated"`
+		UnrepresentedOccurrenceCount int                         `json:"unrepresented_occurrence_count"`
+		Groups                       []contracts.DiagnosticGroup `json:"groups"`
+	}](t, output.OutputFiles, "diagnostics.json")
+	if diagnosticsFile.SchemaVersion != "notarius.diagnostics.v1" || diagnosticsFile.GroupCount != len(output.Diagnostics.Groups) || !reflect.DeepEqual(diagnosticsFile.Groups, output.Diagnostics.Groups) || diagnosticsFile.OccurrenceCount != diagnosticGroupOccurrences(output.Diagnostics.Groups)+output.Diagnostics.UnrepresentedOccurrenceCount || diagnosticsFile.Truncated != output.Diagnostics.Truncated || diagnosticsFile.UnrepresentedOccurrenceCount != output.Diagnostics.UnrepresentedOccurrenceCount {
+		t.Fatalf("diagnostics file = %#v, run diagnostics = %#v", diagnosticsFile, output.Diagnostics)
 	}
 	manifest := decodeAssembledOutput[artifacts.RunManifest](t, output.OutputFiles, "manifest.json")
 	if len(manifest.ArtifactLanes) != 1 || manifest.ArtifactLanes[0].Normalizer != spellnormalize.Key {
@@ -155,14 +166,14 @@ func TestAssembledSpellPipelineHonorsNormalizeValidatorOverride(t *testing.T) {
 	if err != nil || output.Manifest.ValidationStatus != "approved" || len(output.Rejected) != 0 || len(output.NormalizeOutputs) != 1 {
 		t.Fatalf("Run() error = %v output = %#v, want approved override run", err, output)
 	}
-	for _, warning := range output.Warnings {
-		if warning.ReasonCode == "spell_not_near_source" {
-			t.Fatalf("warnings = %#v, want explicit validator override to replace default relatedness chain", output.Warnings)
+	for _, group := range output.Diagnostics.Groups {
+		if group.ReasonCode == "spell_not_near_source" {
+			t.Fatalf("diagnostics = %#v, want explicit validator override to replace default relatedness chain", output.Diagnostics)
 		}
 	}
 }
 
-func TestAssembledSpellPipelinePromotesTerminalUnknownSpellWarning(t *testing.T) {
+func TestAssembledSpellPipelinePromotesTerminalUnknownSpellDiagnostics(t *testing.T) {
 	registries, resolved, _ := assembledSpellPipeline(t, assembledSpellPipelineOptions{unknownSpell: true})
 	resolved.Steps[0].ArtifactLanes[0].NormalizeValidationPolicy.SemanticRejection = pipeline.SemanticRejectionRejectOutput
 	prepared, err := pipeline.Prepare(resolved, registries, pipeline.ModuleDependencies{})
@@ -190,12 +201,12 @@ func TestAssembledSpellPipelinePromotesTerminalUnknownSpellWarning(t *testing.T)
 	if !reflect.DeepEqual(rejectedFile.Rejected, output.Rejected) {
 		t.Fatalf("rejected file = %#v, run rejections = %#v, want durable rejection diagnostic", rejectedFile.Rejected, output.Rejected)
 	}
-	if len(output.Warnings) != 2 || output.Warnings[0].ReasonCode != spellnormalize.ReasonCodeSpellNameUnresolved || output.Warnings[0].Scope != "spell_casts[0]" || output.Warnings[1].ReasonCode != "spell_not_near_source" {
-		t.Fatalf("warnings = %#v, want complete terminal normalize validation warnings", output.Warnings)
+	if len(output.Diagnostics.Groups) != 2 || output.Diagnostics.Groups[0].ReasonCode != spellnormalize.ReasonCodeSpellNameUnresolved || output.Diagnostics.Groups[0].Samples[0].Scope != "spell_casts[0]" || output.Diagnostics.Groups[1].ReasonCode != "spell_not_near_source" {
+		t.Fatalf("diagnostics = %#v, want complete terminal normalize validation diagnostics", output.Diagnostics)
 	}
 }
 
-func TestAssembledSpellPipelinePromotesUnknownSpellWarningWhenOverrideAccepts(t *testing.T) {
+func TestAssembledSpellPipelinePromotesUnknownSpellAdvisoryWhenOverrideAccepts(t *testing.T) {
 	registries, resolved, _ := assembledSpellPipeline(t, assembledSpellPipelineOptions{normalizeValidatorOverride: true, unknownSpell: true})
 	prepared, err := pipeline.Prepare(resolved, registries, pipeline.ModuleDependencies{})
 	if err != nil {
@@ -219,14 +230,20 @@ func TestAssembledSpellPipelinePromotesUnknownSpellWarningWhenOverrideAccepts(t
 	if len(normalized.SpellCasts) != 1 || normalized.SpellCasts[0].Spell != "Mysterious Burst" {
 		t.Fatalf("normalized casts = %#v, want unresolved name preserved", normalized.SpellCasts)
 	}
-	if len(output.Warnings) != 1 || output.Warnings[0].ReasonCode != spellnormalize.ReasonCodeSpellNameUnresolved || output.Warnings[0].Scope != "spell_casts[0]" {
-		t.Fatalf("warnings = %#v, want promoted scoped unresolved-name warning", output.Warnings)
+	if len(output.Diagnostics.Groups) != 1 || output.Diagnostics.Groups[0].ReasonCode != spellnormalize.ReasonCodeSpellNameUnresolved || output.Diagnostics.Groups[0].Samples[0].Scope != "spell_casts[0]" {
+		t.Fatalf("diagnostics = %#v, want promoted scoped unresolved-name diagnostic", output.Diagnostics)
 	}
 	warningsFile := decodeAssembledOutput[struct {
-		Warnings []contracts.Warning `json:"warnings"`
+		Groups []contracts.DiagnosticGroup `json:"groups"`
 	}](t, output.OutputFiles, "warnings.json")
-	if !reflect.DeepEqual(warningsFile.Warnings, output.Warnings) {
-		t.Fatalf("warnings file = %#v, run warnings = %#v, want durable unresolved-name warning", warningsFile.Warnings, output.Warnings)
+	if len(warningsFile.Groups) != 0 {
+		t.Fatalf("warnings file = %#v, want no process warnings for an advisory diagnostic", warningsFile.Groups)
+	}
+	diagnosticsFile := decodeAssembledOutput[struct {
+		Groups []contracts.DiagnosticGroup `json:"groups"`
+	}](t, output.OutputFiles, "diagnostics.json")
+	if !reflect.DeepEqual(diagnosticsFile.Groups, output.Diagnostics.Groups) {
+		t.Fatalf("diagnostics file = %#v, run diagnostics = %#v", diagnosticsFile.Groups, output.Diagnostics)
 	}
 }
 
@@ -429,6 +446,14 @@ func (e *assembledSpellExtractor) chunkIndexesSnapshot() []int {
 	return append([]int(nil), e.chunkIndexes...)
 }
 
+func diagnosticGroupOccurrences(groups []contracts.DiagnosticGroup) int {
+	count := 0
+	for _, group := range groups {
+		count += group.OccurrenceCount
+	}
+	return count
+}
+
 func decodeAssembledOutput[T any](t *testing.T, files []contracts.OutputFile, name string) T {
 	t.Helper()
 	for _, file := range files {

internal/cli/cache_contract_test.go

@@ -23,7 +23,7 @@ func TestRunChunkPlanModePrecedenceAndValidation(t *testing.T) {
 	}{
 		{name: "default", wantStores: 1},
 		{name: "file", fileMode: "bypass"},
-		{name: "environment", envMode: "bypass"},
+		{name: "retired environment has no effect", envMode: "bypass", wantStores: 1},
 		{name: "cli", envMode: "refresh", cliMode: "bypass"},
 	}
 	for _, tt := range tests {
@@ -80,25 +80,14 @@ func TestRunChunkPlanModePrecedenceAndValidation(t *testing.T) {
 	})
 
 	for _, tt := range []struct {
-		name       string
-		fileConfig bool
+		name string
 	}{
-		{name: "invalid environment mode"},
-		{name: "invalid file mode", fileConfig: true},
+		{name: "invalid file mode"},
 	} {
 		t.Run(tt.name, func(t *testing.T) {
 			roots := newStateTestRoots(t)
 			opts := newStateTestHarness().options()
-			if tt.fileConfig {
-				replaceStateTestConfigLine(t, roots.config, "    mode: auto\n", "    mode: invalid\n")
-			} else {
-				opts.LookupEnv = func(name string) (string, bool) {
-					if name == "NOTARIUS_CACHE_CHUNK_PLANS_MODE" {
-						return "invalid", true
-					}
-					return "", false
-				}
-			}
+			replaceStateTestConfigLine(t, roots.config, "    mode: auto\n", "    mode: invalid\n")
 			var stdout, stderr bytes.Buffer
 			code := RunWithOptions([]string{"run", "sample", "--config", roots.config, "--input", roots.input}, &stdout, &stderr, opts)
 			if code != 1 || stdout.Len() != 0 || stderr.Len() == 0 {
@@ -207,16 +196,20 @@ func TestRunAutoReusesPlanWhenRunInputsChange(t *testing.T) {
 	if err != nil {
 		t.Fatal(err)
 	}
-	configText := replaceRequiredOnce(t, string(data), "    chunk: test/chunk\n", `    chunk:
+	configText := replaceRequiredOnce(t, string(data), "    chunk:\n      module: test/chunk\n", `    chunk:
       module: test/chunk
       options:
         strategy: first
 `)
-	configText = replaceRequiredOnce(t, configText, "    output: test/output\n", `      other:
-        extract: test/extract
-        merge: test/merge
-        normalize: test/normalize
-    output: test/output
+	configText = replaceRequiredOnce(t, configText, "    output:\n      module: test/output\n", `      other:
+        extract:
+          module: test/extract
+        merge:
+          module: test/merge
+        normalize:
+          module: test/normalize
+    output:
+      module: test/output
 `)
 	if err := os.WriteFile(roots.config, []byte(configText), 0o600); err != nil {
 		t.Fatal(err)

internal/cli/catalog.go

@@ -157,13 +157,15 @@ func buildProductionLLMClient(ctx context.Context, cfg config.Config, profileID
 		return nil, nil, fmt.Errorf("production asset registry must not be nil")
 	}
 	recorder := llm.NewLLMProfileRecorder()
+	transientRetries := cfg.PromptKit.TransientRetries
 	client, err := llm.NewPromptKitClient(llm.PromptKitClientConfig{
-		ProfileDir:      cfg.PromptKit.ProfileDir,
-		ProfileFile:     cfg.PromptKit.ProfileFile,
-		LocalBackend:    mapPromptKitLocalBackend(cfg.PromptKit.LocalBackend),
-		Assets:          assets,
-		Recorder:        recorder,
-		ReasoningEffort: overrides.ReasoningEffort,
+		ProfileDir:       cfg.PromptKit.ProfileDir,
+		ProfileFile:      cfg.PromptKit.ProfileFile,
+		TransientRetries: &transientRetries,
+		LocalBackend:     mapPromptKitLocalBackend(cfg.PromptKit.LocalBackend),
+		Assets:           assets,
+		Recorder:         recorder,
+		ReasoningEffort:  overrides.ReasoningEffort,
 	})
 	if err != nil {
 		return nil, nil, fmt.Errorf("create PromptKit-backed LLM client: %w", err)

internal/cli/command_contract_test.go

@@ -140,7 +140,7 @@ func TestConfigLoadingFailuresReturnOneWithPathContext(t *testing.T) {
 	stdout.Reset()
 	stderr.Reset()
 	code = RunWithOptions([]string{"config", "validate", "--config", malformed}, &stdout, &stderr, commandContractOptions(t))
-	if code != 1 || !strings.Contains(stderr.String(), malformed) || !strings.Contains(stderr.String(), "parse config file") || stdout.Len() != 0 {
+	if code != 1 || !strings.Contains(stderr.String(), "configuration contains invalid YAML") || stdout.Len() != 0 {
 		t.Fatalf("malformed config: code=%d stdout=%q stderr=%q", code, stdout.String(), stderr.String())
 	}
 }
@@ -185,14 +185,16 @@ func TestConfigValidateResolvesPipelineAndChecksSelection(t *testing.T) {
 }
 
 func TestConfigValidatePipelineDefaultProfileIsOffline(t *testing.T) {
-	configPath := writeCommandConfigContent(t, `version: 4
+	configPath := writeCommandConfigContent(t, `version: 5
 pipelines:
   demo:
     llm_profile: dnd-extraction
-    input: seriatim
+    input:
+      module: seriatim
     artifacts:
       spells:
-        extract: dnd/spells
+        extract:
+          module: dnd/spells
 `)
 	var stdout, stderr bytes.Buffer
 	code := RunWithOptions([]string{"config", "validate", "--config", configPath, "--pipeline", "demo"}, &stdout, &stderr, Options{})
@@ -261,19 +263,21 @@ func commandContractOptionsWithLookup(t *testing.T, lookup func(string) (string,
 
 func writeCommandConfig(t *testing.T, firstID, secondID string) string {
 	t.Helper()
-	content := fmt.Sprintf("version: 4\npipelines:\n  %q:\n    input: seriatim\n  %q:\n    input: seriatim\n", firstID, secondID)
+	content := fmt.Sprintf("version: 5\npipelines:\n  %q:\n    input:\n      module: seriatim\n  %q:\n    input:\n      module: seriatim\n", firstID, secondID)
 	return writeCommandConfigContent(t, content)
 }
 
 func writeResolvableCommandConfig(t *testing.T) string {
 	t.Helper()
-	return writeCommandConfigContent(t, `version: 4
+	return writeCommandConfigContent(t, `version: 5
 pipelines:
   demo:
-    input: seriatim
+    input:
+      module: seriatim
     artifacts:
       spells:
-        extract: dnd/spells
+        extract:
+          module: dnd/spells
 `)
 }
 

internal/cli/configkit_commands.go

@@ -0,0 +1,157 @@
+package cli
+
+import (
+	"context"
+	"encoding/json"
+	"flag"
+	"fmt"
+	"io"
+	"strings"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/notarius/internal/core/config"
+)
+
+func runConfigEffective(args []string, stdout, stderr io.Writer, opts Options) int {
+	fs := flag.NewFlagSet("config effective", flag.ContinueOnError)
+	fs.SetOutput(io.Discard)
+	configPath := fs.String("config", "", "config file path")
+	overlay := fs.String("config-overlay", "", "configuration overlay")
+	if err := fs.Parse(args); err != nil {
+		fmt.Fprintf(stderr, "notarius: %v\n", err)
+		return 2
+	}
+	if fs.NArg() != 0 {
+		fmt.Fprintf(stderr, "notarius: unexpected argument %q\n", fs.Arg(0))
+		return 2
+	}
+	loaded, _, err := loadConfigKit(*configPath, *overlay, nil, opts)
+	if err != nil {
+		writeConfigLoadError(stderr, err)
+		return 1
+	}
+	if err := loaded.WriteEffective(stdout); err != nil {
+		fmt.Fprintf(stderr, "notarius: write effective configuration: %v\n", err)
+		return 1
+	}
+	return 0
+}
+
+func runConfigExplain(args []string, stdout, stderr io.Writer, opts Options) int {
+	fs := flag.NewFlagSet("config explain", flag.ContinueOnError)
+	fs.SetOutput(io.Discard)
+	configPath := fs.String("config", "", "config file path")
+	overlay := fs.String("config-overlay", "", "configuration overlay")
+	if err := fs.Parse(args); err != nil {
+		fmt.Fprintf(stderr, "notarius: %v\n", err)
+		return 2
+	}
+	if fs.NArg() != 1 {
+		fmt.Fprintln(stderr, "notarius: config explain requires exactly one JSON Pointer")
+		return 2
+	}
+	pointer := fs.Arg(0)
+	parsed, err := configkit.ParsePath(pointer)
+	if err != nil || parsed.String() != pointer {
+		fmt.Fprintf(stderr, "notarius: %q is not a canonical JSON Pointer\n", pointer)
+		return 2
+	}
+	loaded, _, err := loadConfigKit(*configPath, *overlay, nil, opts)
+	if err != nil {
+		writeConfigLoadError(stderr, err)
+		return 1
+	}
+	if err := loaded.WriteExplanation(stdout, pointer); err != nil {
+		fmt.Fprintf(stderr, "notarius: write configuration explanation: %v\n", err)
+		return 1
+	}
+	return 0
+}
+
+func runConfigValidate(args []string, stdout, stderr io.Writer, opts Options) int {
+	fs := flag.NewFlagSet("config validate", flag.ContinueOnError)
+	fs.SetOutput(io.Discard)
+	configPath := fs.String("config", "", "config file path")
+	overlay := fs.String("config-overlay", "", "configuration overlay")
+	pipelineID := fs.String("pipeline", "", "pipeline ID")
+	onlyRaw := fs.String("only", "", "comma-separated artifact lanes")
+	if err := fs.Parse(args); err != nil {
+		fmt.Fprintf(stderr, "notarius: %v\n", err)
+		return 2
+	}
+	if fs.NArg() != 0 {
+		fmt.Fprintf(stderr, "notarius: unexpected argument %q\n", fs.Arg(0))
+		return 2
+	}
+	if strings.TrimSpace(*onlyRaw) != "" && strings.TrimSpace(*pipelineID) == "" {
+		fmt.Fprintln(stderr, "notarius: --only requires --pipeline")
+		return 2
+	}
+	only, err := parseOnly(*onlyRaw)
+	if err != nil {
+		fmt.Fprintf(stderr, "notarius: %v\n", err)
+		return 2
+	}
+	loaded, path, err := loadConfigKit(*configPath, *overlay, nil, opts)
+	if err != nil {
+		writeConfigLoadError(stderr, err)
+		return 1
+	}
+	if strings.TrimSpace(*pipelineID) == "" {
+		fmt.Fprintf(stdout, "config %q is valid\n", path)
+		return 0
+	}
+	catalog, err := effectiveCatalog(opts)
+	if err != nil {
+		fmt.Fprintf(stderr, "notarius: %v\n", err)
+		return 1
+	}
+	effective, err := loaded.Config.Resolve(config.ResolveInput{PipelineID: *pipelineID, Only: only, Catalog: catalog})
+	if err != nil {
+		fmt.Fprintf(stderr, "notarius: %v\n", err)
+		return 1
+	}
+	if err := validateExplicitPromptKitProfiles(context.Background(), effective.Config, effectiveLLMProfileIDs(effective.ResolvedPipeline), opts.promptKitAssets); err != nil {
+		fmt.Fprintf(stderr, "notarius: %v\n", err)
+		return 1
+	}
+	fmt.Fprintf(stdout, "config %q is valid for pipeline %q\n", path, strings.TrimSpace(*pipelineID))
+	return 0
+}
+
+func runPipelinesList(args []string, stdout, stderr io.Writer, opts Options) int {
+	fs := flag.NewFlagSet("pipelines list", flag.ContinueOnError)
+	fs.SetOutput(io.Discard)
+	configPath := fs.String("config", "", "config file path")
+	overlay := fs.String("config-overlay", "", "configuration overlay")
+	jsonOutput := fs.Bool("json", false, "write JSON output")
+	if err := fs.Parse(args); err != nil {
+		fmt.Fprintf(stderr, "notarius: %v\n", err)
+		return 2
+	}
+	if fs.NArg() != 0 {
+		fmt.Fprintf(stderr, "notarius: unexpected argument %q\n", fs.Arg(0))
+		return 2
+	}
+	loaded, _, err := loadConfigKit(*configPath, *overlay, nil, opts)
+	if err != nil {
+		writeConfigLoadError(stderr, err)
+		return 1
+	}
+	ids := sortedPipelineIDs(loaded.Config)
+	if *jsonOutput {
+		payload, err := json.Marshal(struct {
+			Pipelines []string `json:"pipelines"`
+		}{Pipelines: ids})
+		if err != nil {
+			fmt.Fprintf(stderr, "notarius: marshal pipeline list: %v\n", err)
+			return 1
+		}
+		fmt.Fprintf(stdout, "%s\n", payload)
+		return 0
+	}
+	for _, id := range ids {
+		fmt.Fprintln(stdout, id)
+	}
+	return 0
+}

internal/cli/configkit_commands_test.go

@@ -0,0 +1,283 @@
+package cli
+
+import (
+	"bytes"
+	"context"
+	"errors"
+	"io"
+	"path/filepath"
+	"strings"
+	"testing"
+
+	"gitea.maximumdirect.net/eric/notarius/internal/core/artifacts"
+	"gitea.maximumdirect.net/eric/notarius/internal/core/config"
+	"gitea.maximumdirect.net/eric/notarius/internal/framework/contracts"
+)
+
+func TestConfigKitReadOnlyCommandsLoadImportsAndOverlays(t *testing.T) {
+	t.Parallel()
+	root := t.TempDir()
+	path := filepath.Join(root, "notarius.yml")
+	writeConfigKitFile(t, filepath.Join(root, "fragment.yml"), "pipelines:\n  imported:\n    input: {module: input}\n")
+	writeConfigKitFile(t, filepath.Join(root, "overlays", "development.yml"), "pipelines:\n  overlaid:\n    input: {module: input}\n")
+	writeConfigKitFile(t, path, "version: 5\nconfigkit:\n  imports:\n    - path: fragment.yml\npipelines:\n  base:\n    input: {module: input}\n")
+	var stdout, stderr bytes.Buffer
+	if code := RunWithOptions([]string{"pipelines", "list", "--config", path, "--config-overlay", "development"}, &stdout, &stderr, commandContractOptions(t)); code != 0 || stdout.String() != "base\nimported\noverlaid\n" {
+		t.Fatalf("list = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+	stdout.Reset()
+	stderr.Reset()
+	if code := RunWithOptions([]string{"config", "validate", "--config", path, "--config-overlay", "development"}, &stdout, &stderr, commandContractOptions(t)); code != 0 || !strings.Contains(stdout.String(), "is valid") {
+		t.Fatalf("validate = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+	for _, selection := range [][]string{nil, {"--config-overlay", ""}, {"--config-overlay", "default"}} {
+		stdout.Reset()
+		stderr.Reset()
+		args := append([]string{"pipelines", "list", "--config", path}, selection...)
+		if code := RunWithOptions(args, &stdout, &stderr, commandContractOptions(t)); code != 0 || stdout.String() != "base\nimported\n" || stderr.Len() != 0 {
+			t.Fatalf("base list %q = %d, %q, %q", selection, code, stdout.String(), stderr.String())
+		}
+	}
+}
+
+func TestPipelineInheritanceCommandsSelectAndInspectDerivedPipelines(t *testing.T) {
+	t.Parallel()
+	path := writeCommandConfigContent(t, `version: 5
+pipelines:
+  " parent ":
+    input:
+      module: seriatim
+    artifacts:
+      spells:
+        extract:
+          module: dnd/spells
+    structured_output_repair_attempts: 2
+  child:
+    extends: " parent "
+    structured_output_repair_attempts: 0
+`)
+	options := commandContractOptions(t)
+
+	var stdout, stderr bytes.Buffer
+	if code := RunWithOptions([]string{"pipelines", "list", "--config", path}, &stdout, &stderr, options); code != 0 || stdout.String() != "child\nparent\n" || stderr.Len() != 0 {
+		t.Fatalf("list = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+
+	stdout.Reset()
+	stderr.Reset()
+	if code := RunWithOptions([]string{"config", "validate", "--config", path, "--pipeline", "child"}, &stdout, &stderr, options); code != 0 || !strings.Contains(stdout.String(), `is valid for pipeline "child"`) || stderr.Len() != 0 {
+		t.Fatalf("validate child = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+
+	stdout.Reset()
+	stderr.Reset()
+	if code := RunWithOptions([]string{"config", "effective", "--config", path}, &stdout, &stderr, options); code != 0 || !strings.Contains(stdout.String(), "module: seriatim") || !strings.Contains(stdout.String(), "structured_output_repair_attempts: 0") || strings.Contains(stdout.String(), "extends:") || stderr.Len() != 0 {
+		t.Fatalf("effective = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+
+	stdout.Reset()
+	stderr.Reset()
+	if code := RunWithOptions([]string{"config", "explain", "--config", path, "/pipelines/child/input/module"}, &stdout, &stderr, options); code != 0 || !strings.Contains(stdout.String(), `path: "/pipelines/child/input/module"`) || !strings.Contains(stdout.String(), "parent") || stderr.Len() != 0 {
+		t.Fatalf("explain inherited input = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+}
+
+func TestPipelineInheritanceLoadFailuresUseRuntimeDiagnostics(t *testing.T) {
+	t.Parallel()
+	for _, test := range []struct {
+		name    string
+		content string
+		args    []string
+		want    string
+	}{
+		{
+			name: "missing parent",
+			content: `version: 5
+pipelines:
+  child:
+    extends: absent
+`,
+			args: []string{"config", "validate", "--pipeline", "child"},
+			want: "inheritance.missing",
+		},
+		{
+			name: "cycle",
+			content: `version: 5
+pipelines:
+  first:
+    extends: second
+  second:
+    extends: first
+`,
+			args: []string{"config", "validate", "--pipeline", "first"},
+			want: "cycle",
+		},
+		{
+			name: "invalid directive type",
+			content: `version: 5
+pipelines:
+  child:
+    extends: 7
+`,
+			args: []string{"config", "validate", "--pipeline", "child"},
+			want: "extends",
+		},
+		{
+			name: "unselected missing parent",
+			content: `version: 5
+pipelines:
+  parent:
+    input:
+      module: seriatim
+  child:
+    extends: parent
+  unrelated:
+    extends: absent
+`,
+			args: []string{"config", "validate", "--pipeline", "child"},
+			want: "inheritance.missing",
+		},
+		{
+			name: "exact sibling mismatch",
+			content: `version: 5
+pipelines:
+  parent:
+    input:
+      module: seriatim
+  child:
+    extends: "parent "
+`,
+			args: []string{"pipelines", "list"},
+			want: "inheritance.missing",
+		},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			t.Parallel()
+			path := writeCommandConfigContent(t, test.content)
+			args := append([]string{}, test.args...)
+			args = append(args, "--config", path)
+			var stdout, stderr bytes.Buffer
+			if code := RunWithOptions(args, &stdout, &stderr, commandContractOptions(t)); code != 1 || stdout.Len() != 0 || stderr.Len() == 0 || !strings.Contains(stderr.String(), test.want) {
+				t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout.String(), stderr.String())
+			}
+		})
+	}
+}
+
+func TestRetiredConfigProfileFlagUsesNormalUnknownFlagBehavior(t *testing.T) {
+	t.Parallel()
+
+	for _, args := range [][]string{
+		{"run", "sample", "--config-profile=development"},
+		{"config", "validate", "--config-profile=development"},
+		{"config", "effective", "--config-profile=development"},
+		{"config", "explain", "--config-profile=development", ""},
+		{"pipelines", "list", "--config-profile=development"},
+	} {
+		t.Run(strings.Join(args[:2], " "), func(t *testing.T) {
+			var stdout, stderr bytes.Buffer
+			if code := RunWithOptions(args, &stdout, &stderr, commandContractOptions(t)); code != 2 || stdout.Len() != 0 || !strings.Contains(stderr.String(), "not defined") {
+				t.Fatalf("args=%q code=%d stdout=%q stderr=%q", args, code, stdout.String(), stderr.String())
+			}
+		})
+	}
+}
+
+func TestConfigKitReadOnlyCommandsRejectVersionFour(t *testing.T) {
+	t.Parallel()
+	path := filepath.Join(t.TempDir(), "notarius.yml")
+	writeConfigKitFile(t, path, "version: 4\n")
+	var stdout, stderr bytes.Buffer
+	if code := runPipelinesList([]string{"--config", path}, &stdout, &stderr, commandContractOptions(t)); code != 1 || !strings.Contains(stderr.String(), "version") {
+		t.Fatalf("list = %d, %q", code, stderr.String())
+	}
+}
+
+func TestConfigurationInspectionCommandsRenderSafeConfigKitViews(t *testing.T) {
+	t.Parallel()
+	root := t.TempDir()
+	path := filepath.Join(root, "notarius.yml")
+	writeConfigKitFile(t, path, `version: 5
+concurrency:
+  total_llm: 4
+pipelines:
+  "0":
+    input: {module: input}
+`)
+	writeConfigKitFile(t, filepath.Join(root, "overlays", "development.yml"), "concurrency:\n  total_llm: 3\n")
+	writeConfigKitFile(t, filepath.Join(root, "overlays", "retired.yml"), "pipelines: null\n")
+
+	providerCalled := false
+	opts := commandContractOptions(t)
+	opts.LLMClientFactory = func(context.Context, config.Config, string, LLMRuntimeOverrides) (contracts.StructuredLLMClient, []artifacts.LLMProfileManifest, error) {
+		providerCalled = true
+		return nil, nil, errors.New("LLM client must not be constructed")
+	}
+
+	var stdout, stderr bytes.Buffer
+	if code := RunWithOptions([]string{"config", "effective", "--config", path, "--config-overlay", "development"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), "total_llm: 3") || stderr.Len() != 0 {
+		t.Fatalf("effective = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+	if providerCalled {
+		t.Fatal("config effective constructed an LLM client")
+	}
+
+	stdout.Reset()
+	stderr.Reset()
+	if code := RunWithOptions([]string{"config", "explain", "--config", path, "--config-overlay", "development", "/concurrency/total_llm"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), `path: "/concurrency/total_llm"`) || stderr.Len() != 0 {
+		t.Fatalf("explain effective = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+
+	stdout.Reset()
+	stderr.Reset()
+	if code := RunWithOptions([]string{"config", "explain", "--config", path, ""}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), `path: ""`) || stderr.Len() != 0 {
+		t.Fatalf("explain root = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+
+	stdout.Reset()
+	stderr.Reset()
+	if code := RunWithOptions([]string{"config", "explain", "--config", path, "--config-overlay", "retired", "/pipelines/0"}, &stdout, &stderr, opts); code != 0 || !strings.Contains(stdout.String(), `path: "/pipelines/0"`) || stderr.Len() != 0 {
+		t.Fatalf("explain removed mapping key = %d, %q, %q", code, stdout.String(), stderr.String())
+	}
+}
+
+func TestConfigExplainRejectsInvalidAndUnknownPointers(t *testing.T) {
+	t.Parallel()
+	path := writeCommandConfig(t, "session", "other")
+	for _, test := range []struct {
+		name     string
+		pointer  string
+		wantCode int
+	}{
+		{name: "missing", wantCode: 2},
+		{name: "malformed escape", pointer: "/pipelines~2session", wantCode: 2},
+		{name: "unknown", pointer: "/unknown", wantCode: 1},
+		{name: "invalid sequence index", pointer: "/pipelines/session/steps/+0", wantCode: 1},
+	} {
+		t.Run(test.name, func(t *testing.T) {
+			var stdout, stderr bytes.Buffer
+			args := []string{"config", "explain", "--config", path}
+			if test.name != "missing" {
+				args = append(args, test.pointer)
+			}
+			if code := RunWithOptions(args, &stdout, &stderr, commandContractOptions(t)); code != test.wantCode || stdout.Len() != 0 || stderr.Len() == 0 {
+				t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout.String(), stderr.String())
+			}
+		})
+	}
+}
+
+func TestConfigInspectionCommandsReportWriterFailures(t *testing.T) {
+	t.Parallel()
+	path := writeCommandConfig(t, "session", "other")
+	var stderr bytes.Buffer
+	if code := RunWithOptions([]string{"config", "effective", "--config", path}, failingInspectionWriter{}, &stderr, commandContractOptions(t)); code != 1 || !strings.Contains(stderr.String(), "write effective configuration") {
+		t.Fatalf("effective writer failure = %d, %q", code, stderr.String())
+	}
+}
+
+type failingInspectionWriter struct{}
+
+func (failingInspectionWriter) Write([]byte) (int, error) {
+	return 0, io.ErrClosedPipe
+}

internal/cli/configkit_load.go

@@ -0,0 +1,49 @@
+package cli
+
+import (
+	"errors"
+	"fmt"
+	"io"
+	"os"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+	"gitea.maximumdirect.net/eric/notarius/internal/core/config"
+)
+
+func loadConfigKit(configPath, overlay string, overrides []configkit.Override, opts Options) (*config.LoadedConfig, string, error) {
+	path, err := discoverConfigPath(configPath, opts)
+	if err != nil {
+		return nil, "", err
+	}
+	workingDirectory, err := os.Getwd()
+	if err != nil {
+		return nil, "", fmt.Errorf("determine invocation directory: %w", err)
+	}
+	loaded, err := config.Load(path, config.LoadOptions{Overlay: overlay, Overrides: overrides, InvocationDirectory: workingDirectory})
+	if err != nil {
+		return nil, "", err
+	}
+	return loaded, path, nil
+}
+
+func writeConfigLoadError(output io.Writer, err error) {
+	var loadError *configkit.LoadError
+	if errors.As(err, &loadError) {
+		if writeErr := configkit.WriteDiagnostics(output, loadError.Diagnostics()); writeErr == nil {
+			// ConfigKit's locations contain source IDs. Keep its renderer and
+			// supply the acquired-source legend so imported/overlay errors can
+			// be traced to a file. Quoting also escapes terminal controls.
+			for _, source := range loadError.Sources() {
+				label := source.Path
+				if label == "" {
+					label = source.Label
+				}
+				if _, err := fmt.Fprintf(output, "source %q: %q\n", source.ID, label); err != nil {
+					return
+				}
+			}
+			return
+		}
+	}
+	fmt.Fprintf(output, "notarius: %v\n", err)
+}

internal/cli/configkit_load_test.go

@@ -0,0 +1,85 @@
+package cli
+
+import (
+	"bytes"
+	"os"
+	"path/filepath"
+	"strconv"
+	"strings"
+	"testing"
+
+	configkit "gitea.maximumdirect.net/eric/ConfigKit"
+)
+
+func TestConfigLoadDiagnosticsIdentifyComposedSources(t *testing.T) {
+	t.Parallel()
+	for _, overlay := range []bool{false, true} {
+		t.Run(strconv.FormatBool(overlay), func(t *testing.T) {
+			root := t.TempDir()
+			main := filepath.Join(root, "config.yml")
+			fragment := filepath.Join(root, "pipeline\n\x1b.yml")
+			args := []string{"config", "validate", "--config", main}
+			if overlay {
+				fragment = filepath.Join(root, "overlays", "development.yml")
+				writeConfigKitFile(t, main, "version: 5\n")
+				args = append(args, "--config-overlay", "development")
+			} else {
+				writeConfigKitFile(t, main, "version: 5\nconfigkit:\n  imports:\n    - path: "+strconv.Quote(filepath.Base(fragment))+"\n")
+			}
+			writeConfigKitFile(t, fragment, "concurrency: {total_llm: invalid-private-value}\n")
+			var stdout, stderr bytes.Buffer
+			if code := RunWithOptions(args, &stdout, &stderr, commandContractOptions(t)); code != 1 {
+				t.Fatalf("status = %d; %s", code, stderr.String())
+			}
+			got := stderr.String()
+			if stdout.Len() != 0 || !strings.Contains(got, "decode.type") ||
+				!strings.Contains(got, "source-2:1:") ||
+				!strings.Contains(got, strconv.Quote(fragment)) ||
+				strings.Contains(got, "invalid-private-value") ||
+				strings.ContainsRune(got, '\x1b') {
+				t.Fatalf("stdout = %q; stderr = %q", stdout.String(), got)
+			}
+		})
+	}
+}
+
+func TestLoadConfigKitUsesDiscoveryOverlayAndOverrides(t *testing.T) {
+	t.Parallel()
+	root := t.TempDir()
+	path := filepath.Join(root, "notarius.yml")
+	writeConfigKitFile(t, path, "version: 5\npipelines:\n  base:\n    input: {module: input}\n")
+	overlays := filepath.Join(root, "overlays")
+	writeConfigKitFile(t, filepath.Join(overlays, "development.yml"), "pipelines:\n  overlaid:\n    input: {module: input}\n")
+	loaded, gotPath, err := loadConfigKit(path, "development", []configkit.Override{{Path: configkit.Keys("output", "directory"), Value: "generated", Flag: "--output"}}, commandContractOptions(t))
+	if err != nil {
+		t.Fatalf("loadConfigKit() error = %v", err)
+	}
+	if gotPath != path || loaded.Config.Pipelines["overlaid"].Input.Module != "input" || loaded.Config.Output.Directory == "generated" {
+		t.Fatalf("loaded = %#v, path=%q", loaded.Config, gotPath)
+	}
+}
+
+func TestWriteConfigLoadErrorUsesSafeDiagnostics(t *testing.T) {
+	t.Parallel()
+	path := filepath.Join(t.TempDir(), "invalid.yml")
+	writeConfigKitFile(t, path, "version: 4\n")
+	_, _, err := loadConfigKit(path, "", nil, commandContractOptions(t))
+	if err == nil {
+		t.Fatal("loadConfigKit() error = nil")
+	}
+	var output bytes.Buffer
+	writeConfigLoadError(&output, err)
+	if !strings.Contains(output.String(), "version") || strings.Contains(output.String(), "notarius: configkit") {
+		t.Fatalf("diagnostics = %q", output.String())
+	}
+}
+
+func writeConfigKitFile(t *testing.T, path, contents string) {
+	t.Helper()
+	if err := os.MkdirAll(filepath.Dir(path), 0o700); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(path, []byte(contents), 0o600); err != nil {
+		t.Fatal(err)
+	}
+}

internal/cli/dnd_enemy_events_contract_test.go

@@ -264,13 +264,29 @@ func completeExampleConfigWithTemporaryCache(t *testing.T) string {
 	updated := strings.Replace(string(content), "directory: ./notarius-cache/chunk-plans", fmt.Sprintf("directory: %q", filepath.Join(cacheRoot, "chunk-plans")), 1)
 	updated = strings.Replace(updated, "directory: ./notarius-cache/checkpoints", fmt.Sprintf("directory: %q", filepath.Join(cacheRoot, "checkpoints")), 1)
 	for relative, absolute := range map[string]string{
-		"./dnd-party.txt":          repositoryPath("examples", "dnd-party.txt"),
-		"./dnd-glossary.txt":       repositoryPath("examples", "dnd-glossary.txt"),
-		"./dnd-spell-catalog.json": repositoryPath("examples", "dnd-spell-catalog.json"),
+		"./llm-profiles/dnd-extraction.yml": repositoryPath("examples", "llm-profiles", "dnd-extraction.yml"),
 	} {
 		updated = strings.ReplaceAll(updated, relative, fmt.Sprintf("%q", absolute))
 	}
-	path := filepath.Join(t.TempDir(), "dnd-complete.config.yml")
+	root := t.TempDir()
+	fragment, err := os.ReadFile(repositoryPath("examples", "pipelines", "dnd-session.yml"))
+	if err != nil {
+		t.Fatal(err)
+	}
+	for relative, absolute := range map[string]string{
+		"../dnd-party.txt":          repositoryPath("examples", "dnd-party.txt"),
+		"../dnd-glossary.txt":       repositoryPath("examples", "dnd-glossary.txt"),
+		"../dnd-spell-catalog.json": repositoryPath("examples", "dnd-spell-catalog.json"),
+	} {
+		fragment = []byte(strings.ReplaceAll(string(fragment), relative, fmt.Sprintf("%q", absolute)))
+	}
+	if err := os.MkdirAll(filepath.Join(root, "pipelines"), 0o700); err != nil {
+		t.Fatal(err)
+	}
+	if err := os.WriteFile(filepath.Join(root, "pipelines", "dnd-session.yml"), fragment, 0o600); err != nil {
+		t.Fatal(err)
+	}
+	path := filepath.Join(root, "dnd-complete.config.yml")
 	if err := os.WriteFile(path, []byte(updated), 0o600); err != nil {
 		t.Fatal(err)
 	}

internal/cli/dnd_scene_descriptions_contract_test.go

@@ -91,8 +91,8 @@ func TestProductionSceneDescriptionWorkflow(t *testing.T) {
 	if !reflect.DeepEqual(durable, want) {
 		t.Fatalf("durable output payload = %#v, want %#v", durable, want)
 	}
-	if len(output.Warnings) != 0 {
-		t.Fatalf("warnings = %#v, want grounded descriptions without warnings", output.Warnings)
+	if len(output.Diagnostics.Groups) != 0 {
+		t.Fatalf("diagnostics = %#v, want grounded descriptions without diagnostics", output.Diagnostics)
 	}
 }
 

internal/cli/example_contract_test.go

@@ -3,6 +3,7 @@ package cli
 import (
 	"context"
 	"encoding/json"
+	"fmt"
 	"os"
 	"path/filepath"
 	"sort"
@@ -25,6 +26,7 @@ import (
 
 func TestMaintainedExamplesLoadResolveAndList(t *testing.T) {
 	components := productionTestComponents(t)
+	completePipelines := make(map[string]pipeline.ResolvedPipeline)
 	for _, example := range maintainedExampleFiles(t) {
 		t.Run(example.name, func(t *testing.T) {
 			cfg := loadMaintainedExample(t, example.path)
@@ -58,9 +60,45 @@ func TestMaintainedExamplesLoadResolveAndList(t *testing.T) {
 					t.Fatalf("materialize maintained example references for %q: %v", pipelineID, err)
 				}
 				if example.name == "complete" {
+					if pipelineID == "dnd-session-development" {
+						parent, found := completePipelines["dnd-session"]
+						if !found {
+							t.Fatal("complete parent pipeline was not resolved before its development variant")
+						}
+						if strings.Join(exampleStepLaneIDs(materialized), "|") != strings.Join(exampleStepLaneIDs(parent), "|") {
+							t.Fatalf("development variant steps and lanes = %v, want parent composition %v", exampleStepLaneIDs(materialized), exampleStepLaneIDs(parent))
+						}
+						if got, want := strings.Join(generatedReferenceBindingDescriptions(materialized), "|"), strings.Join(generatedReferenceBindingDescriptions(parent), "|"); got != want {
+							t.Fatalf("development generated reference bindings = %q, want parent bindings %q", got, want)
+						}
+						eligibleBindings := 0
+						for _, step := range materialized.Steps {
+							for _, lane := range step.ArtifactLanes {
+								for _, binding := range []struct {
+									module         pipeline.ModuleBinding
+									executionClass contracts.ExecutionClass
+								}{
+									{module: lane.Extract, executionClass: lane.ExtractExecutionClass},
+									{module: lane.Normalize, executionClass: lane.NormalizeExecutionClass},
+								} {
+									if binding.executionClass != "llm_backed" {
+										continue
+									}
+									eligibleBindings++
+									if got := binding.module.StructuredOutputRepairAttempts; got == nil || *got != 0 {
+										t.Fatalf("development %s repair attempts = %v, want explicit zero", binding.module.Module, got)
+									}
+								}
+							}
+						}
+						if eligibleBindings == 0 {
+							t.Fatal("development variant had no eligible LLM bindings for repair policy")
+						}
+					}
 					if got := exampleStepLaneIDs(materialized); strings.Join(got, "|") != "describe-session:item-registry,location-registry,npc-registry,scene-descriptions|extract-events:combat-turns,item-occurrences,location-occurrences,npc-occurrences,spells|track-enemies:enemy-events" {
 						t.Fatalf("complete example steps and lanes = %v, want the documented D&D extractor composition", got)
 					}
+					completePipelines[pipelineID] = materialized
 					locationLane := referenceContractLane(t, materialized, "location-registry")
 					if locationLane.ArtifactKind != dnd.LocationRegistryKind || locationLane.Extract.Module != locationextract.Key || locationLane.Extract.Retries != 2 || locationLane.Merge.Module != pipeline.DefaultMergeModule || locationLane.Normalize.Module != locationnormalize.Key || locationLane.Normalize.Retries != 2 {
 						t.Fatalf("location lane = %#v, want typed registry composition", locationLane)
@@ -136,19 +174,26 @@ func TestMaintainedConfigurationExampleSet(t *testing.T) {
 		t.Fatalf("maintained configuration examples = %q, want only the minimal and complete D&D examples", got)
 	}
 
-	profileEntries, err := os.ReadDir(repositoryPath("examples", "profiles"))
+	overlayEntries, err := os.ReadDir(repositoryPath("examples", "overlays"))
 	if err != nil {
 		t.Fatal(err)
 	}
 	names = names[:0]
-	for _, entry := range profileEntries {
+	for _, entry := range overlayEntries {
 		if !entry.IsDir() && strings.HasSuffix(entry.Name(), ".yml") {
 			names = append(names, entry.Name())
 		}
 	}
 	sort.Strings(names)
-	if got := strings.Join(names, ","); got != "dnd-extraction.yml" {
-		t.Fatalf("maintained operator profiles = %q, want dnd-extraction.yml", got)
+	if got := strings.Join(names, ","); got != "development.yml" {
+		t.Fatalf("maintained configuration overlays = %q, want development.yml", got)
+	}
+	llmProfiles, err := os.ReadDir(repositoryPath("examples", "llm-profiles"))
+	if err != nil {
+		t.Fatal(err)
+	}
+	if len(llmProfiles) != 1 || llmProfiles[0].Name() != "dnd-extraction.yml" {
+		t.Fatalf("maintained LLM profiles = %#v, want dnd-extraction.yml", llmProfiles)
 	}
 }
 
@@ -157,12 +202,16 @@ func TestMaintainedExamplesValidateEffectiveProfilesOffline(t *testing.T) {
 	t.Setenv("OPENROUTER_API_KEY", "")
 	for _, example := range maintainedExampleFiles(t) {
 		t.Run(example.name, func(t *testing.T) {
-			var stdout, stderr strings.Builder
-			code := RunWithOptions([]string{
-				"config", "validate", "--config", example.path, "--pipeline", "dnd-session",
-			}, &stdout, &stderr, Options{})
-			if code != 0 || stderr.Len() != 0 || !strings.Contains(stdout.String(), `valid for pipeline "dnd-session"`) {
-				t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout.String(), stderr.String())
+			for _, pipelineID := range example.pipelineIDs {
+				t.Run(pipelineID, func(t *testing.T) {
+					var stdout, stderr strings.Builder
+					code := RunWithOptions([]string{
+						"config", "validate", "--config", example.path, "--pipeline", pipelineID,
+					}, &stdout, &stderr, Options{})
+					if code != 0 || stderr.Len() != 0 || !strings.Contains(stdout.String(), `valid for pipeline "`+pipelineID+`"`) {
+						t.Fatalf("code=%d stdout=%q stderr=%q", code, stdout.String(), stderr.String())
+					}
+				})
 			}
 		})
 	}
@@ -181,6 +230,31 @@ func exampleStepLaneIDs(resolved pipeline.ResolvedPipeline) []string {
 	return result
 }
 
+func generatedReferenceBindingDescriptions(resolved pipeline.ResolvedPipeline) []string {
+	var descriptions []string
+	for _, step := range resolved.Steps {
+		for _, lane := range step.ArtifactLanes {
+			for _, target := range []struct {
+				name   string
+				target pipeline.ResolvedReferenceTarget
+			}{
+				{name: "extract", target: lane.ExtractReferences},
+				{name: "merge", target: lane.MergeReferences},
+				{name: "normalize", target: lane.NormalizeReferences},
+			} {
+				for _, binding := range target.target.Bindings {
+					if binding.Artifact == nil {
+						continue
+					}
+					descriptions = append(descriptions, fmt.Sprintf("%s/%s/%s/%s=%s/%s", step.ID, lane.ID, target.name, binding.SlotName, binding.Artifact.Step, binding.Artifact.Lane))
+				}
+			}
+		}
+	}
+	sort.Strings(descriptions)
+	return descriptions
+}
+
 func TestMaintainedMinimalInvocationProducesJSONBundle(t *testing.T) {
 	outputRoot := filepath.Join(t.TempDir(), "output")
 	fake := &productionFakeLLMClient{}
@@ -239,10 +313,10 @@ func TestMaintainedMinimalInvocationProducesJSONBundle(t *testing.T) {
 		t.Fatalf("rejected = %#v, want empty rejection list", rejected.Rejected)
 	}
 	warnings := readProductionJSON[struct {
-		Warnings []json.RawMessage `json:"warnings"`
+		Groups []json.RawMessage `json:"groups"`
 	}](t, filepath.Join(runRoot, "warnings.json"))
-	if len(warnings.Warnings) != 0 {
-		t.Fatalf("warnings = %#v, want empty warning list", warnings.Warnings)
+	if len(warnings.Groups) != 0 {
+		t.Fatalf("warnings = %#v, want empty warning list", warnings.Groups)
 	}
 }
 

internal/cli/npc_registry_contract_test.go

@@ -23,7 +23,7 @@ func TestOversizedNPCRegistryFailsBeforeRuntimeAndCheckpointConstruction(t *test
 		t.Fatal(err)
 	}
 	checkpointRoot := filepath.Join(t.TempDir(), "checkpoints")
-	content := fmt.Sprintf(`version: 4
+	content := fmt.Sprintf(`version: 5
 cache:
   chunk_plans:
     mode: bypass
@@ -32,14 +32,17 @@ cache:
     directory: %q
 pipelines:
   dnd-session:
-    input: seriatim
+    input:
+      module: seriatim
     artifacts:
       spells:
         extract:
           module: dnd/spells
           references:
-            npc_registry: %q
-        normalize: dnd/spells
+            npc_registry:
+              path: %q
+        normalize:
+          module: dnd/spells
 `, checkpointRoot, npcPath)
 	configPath := filepath.Join(t.TempDir(), "config.yml")
 	if err := os.WriteFile(configPath, []byte(content), 0o600); err != nil {

internal/cli/production_contract_test.go

@@ -19,8 +19,6 @@ import (
 	"testing/fstest"
 	"time"
 
-	"gopkg.in/yaml.v3"
-
 	"gitea.maximumdirect.net/eric/notarius/internal/core/artifacts"
 	"gitea.maximumdirect.net/eric/notarius/internal/core/config"
 	"gitea.maximumdirect.net/eric/notarius/internal/framework/chunkmap"
@@ -333,61 +331,8 @@ func TestProductionPromptAssetsPrepareWithoutProviderCredentials(t *testing.T) {
 	if err != nil {
 		t.Fatalf("production prompt engine: %v", err)
 	}
-	promptFS, err := components.assets.PromptFS()
-	if err != nil {
-		t.Fatalf("production prompt assets: %v", err)
-	}
-	type manifest struct {
-		ID      string `yaml:"id"`
-		Version string `yaml:"version"`
-		Inputs  []struct {
-			Name string `yaml:"name"`
-		} `yaml:"inputs"`
-		Messages []struct {
-			Role string `yaml:"role"`
-		} `yaml:"messages"`
-	}
-	preparedPrompts := 0
-	if err := fs.WalkDir(promptFS, ".", func(path string, entry fs.DirEntry, walkErr error) error {
-		if walkErr != nil {
-			return walkErr
-		}
-		if entry.IsDir() || filepath.Base(path) != "prompt.yaml" {
-			return nil
-		}
-		data, err := fs.ReadFile(promptFS, path)
-		if err != nil {
-			return err
-		}
-		var prompt manifest
-		if err := yaml.Unmarshal(data, &prompt); err != nil {
-			return err
-		}
-		for _, message := range prompt.Messages {
-			if message.Role != promptkit.RoleSystem && message.Role != promptkit.RoleUser {
-				return fmt.Errorf("production prompt %q uses role %q, want system or user", prompt.ID, message.Role)
-			}
-		}
-		inputs := make(map[string]promptkit.ArtifactRef, len(prompt.Inputs))
-		for _, input := range prompt.Inputs {
-			inputs[input.Name] = promptkit.Inline(`{}`)
-		}
-		prepared, err := engine.Prepare(context.Background(), promptkit.RunRequest{
-			PromptID: prompt.ID, PromptVersion: prompt.Version, ProfileID: "assembled-prompt-test", Inputs: inputs,
-		})
-		if err != nil {
-			return fmt.Errorf("prepare production prompt %q: %w", prompt.ID, err)
-		}
-		if prepared.OutputContract.RepairAttempts != 1 {
-			return fmt.Errorf("prompt %q repair attempts = %d, want 1", prompt.ID, prepared.OutputContract.RepairAttempts)
-		}
-		preparedPrompts++
-		return nil
-	}); err != nil {
-		t.Fatal(err)
-	}
-	if preparedPrompts == 0 {
-		t.Fatal("prepared no production prompts")
+	if engine == nil {
+		t.Fatal("production PromptKit engine is nil")
 	}
 }
 
@@ -612,11 +557,16 @@ func TestNormalizeOptionsSharesProductionProfileAssetsWithDefaultRuntime(t *test
 func TestProductionLLMClientFactoryUsesConfiguredLocalBackend(t *testing.T) {
 	var providerCalls atomic.Int32
 	server := httptest.NewServer(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
-		providerCalls.Add(1)
+		call := providerCalls.Add(1)
 		if r.URL.Path != "/v1/chat/completions" {
 			t.Errorf("provider path = %q, want /v1/chat/completions", r.URL.Path)
 		}
 		w.Header().Set("Content-Type", "application/json")
+		if call == 1 {
+			w.WriteHeader(http.StatusServiceUnavailable)
+			_, _ = w.Write([]byte(`{"error":{"message":"transient"}}`))
+			return
+		}
 		_, _ = w.Write([]byte(`{
 			"choices": [{"message": {"role": "assistant", "content": "{\"ok\":true}"}}],
 			"usage": {"prompt_tokens": 3, "completion_tokens": 4, "total_tokens": 7}
@@ -651,6 +601,7 @@ output:
 
 	cfg := config.Default()
 	cfg.PromptKit.ProfileFile = profilePath
+	cfg.PromptKit.TransientRetries = 1
 	cfg.PromptKit.LocalBackend = &config.PromptKitLocalBackendConfig{
 		Endpoint:         server.URL + "/v1",
 		ConcurrencyLimit: 2,
@@ -679,8 +630,8 @@ output:
 	if err != nil {
 		t.Fatalf("CompleteStructured() error = %v, want nil", err)
 	}
-	if providerCalls.Load() != 1 {
-		t.Fatalf("provider calls = %d, want 1", providerCalls.Load())
+	if providerCalls.Load() != 2 {
+		t.Fatalf("provider calls = %d, want 2", providerCalls.Load())
 	}
 	provider, ok := client.(contracts.LLMProfileManifestProvider)
 	if !ok {
@@ -737,13 +688,13 @@ func TestProductionConfigValidationCoversModuleAndVariantFailures(t *testing.T)
 	}{
 		{
 			name:      "unknown module",
-			content:   replaceRequiredOnce(t, base, "    input: seriatim\n", "    input: missing/input\n"),
+			content:   replaceRequiredOnce(t, base, "    input:\n      module: seriatim\n", "    input:\n      module: missing/input\n"),
 			options:   productionCLIOptions(t),
 			fragments: []string{"pipeline \"dnd-session\"", "input", "missing/input"},
 		},
 		{
 			name:      "unknown validator",
-			content:   replaceRequiredOnce(t, base, "        extract: dnd/spells\n", "        extract:\n          module: dnd/spells\n          validators:\n            - module: missing/validator\n"),
+			content:   replaceRequiredOnce(t, base, "        extract:\n          module: dnd/spells\n", "        extract:\n          module: dnd/spells\n          validators:\n            - module: missing/validator\n"),
 			options:   productionCLIOptions(t),
 			fragments: []string{"validator", "missing/validator"},
 		},
@@ -755,7 +706,7 @@ func TestProductionConfigValidationCoversModuleAndVariantFailures(t *testing.T)
 		},
 		{
 			name:      "deterministic validator with profile",
-			content:   replaceRequiredOnce(t, base, "        extract: dnd/spells\n", "        extract:\n          module: dnd/spells\n          validators:\n            - module: generic/valid_json\n              llm_profile: forbidden-profile\n"),
+			content:   replaceRequiredOnce(t, base, "        extract:\n          module: dnd/spells\n", "        extract:\n          module: dnd/spells\n          validators:\n            - module: generic/valid_json\n              llm_profile: forbidden-profile\n"),
 			options:   productionCLIOptions(t),
 			fragments: []string{"deterministic validator", "llm_profile"},
 		},
@@ -779,7 +730,7 @@ func TestProductionConfigValidationCoversModuleAndVariantFailures(t *testing.T)
 
 func TestProductionNormalizeValidatorOverrideRemainsAuthoritative(t *testing.T) {
 	base := string(readRepositoryFile(t, "examples", "dnd-minimal.config.yml"))
-	content := replaceRequiredOnce(t, base, "        normalize: dnd/spells\n", "        normalize:\n          module: dnd/spells\n          validators:\n            - module: generic/always_accept\n            - module: generic/valid_json\n")
+	content := replaceRequiredOnce(t, base, "        normalize:\n          module: dnd/spells\n", "        normalize:\n          module: dnd/spells\n          validators:\n            - module: generic/always_accept\n            - module: generic/valid_json\n")
 	path := writeProductionContractConfig(t, content)
 	components := productionTestComponents(t)
 	effective, err := loadMaintainedExample(t, path).Resolve(resolveInputForMaintainedExample(components, "dnd-session"))
@@ -852,10 +803,10 @@ func TestProductionSceneRunRecordsAnnotationFreeChunkPlanAndProvenance(t *testin
 		t.Fatalf("chunk map range annotations = %#v, want none", chunkMap.Chunks[0].Annotations)
 	}
 	warnings := readProductionJSON[struct {
-		Warnings []contracts.Warning `json:"warnings"`
+		Groups []contracts.DiagnosticGroup `json:"groups"`
 	}](t, filepath.Join(outputRoot, productionRunID, "warnings.json"))
-	if len(warnings.Warnings) != 0 {
-		t.Fatalf("warnings = %#v, want none", warnings.Warnings)
+	if len(warnings.Groups) != 0 {
+		t.Fatalf("warnings = %#v, want none", warnings.Groups)
 	}
 	if len(fake.requestsFor(scenes.PromptID)) != 1 || len(fake.requestsFor(spells.PromptID)) != 1 || len(fake.requestsFor(itemoccurrenceextract.PromptID)) != 1 {
 		t.Fatalf("fake prompt requests = %#v, want one scene, spell, and item-occurrence request", fake.requestPrompts())
@@ -873,13 +824,13 @@ func maintainedExampleFiles(t *testing.T) []maintainedExample {
 	t.Helper()
 	return []maintainedExample{
 		{name: "minimal", path: repositoryPath("examples", "dnd-minimal.config.yml"), transcriptPath: repositoryPath("examples", "seriatim-minimal-transcript.json"), pipelineIDs: []string{"dnd-session"}},
-		{name: "complete", path: repositoryPath("examples", "dnd-complete.config.yml"), transcriptPath: repositoryPath("examples", "dnd-complete-transcript.json"), pipelineIDs: []string{"dnd-session"}},
+		{name: "complete", path: repositoryPath("examples", "dnd-complete.config.yml"), transcriptPath: repositoryPath("examples", "dnd-complete-transcript.json"), pipelineIDs: []string{"dnd-session", "dnd-session-development"}},
 	}
 }
 
 func productionSpellCatalogContractConfig(t *testing.T) string {
 	t.Helper()
-	return fmt.Sprintf(`version: 4
+	return fmt.Sprintf(`version: 5
 cache:
   chunk_plans:
     mode: bypass
@@ -888,21 +839,26 @@ cache:
     directory: ""
 pipelines:
   dnd-session:
-    input: seriatim
+    input:
+      module: seriatim
     references:
-      party: %q
-      glossary: %q
+      party:
+        path: %q
+      glossary:
+        path: %q
     artifacts:
       spells:
         extract:
           module: dnd/spells
           retries: 2
           references:
-            spell_catalog: %q
+            spell_catalog:
+              path: %q
         normalize:
           module: dnd/spells
           references:
-            spell_catalog: %q
+            spell_catalog:
+              path: %q
 `, repositoryPath("examples", "dnd-party.txt"), repositoryPath("examples", "dnd-glossary.txt"), repositoryPath("examples", "dnd-spell-catalog.json"), repositoryPath("examples", "dnd-spell-catalog.json"))
 }
 
@@ -913,14 +869,11 @@ func writeProductionSpellCatalogContractConfig(t *testing.T) string {
 
 func loadMaintainedExample(t *testing.T, path string) config.Config {
 	t.Helper()
-	fileConfig, err := config.LoadFileConfig(path)
+	loaded, err := config.Load(path, config.LoadOptions{})
 	if err != nil {
 		t.Fatalf("load maintained config %q: %v", path, err)
 	}
-	cfg := config.Default()
-	if err := cfg.ApplyFileConfig(fileConfig); err != nil {
-		t.Fatalf("apply maintained config %q: %v", path, err)
-	}
+	cfg := loaded.RuntimeConfig()
 	if err := cfg.Validate(); err != nil {
 		t.Fatalf("validate maintained config %q: %v", path, err)
 	}
@@ -977,7 +930,7 @@ func productionRunOptions(t *testing.T, fake *productionFakeLLMClient) Options {
 }
 
 func productionRunConfig(outputRoot, chunkModule string) string {
-	return fmt.Sprintf(`version: 4
+	return fmt.Sprintf(`version: 5
 output:
   directory: %q
 cache:
@@ -988,8 +941,10 @@ debug:
   directory: %q
 pipelines:
   dnd-session:
-    input: seriatim
-    chunk: %s
+    input:
+      module: seriatim
+    chunk:
+      module: %s
     output:
       module: json
       options:
@@ -998,8 +953,10 @@ pipelines:
       - id: identify-items
         artifacts:
           item-registry:
-            extract: dnd/item-registry
-            normalize: dnd/item-registry
+            extract:
+              module: dnd/item-registry
+            normalize:
+              module: dnd/item-registry
       - id: extract-occurrences
         references:
           item_registry:
@@ -1008,9 +965,11 @@ pipelines:
               lane: item-registry
         artifacts:
           spells:
-            extract: dnd/spells
+            extract:
+              module: dnd/spells
           item-occurrences:
-            extract: dnd/item-occurrences
+            extract:
+              module: dnd/item-occurrences
 `, outputRoot, filepath.Join(filepath.Dir(outputRoot), "debug"), chunkModule)
 }
 

internal/cli/recompute_execution_contract_test.go

@@ -194,7 +194,7 @@ func (recomputeTestOutput) Encode(_ context.Context, req contracts.OutputRequest
 func newRecomputeTestRoots(t *testing.T) stateTestRoots {
 	t.Helper()
 	roots := newStateTestRoots(t)
-	config := fmt.Sprintf(`version: 4
+	config := fmt.Sprintf(`version: 5
 output:
   directory: %q
 cache:
@@ -208,19 +208,27 @@ debug:
   directory: %q
 pipelines:
   sample:
-    input: test/input
-    chunk: test/chunk
+    input:
+      module: test/input
+    chunk:
+      module: test/chunk
     steps:
       - id: first
         artifacts:
           producer:
-            extract: test/extract/producer
-            merge: test/merge
-            normalize: test/normalize
+            extract:
+              module: test/extract/producer
+            merge:
+              module: test/merge
+            normalize:
+              module: test/normalize
           unrelated:
-            extract: test/extract/unrelated
-            merge: test/merge
-            normalize: test/normalize
+            extract:
+              module: test/extract/unrelated
+            merge:
+              module: test/merge
+            normalize:
+              module: test/normalize
       - id: second
         references:
           upstream:
@@ -229,9 +237,12 @@ pipelines:
               lane: producer
         artifacts:
           middle:
-            extract: test/extract/middle
-            merge: test/merge
-            normalize: test/normalize
+            extract:
+              module: test/extract/middle
+            merge:
+              module: test/merge
+            normalize:
+              module: test/normalize
       - id: third
         references:
           upstream:
@@ -240,10 +251,14 @@ pipelines:
               lane: middle
         artifacts:
           dependent:
-            extract: test/extract/dependent
-            merge: test/merge
-            normalize: test/normalize
-    output: test/recompute-output
+            extract:
+              module: test/extract/dependent
+            merge:
+              module: test/merge
+            normalize:
+              module: test/normalize
+    output:
+      module: test/recompute-output
 `, roots.output, roots.plans, roots.checkpoints, roots.debug)
 	if err := os.WriteFile(roots.config, []byte(config), 0o600); err != nil {
 		t.Fatal(err)

internal/cli/reference_contract_test.go

@@ -4,6 +4,7 @@ import (
 	"bytes"
 	"os"
 	"path/filepath"
+	"slices"
 	"strings"
 	"testing"
 
@@ -14,20 +15,16 @@ import (
 
 func TestReferenceSelectorsParseAndApplyAllDocumentedForms(t *testing.T) {
 	tests := []struct {
-		name      string
-		selector  string
-		only      []string
-		wantStage pipeline.ModuleStage
-		wantLane  string
-		wantSlot  string
+		name     string
+		selector string
+		want     []string
 	}{
-		{name: "flat", selector: "alpha-slot", wantStage: pipeline.StageExtract, wantLane: "alpha", wantSlot: "alpha-slot"},
-		{name: "chunk", selector: "chunk.chunk-slot", wantStage: pipeline.StageChunk, wantSlot: "chunk-slot"},
-		{name: "merge", selector: "merge.alpha-merge", only: []string{"alpha"}, wantStage: pipeline.StageMerge, wantLane: "alpha", wantSlot: "alpha-merge"},
-		{name: "lane", selector: "alpha.alpha-slot", wantStage: pipeline.StageExtract, wantLane: "alpha", wantSlot: "alpha-slot"},
-		{name: "lane extract", selector: "alpha.extract.alpha-slot", wantStage: pipeline.StageExtract, wantLane: "alpha", wantSlot: "alpha-slot"},
-		{name: "lane merge", selector: "alpha.merge.alpha-merge", wantStage: pipeline.StageMerge, wantLane: "alpha", wantSlot: "alpha-merge"},
-		{name: "lane normalize", selector: "alpha.normalize.alpha-normalize", wantStage: pipeline.StageNormalize, wantLane: "alpha", wantSlot: "alpha-normalize"},
+		{name: "pipeline", selector: "shared", want: []string{"alpha.extract.shared", "alpha.merge.shared", "alpha.normalize.shared", "beta.extract.shared", "beta.merge.shared", "beta.normalize.shared"}},
+		{name: "chunk", selector: "chunk.chunk-slot", want: []string{"chunk.chunk-slot"}},
+		{name: "lane", selector: "alpha.shared", want: []string{"alpha.extract.shared", "alpha.merge.shared", "alpha.normalize.shared"}},
+		{name: "lane extract", selector: "alpha.extract.alpha-slot", want: []string{"alpha.extract.alpha-slot"}},
+		{name: "lane merge", selector: "alpha.merge.alpha-merge", want: []string{"alpha.merge.alpha-merge"}},
+		{name: "lane normalize", selector: "alpha.normalize.alpha-normalize", want: []string{"alpha.normalize.alpha-normalize"}},
 	}
 	for _, tt := range tests {
 		t.Run(tt.name, func(t *testing.T) {
@@ -37,70 +34,135 @@ func TestReferenceSelectorsParseAndApplyAllDocumentedForms(t *testing.T) {
 			if err != nil {
 				t.Fatal(err)
 			}
-			overrides, _, err := resolveCLIReferenceRequests(cfg, "demo", tt.only, catalog, []cliReferenceRequest{{Selector: selector, Source: "reference.txt"}}, nil)
+			overrides, _, err := resolveCLIReferenceRequests(cfg, "demo", nil, catalog, []cliReferenceRequest{{Selector: selector, Source: "reference.txt"}}, nil)
 			if err != nil {
 				t.Fatalf("resolve selector: %v", err)
 			}
-			if len(overrides) != 1 {
-				t.Fatalf("overrides = %#v, want one binding", overrides)
+			if got := referenceContractBindingLabels(overrides); !slices.Equal(got, tt.want) {
+				t.Fatalf("binding targets = %#v, want %#v", got, tt.want)
 			}
-			got := overrides[0]
-			if got.Stage != tt.wantStage || got.LaneID != tt.wantLane || got.SlotName != tt.wantSlot || got.BindingSource != contracts.ReferenceBindingSourceCLI {
-				t.Fatalf("binding = %#v, want %s/%s/%s from CLI", got, tt.wantStage, tt.wantLane, tt.wantSlot)
-			}
-		})
-	}
-}
-
-func TestReferenceSelectorsRejectAmbiguityWithSpecificSuggestions(t *testing.T) {
-	cfg := referenceContractConfig()
-	catalog := referenceContractCatalog(t, true, true)
-	for _, tt := range []struct {
-		name     string
-		selector string
-		want     []string
-	}{
-		{name: "flat shared slot", selector: "shared", want: []string{"alpha.extract.shared", "beta.extract.shared"}},
-		{name: "lane shared slot", selector: "alpha.shared", want: []string{"alpha.extract.shared", "alpha.merge.shared", "alpha.normalize.shared"}},
-		{name: "all mergers", selector: "merge.shared", want: []string{"alpha.merge.shared", "beta.merge.shared"}},
-	} {
-		t.Run(tt.name, func(t *testing.T) {
-			selector, err := parseReferenceSelector(tt.selector, "--reference")
-			if err != nil {
-				t.Fatal(err)
-			}
-			_, _, err = resolveCLIReferenceRequests(cfg, "demo", nil, catalog, []cliReferenceRequest{{Selector: selector, Source: "reference.txt"}}, nil)
-			if err == nil {
-				t.Fatal("resolve selector succeeded, want ambiguity error")
-			}
-			for _, fragment := range tt.want {
-				if !strings.Contains(err.Error(), fragment) {
-					t.Fatalf("error = %q, want suggestion %q", err, fragment)
+			for _, binding := range overrides {
+				if binding.Source != "reference.txt" || binding.BindingSource != contracts.ReferenceBindingSourceCLI {
+					t.Fatalf("binding = %#v, want CLI source", binding)
 				}
 			}
 		})
 	}
 }
 
-func TestReferenceSelectorsRespectSelectedLanesBeforeMaterialization(t *testing.T) {
+func TestReferenceSelectorSpecificityAndFinalOccurrenceChooseConcreteBindings(t *testing.T) {
+	cfg := referenceContractConfig()
+	catalog := referenceContractCatalog(t, true, true)
+	requests := []cliReferenceRequest{
+		{Selector: mustParseReferenceSelector(t, "shared", "--reference"), Source: "pipeline-first.txt"},
+		{Selector: mustParseReferenceSelector(t, "shared", "--reference"), Source: "pipeline-final.txt"},
+		{Selector: mustParseReferenceSelector(t, "alpha.shared", "--reference"), Source: "lane.txt"},
+		{Selector: mustParseReferenceSelector(t, "alpha.extract.shared", "--reference"), Source: "binding.txt"},
+	}
+	overrides, unbinds, err := resolveCLIReferenceRequests(cfg, "demo", nil, catalog, requests, nil)
+	if err != nil {
+		t.Fatal(err)
+	}
+	if len(unbinds) != 0 {
+		t.Fatalf("unbinds = %#v, want none", unbinds)
+	}
+	want := map[string]string{
+		"alpha.extract.shared":   "binding.txt",
+		"alpha.merge.shared":     "lane.txt",
+		"alpha.normalize.shared": "lane.txt",
+		"beta.extract.shared":    "pipeline-final.txt",
+		"beta.merge.shared":      "pipeline-final.txt",
+		"beta.normalize.shared":  "pipeline-final.txt",
+	}
+	for _, binding := range overrides {
+		label := referenceContractBindingLabel(binding)
+		if binding.Source != want[label] {
+			t.Fatalf("binding %s source = %q, want %q", label, binding.Source, want[label])
+		}
+		delete(want, label)
+	}
+	if len(want) != 0 {
+		t.Fatalf("missing bindings: %#v", want)
+	}
+}
+
+func TestCompleteDNDSharedCLIReferencesExpandAcrossCompatibleTargets(t *testing.T) {
+	cfg := loadMaintainedExample(t, repositoryPath("examples", "dnd-complete.config.yml"))
+	catalog := catalogFromRegistries(productionTestComponents(t).registries)
+	sources := map[string]string{
+		"party":         "/references/party.txt",
+		"players":       "/references/players.txt",
+		"glossary":      "/references/glossary.txt",
+		"spell_catalog": "/references/spells.json",
+	}
+	requests := make([]cliReferenceRequest, 0, len(sources))
+	for _, slot := range []string{"party", "players", "glossary", "spell_catalog"} {
+		requests = append(requests, cliReferenceRequest{
+			Selector: mustParseReferenceSelector(t, slot, "--reference"),
+			Source:   sources[slot],
+		})
+	}
+	overrides, unbinds, err := resolveCLIReferenceRequests(cfg, "dnd-session", nil, catalog, requests, nil)
+	if err != nil {
+		t.Fatalf("expand complete D&D references: %v", err)
+	}
+	if len(unbinds) != 0 {
+		t.Fatalf("unbinds = %#v, want none", unbinds)
+	}
+
+	actual := make(map[string]pipeline.ReferenceBinding, len(overrides))
+	for _, binding := range overrides {
+		actual[referenceContractBindingLabel(binding)] = binding
+	}
+	targets, err := selectedReferenceTargets(cfg, "dnd-session", nil, catalog)
+	if err != nil {
+		t.Fatal(err)
+	}
+	matched := make(map[string]int, len(sources))
+	for _, target := range targets {
+		for slot, sourcePath := range sources {
+			if _, ok := target.slots[slot]; !ok {
+				continue
+			}
+			matched[slot]++
+			label := targetLabel(target) + "." + slot
+			binding, ok := actual[label]
+			if !ok || binding.Source != sourcePath || binding.BindingSource != contracts.ReferenceBindingSourceCLI {
+				t.Fatalf("binding %q = %#v, want CLI source %q", label, binding, sourcePath)
+			}
+		}
+	}
+	for slot := range sources {
+		if matched[slot] < 2 {
+			t.Fatalf("reference %q matched %d target(s), want a shared D&D reference", slot, matched[slot])
+		}
+	}
+	if _, err := cfg.Resolve(config.ResolveInput{PipelineID: "dnd-session", Catalog: catalog, ReferenceOverrides: overrides}); err != nil {
+		t.Fatalf("resolve complete D&D CLI references: %v", err)
+	}
+}
+
+func TestReferenceSelectorsRejectInvalidOrUnselectedScopesBeforeMaterialization(t *testing.T) {
 	cfg := referenceContractConfig()
 	catalog := referenceContractCatalog(t, true, true)
 	for _, tt := range []struct {
 		name     string
 		selector string
+		only     []string
 		want     string
 	}{
-		{name: "unselected lane", selector: "beta.extract.beta-slot", want: `reference lane "beta" is not selected`},
+		{name: "pipeline slot", selector: "missing", want: `reference slot "missing" is not declared by any selected target`},
+		{name: "lane slot", selector: "alpha.missing", want: `reference slot "missing" is not declared by selected lane "alpha"`},
+		{name: "binding slot", selector: "alpha.extract.missing", want: `reference slot "missing" is not declared`},
+		{name: "former merge shorthand", selector: "merge.shared", want: `reference lane "merge" is not selected`},
+		{name: "unselected lane", selector: "beta.extract.beta-slot", only: []string{"alpha"}, want: `reference lane "beta" is not selected`},
 		{name: "unknown lane", selector: "missing.extract.beta-slot", want: `reference lane "missing" is not selected`},
 	} {
 		t.Run(tt.name, func(t *testing.T) {
-			selector, err := parseReferenceSelector(tt.selector, "--reference")
-			if err != nil {
-				t.Fatal(err)
-			}
-			_, _, err = resolveCLIReferenceRequests(cfg, "demo", []string{"alpha"}, catalog, []cliReferenceRequest{{Selector: selector, Source: filepath.Join(t.TempDir(), "missing.txt")}}, nil)
+			selector := mustParseReferenceSelector(t, tt.selector, "--reference")
+			_, _, err := resolveCLIReferenceRequests(cfg, "demo", tt.only, catalog, []cliReferenceRequest{{Selector: selector, Source: filepath.Join(t.TempDir(), "missing.txt")}}, nil)
 			if err == nil || !strings.Contains(err.Error(), tt.want) || strings.Contains(err.Error(), "missing.txt") {
-				t.Fatalf("error = %v, want selection failure before file access", err)
+				t.Fatalf("error = %v, want selection failure containing %q before file access", err, tt.want)
 			}
 		})
 	}
@@ -131,40 +193,50 @@ func TestReferenceSyntaxErrorsReturnTwo(t *testing.T) {
 	}
 }
 
-func TestReferenceOverridesUseFinalExactTargetBinding(t *testing.T) {
+func TestReferenceBindAndUnbindSpecificity(t *testing.T) {
 	cfg := referenceContractConfig()
 	catalog := referenceContractCatalog(t, true, true)
-	alphaShared, err := parseReferenceSelector("alpha.extract.shared", "--reference")
-	if err != nil {
-		t.Fatal(err)
-	}
-	betaShared, err := parseReferenceSelector("beta.extract.shared", "--reference")
-	if err != nil {
-		t.Fatal(err)
-	}
-	overrides, unbinds, err := resolveCLIReferenceRequests(cfg, "demo", nil, catalog, []cliReferenceRequest{
-		{Selector: alphaShared, Source: "alpha-first.txt"},
-		{Selector: alphaShared, Source: "alpha-final.txt"},
-		{Selector: betaShared, Source: "beta-only.txt"},
-	}, nil)
-	if err != nil {
-		t.Fatal(err)
-	}
-	if len(unbinds) != 0 {
-		t.Fatalf("unbinds = %#v, want none", unbinds)
-	}
-	effective, err := cfg.Resolve(config.ResolveInput{PipelineID: "demo", Catalog: catalog, ReferenceOverrides: overrides})
-	if err != nil {
-		t.Fatalf("resolve pipeline: %v", err)
-	}
-	alpha := referenceContractLane(t, effective.ResolvedPipeline, "alpha")
-	beta := referenceContractLane(t, effective.ResolvedPipeline, "beta")
-	if source := referenceContractBindingSource(alpha.ExtractReferences.Bindings, "shared"); source != "alpha-final.txt" {
-		t.Fatalf("alpha shared source = %q, want final exact-target override", source)
-	}
-	if source := referenceContractBindingSource(beta.ExtractReferences.Bindings, "shared"); source != "beta-only.txt" {
-		t.Fatalf("beta shared source = %q, want target-specific override", source)
-	}
+	t.Run("specific unbind carves out broad binding", func(t *testing.T) {
+		overrides, unbinds, err := resolveCLIReferenceRequests(cfg, "demo", nil, catalog,
+			[]cliReferenceRequest{{Selector: mustParseReferenceSelector(t, "shared", "--reference"), Source: "shared.txt"}},
+			[]cliReferenceUnbindRequest{{Selector: mustParseReferenceSelector(t, "alpha.extract.shared", "--without-reference")}},
+		)
+		if err != nil {
+			t.Fatal(err)
+		}
+		if got := referenceContractBindingLabels(overrides); slices.Contains(got, "alpha.extract.shared") || len(got) != 5 {
+			t.Fatalf("overrides = %#v, want all shared targets except alpha extract", got)
+		}
+		if got := referenceContractUnbindLabels(unbinds); !slices.Equal(got, []string{"alpha.extract.shared"}) {
+			t.Fatalf("unbinds = %#v, want alpha extract", got)
+		}
+	})
+
+	t.Run("specific binding restores broad unbind", func(t *testing.T) {
+		overrides, unbinds, err := resolveCLIReferenceRequests(cfg, "demo", nil, catalog,
+			[]cliReferenceRequest{{Selector: mustParseReferenceSelector(t, "alpha.extract.shared", "--reference"), Source: "alpha.txt"}},
+			[]cliReferenceUnbindRequest{{Selector: mustParseReferenceSelector(t, "shared", "--without-reference")}},
+		)
+		if err != nil {
+			t.Fatal(err)
+		}
+		if got := referenceContractBindingLabels(overrides); !slices.Equal(got, []string{"alpha.extract.shared"}) {
+			t.Fatalf("overrides = %#v, want alpha extract", got)
+		}
+		if got := referenceContractUnbindLabels(unbinds); slices.Contains(got, "alpha.extract.shared") || len(got) != 5 {
+			t.Fatalf("unbinds = %#v, want all shared targets except alpha extract", got)
+		}
+	})
+
+	t.Run("same specificity conflicts", func(t *testing.T) {
+		_, _, err := resolveCLIReferenceRequests(cfg, "demo", nil, catalog,
+			[]cliReferenceRequest{{Selector: mustParseReferenceSelector(t, "alpha.shared", "--reference"), Source: "alpha.txt"}},
+			[]cliReferenceUnbindRequest{{Selector: mustParseReferenceSelector(t, "alpha.shared", "--without-reference")}},
+		)
+		if err == nil || !strings.Contains(err.Error(), "same specificity") {
+			t.Fatalf("error = %v, want same-specificity conflict", err)
+		}
+	})
 }
 
 func TestReferenceUnbindsRemoveOptionalAndProtectRequiredSlots(t *testing.T) {
@@ -217,7 +289,7 @@ func TestReferenceMaterializationSeparatesCLIAndConfigPathOrigins(t *testing.T)
 	workingDir := t.TempDir()
 	cfg := referenceContractConfig()
 	configPath := filepath.Join(configDir, "config.yml")
-	if err := os.WriteFile(configPath, []byte("version: 4\n"), 0o600); err != nil {
+	if err := os.WriteFile(configPath, []byte("version: 5\n"), 0o600); err != nil {
 		t.Fatal(err)
 	}
 	if err := os.WriteFile(filepath.Join(configDir, "required.txt"), []byte("config reference"), 0o600); err != nil {
@@ -257,6 +329,52 @@ func TestReferenceMaterializationSeparatesCLIAndConfigPathOrigins(t *testing.T)
 	}
 }
 
+func TestPipelineScopedCLIReferenceProtectsGeneratedHandoff(t *testing.T) {
+	cfg := referenceContractConfig()
+	profile := cfg.Pipelines["demo"]
+	alpha := profile.Artifacts["alpha"]
+	beta := profile.Artifacts["beta"]
+	alpha.Extract.References["shared"] = pipeline.GeneratedReference("produce", "beta")
+	profile.Artifacts = nil
+	profile.Steps = []pipeline.PipelineStepProfile{
+		{ID: "produce", Artifacts: map[string]pipeline.ArtifactLaneProfile{"beta": beta}},
+		{ID: "consume", Artifacts: map[string]pipeline.ArtifactLaneProfile{"alpha": alpha}},
+	}
+	cfg.Pipelines["demo"] = profile
+	catalog := referenceContractCatalog(t, true, true)
+
+	t.Run("binding conflicts before file access", func(t *testing.T) {
+		overrides, _, err := resolveCLIReferenceRequests(cfg, "demo", nil, catalog, []cliReferenceRequest{{
+			Selector: mustParseReferenceSelector(t, "shared", "--reference"),
+			Source:   filepath.Join(t.TempDir(), "never-read.json"),
+		}}, nil)
+		if err != nil {
+			t.Fatalf("expand CLI reference: %v", err)
+		}
+		_, err = cfg.Resolve(config.ResolveInput{PipelineID: "demo", Catalog: catalog, ReferenceOverrides: overrides})
+		if err == nil || !strings.Contains(err.Error(), "conflicting generated and external bindings") || strings.Contains(err.Error(), "never-read.json") {
+			t.Fatalf("resolve error = %v, want generated/external conflict before file access", err)
+		}
+	})
+
+	t.Run("unbind leaves generated source intact", func(t *testing.T) {
+		_, unbinds, err := resolveCLIReferenceRequests(cfg, "demo", nil, catalog, nil, []cliReferenceUnbindRequest{{
+			Selector: mustParseReferenceSelector(t, "shared", "--without-reference"),
+		}})
+		if err != nil {
+			t.Fatalf("expand CLI unbind: %v", err)
+		}
+		effective, err := cfg.Resolve(config.ResolveInput{PipelineID: "demo", Catalog: catalog, ReferenceUnbinds: unbinds})
+		if err != nil {
+			t.Fatalf("resolve generated reference with CLI unbind: %v", err)
+		}
+		binding := referenceContractFindBinding(referenceContractLane(t, effective.ResolvedPipeline, "alpha").ExtractReferences.Bindings, "shared")
+		if binding == nil || binding.Artifact == nil || binding.Artifact.Step != "produce" || binding.Artifact.Lane != "beta" {
+			t.Fatalf("generated binding = %#v, want preserved produce/beta handoff", binding)
+		}
+	})
+}
+
 func TestReferenceTargetLookupUsesArtifactVariantsAndReportsMissingContext(t *testing.T) {
 	cfg := referenceContractConfig()
 	full := referenceContractCatalog(t, true, true)
@@ -368,7 +486,7 @@ func referenceContractCatalog(t *testing.T, includeBetaMerger, includeBetaNormal
 	register(registries.Chunkers.RegisterWithSpec(pipeline.ModuleSpec{Key: "reference/chunk", Stage: pipeline.StageChunk, ExecutionClass: contracts.ExecutionClassDeterministic, Requires: []string{"source"}, Provides: []string{"chunks"}, ReferenceSlots: []contracts.ReferenceSlot{{Name: "chunk-slot"}, {Name: "required-chunk", Required: true}}}, func() (contracts.Chunker, error) { return stateTestChunker{}, nil }))
 	register(pipeline.RegisterArtifactCodec(registries.ArtifactCodecs, referenceContractCodecA{}))
 	register(pipeline.RegisterArtifactCodec(registries.ArtifactCodecs, referenceContractCodecB{}))
-	register(pipeline.RegisterExtractor(registries.Extractors, pipeline.ModuleSpec{Key: "reference/extract-alpha", Stage: pipeline.StageExtract, ExecutionClass: contracts.ExecutionClassDeterministic, Requires: []string{"chunks"}, Provides: []string{"artifact"}, ArtifactKind: referenceContractKindAlpha, ReferenceSlots: []contracts.ReferenceSlot{{Name: "shared"}, {Name: "alpha-slot"}, {Name: "required-extract", Required: true}}}, func() (contracts.Extractor[stateTestArtifact], error) { return stateTestExtractor{}, nil }))
+	register(pipeline.RegisterExtractor(registries.Extractors, pipeline.ModuleSpec{Key: "reference/extract-alpha", Stage: pipeline.StageExtract, ExecutionClass: contracts.ExecutionClassDeterministic, Requires: []string{"chunks"}, Provides: []string{"artifact"}, ArtifactKind: referenceContractKindAlpha, ReferenceSlots: []contracts.ReferenceSlot{{Name: "shared", AcceptedArtifactKinds: []contracts.ArtifactKind{referenceContractKindBeta}, AcceptedMediaTypes: []string{"application/json"}}, {Name: "alpha-slot"}, {Name: "required-extract", Required: true}}}, func() (contracts.Extractor[stateTestArtifact], error) { return stateTestExtractor{}, nil }))
 	register(pipeline.RegisterExtractor(registries.Extractors, pipeline.ModuleSpec{Key: "reference/extract-beta", Stage: pipeline.StageExtract, ExecutionClass: contracts.ExecutionClassDeterministic, Requires: []string{"chunks"}, Provides: []string{"artifact"}, ArtifactKind: referenceContractKindBeta, ReferenceSlots: []contracts.ReferenceSlot{{Name: "shared"}, {Name: "beta-slot"}, {Name: "required-extract", Required: true}}}, func() (contracts.Extractor[stateTestArtifact], error) { return stateTestExtractor{}, nil }))
 	register(pipeline.RegisterMerger(registries.Mergers, pipeline.ModuleSpec{Key: "reference/shared-merge", Stage: pipeline.StageMerge, ExecutionClass: contracts.ExecutionClassDeterministic, Requires: []string{"artifact"}, Provides: []string{"merged"}, ArtifactKind: referenceContractKindAlpha, ReferenceSlots: []contracts.ReferenceSlot{{Name: "shared"}, {Name: "alpha-merge"}, {Name: "required-merge", Required: true}}}, func() (contracts.Merger[stateTestArtifact], error) { return stateTestMerger{}, nil }))
 	if includeBetaMerger {
@@ -444,6 +562,42 @@ func referenceContractBindingSource(bindings []pipeline.ReferenceBinding, slot s
 	return ""
 }
 
+func mustParseReferenceSelector(t *testing.T, value, flagName string) cliReferenceSelector {
+	t.Helper()
+	selector, err := parseReferenceSelector(value, flagName)
+	if err != nil {
+		t.Fatal(err)
+	}
+	return selector
+}
+
+func referenceContractBindingLabels(bindings []pipeline.ReferenceBinding) []string {
+	labels := make([]string, 0, len(bindings))
+	for _, binding := range bindings {
+		labels = append(labels, referenceContractBindingLabel(binding))
+	}
+	return labels
+}
+
+func referenceContractBindingLabel(binding pipeline.ReferenceBinding) string {
+	if binding.Stage == pipeline.StageChunk {
+		return "chunk." + binding.SlotName
+	}
+	return binding.LaneID + "." + string(binding.Stage) + "." + binding.SlotName
+}
+
+func referenceContractUnbindLabels(unbinds []pipeline.ReferenceUnbind) []string {
+	labels := make([]string, 0, len(unbinds))
+	for _, unbind := range unbinds {
+		labels = append(labels, referenceContractBindingLabel(pipeline.ReferenceBinding{
+			Stage:    unbind.Stage,
+			LaneID:   unbind.LaneID,
+			SlotName: unbind.SlotName,
+		}))
+	}
+	return labels
+}
+
 func referenceContractFindBinding(bindings []pipeline.ReferenceBinding, slot string) *pipeline.ReferenceBinding {
 	for i := range bindings {
 		if bindings[i].SlotName == slot {