iints-sdk-python35 1.3.1__tar.gz → 1.4.0__tar.gz

iints_sdk_python35-1.4.0/LICENSE

@@ -0,0 +1,173 @@
+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.
+
+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

iints_sdk_python35-1.3.1/LICENSE → iints_sdk_python35-1.4.0/LICENSE-MIT-IINTS-LEGACY

@@ -19,10 +19,3 @@ 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.
-
-ACADEMIC USE DISCLAIMER:
-This software is intended for academic research purposes only. It is not 
-intended for clinical use or as a medical device. Users must comply with 
-all applicable regulations and obtain proper approvals before any clinical 
-application. The authors disclaim any responsibility for clinical use of 
-this software.

iints_sdk_python35-1.4.0/NOTICE

@@ -0,0 +1,17 @@
+IINTS-AF SDK
+Copyright (c) 2026 IINTS-AF Contributors
+
+This distribution now bundles MDMP components directly inside the SDK source tree,
+including `mdmp_core`, `mdmp_ai`, `mdmp_flavors`, and `mdmp_integrations`.
+
+Bundled MDMP code originates from the MDMP project and is included here under
+the Apache License, Version 2.0.
+
+The original IINTS-AF SDK was previously distributed under the MIT License.
+The preserved MIT notice for legacy IINTS-origin portions is included in:
+
+`LICENSE-MIT-IINTS-LEGACY`
+
+Research-use notice:
+This software is intended for academic and pre-clinical research purposes only.
+It is not a medical device and does not provide clinical dosing advice.

{iints_sdk_python35-1.3.1/src/iints_sdk_python35.egg-info → iints_sdk_python35-1.4.0}/PKG-INFO

@@ -1,20 +1,22 @@
 Metadata-Version: 2.4
 Name: iints-sdk-python35
-Version: 1.3.1
+Version: 1.4.0
 Summary: A pre-clinical Edge-AI SDK for diabetes management validation.
 Author-email: Rune Bobbaers <rune.bobbaers@gmail.com>
+License-Expression: Apache-2.0
 Project-URL: Homepage, https://github.com/python35/IINTS-SDK
 Classifier: Programming Language :: Python :: 3
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
-Classifier: License :: OSI Approved :: MIT License
 Classifier: Operating System :: OS Independent
 Classifier: Development Status :: 5 - Production/Stable
 Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE
+License-File: NOTICE
+License-File: LICENSE-MIT-IINTS-LEGACY
 Requires-Dist: fpdf2>=2.8.0
 Requires-Dist: matplotlib>=3.5.0
 Requires-Dist: numpy>=1.24.0
@@ -46,7 +48,7 @@ Requires-Dist: h5py>=3.10.0; extra == "research"
 Requires-Dist: onnx>=1.16.0; extra == "research"
 Requires-Dist: onnxscript>=0.1.0; extra == "research"
 Provides-Extra: mdmp
-Requires-Dist: mdmp-protocol>=0.3.0; extra == "mdmp"
+Requires-Dist: cryptography>=42.0.0; extra == "mdmp"
 Dynamic: license-file
 
 # IINTS-AF SDK
