mesa-core 1.0.0__tar.gz

mesa_core-1.0.0/.claude/settings.local.json

@@ -0,0 +1,14 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(curl -s -o /dev/null -w \"%{http_code}\" https://pypi.org/pypi/mesa-core/json)",
+      "Bash(curl -s https://pypi.org/simple/mesa-core/ -H \"Accept: application/vnd.pypi.simple.v1+json\" -o /dev/null -w \"%{http_code}\")",
+      "Bash(curl -s https://raw.githubusercontent.com/home-assistant/core/dev/script/hassfest/manifest.py)",
+      "Bash(python3 -m venv .venv)",
+      "Bash(.venv/bin/pip -q install -e \".[dev]\")",
+      "Bash(.venv/bin/ruff check *)",
+      "Bash(.venv/bin/mypy)",
+      "Bash(.venv/bin/pytest tests/ -q)"
+    ]
+  }
+}

mesa_core-1.0.0/.github/workflows/ci.yml

@@ -0,0 +1,27 @@
+name: CI
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+    strategy:
+      fail-fast: false
+      matrix:
+        python-version: ["3.11", "3.12", "3.13", "3.14"]
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-python@v5
+        with:
+          python-version: ${{ matrix.python-version }}
+      - name: Install
+        run: pip install -e ".[dev,fastmcp,mcp]"
+      - name: Lint
+        run: ruff check .
+      - name: Type check
+        run: mypy
+      - name: Test
+        run: pytest tests/ -v

mesa_core-1.0.0/.gitignore

@@ -0,0 +1,13 @@
+__pycache__/
+*.py[cod]
+*.egg-info/
+dist/
+build/
+.venv/
+.mypy_cache/
+.ruff_cache/
+.pytest_cache/
+.DS_Store
+
+# Internal-only developer notes (not for publication)
+AUDIT-NOTES.md

mesa_core-1.0.0/CLAUDE.md

@@ -0,0 +1,61 @@
+## 1. Think Before Coding
+
+**Don't assume. Don't hide confusion. Surface tradeoffs.**
+
+Before implementing:
+- State your assumptions explicitly. If uncertain, ask.
+- If multiple interpretations exist, present them - don't pick silently.
+- If a simpler approach exists, say so. Push back when warranted.
+- If something is unclear, stop. Name what's confusing. Ask.
+
+## 2. Simplicity First
+
+**Minimum code that solves the problem. Nothing speculative.**
+
+- No features beyond what was asked.
+- No abstractions for single-use code.
+- No "flexibility" or "configurability" that wasn't requested.
+- No error handling for impossible scenarios.
+- If you write 200 lines and it could be 50, rewrite it.
+
+Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
+
+## 3. Surgical Changes
+
+**Touch only what you must. Clean up only your own mess.**
+
+When editing existing code:
+- Don't "improve" adjacent code, comments, or formatting.
+- Don't refactor things that aren't broken.
+- Match existing style, even if you'd do it differently.
+- If you notice unrelated dead code, mention it - and await instructions.
+
+When your changes create orphans:
+- Remove imports/variables/functions that YOUR changes made unused.
+- Don't remove pre-existing dead code unless asked.
+- Always mention orphans, and await instructions.
+
+The test: Every changed line should trace directly to the user's request.
+
+## 4. Goal-Driven Execution
+
+**Define success criteria. Loop until verified.**
+
+Transform tasks into verifiable goals:
+- "Add validation" → "Write tests for invalid inputs, then make them pass"
+- "Fix the bug" → "Write a test that reproduces it, then make it pass"
+- "Refactor X" → "Ensure tests pass before and after"
+
+For multi-step tasks, state a brief plan:
+```
+1. [Step] → verify: [check]
+2. [Step] → verify: [check]
+3. [Step] → verify: [check]
+```
+
+**Style and formatting:**
+- Never use em dashes (—) or en dashes (–) anywhere. Use commas, periods, hyphens, or semicolons instead.
+- Never use ASCII arrows (→) unless the character is specifically required by a protocol or format.
+- No emojis anywhere in source code, comments, or documentation, unless it is needed for UI output.
+- No forced line breaks in prose paragraphs in Markdown files.
+

mesa_core-1.0.0/CONTRIBUTING.md

