awp-python 0.1.0a1__tar.gz → 0.1.0a2__tar.gz

{awp_python-0.1.0a1 → awp_python-0.1.0a2}/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.1.0a2
+
+Targets specification revision `0.1-draft.8`.
+
+- `awp_sim`: the world checks the arm against its envelope after every step; leaving it emits `envelope_violation` and fails the executing action with reason `envelope` (AWP-ENV-003). `World.disturb` and `Server.disturb` inject an external disturbance.
+- `awp_sim`: a stop during servo motion ends at the envelope's boundary instead of past it.
+- `conformance/`: reports for Core World in both time models and the evidence for their manual rows, with tests in `tests/test_evidence.py`.
+
 ## 0.1.0a1
 
 First release, targeting specification revision `0.1-draft.7`.

{awp_python-0.1.0a1 → awp_python-0.1.0a2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: awp-python
-Version: 0.1.0a1
+Version: 0.1.0a2
 Summary: Agent World Protocol client protocol layer and reference world for Python.
 Project-URL: Specification, https://www.agentworldprotocol.com
 Project-URL: Source, https://github.com/Hyperduality/awp-python
@@ -26,11 +26,13 @@ Python implementation of the [Agent World Protocol](https://www.agentworldprotoc
 - **`awp`** — the client protocol layer. `ClientConnection` is the agent side of AWP as a sans-IO state machine; `awp.aio.AsyncClient` drives it over a WebSocket.
 - **`awp_sim`** — the reference world. A sans-IO world engine with a simulated arm, a WebSocket server, an audit log, and a scenario suite that records wire traces.
 
-It targets specification revision **`0.1-draft.7`**, pinned as the `spec/` submodule. This is an alpha: the API will change with the draft.
+It targets specification revision **`0.1-draft.8`**, pinned as the `spec/` submodule. This is an alpha: the API will change with the draft.
 
 ## Status
 
-The world and client target **Core World** and **Core Agent** for both time models, and the world the **sim** profile in lockstep, *self-assessed against 0.1-draft.7*: [awp-conformance](https://github.com/Hyperduality/awp-conformance) reports no failure against any configuration and leaves a few requirements untested. Every recorded trace also passes the spec's own checker, which verifies schemas, the action lifecycle table, idempotency, replay, and frame sequencing.
+![AWP: Core World, AWP-conformant against 0.1-draft.8](https://img.shields.io/badge/AWP-Core_World%2C_conformant_0.1--draft.8-555)
+
+The world is **Core World: AWP-conformant against 0.1-draft.8** in both time models: [awp-conformance](https://github.com/Hyperduality/awp-conformance) reports no failure and nothing untested, and [`conformance/`](conformance/README.md) holds the reports and the evidence for their manual rows. The **sim** profile in lockstep and the client as **Core Agent** in both time models are *self-assessed against 0.1-draft.8*: the suite reports no failure and leaves a few requirements untested. Every recorded trace also passes the spec's own checker, which verifies schemas, the action lifecycle table, idempotency, replay, and frame sequencing.
 
 | Implemented | Not implemented |
 |---|---|
@@ -38,7 +40,7 @@ The world and client target **Core World** and **Core Agent** for both time mode
 | Inline and `ws` stream bindings; binary frame codec (all spec vectors) | Other stream bindings (`webrtc`, `webtransport`, `shm`, `grpc`) |
 | Full action lifecycle; preemption (`replace`, `queue`, `reject`, `blend`); idempotency | Standing approvals, grant expiry |
 | Watchdog and safe state, heartbeats, resumption with replay and acknowledgement | Multi-bind and shared control (one embodiment) |
-| Spatial, velocity, and rate envelopes (`command_check`) | Robotics profile (a simulated arm proves nothing physical) |
+| Spatial, velocity, and rate envelopes (`command_check`), monitored during execution | Robotics profile (a simulated arm proves nothing physical) |
 | Audit log with redaction and hash chain; e-stop; `world.reset` | |
 | Beyond Core (`--features`): task, approval, transfer, seeding, snapshots, replay bundles, a servo command channel | |
 
@@ -107,7 +109,7 @@ The connection tracks the action lifecycle against the spec's transition table,
 src/awp/            client protocol layer (sans-IO), asyncio adapter, frame codec, schemas
 src/awp/_spec/      schemas and lifecycle table bundled from spec/ (scripts/sync_spec.py)
 src/awp_sim/        world engine, arm, server, audit log, loopback, scenarios, CLI
-spec/               agent-world-protocol, pinned at spec-v0.1-draft.7
+spec/               agent-world-protocol, pinned at spec-v0.1-draft.8
 scripts/            spec sync and trace checking
 ```
 

{awp_python-0.1.0a1 → awp_python-0.1.0a2}/README.md

@@ -5,11 +5,13 @@ Python implementation of the [Agent World Protocol](https://www.agentworldprotoc
 - **`awp`** — the client protocol layer. `ClientConnection` is the agent side of AWP as a sans-IO state machine; `awp.aio.AsyncClient` drives it over a WebSocket.
 - **`awp_sim`** — the reference world. A sans-IO world engine with a simulated arm, a WebSocket server, an audit log, and a scenario suite that records wire traces.
 
-It targets specification revision **`0.1-draft.7`**, pinned as the `spec/` submodule. This is an alpha: the API will change with the draft.
+It targets specification revision **`0.1-draft.8`**, pinned as the `spec/` submodule. This is an alpha: the API will change with the draft.
 
 ## Status
 
-The world and client target **Core World** and **Core Agent** for both time models, and the world the **sim** profile in lockstep, *self-assessed against 0.1-draft.7*: [awp-conformance](https://github.com/Hyperduality/awp-conformance) reports no failure against any configuration and leaves a few requirements untested. Every recorded trace also passes the spec's own checker, which verifies schemas, the action lifecycle table, idempotency, replay, and frame sequencing.
+![AWP: Core World, AWP-conformant against 0.1-draft.8](https://img.shields.io/badge/AWP-Core_World%2C_conformant_0.1--draft.8-555)
+
+The world is **Core World: AWP-conformant against 0.1-draft.8** in both time models: [awp-conformance](https://github.com/Hyperduality/awp-conformance) reports no failure and nothing untested, and [`conformance/`](conformance/README.md) holds the reports and the evidence for their manual rows. The **sim** profile in lockstep and the client as **Core Agent** in both time models are *self-assessed against 0.1-draft.8*: the suite reports no failure and leaves a few requirements untested. Every recorded trace also passes the spec's own checker, which verifies schemas, the action lifecycle table, idempotency, replay, and frame sequencing.
 
 | Implemented | Not implemented |
 |---|---|
@@ -17,7 +19,7 @@ The world and client target **Core World** and **Core Agent** for both time mode
 | Inline and `ws` stream bindings; binary frame codec (all spec vectors) | Other stream bindings (`webrtc`, `webtransport`, `shm`, `grpc`) |
 | Full action lifecycle; preemption (`replace`, `queue`, `reject`, `blend`); idempotency | Standing approvals, grant expiry |
 | Watchdog and safe state, heartbeats, resumption with replay and acknowledgement | Multi-bind and shared control (one embodiment) |
-| Spatial, velocity, and rate envelopes (`command_check`) | Robotics profile (a simulated arm proves nothing physical) |
+| Spatial, velocity, and rate envelopes (`command_check`), monitored during execution | Robotics profile (a simulated arm proves nothing physical) |
 | Audit log with redaction and hash chain; e-stop; `world.reset` | |
 | Beyond Core (`--features`): task, approval, transfer, seeding, snapshots, replay bundles, a servo command channel | |
 
@@ -86,7 +88,7 @@ The connection tracks the action lifecycle against the spec's transition table,
 src/awp/            client protocol layer (sans-IO), asyncio adapter, frame codec, schemas
 src/awp/_spec/      schemas and lifecycle table bundled from spec/ (scripts/sync_spec.py)
 src/awp_sim/        world engine, arm, server, audit log, loopback, scenarios, CLI
-spec/               agent-world-protocol, pinned at spec-v0.1-draft.7
+spec/               agent-world-protocol, pinned at spec-v0.1-draft.8
 scripts/            spec sync and trace checking
 ```
 

awp_python-0.1.0a2/conformance/README.md

@@ -0,0 +1,63 @@
+# Conformance
+
+![AWP: Core World, AWP-conformant against 0.1-draft.8](https://img.shields.io/badge/AWP-Core_World%2C_conformant_0.1--draft.8-555)
+
+| Class | Configuration | Claim | Report |
+|---|---|---|---|
+| Core World | `awp-sim serve --mode lockstep` | Core World (lockstep): AWP-conformant against 0.1-draft.8 (awp-conformance 0.1.0a2) | [`core-world-lockstep.json`](core-world-lockstep.json) |
+| Core World | `awp-sim serve` | Core World (streaming): AWP-conformant against 0.1-draft.8 (awp-conformance 0.1.0a2) | [`core-world-streaming.json`](core-world-streaming.json) |
+
+Each report, from awp-conformance 0.1.0a2 against awp-python 0.1.0a2, has no failure and nothing untested; the evidence for its `manual` rows follows (AWP-CNF-005). Every other configuration remains self-assessed against 0.1-draft.8.
+
+## Reproduce
+
+```bash
+pip install --pre awp-python awp-conformance
+curl -LO https://raw.githubusercontent.com/Hyperduality/awp-conformance/v0.1.0a2/fixtures/awp-sim.json
+awp-sim serve --mode lockstep &          # or `awp-sim serve` for streaming
+export AWP_SIM_PID=$!
+awp-conformance world ws://127.0.0.1:8710 --fixture awp-sim.json --out report/
+```
+
+The fixture's e-stop hooks signal `$AWP_SIM_PID`; without it the e-stop test is skipped and AWP-EVT-002 is reported untested. The tests cited below run in this repository's CI:
+
+```bash
+uv run pytest tests/test_frames.py tests/test_evidence.py
+```
+
+## Manual evidence
+
+### AWP-DAT-002, AWP-TRN-009 — latest-wins delivery (streaming)
+
+- **Drop policy.** Each connection's send queue (`_Outbox`, [`src/awp_sim/server.py`](../src/awp_sim/server.py)) holds at most one unsent frame per latest-wins channel and replaces it when a newer one is produced; control messages and reliable frames queue in order, so a stalled latest-wins channel delays them by at most its one pending frame. A peer that stops reading is disconnected at 10,000 pending items rather than buffered without limit.
+- **Stalled-receiver test.** `test_a_stalled_receiver_holds_one_frame_per_latest_wins_channel`: 1,000 `proprio` frames and 10 `arm_state` frames are produced while nothing drains the queue; one `proprio` frame, the newest, and all 10 `arm_state` frames remain, in order.
+
+### AWP-DAT-008 — frame test vectors
+
+`test_vectors` (`tests/test_frames.py`) decodes every vector in `schemas/test-vectors/frames.json` of the `spec/` submodule, pinned at `spec-v0.1-draft.8`: the 10 valid vectors to the listed fields, and the 7 marked `expect_error` rejected with the listed error. `test_roundtrip_without_vendor` re-encodes the 8 valid vectors without an unknown extension or reserved bits byte for byte.
+
+### AWP-ENV-003 — envelope violations during execution
+
+After every simulation step the world checks the arm against its envelope: position within `aabb_m`, speed within `max_velocity_mps`. On leaving it, the world stops the arm, emits `world.event: envelope_violation` to every session, and fails the executing action with reason `envelope` once its safe abort completes. An external disturbance is injected with `World.disturb(offset_m)` (or `Server.disturb`).
+
+- `test_a_disturbance_during_execution_fails_the_action`: in each time model, a move is executing when the arm is pushed out of the envelope; the world emits `envelope_violation` and the move ends `failed` with reason `envelope`.
+- `test_commanded_motion_never_leaves_the_envelope`: 400 seeded random submissions, replacements, queued moves, stops, and cancels in each time model, checked after every advance; no violation is reported.
+- `test_servo_motion_never_leaves_the_envelope`: servo setpoints toward the walls, and stops during them.
+
+### AWP-UNI-001 — SI units and unit suffixes
+
+The fields awp-sim defines, reviewed:
+
+| Field | Where | Unit |
+|---|---|---|
+| `p_m` | `proprio` payload | m |
+| `v_mps` | `proprio` payload; `servo_arm` setpoints | m/s |
+| `target_m` | `arm_state` payload | m |
+| `max_velocity_mps` | `move_to_pose` params | m/s |
+| `phase`, `action_id` | `arm_state` payload | not physical |
+
+Every other field is defined by the specification's schemas. `test_world_defined_fields_carry_si_suffixes` collects every action parameter, channel schema field, and payload field across every feature, and fails on any field not reviewed as non-physical that lacks a unit suffix.
+
+### AWP-VER-009 — the draft revision is named
+
+The [README](../README.md) and the [awp-sim page](https://www.agentworldprotocol.com/adapters/awp-sim) name `0.1-draft.8`; `awp.SPEC_REVISION` is `"0.1-draft.8"`; the `spec/` submodule is pinned at the tag `spec-v0.1-draft.8`; each report records `"specification": "0.1-draft.8"` and its claim names the revision.