@@ -71,7 +73,7 @@ Docs (GitHub Pages): [python35.github.io/IINTS-SDK](https://python35.github.io/I
 python3 -m venv .venv
 source .venv/bin/activate
 python -m pip install -U pip
-pip install iints-sdk-python35
+python -m pip install -U "iints-sdk-python35[mdmp]"
 ```
 
 ```bash
@@ -81,6 +83,16 @@ cd iints_quickstart
 iints presets run --name baseline_t1d --algo algorithms/example_algorithm.py
 ```
 
+If you want the clearest install/path rules first, read:
+- `docs/INSTALLATION.md`
+- `docs/AI_ASSISTANT.md` for the small Ollama setup and SDK linking flow
+- `docs/EVIDENCE_BASE.md` for the full medical + technical source legend
+
+Short rule:
+- installed `iints ...` commands can run from any folder
+- `python -m pip install -e ".[mdmp]"` only works from the SDK repo root
+- after `iints quickstart`, switch into the generated project folder
+
 ## CareLink Import
 
 The SDK can now ingest Medtronic CareLink / MiniMed CSV exports and convert them into the standard IINTS schema:
@@ -127,23 +139,37 @@ That workbench is designed for three things:
 The SDK now includes a research-only AI assistant layer for explanations and run summaries.
 It is gated by MDMP verification before any LLM call is allowed.
 
-Use an active virtual environment for the full flow:
+Use an active virtual environment for the full flow.
+
+If you installed the released SDK from PyPI, run:
 
 ```bash
 python3 -m venv .venv
 source .venv/bin/activate
 python -m pip install -U pip
-python -m pip install -e ".[mdmp]"
+python -m pip install -U "iints-sdk-python35[mdmp]"
+```
+
+If you are developing from source instead, first move into the SDK repo root and then run:
+
+```bash
+cd /path/to/IINTS-SDK
+python -m pip install -U -e ".[mdmp]"
 ```
 
 Run the open local Mistral model locally with Ollama:
 
 ```bash
-python -m pip install -e ".[mdmp]"
 ollama pull ministral-3:8b
 iints ai models
 ```
 
+If you want the short "install Ollama + link it to the SDK" guide, read:
+- `docs/AI_ASSISTANT.md`
+
+If you want the full legend of medical, dataset, runtime, and emulator references used across the project docs:
+- `docs/EVIDENCE_BASE.md`
+
 Recommended first-time setup:
 
 ```bash
@@ -239,14 +265,54 @@ You can also run it through the CLI:
 iints demo-booth --output-dir results/booth_demo
 ```
 
+For a cleaner live explanation, show this source file first:
+
+```bash
+examples/demos/07_live_stage_demo.py
+```
+
+That file is deliberately small and readable, so you can point to:
+- `PATIENT_CONFIG`
+- `OUTPUT_DIR`
+- `DURATION_MINUTES`
+- `TIME_STEP_MINUTES`
+- `SEED`
+
+Then run:
+
+```bash
+./scripts/run_live_stage_demo.sh
+```
+
+That shell wrapper resolves the SDK repo root automatically, so it still works if you launch it from another working directory via its full path.
+
+And open:
+- `results/booth_demo_live/booth_demo_poster.png`
+- `results/booth_demo_live/JURY_TALK_TRACK.md`
+- `results/booth_demo_live/BEURS_LIVE_DEMO_SCRIPT.txt`
+
+What makes this script good for a booth:
+- it visibly calls `run_full(...)`
+- it visibly calls `generate_results_poster(...)`
+- it visibly calls `prepare_ai_ready_artifacts(...)`
+- you can point to one patient setting and explain how the same pipeline reruns for another patient
+
+If you installed the SDK on another machine and do not have the repository checkout there, export the same demo code with:
+
+```bash
+iints demo-export --output-dir iints_demo
+cd iints_demo
+python 07_live_stage_demo.py
+```
+
 ## Updating The SDK
 
-If another machine is missing newer commands like `iints ai ...` or `iints demo-booth`, upgrade inside the active virtual environment:
+If another machine is missing newer commands like `iints ai ...` or `iints demo-booth`, upgrade inside the active virtual environment to the latest release:
 
 ```bash
 source .venv/bin/activate
 python -m pip install -U pip
-python -m pip install -U "iints-sdk-python35[mdmp]==1.3.1"
+python -m pip install -U "iints-sdk-python35[mdmp]"
 hash -r
 python -c "import iints; print(iints.__version__)"
 ```
@@ -260,6 +326,8 @@ iints-sdk-doctor
 Full guide:
 - `docs/UPDATING.md`
 
+If you specifically need to reproduce a known environment, you can pin an exact release number instead of using the unpinned upgrade command above.
+
 Troubleshooting:
 - If `iints ai ...` says `No such command 'ai'`, your environment usually still has a legacy `iints` package installed alongside `iints-sdk-python35`.
 - Run `iints-sdk-doctor` first.
@@ -267,7 +335,7 @@ Troubleshooting:
 
 ```bash
 python -m pip uninstall -y iints iints-sdk-python35
-python -m pip install -U "iints-sdk-python35[mdmp]==1.3.1"
+python -m pip install -U "iints-sdk-python35[mdmp]"
 hash -r
 ```
 
@@ -287,13 +355,13 @@ iints mdmp validate mdmp_contract.yaml data/my_cgm.csv --output-json results/mdm
 iints mdmp visualizer results/mdmp_report.json --output-html results/mdmp_dashboard.html
 ```
 
-Use standalone MDMP backend (optional):
+Use bundled `mdmp_core` backend (optional):
 
 ```bash
 export IINTS_MDMP_BACKEND=mdmp_core
 ```
 
-Staleness / lineage checks (standalone MDMP CLI):
+Staleness / lineage checks via the bundled `mdmp` CLI:
 
 ```bash
 mdmp fingerprint-record data/my_cgm.csv --output-json results/fingerprint.json --expires-days 365
@@ -303,21 +371,17 @@ mdmp registry init --registry registry/mdmp_registry.json
 mdmp registry push --registry registry/mdmp_registry.json --report results/mdmp_report.json
 ```
 
-## Dual Repo Workflow
-- SDK repo: `python35/IINTS-SDK`
-- MDMP repo: `python35/MDMP`
+## Bundled MDMP
 
-Local helper scripts:
-- `tools/dev/dual_repo_status.sh`
-- `tools/dev/dual_repo_commit_push.sh`
+MDMP now ships inside the SDK, so the SDK no longer depends on a separate public MDMP repository checkout.
 
-Full process: `docs/DUAL_REPO_WORKFLOW.md`
+That means:
+- `iints mdmp ...` stays available
+- the bundled `mdmp` CLI can still be used
+- local AI signing and verification can still use `mdmp_core`
 
-MDMP sync CI gate:
-- `.github/workflows/mdmp-sync.yml`
-- Uses private-repo checkout when `MDMP_REPO_TOKEN` is configured.
-- Falls back to `mdmp-protocol` from PyPI when checkout is unavailable.
-- Auto dependency updates for MDMP are handled via Dependabot (`.github/dependabot.yml`).
+Reference:
+- `docs/DUAL_REPO_WORKFLOW.md`
 
 ## Tools Layout
 

{iints_sdk_python35-1.3.1 → iints_sdk_python35-1.4.0}/README.md

@@ -20,7 +20,7 @@ Docs (GitHub Pages): [python35.github.io/IINTS-SDK](https://python35.github.io/I
 python3 -m venv .venv
 source .venv/bin/activate
 python -m pip install -U pip
-pip install iints-sdk-python35
+python -m pip install -U "iints-sdk-python35[mdmp]"
 ```
 
 ```bash
@@ -30,6 +30,16 @@ cd iints_quickstart
 iints presets run --name baseline_t1d --algo algorithms/example_algorithm.py
 ```
 
+If you want the clearest install/path rules first, read:
+- `docs/INSTALLATION.md`
+- `docs/AI_ASSISTANT.md` for the small Ollama setup and SDK linking flow
+- `docs/EVIDENCE_BASE.md` for the full medical + technical source legend
+
+Short rule:
+- installed `iints ...` commands can run from any folder
+- `python -m pip install -e ".[mdmp]"` only works from the SDK repo root
+- after `iints quickstart`, switch into the generated project folder
+
 ## CareLink Import
 
 The SDK can now ingest Medtronic CareLink / MiniMed CSV exports and convert them into the standard IINTS schema:
@@ -76,23 +86,37 @@ That workbench is designed for three things:
 The SDK now includes a research-only AI assistant layer for explanations and run summaries.
 It is gated by MDMP verification before any LLM call is allowed.
 
-Use an active virtual environment for the full flow:
+Use an active virtual environment for the full flow.
+
+If you installed the released SDK from PyPI, run:
 
 ```bash
 python3 -m venv .venv
 source .venv/bin/activate
 python -m pip install -U pip
-python -m pip install -e ".[mdmp]"
+python -m pip install -U "iints-sdk-python35[mdmp]"
+```
+
+If you are developing from source instead, first move into the SDK repo root and then run:
+
+```bash
+cd /path/to/IINTS-SDK
+python -m pip install -U -e ".[mdmp]"
 ```
 
 Run the open local Mistral model locally with Ollama:
 
 ```bash
-python -m pip install -e ".[mdmp]"
 ollama pull ministral-3:8b
 iints ai models
 ```
 
+If you want the short "install Ollama + link it to the SDK" guide, read:
+- `docs/AI_ASSISTANT.md`
+
+If you want the full legend of medical, dataset, runtime, and emulator references used across the project docs:
+- `docs/EVIDENCE_BASE.md`
+
 Recommended first-time setup:
 
 ```bash
@@ -188,14 +212,54 @@ You can also run it through the CLI:
 iints demo-booth --output-dir results/booth_demo
 ```
 
+For a cleaner live explanation, show this source file first:
+
+```bash
+examples/demos/07_live_stage_demo.py
+```
+
+That file is deliberately small and readable, so you can point to:
+- `PATIENT_CONFIG`
+- `OUTPUT_DIR`
+- `DURATION_MINUTES`
+- `TIME_STEP_MINUTES`
+- `SEED`
+
+Then run:
+
+```bash
+./scripts/run_live_stage_demo.sh
+```
+
+That shell wrapper resolves the SDK repo root automatically, so it still works if you launch it from another working directory via its full path.
+
+And open:
+- `results/booth_demo_live/booth_demo_poster.png`
+- `results/booth_demo_live/JURY_TALK_TRACK.md`
+- `results/booth_demo_live/BEURS_LIVE_DEMO_SCRIPT.txt`
+
+What makes this script good for a booth:
+- it visibly calls `run_full(...)`
+- it visibly calls `generate_results_poster(...)`
+- it visibly calls `prepare_ai_ready_artifacts(...)`
+- you can point to one patient setting and explain how the same pipeline reruns for another patient
+
+If you installed the SDK on another machine and do not have the repository checkout there, export the same demo code with:
+
+```bash
+iints demo-export --output-dir iints_demo
+cd iints_demo
+python 07_live_stage_demo.py
+```
+
 ## Updating The SDK
 
-If another machine is missing newer commands like `iints ai ...` or `iints demo-booth`, upgrade inside the active virtual environment:
+If another machine is missing newer commands like `iints ai ...` or `iints demo-booth`, upgrade inside the active virtual environment to the latest release:
 
 ```bash
 source .venv/bin/activate
 python -m pip install -U pip
-python -m pip install -U "iints-sdk-python35[mdmp]==1.3.1"
+python -m pip install -U "iints-sdk-python35[mdmp]"
 hash -r
 python -c "import iints; print(iints.__version__)"
 ```
@@ -209,6 +273,8 @@ iints-sdk-doctor
 Full guide:
 - `docs/UPDATING.md`
 
+If you specifically need to reproduce a known environment, you can pin an exact release number instead of using the unpinned upgrade command above.
+
 Troubleshooting:
 - If `iints ai ...` says `No such command 'ai'`, your environment usually still has a legacy `iints` package installed alongside `iints-sdk-python35`.
 - Run `iints-sdk-doctor` first.
@@ -216,7 +282,7 @@ Troubleshooting:
 
 ```bash
 python -m pip uninstall -y iints iints-sdk-python35
-python -m pip install -U "iints-sdk-python35[mdmp]==1.3.1"
+python -m pip install -U "iints-sdk-python35[mdmp]"
 hash -r
 ```
 
@@ -236,13 +302,13 @@ iints mdmp validate mdmp_contract.yaml data/my_cgm.csv --output-json results/mdm
 iints mdmp visualizer results/mdmp_report.json --output-html results/mdmp_dashboard.html
 ```
 
-Use standalone MDMP backend (optional):
+Use bundled `mdmp_core` backend (optional):
 
 ```bash
 export IINTS_MDMP_BACKEND=mdmp_core
 ```
 
-Staleness / lineage checks (standalone MDMP CLI):
+Staleness / lineage checks via the bundled `mdmp` CLI:
 
 ```bash
 mdmp fingerprint-record data/my_cgm.csv --output-json results/fingerprint.json --expires-days 365
@@ -252,21 +318,17 @@ mdmp registry init --registry registry/mdmp_registry.json
 mdmp registry push --registry registry/mdmp_registry.json --report results/mdmp_report.json
 ```
 
-## Dual Repo Workflow
-- SDK repo: `python35/IINTS-SDK`
-- MDMP repo: `python35/MDMP`
+## Bundled MDMP
 
-Local helper scripts:
-- `tools/dev/dual_repo_status.sh`
-- `tools/dev/dual_repo_commit_push.sh`
+MDMP now ships inside the SDK, so the SDK no longer depends on a separate public MDMP repository checkout.
 
-Full process: `docs/DUAL_REPO_WORKFLOW.md`
+That means:
+- `iints mdmp ...` stays available
+- the bundled `mdmp` CLI can still be used
+- local AI signing and verification can still use `mdmp_core`
 
-MDMP sync CI gate:
-- `.github/workflows/mdmp-sync.yml`
-- Uses private-repo checkout when `MDMP_REPO_TOKEN` is configured.
-- Falls back to `mdmp-protocol` from PyPI when checkout is unavailable.
-- Auto dependency updates for MDMP are handled via Dependabot (`.github/dependabot.yml`).
+Reference:
+- `docs/DUAL_REPO_WORKFLOW.md`
 
 ## Tools Layout
 

{iints_sdk_python35-1.3.1 → iints_sdk_python35-1.4.0}/pyproject.toml

@@ -1,15 +1,17 @@
 [build-system]
-requires = ["setuptools>=61.0"]
+requires = ["setuptools>=77.0.0"]
 build-backend = "setuptools.build_meta"
 
 [project]
 name = "iints-sdk-python35" 
-version = "1.3.1"
+version = "1.4.0"
 authors = [
   { name="Rune Bobbaers", email="rune.bobbaers@gmail.com" },
 ]
 description = "A pre-clinical Edge-AI SDK for diabetes management validation."
 readme = "README.md"
+license = "Apache-2.0"
+license-files = ["LICENSE", "NOTICE", "LICENSE-MIT-IINTS-LEGACY"]
 requires-python = ">=3.10"
 classifiers = [
     "Programming Language :: Python :: 3",
@@ -17,7 +19,6 @@ classifiers = [
     "Programming Language :: Python :: 3.11",
     "Programming Language :: Python :: 3.12",
     "Programming Language :: Python :: 3.13",
-    "License :: OSI Approved :: MIT License",
     "Operating System :: OS Independent",
     "Development Status :: 5 - Production/Stable",
 ]
@@ -60,12 +61,13 @@ research = [
   "onnxscript>=0.1.0",
 ]
 mdmp = [
-  "mdmp-protocol>=0.3.0",
+  "cryptography>=42.0.0",
 ]
 
 [project.scripts]
 iints = "iints.cli.cli:app"
 iints-sdk-doctor = "iints_sdk_python35_doctor:main"
+mdmp = "mdmp_core.cli:app"
 
 [project.entry-points."iints.algorithms"]
 "PID Controller" = "iints.core.algorithms.pid_controller:PIDController"
@@ -92,3 +94,7 @@ iints = [
   "presets/*.json",
   "presets/*.yaml",
 ]
+mdmp_core = [
+  "keys/*.pem",
+  "data/conformance/vectors/*.json",
+]

{iints_sdk_python35-1.3.1 → iints_sdk_python35-1.4.0}/src/iints/__init__.py

@@ -11,7 +11,7 @@ except ImportError:  # pragma: no cover - Python < 3.8 fallback
 try:
     __version__ = version("iints-sdk-python35")
 except PackageNotFoundError:  # pragma: no cover - source tree fallback
-    __version__ = "1.3.1"
+    __version__ = "1.4.0"
 
 # Note to developers: this SDK is currently maintained by a single author.
 # Please report bugs via GitHub issues and feel free to contribute fixes via PRs.