@@ -0,0 +1,52 @@
+# Contributing to mesa-core
+
+Thanks for your interest in mesa-core. This is a short read, because the project has one rule that is easy to miss and shapes everything else.
+
+## mesa-core is a reference implementation, not a standalone library
+
+mesa-core implements the MESA Specification. As the spec states (Section 23, "Reference implementation"), when the specification and mesa-core behaviour diverge, the specification takes precedence. That changes what a contribution means here:
+
+- An implementation bug is code that does not match what the spec says. Fixing it is always welcome; open a pull request.
+
+- A behaviour or semantics change is a change to what the spec says should happen: anything that alters the effective profile a given input produces. These need a spec discussion first. Open an issue that cites the relevant spec section before sending a PR, so the spec and the implementation move together rather than drifting apart.
+
+If you are unsure which category your change falls into, open an issue and ask. That is never the wrong move.
+
+## Reporting a spec/implementation divergence
+
+If you find a place where mesa-core does something the spec does not describe, or contradicts it, that is a bug report worth filing on its own. Open a GitHub issue with the spec section, the observed behaviour, and a minimal profile that reproduces it.
+
+## Development setup
+
+The README has the canonical setup. In short:
+
+```bash
+git clone https://github.com/sfox38/mesa-core
+cd mesa-core
+pip install -e ".[dev]"
+```
+
+CI runs three gates on every push and pull request, across Python 3.11 through 3.14. Run them locally before you push:
+
+```bash
+ruff check .       # lint and import order
+mypy               # strict type checking
+pytest tests/ -v   # conformance suite
+```
+
+A change that touches resolution, enforcement, or validation should come with a conformance test under `tests/conformance/` that pins the behaviour, in the style of the existing tests.
+
+## Code style
+
+mesa-core favours small, surgical changes that match the surrounding code.
+
+- Keep changes minimal and traceable to a stated goal. Prefer the simplest code that solves the problem.
+- Safety logic is fail-closed: an evaluation that cannot be completed must tighten, never loosen. Preserve this property in anything you touch.
+
+## Versioning
+
+mesa-core follows the schema versioning in spec Section 23: patch (1.0.x) fixes errors, minor (1.x.0) adds optional fields, and major (x.0.0) may introduce breaking changes with a documented migration path.
+
+## License
+
+By contributing, you agree that your contributions are licensed under the Apache License 2.0, the same license as the project.

mesa_core-1.0.0/LICENSE

@@ -0,0 +1,196 @@
+                                 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 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, as defined in Section 5, any work of
+      authorship, including the original version of the Work and any
+      modifications or additions to that Work or Derivative Works of the
+      Work, that is intentionally submitted to the 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 designated in writing by the copyright owner as "Not a
+      Contribution."
+
+      "Contributor" shall mean Licensor and any Legal Entity on behalf of
+      whom a Contribution has been received by the Licensor and included
+      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, You must include a readable copy of the
+          attribution notices contained within such NOTICE file, 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 license statement for Your modifications and
+      may provide additional grant of rights to use, copy, modify, merge,
+      publish, distribute, sublicense, and/or sell copies of the Work,
+      subject to Your compliance with the terms of 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 reproducing 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 exemplary 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 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 charge a
+      fee on behalf to all other Contributors whose liability obligations
+      are not expressly stated in the License, but only on behalf of
+      parties exercising rights under this License, and only if You
+      accept that all such warranty or additional liability is solely
+      Your responsibility.
+
+   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 in use. An end-line or comment
+      delimiter may be needed for some file formats.
+
+   Copyright 2026 Steven Fox
+
+   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.

mesa_core-1.0.0/PKG-INFO

