mission-directives 2.0.1__tar.gz

mission_directives-2.0.1/.gitignore

@@ -0,0 +1,47 @@
+__pycache__/
+*.pyc
+.pytest_cache/
+.ruff_cache/
+.mypy_cache/
+.coverage
+coverage/
+htmlcov/
+*.log
+npm-debug.log*
+pnpm-debug.log*
+yarn-debug.log*
+.DS_Store
+Thumbs.db
+.prompt_suite/logs/
+BODY_QUALITY_AUDIT.json
+BODY_QUALITY_AUDIT.md
+EVALUATION_STATUS.json
+TEST_RESULTS.json
+VALIDATION.json
+
+.prompt_suite/results/
+.prompt_suite/runtime/
+.prompt_suite/*.lock
+.prompt_suite/agent-guidance-receipt.json
+agent-guidance-receipt.json
+
+.agents/
+.codex/
+.venv/
+venv/
+
+# Astro generated and dependency trees
+site/node_modules/
+site/dist/
+site/.astro/
+prompt_imports/
+infographics/
+infographic/
+blog/
+blog.zip
+
+# Python package build output
+dist/
+build/
+*.egg-info/
+src/mission_directives/_runtime/

mission_directives-2.0.1/LICENSE

@@ -0,0 +1,7 @@
+Mission Directives is dual-licensed under either of the following licenses at
+your option:
+
+- MIT License (see LICENSE-MIT)
+- Apache License, Version 2.0 (see LICENSE-APACHE)
+
+SPDX-License-Identifier: MIT OR Apache-2.0

mission_directives-2.0.1/LICENSE-APACHE

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

mission_directives-2.0.1/LICENSE-MIT

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Manoj Pisini
+
+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.

mission_directives-2.0.1/PKG-INFO

@@ -0,0 +1,268 @@
+Metadata-Version: 2.4
+Name: mission-directives
+Version: 2.0.1
+Summary: Deterministic prompt routing, project context, and verifiable agent workflows.
+Project-URL: Homepage, https://manojpisini.github.io/mission-directives/
+Project-URL: Documentation, https://manojpisini.github.io/mission-directives/
+Project-URL: Repository, https://github.com/manojpisini/mission-directives
+Project-URL: Issues, https://github.com/manojpisini/mission-directives/issues
+Author: Manoj Pisini
+License-Expression: MIT OR Apache-2.0
+License-File: LICENSE-APACHE
+License-File: LICENSE-MIT
+Keywords: agents,automation,cli,orchestration,prompts
+Classifier: Development Status :: 4 - Beta
+Classifier: Environment :: Console
+Classifier: Intended Audience :: Developers
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Requires-Python: >=3.11
+Requires-Dist: jsonschema<5,>=4.20
+Requires-Dist: markdown-it-py<5,>=3
+Requires-Dist: pyyaml<7,>=6.0
+Requires-Dist: uvicorn<1,>=0.30
+Description-Content-Type: text/markdown
+
+<p align="center">
+  <img src="assets/readme/mission-directives-banner.svg" alt="Mission Directives" width="100%" />
+</p>
+
+<p align="center">
+  <a href="https://github.com/manojpisini/mission-directives/actions/workflows/validate.yml"><img src="https://github.com/manojpisini/mission-directives/actions/workflows/validate.yml/badge.svg" alt="Validate Mission Directives" /></a>
+  <a href="https://github.com/manojpisini/mission-directives/actions/workflows/deploy-docs.yml"><img src="https://github.com/manojpisini/mission-directives/actions/workflows/deploy-docs.yml/badge.svg" alt="Deploy documentation" /></a>
+</p>
+
+<p align="center">
+  <strong>Bounded, reviewable, and verifiable agent work.</strong><br />
+  <a href="https://manojpisini.github.io/mission-directives/">Documentation site</a>
+</p>
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+Mission Directives is a curated prompt and orchestration suite for turning natural-language requests into the smallest coherent prompt, scenario, or workflow graph needed for the outcome. It keeps selection deterministic, authority explicit, and completion tied to evidence instead of asking a model to load a whole library and guess.
+
+Current release: **2.0.1**
+
+<p align="center">
+  <img src="assets/readme/routing-flow.svg" alt="Mission Directives routing flow: route, explain, plan, and verify." width="100%" />
+</p>
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## What It Provides
+
+- **Deterministic routing:** exact IDs, shortcuts, keyword concepts, route hints, typo recovery, metadata scoring, and calibrated no-match behavior.
+- **Stable prompt contracts:** permanent `MD-*` identities, typed inputs and outputs, operating modes, risk levels, evidence lanes, and completion gates.
+- **Scenario graphs:** atomic and composite workflows with phases, locks, branches, approvals, assurance requirements, and external-action boundaries.
+- **Pinned project runtime:** the installed CLI creates an isolated `.mission-directives/` workspace containing prompts, catalogs, schemas, configuration, outputs, and an independent local viewer.
+- **Project context fast path:** schema-validated project knowledge reduces repeated repository scans without granting authority or overriding current evidence.
+- **Verification discipline:** every route is complete only when the requested artifact satisfies its task-specific verification contract and residuals are explicit.
+
+<p align="center">
+  <img src="assets/readme/inventory.svg" alt="Repository inventory: 257 prompts, 257 atomic routes, 110 composite scenarios, 62 manuals, and 32 reciprocal pairs." width="100%" />
+</p>
+
+Repository inventory: **257 prompts**, **257 atomic routes**, **110 composite scenarios**, **32 reciprocal investigation/execution pairs**, and **62 repository manuals**.
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## How It Works
+
+```text
+request
+  -> parse MD invocation, exact IDs, intent, depth, and assurance modifiers
+  -> resolve shortcut owners and candidate metadata without loading prompt bodies
+  -> rank prompt, scenario, pack, and skill candidates
+  -> explain the selected graph, modes, inputs, approvals, and verification duties
+  -> plan or execute inside the declared authority boundary
+  -> verify the exact result and record evidence, unknowns, residuals, and receipts
+```
+
+Prompt numbers are stable addresses, not lifecycle state. Department packs help discovery; they are not bundles to load in full.
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Requirements
+
+- Python 3.11 or newer.
+- Git is required for normal development.
+- PowerShell 7 is recommended for Windows wrappers.
+- Bash is required only for POSIX wrappers.
+- The documentation site uses `pnpm`.
+
+Runtime dependencies for installed projects are in [requirements-runtime.txt](requirements-runtime.txt). Repository development and validation dependencies are in [requirements-dev.txt](requirements-dev.txt).
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Quick Start
+
+```bash
+uv tool install mission-directives
+cd /path/to/project
+mission-directives init --tracking ignored
+mission-directives config validate
+mission-directives route "MD advanced audit fix verify repository"
+mission-directives view
+```
+
+`pipx install mission-directives` and `python -m pip install --user mission-directives` are also supported. The `mission-directives` executable is used deliberately; `md` is already an all-scope PowerShell alias.
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Install Into a Project
+
+Initialize the current directory or an explicit project path:
+
+```bash
+mission-directives init
+mission-directives init /absolute/path/to/project --tracking outputs
+```
+
+The initializer stages and verifies the declared runtime payload before promoting it to `.mission-directives/runtime`. It also creates Project Config, the independent local viewer, seven output categories, managed guidance blocks, state receipts, and the selected `.gitignore` policy in one rollback-capable transaction.
+
+Tracking modes are `ignored` (ignore the full workspace), `outputs` (track Project Config and output categories), and `all` (track the pinned runtime and local site while ignoring transient state). Existing managed installations can use `mission-directives upgrade`; legacy managed layouts use `mission-directives migrate . --dry-run` before `--apply`.
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Daily Usage
+
+Route the full request:
+
+```bash
+mission-directives route "MD advanced repository mission drift and simplification audit"
+mission-directives lookup "cleanup dead code safely" --limit 8
+mission-directives compare C-108 C-63
+mission-directives explain C-108
+mission-directives plan C-108 --mode AUDIT_ONLY --root . --dry-run
+```
+
+Installed-project routing dispatches through the pinned `.mission-directives/runtime`, so a later global package upgrade cannot silently change project behavior.
+
+## Project Config and Outputs
+
+`.mission-directives/project.json` is a validated project knowledge cache. Agents read it before broad discovery, then verify only fields that are missing, stale, contradicted, or material to a high-risk decision. Current user instructions and repository evidence always win; the config cannot authorize mutation, deployment, publication, credentials, or external actions.
+
+```bash
+mission-directives config show
+mission-directives config validate
+mission-directives config refresh --dry-run
+mission-directives config open
+```
+
+Existing logical paths under `results/`, `reports/`, `artifacts/`, `plans/`, `outputs/`, `docs/`, and `logs/` resolve beneath `.mission-directives/`. `mission-directives view` serves those unchanged files through a loopback-only Uvicorn application with category indexes, Markdown articles, attachment previews, Project Config editing, and an authorized shutdown control. Restart it from any project subdirectory with the same command.
+
+Common entry points:
+
+| Request | Route | Purpose |
+| --- | --- | --- |
+| Clarify route-changing ambiguity | `MD-191` | Ask only questions that alter authority, evidence, output, budget, or acceptance criteria. |
+| Add or refine a prompt | `MD-199` | Review overlap, normalize, register, test, and add one prompt. |
+| Audit, fix, and verify | `C-108` | Run a convergent remediation workflow. |
+| Deep research | `C-26` | Produce an evidence-backed research report. |
+| Professional report | `C-95` | Build and verify a report pipeline. |
+| Feature delivery | `C-63` | Plan, implement, test, and document a feature. |
+| Prompt engineering | `C-94` | Create, optimize, evaluate, or repair prompts. |
+| Personal work system | `MD-138` | Organize goals, projects, tasks, notes, and decisions. |
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Operating Modes
+
+| Mode | Boundary |
+| --- | --- |
+| `AUDIT_ONLY` | Inspect, retrieve, analyze, compare, and report without mutation. |
+| `PLAN_ONLY` | Produce plans, specifications, decisions, or acceptance criteria. |
+| `DRAFT_ONLY` | Produce local drafts without implying publication or acceptance. |
+| `APPLY_SAFE` | Make reversible local changes inside explicit authority. |
+| `APPLY_APPROVED` | Perform the exact approved consequential action with receipts and recovery controls. |
+| `VERIFY_ONLY` | Independently verify an artifact or claimed result without changing it. |
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Documentation Site
+
+The documentation site is a static Astro build that uses the checked-in landing/documentation HTML, CSS, and JS shell. The generator publishes a sectioned documentation hub: `docs.html` for overview, `guides.html` for task guides, `manuals.html` for the generated manual library, `reference.html` for runtime contracts, `prompts.html` for every prompt, `scenarios.html` for atomic and composite scenarios, `pairs.html` for reciprocal pairs, and every root `docs/*.md` file as a static manual page under `reference/manuals/`.
+
+```bash
+cd site
+pnpm install
+pnpm run generate
+pnpm run build
+pnpm run check
+```
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Repository Layout
+
+| Path | Purpose |
+| --- | --- |
+| `prompts/` | Canonical prompt bodies. |
+| `catalog.json` | Prompt identities, metadata, and relationships. |
+| `SCENARIO_CATALOG.json` | Atomic and composite route graphs. |
+| `config/` | Router keywords, runtime payload allowlist, templates, packs, and capability graph. |
+| `policies/` | Authorization, evidence, routing, install, loop, and agent guidance policies. |
+| `schemas/` | Typed contracts and imported source schemas. |
+| `tools/` | Router, installer, generators, validators, and wrappers. |
+| `src/mission_directives/` | Packaged CLI, project lifecycle, Project Config, and local viewer. |
+| `pyproject.toml` | Public Python distribution metadata and console entry point. |
+| `docs/` | User, operator, authoring, security, and maintenance manuals. |
+| `site/` | Static documentation site source. |
+| `tests/` / `evaluations/` | Repository-only validation and evaluation assets. |
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Validation
+
+Before committing runtime, manifest, prompt, schema, docs, or site changes, run the smallest checks that cover the touched surface. For broad changes:
+
+```bash
+python tools/build_manifest.py
+python -m pytest
+python tools/validate_suite.py
+uv build
+python tools/package_smoke.py dist
+cd site && pnpm run check
+```
+
+`tools/validate_suite.py` checks structural contracts, deterministic runtime tests, fixture coverage, identity contracts, CI configuration, lock safety, generated artifact reproducibility, and manifest integrity. It does not certify live model quality or external-world outcomes.
+
+Before every broad push, follow the complete ordered checklist in the [GitHub Actions Failure History and Pre-Push Guide](docs/GITHUB_ACTIONS_FAILURE_HISTORY_AND_PRE_PUSH_GUIDE.md). It records all 30 historical validation failures, their fixes, cross-platform prevention rules, the Node 24 action baseline, and the package/site checks required before a push.
+
+Repository agents read [MEMORY.md](MEMORY.md) before workflow, manifest, release, installer, wrapper, documentation-generation, or publishing changes and append only verified durable lessons after completion.
+
+<p align="center">
+  <img src="assets/readme/divider.svg" alt="" width="100%" />
+</p>
+
+## Contributing
+
+Start with the [Contributor Guide](docs/CONTRIBUTOR_GUIDE.md) and [pre-push guide](docs/GITHUB_ACTIONS_FAILURE_HISTORY_AND_PRE_PUSH_GUIDE.md). Keep prompt identities stable, update generated registries through their owning tools, add focused regression coverage, rebuild `MANIFEST.json`, and run the validation commands above. Commit messages use past-tense declarative wording without first-person pronouns, for example `Added packaged runtime validation`.
+
+## License
+
+Mission Directives is available under your choice of [MIT](LICENSE-MIT) or [Apache-2.0](LICENSE-APACHE). See [LICENSE](LICENSE) for the dual-license notice.