mpac 0.1.0__tar.gz

mpac-0.1.0/LICENSE

@@ -0,0 +1,190 @@
+                                 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 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 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 the 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 any 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
+
+   Copyright 2026 Kaiyang Qian
+
+   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.

mpac-0.1.0/PKG-INFO

@@ -0,0 +1,260 @@
+Metadata-Version: 2.4
+Name: mpac
+Version: 0.1.0
+Summary: MPAC (Multi-Principal Agent Coordination Protocol) — coordinate multiple AI agents serving different principals over shared state
+Author-email: Kaiyang Qian <kaiyang.2.qian@ucdenver.edu>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/KaiyangQ/mpac-protocol
+Project-URL: Repository, https://github.com/KaiyangQ/mpac-protocol
+Project-URL: Specification, https://github.com/KaiyangQ/mpac-protocol/blob/main/SPEC.md
+Project-URL: Two-machine demo, https://github.com/KaiyangQ/mpac-protocol/tree/main/examples/two_machine_demo
+Project-URL: Issues, https://github.com/KaiyangQ/mpac-protocol/issues
+Keywords: mpac,multi-agent,agent-coordination,ai-agents,llm,claude,protocol,coordination,mcp,a2a
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.9
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Scientific/Engineering :: Artificial Intelligence
+Classifier: Topic :: Software Development :: Libraries :: Python Modules
+Classifier: Topic :: System :: Distributed Computing
+Requires-Python: >=3.9
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: websockets>=12.0
+Requires-Dist: anthropic>=0.40.0
+Dynamic: license-file
+
+# mpac-protocol
+
+**Multi-Principal Agent Coordination Protocol — Python reference runtime.**
+
+When multiple AI agents — each serving a different person, team, or
+organization — need to work together over shared state, existing
+protocols come up short. MCP standardizes how one agent invokes tools;
+A2A standardizes how one orchestrator delegates to its own workers;
+neither covers what happens when two agents from *different* principals
+meet as peers over a shared repository, a shared itinerary, a shared
+contract draft, or any other piece of state that neither principal
+controls alone.
+
+**MPAC** is the application-layer protocol that fills that gap. It
+defines how agents declare intent before acting, how the coordinator
+surfaces overlap as structured conflicts, how those conflicts get
+resolved with explicit governance authority, and how every consequential
+action carries causal context for after-the-fact audit across
+organizational boundaries.
+
+This package is the Python reference runtime: a WebSocket coordinator,
+an interactive Claude-backed agent, and the full protocol state machine
+from the specification.
+
+## Install
+
+```bash
+pip install mpac
+```
+
+Python 3.9+ required. The package depends on `websockets` and
+`anthropic`; bring your own Anthropic API key.
+
+## Minimal example
+
+Host side — start a coordinator that shares any directory on your
+machine:
+
+```python
+import asyncio
+from mpac_protocol import MPACServer
+
+async def main():
+    server = MPACServer(
+        session_id="collab-session-001",
+        host="0.0.0.0",
+        port=8766,
+        workspace_dir="/path/to/any/directory/you/want/to/share",
+    )
+    await server.run()
+
+asyncio.run(main())
+```
+
+The loader walks `workspace_dir` recursively and safely skips VCS
+metadata (`.git`, `.hg`), build caches (`__pycache__`, `node_modules`,
+`.venv`, `dist`, `build`, …), IDE configs, OS cruft, and binary files.
+Whatever text files remain become the shared workspace. The pip package
+does **not** bundle any workspace files of its own.
+
+Guest side — connect an interactive agent to someone else's
+coordinator:
+
+```python
+import asyncio
+from mpac_protocol import MPACAgent
+
+async def main():
+    agent = MPACAgent(
+        name="Bob",
+        api_key="sk-ant-...",
+        model="claude-sonnet-4-6",
+        role_description="Collaborative AI agent operated by Bob",
+        roles=["contributor"],       # optional: owner, arbiter, contributor
+        principal_id="agent:Bob",    # optional: custom identity
+    )
+    await agent.connect("ws://192.168.1.42:8766", "collab-session-001")
+    await agent.run_interactive()
+    await agent.close()
+
+asyncio.run(main())
+```
+
+## Two-machine worked example
+
+A complete, copy-paste end-to-end example for two people on two
+different computers lives in the repo at
+[`examples/two_machine_demo/`](https://github.com/KaiyangQ/mpac-protocol/tree/main/examples/two_machine_demo).
+It ships a host `run.py`, a guest `run.py`, a sample workspace with
+three buggy Python files, and a README walking through both LAN mode
+(same WiFi) and Internet mode (ngrok).
+
+Clone and try it:
+
+```bash
+git clone https://github.com/KaiyangQ/mpac-protocol.git mpac
+cd mpac/examples/two_machine_demo/host
+cp config.example.json config.json   # add your Anthropic API key
+python run.py                        # prints the WebSocket URL to share
+```
+
+## API reference
+
+### MPACServer
+
+```python
+MPACServer(
+    session_id:    str,
+    host:          str  = "0.0.0.0",
+    port:          int  = 8766,
+    workspace_dir: str | None = None,   # directory to share; None = empty workspace
+    # Optional coordinator tuning (passed via **kwargs):
+    execution_model:          str   = "post_commit",   # or "pre_commit"
+    compliance_profile:       str   = "core",           # or "governance"
+    security_profile:         str   = "open",           # or "authenticated", "verified"
+    unavailability_timeout_sec: float = 90.0,
+    resolution_timeout_sec:     float = 300.0,
+    intent_claim_grace_sec:     float = 0.0,
+    role_policy:              dict | None = None,
+)
+```
+
+Call `await server.run()` to start listening. The server loads every
+text file under `workspace_dir` into an in-memory `FileStore`, skipping
+VCS metadata, build caches, and binary files automatically.
+
+### MPACAgent
+
+```python
+MPACAgent(
+    name:             str,
+    api_key:          str,               # Anthropic API key
+    model:            str  = "claude-sonnet-4-6",
+    role_description: str | None = None,
+    roles:            list[str] | None = None,       # default: ["contributor"]
+    principal_id:     str | None = None,              # default: "agent:{name}"
+)
+```
+
+#### Connection
+
+```python
+await agent.connect(
+    uri:           str,            # ws:// or wss:// — any WebSocket endpoint
+    session_id:    str,
+    extra_headers: dict | None = None,  # transport-specific HTTP headers
+)
+```
+
+The protocol is transport-agnostic. Pass any reachable WebSocket URI —
+LAN address, SSH tunnel, Cloudflare Tunnel, Tailscale, or any relay
+service. Use `extra_headers` for transports that require custom HTTP
+headers during the handshake.
+
+#### High-level workflows
+
+| Method | Description |
+|--------|------------|
+| `run_interactive()` | Interactive CLI: view files, give tasks, see diffs |
+| `execute_task(task)` | Programmatic: intent → conflict check → fix → commit |
+| `run_task(task)` | Full lifecycle: HELLO → execute_task → GOODBYE |
+
+#### Extended protocol operations
+
+| Method | Protocol Feature |
+|--------|-----------------|
+| `do_propose(intent_id, op_id, target)` | Pre-commit authorization (OP_PROPOSE) |
+| `propose_and_commit(...)` | Complete pre-commit flow (propose → auth → commit) |
+| `do_claim_intent(...)` | Fault recovery: take over a crashed agent's intent |
+| `do_escalate_conflict(...)` | Escalate a dispute to a designated arbiter |
+| `do_resolve_conflict(...)` | Arbiter renders a binding resolution |
+| `do_ack_conflict(...)` | Acknowledge or dispute a conflict |
+| `do_heartbeat(status)` | Maintain liveness |
+| `do_update_intent(...)` | Modify intent scope or objective mid-session |
+
+### Lower-level building blocks
+
+If you want to embed MPAC into your own agent runtime instead of using
+`MPACAgent`, the `mpac_protocol.core` module exposes:
+`SessionCoordinator`, state machines, envelopes, scope objects,
+watermarks, and principal models.
+
+## Protocol specification
+
+The full normative specification is [`SPEC.md`](https://github.com/KaiyangQ/mpac-protocol/blob/main/SPEC.md)
+on the `opensource` branch — 30 sections covering all five layers
+(Session, Intent, Operation, Conflict, Governance), 21 message types,
+three state machines with normative transition tables, two execution
+models (pre-commit / post-commit), three security profiles (open /
+authenticated / verified), Lamport-clock causal watermarking,
+optimistic concurrency control, and Backend Health Monitoring.
+
+The runtime in this package is faithful to that specification and is
+cross-tested against an independent TypeScript reference implementation
+in the same repository (14 messages exchanged bidirectionally with
+byte-identical wire format).
+
+## Scope — protocol, not platform
+
+MPAC defines **what agents say to each other**: intent declarations,
+conflict detection, resolution negotiation, causal-context commits, and
+governance authority. It does not prescribe how the underlying network
+is provisioned. The reference runtime uses WebSocket as a convenient
+default transport, but the coordinator can sit behind any infrastructure
+you choose — a LAN socket, an SSH tunnel, a cloud relay, a mesh VPN, or
+a managed WebSocket service. Networking, deployment topology, and
+infrastructure automation are engineering concerns outside the protocol
+boundary; MPAC intentionally stays silent on them so that implementers
+are free to make their own trade-offs.
+
+## Status
+
+**Draft / experimental.** The protocol is at v0.1.13. This package is
+at 0.1.0. Not yet stable for production interoperability — intended for
+reference implementations, research prototypes, and early ecosystem
+feedback.
+
+## License
+
+Apache-2.0. See [`LICENSE`](https://github.com/KaiyangQ/mpac-protocol/blob/main/LICENSE).
+
+## Links
+
+- [GitHub repository](https://github.com/KaiyangQ/mpac-protocol)
+- [v0.1.13 release notes](https://github.com/KaiyangQ/mpac-protocol/releases/tag/v0.1.13)
+- [Specification (SPEC.md)](https://github.com/KaiyangQ/mpac-protocol/blob/main/SPEC.md)
+- [Two-machine demo](https://github.com/KaiyangQ/mpac-protocol/tree/main/examples/two_machine_demo)
+- [Report an issue](https://github.com/KaiyangQ/mpac-protocol/issues)

mpac-0.1.0/README.md

@@ -0,0 +1,228 @@
+# mpac-protocol
+
+**Multi-Principal Agent Coordination Protocol — Python reference runtime.**
+
+When multiple AI agents — each serving a different person, team, or
+organization — need to work together over shared state, existing
+protocols come up short. MCP standardizes how one agent invokes tools;
+A2A standardizes how one orchestrator delegates to its own workers;
+neither covers what happens when two agents from *different* principals
+meet as peers over a shared repository, a shared itinerary, a shared
+contract draft, or any other piece of state that neither principal
+controls alone.
+
+**MPAC** is the application-layer protocol that fills that gap. It
+defines how agents declare intent before acting, how the coordinator
+surfaces overlap as structured conflicts, how those conflicts get
+resolved with explicit governance authority, and how every consequential
+action carries causal context for after-the-fact audit across
+organizational boundaries.
+
+This package is the Python reference runtime: a WebSocket coordinator,
+an interactive Claude-backed agent, and the full protocol state machine
+from the specification.
+
+## Install
+
+```bash
+pip install mpac
+```
+
+Python 3.9+ required. The package depends on `websockets` and
+`anthropic`; bring your own Anthropic API key.
+
+## Minimal example
+
+Host side — start a coordinator that shares any directory on your
+machine:
+
+```python
+import asyncio
+from mpac_protocol import MPACServer
+
+async def main():
+    server = MPACServer(
+        session_id="collab-session-001",
+        host="0.0.0.0",
+        port=8766,
+        workspace_dir="/path/to/any/directory/you/want/to/share",
+    )
+    await server.run()
+
+asyncio.run(main())
+```
+
+The loader walks `workspace_dir` recursively and safely skips VCS
+metadata (`.git`, `.hg`), build caches (`__pycache__`, `node_modules`,
+`.venv`, `dist`, `build`, …), IDE configs, OS cruft, and binary files.
+Whatever text files remain become the shared workspace. The pip package
+does **not** bundle any workspace files of its own.
+
+Guest side — connect an interactive agent to someone else's
+coordinator:
+
+```python
+import asyncio
+from mpac_protocol import MPACAgent
+
+async def main():
+    agent = MPACAgent(
+        name="Bob",
+        api_key="sk-ant-...",
+        model="claude-sonnet-4-6",
+        role_description="Collaborative AI agent operated by Bob",
+        roles=["contributor"],       # optional: owner, arbiter, contributor
+        principal_id="agent:Bob",    # optional: custom identity
+    )
+    await agent.connect("ws://192.168.1.42:8766", "collab-session-001")
+    await agent.run_interactive()
+    await agent.close()
+
+asyncio.run(main())
+```
+
+## Two-machine worked example
+
+A complete, copy-paste end-to-end example for two people on two
+different computers lives in the repo at
+[`examples/two_machine_demo/`](https://github.com/KaiyangQ/mpac-protocol/tree/main/examples/two_machine_demo).
+It ships a host `run.py`, a guest `run.py`, a sample workspace with
+three buggy Python files, and a README walking through both LAN mode
+(same WiFi) and Internet mode (ngrok).
+
+Clone and try it:
+
+```bash
+git clone https://github.com/KaiyangQ/mpac-protocol.git mpac
+cd mpac/examples/two_machine_demo/host
+cp config.example.json config.json   # add your Anthropic API key
+python run.py                        # prints the WebSocket URL to share
+```
+
+## API reference
+
+### MPACServer
+
+```python
+MPACServer(
+    session_id:    str,
+    host:          str  = "0.0.0.0",
+    port:          int  = 8766,
+    workspace_dir: str | None = None,   # directory to share; None = empty workspace
+    # Optional coordinator tuning (passed via **kwargs):
+    execution_model:          str   = "post_commit",   # or "pre_commit"
+    compliance_profile:       str   = "core",           # or "governance"
+    security_profile:         str   = "open",           # or "authenticated", "verified"
+    unavailability_timeout_sec: float = 90.0,
+    resolution_timeout_sec:     float = 300.0,
+    intent_claim_grace_sec:     float = 0.0,
+    role_policy:              dict | None = None,
+)
+```
+
+Call `await server.run()` to start listening. The server loads every
+text file under `workspace_dir` into an in-memory `FileStore`, skipping
+VCS metadata, build caches, and binary files automatically.
+
+### MPACAgent
+
+```python
+MPACAgent(
+    name:             str,
+    api_key:          str,               # Anthropic API key
+    model:            str  = "claude-sonnet-4-6",
+    role_description: str | None = None,
+    roles:            list[str] | None = None,       # default: ["contributor"]
+    principal_id:     str | None = None,              # default: "agent:{name}"
+)
+```
+
+#### Connection
+
+```python
+await agent.connect(
+    uri:           str,            # ws:// or wss:// — any WebSocket endpoint
+    session_id:    str,
+    extra_headers: dict | None = None,  # transport-specific HTTP headers
+)
+```
+
+The protocol is transport-agnostic. Pass any reachable WebSocket URI —
+LAN address, SSH tunnel, Cloudflare Tunnel, Tailscale, or any relay
+service. Use `extra_headers` for transports that require custom HTTP
+headers during the handshake.
+
+#### High-level workflows
+
+| Method | Description |
+|--------|------------|
+| `run_interactive()` | Interactive CLI: view files, give tasks, see diffs |
+| `execute_task(task)` | Programmatic: intent → conflict check → fix → commit |
+| `run_task(task)` | Full lifecycle: HELLO → execute_task → GOODBYE |
+
+#### Extended protocol operations
+
+| Method | Protocol Feature |
+|--------|-----------------|
+| `do_propose(intent_id, op_id, target)` | Pre-commit authorization (OP_PROPOSE) |
+| `propose_and_commit(...)` | Complete pre-commit flow (propose → auth → commit) |
+| `do_claim_intent(...)` | Fault recovery: take over a crashed agent's intent |
+| `do_escalate_conflict(...)` | Escalate a dispute to a designated arbiter |
+| `do_resolve_conflict(...)` | Arbiter renders a binding resolution |
+| `do_ack_conflict(...)` | Acknowledge or dispute a conflict |
+| `do_heartbeat(status)` | Maintain liveness |
+| `do_update_intent(...)` | Modify intent scope or objective mid-session |
+
+### Lower-level building blocks
+
+If you want to embed MPAC into your own agent runtime instead of using
+`MPACAgent`, the `mpac_protocol.core` module exposes:
+`SessionCoordinator`, state machines, envelopes, scope objects,
+watermarks, and principal models.
+
+## Protocol specification
+
+The full normative specification is [`SPEC.md`](https://github.com/KaiyangQ/mpac-protocol/blob/main/SPEC.md)
+on the `opensource` branch — 30 sections covering all five layers
+(Session, Intent, Operation, Conflict, Governance), 21 message types,
+three state machines with normative transition tables, two execution
+models (pre-commit / post-commit), three security profiles (open /
+authenticated / verified), Lamport-clock causal watermarking,
+optimistic concurrency control, and Backend Health Monitoring.
+
+The runtime in this package is faithful to that specification and is
+cross-tested against an independent TypeScript reference implementation
+in the same repository (14 messages exchanged bidirectionally with
+byte-identical wire format).
+
+## Scope — protocol, not platform
+
+MPAC defines **what agents say to each other**: intent declarations,
+conflict detection, resolution negotiation, causal-context commits, and
+governance authority. It does not prescribe how the underlying network
+is provisioned. The reference runtime uses WebSocket as a convenient
+default transport, but the coordinator can sit behind any infrastructure
+you choose — a LAN socket, an SSH tunnel, a cloud relay, a mesh VPN, or
+a managed WebSocket service. Networking, deployment topology, and
+infrastructure automation are engineering concerns outside the protocol
+boundary; MPAC intentionally stays silent on them so that implementers
+are free to make their own trade-offs.
+
+## Status
+
+**Draft / experimental.** The protocol is at v0.1.13. This package is
+at 0.1.0. Not yet stable for production interoperability — intended for
+reference implementations, research prototypes, and early ecosystem
+feedback.
+
+## License
+
+Apache-2.0. See [`LICENSE`](https://github.com/KaiyangQ/mpac-protocol/blob/main/LICENSE).
+
+## Links
+
+- [GitHub repository](https://github.com/KaiyangQ/mpac-protocol)
+- [v0.1.13 release notes](https://github.com/KaiyangQ/mpac-protocol/releases/tag/v0.1.13)
+- [Specification (SPEC.md)](https://github.com/KaiyangQ/mpac-protocol/blob/main/SPEC.md)
+- [Two-machine demo](https://github.com/KaiyangQ/mpac-protocol/tree/main/examples/two_machine_demo)
+- [Report an issue](https://github.com/KaiyangQ/mpac-protocol/issues)