@@ -0,0 +1,143 @@
+Metadata-Version: 2.4
+Name: mesa-core
+Version: 1.0.0
+Summary: Reference implementation of the MESA specification: a semantic safety and coordination layer for AI-operated smart environments.
+Project-URL: Homepage, https://github.com/sfox38/mesa-core
+Project-URL: Documentation, https://github.com/sfox38/mesa-core/tree/main/documents
+Author-email: Steven Fox <sfox38@gmail.com>
+License: Apache-2.0
+License-File: LICENSE
+Keywords: ai-agents,home-assistant,mcp,semantics,smart-home
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Typing :: Typed
+Requires-Python: >=3.11
+Provides-Extra: dev
+Requires-Dist: jsonschema>=4; extra == 'dev'
+Requires-Dist: mypy>=1.11; extra == 'dev'
+Requires-Dist: pytest>=8; extra == 'dev'
+Requires-Dist: ruff>=0.6; extra == 'dev'
+Provides-Extra: fastmcp
+Requires-Dist: fastmcp; extra == 'fastmcp'
+Provides-Extra: mcp
+Requires-Dist: mcp; extra == 'mcp'
+Provides-Extra: test
+Requires-Dist: jsonschema>=4; extra == 'test'
+Requires-Dist: pytest>=8; extra == 'test'
+Description-Content-Type: text/markdown
+
+
+# mesa-core
+
+[![CI](https://github.com/sfox38/mesa-core/actions/workflows/ci.yml/badge.svg)](https://github.com/sfox38/mesa-core/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/mesa-core.svg)](https://pypi.org/project/mesa-core/)
+
+mesa-core decides whether an AI agent should be allowed to act on a smart-home device, and how cautious it should be about it.
+
+When an assistant tries to turn on a light, unlock the front door, or change the thermostat, mesa-core answers three questions: is this allowed, should the user confirm it first, and why. It ships with safe defaults (a light is fine to control automatically; unlike a lock) that you refine for each home.
+
+It is the reference implementation of the [MESA specification](documents/MESA-Specification.md). It has no runtime dependencies and never talks to Home Assistant directly: you hand it device state through callback functions, and it hands you decisions.
+
+```bash
+pip install mesa-core
+```
+
+## Quick look
+
+```python
+from mesa_core import MesaEnforcer, ProfileStore
+from mesa_core.backends import MemoryBackend
+
+enforcer = MesaEnforcer(ProfileStore(backend=MemoryBackend()))
+
+# An AI agent wants to unlock the front door. Should it?
+result = enforcer.evaluate("lock.front_door", "lock.unlock")
+
+result.allowed   # False
+result.reason    # "Entity is prohibited by policy: lock.front_door"
+```
+
+## How decisions work
+
+- Every device has a control mode: act freely, ask the user first, read-only, or never act.
+- Devices you have not configured fall back to safe defaults: lights act freely, locks and alarm panels are off-limits, everything else asks first.
+- Rules can be set for a single device, an area, or a whole device type, and are combined with a bias toward caution: the more restrictive rule wins, and anything that cannot be checked blocks rather than allows.
+- You can add finer limits (cap the speaker volume after 10pm) and time-based rules (no blinds before sunrise).
+
+## Asking the user to confirm
+
+When a device is set to confirm first, `evaluate` returns a challenge instead of a yes. Show the action to the user, then call again with the token from the approved challenge.
+
+```python
+result = enforcer.evaluate("cover.garage", "cover.open_cover")
+if result.confirmation_challenge:
+    # present result.confirmation_challenge to the user; once approved,
+    # build a confirmation_token from it and re-submit the same call:
+    result = enforcer.evaluate(
+        "cover.garage", "cover.open_cover",
+        confirmation_token=approved_token,
+    )
+```
+
+## Reading a device's profile
+
+`ProfileStore` resolves the effective profile after inheritance and defaults. Use a file backend to persist profiles under your HA config:
+
+```python
+from mesa_core import ProfileStore
+from mesa_core.backends import JsonFileBackend
+
+store = ProfileStore(backend=JsonFileBackend("/config/mesa/"))
+profile = store.get_effective("light.living_room_ceiling")
+profile.operational_boundaries.control_mode   # ControlMode.AUTONOMOUS
+```
+
+## Exposing it to an AI agent (MCP)
+
+Register MESA's tools into an MCP server so the agent can look up profiles and caller context for itself.
+
+```python
+from mesa_core.mcp import register_mesa_tools
+
+register_mesa_tools(store, adapter="fastmcp", server=app)
+```
+
+Adapters ship for FastMCP and the MCP Python SDK (`pip install "mesa-core[fastmcp]"` or `"mesa-core[mcp]"`). Any other framework can implement a small registration protocol.
+
+## Loading profiles shipped by integrations
+
+An HA integration can ship a `mesa_profile.json` describing its own devices. Load it with:
+
+```python
+from mesa_core import import_from_integration
+
+profile = import_from_integration("/config/custom_components/my_integration")
+if profile is not None:
+    store.set_domain_profile(profile.entity_id, profile)
+```
+
+## Documentation
+
+- [MESA Overview](documents/MESA-Overview.md) - the problem MESA solves, in plain terms
+- [Getting Started](documents/MESA-Getting-Started.md) - write your first profile
+- [Specification](documents/MESA-Specification.md) - the full normative reference
+- [Enrichment](documents/MESA-Enrichment.md) - optional advanced domains
+- [Module Proposal](documents/MESA-Module.md) - how this library is built
+
+## Status
+
+mesa-core v1.0 is ready for use: profile storage and inheritance, enforcement with confirmation, the MCP retrieval tools, and privacy controls are all implemented.
+
+```bash
+git clone https://github.com/sfox38/mesa-core
+cd mesa-core
+pip install -e ".[dev]"
+pytest tests/ -v       # test suite
+ruff check . && mypy   # lint and type check
+```

mesa_core-1.0.0/README.md

@@ -0,0 +1,109 @@
+
+# mesa-core
+
+[![CI](https://github.com/sfox38/mesa-core/actions/workflows/ci.yml/badge.svg)](https://github.com/sfox38/mesa-core/actions/workflows/ci.yml)
+[![PyPI](https://img.shields.io/pypi/v/mesa-core.svg)](https://pypi.org/project/mesa-core/)
+
+mesa-core decides whether an AI agent should be allowed to act on a smart-home device, and how cautious it should be about it.
+
+When an assistant tries to turn on a light, unlock the front door, or change the thermostat, mesa-core answers three questions: is this allowed, should the user confirm it first, and why. It ships with safe defaults (a light is fine to control automatically; unlike a lock) that you refine for each home.
+
+It is the reference implementation of the [MESA specification](documents/MESA-Specification.md). It has no runtime dependencies and never talks to Home Assistant directly: you hand it device state through callback functions, and it hands you decisions.
+
+```bash
+pip install mesa-core
+```
+
+## Quick look
+
+```python
+from mesa_core import MesaEnforcer, ProfileStore
+from mesa_core.backends import MemoryBackend
+
+enforcer = MesaEnforcer(ProfileStore(backend=MemoryBackend()))
+
+# An AI agent wants to unlock the front door. Should it?
+result = enforcer.evaluate("lock.front_door", "lock.unlock")
+
+result.allowed   # False
+result.reason    # "Entity is prohibited by policy: lock.front_door"
+```
+
+## How decisions work
+
+- Every device has a control mode: act freely, ask the user first, read-only, or never act.
+- Devices you have not configured fall back to safe defaults: lights act freely, locks and alarm panels are off-limits, everything else asks first.
+- Rules can be set for a single device, an area, or a whole device type, and are combined with a bias toward caution: the more restrictive rule wins, and anything that cannot be checked blocks rather than allows.
+- You can add finer limits (cap the speaker volume after 10pm) and time-based rules (no blinds before sunrise).
+
+## Asking the user to confirm
+
+When a device is set to confirm first, `evaluate` returns a challenge instead of a yes. Show the action to the user, then call again with the token from the approved challenge.
+
+```python
+result = enforcer.evaluate("cover.garage", "cover.open_cover")
+if result.confirmation_challenge:
+    # present result.confirmation_challenge to the user; once approved,
+    # build a confirmation_token from it and re-submit the same call:
+    result = enforcer.evaluate(
+        "cover.garage", "cover.open_cover",
+        confirmation_token=approved_token,
+    )
+```
+
+## Reading a device's profile
+
+`ProfileStore` resolves the effective profile after inheritance and defaults. Use a file backend to persist profiles under your HA config:
+
+```python
+from mesa_core import ProfileStore
+from mesa_core.backends import JsonFileBackend
+
+store = ProfileStore(backend=JsonFileBackend("/config/mesa/"))
+profile = store.get_effective("light.living_room_ceiling")
+profile.operational_boundaries.control_mode   # ControlMode.AUTONOMOUS
+```
+
+## Exposing it to an AI agent (MCP)
+
+Register MESA's tools into an MCP server so the agent can look up profiles and caller context for itself.
+
+```python
+from mesa_core.mcp import register_mesa_tools
+
+register_mesa_tools(store, adapter="fastmcp", server=app)
+```
+
+Adapters ship for FastMCP and the MCP Python SDK (`pip install "mesa-core[fastmcp]"` or `"mesa-core[mcp]"`). Any other framework can implement a small registration protocol.
+
+## Loading profiles shipped by integrations
+
+An HA integration can ship a `mesa_profile.json` describing its own devices. Load it with:
+
+```python
+from mesa_core import import_from_integration
+
+profile = import_from_integration("/config/custom_components/my_integration")
+if profile is not None:
+    store.set_domain_profile(profile.entity_id, profile)
+```
+
+## Documentation
+
+- [MESA Overview](documents/MESA-Overview.md) - the problem MESA solves, in plain terms
+- [Getting Started](documents/MESA-Getting-Started.md) - write your first profile
+- [Specification](documents/MESA-Specification.md) - the full normative reference
+- [Enrichment](documents/MESA-Enrichment.md) - optional advanced domains
+- [Module Proposal](documents/MESA-Module.md) - how this library is built
+
+## Status
+
+mesa-core v1.0 is ready for use: profile storage and inheritance, enforcement with confirmation, the MCP retrieval tools, and privacy controls are all implemented.
+
+```bash
+git clone https://github.com/sfox38/mesa-core
+cd mesa-core
+pip install -e ".[dev]"
+pytest tests/ -v       # test suite
+ruff check . && mypy   # lint and type check
+```

mesa_core-1.0.0/SECURITY.md

@@ -0,0 +1,49 @@
+# Security Policy
+
+mesa-core is a safety enforcement component: it decides whether an AI agent's action against a smart-home entity is permitted. A bug that causes it to allow something it should block is a security issue, not just a defect. This policy describes what to report and how.
+
+## Supported versions
+
+| Version | Supported |
+|---|---|
+| 1.0.x   | Yes       |
+| < 1.0   | No        |
+
+Security fixes are released as patch versions and noted in the changelog.
+
+## Reporting a vulnerability
+
+Please do not open a public issue for a suspected vulnerability.
+
+Report it privately by either:
+
+- GitHub's "Report a vulnerability" button under the repository's Security tab (a private advisory), or
+- email to sfox38@gmail.com with "mesa-core security" in the subject.
+
+Include the affected version, the impact, and a minimal profile plus service call that reproduces it. mesa-core has zero runtime dependencies, so a reproduction is usually a small self-contained Python snippet.
+
+This is a solo-maintained project. Expect an acknowledgement within five business days and an assessment of severity and fix timeline shortly after. Please allow a reasonable window for a fix before any public disclosure.
+
+## What is in scope
+
+The bug that matters most here is a fail-open: an outcome that should be denied but is allowed. For example:
+
+- A `control_mode: prohibited` or `read_only` entity that is nonetheless actionable in enforced mode.
+- An active `declared_limit`, `temporal_constraint`, or privacy classification that fails to apply when it should.
+- Conflict resolution (Rules A-E) loosening a value that should only tighten, for example an inherited `prohibited` being downgraded.
+- The confirmation protocol (Section 6.6) accepting a token that does not bind to the exact entity, service, and parameters challenged, or honouring a reused single-use token.
+- An evaluation error that opens access rather than failing closed.
+
+Reports framed against a specific spec section are the most actionable.
+
+## What is out of scope
+
+These are documented design boundaries, not vulnerabilities. They are described in spec Section 3 (Security Considerations) and the project's design notes:
+
+- Deliberately deceptive agents. MESA's threat model assumes cooperative agents. A malicious agent that ignores boundaries is out of scope at the metadata layer; Home Assistant's native access control is the required backstop. Enforced mode and native HA permissions are meant to be used together, and neither alone is sufficient.
+- Global state invariants across calls. mesa-core evaluates one call at a time. It does not solve cross-entity transition invariants (for example "never leave the door unlocked while the alarm is disarmed"); that is an automation-layer concern.
+- Non-canonical inputs. mesa-core matches service names, entity IDs, and state values exactly against their canonical Home Assistant forms. Canonicalising incoming calls before evaluation is the host's responsibility (spec Section 6); a non-canonical call that slips past a boundary is a host integration bug, not a mesa-core vulnerability.
+- Over-restriction via erroneous or poisoned profiles. A profile that wrongly over-restricts is handled by the removal path in spec Section 3, not as a security report.
+
+If you are unsure whether something is in scope, report it privately anyway and we will sort it out.
+