bitspark-bitwire 0.5.0__tar.gz → 0.7.0__tar.gz

{bitspark_bitwire-0.5.0/src/bitspark_bitwire.egg-info → bitspark_bitwire-0.7.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: bitspark-bitwire
-Version: 0.5.0
+Version: 0.7.0
 Summary: Addressless wires and addressed access over ontos values
 Author: Bitspark
 License-Expression: Apache-2.0
@@ -28,3 +28,12 @@ values (a nominal interface in Java), not opaque route access.
 See the repository's docs/wire/contract.md and docs/wire/carriers.md. Version 0.5.0
 is a clean breaking replacement; compilation and packaged consumers check the
 native surface, while bitruntime supplies independently tested implementations.
+
+The public hydrated declarations add recursive atoms, tuples and send-only live
+wires above the ground boundary. HydratedEndpoint retains receive/lifetime
+ownership; its wire view conveys only sending. Arrival context is established by
+composition outside the message. Runtime construction and recognition enforce
+finite immutable tuples, ground canonicalization and owned capability identity;
+implementing a native interface alone does not make a foreign object exportable.
+See [hydrated native contracts](../../docs/wire/hydrated-native.md) and
+[decision 0019](../../docs/decisions/0019-hydrated-wire-protocol.md).

bitspark_bitwire-0.7.0/README.md

@@ -0,0 +1,19 @@
+# py wire presentation
+
+Addressless Wire sends a ground ontos value. Endpoint adds receive ownership and
+closure. AddressedWire adds an exact byte-path argument; AddressedEndpoint carries
+that layer over one endpoint. WireNode is the complete deixis structure over Wire
+values (a nominal interface in Java), not opaque route access.
+
+See the repository's docs/wire/contract.md and docs/wire/carriers.md. Version 0.5.0
+is a clean breaking replacement; compilation and packaged consumers check the
+native surface, while bitruntime supplies independently tested implementations.
+
+The public hydrated declarations add recursive atoms, tuples and send-only live
+wires above the ground boundary. HydratedEndpoint retains receive/lifetime
+ownership; its wire view conveys only sending. Arrival context is established by
+composition outside the message. Runtime construction and recognition enforce
+finite immutable tuples, ground canonicalization and owned capability identity;
+implementing a native interface alone does not make a foreign object exportable.
+See [hydrated native contracts](../../docs/wire/hydrated-native.md) and
+[decision 0019](../../docs/decisions/0019-hydrated-wire-protocol.md).

{bitspark_bitwire-0.5.0 → bitspark_bitwire-0.7.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "bitspark-bitwire"
-version = "0.5.0"
+version = "0.7.0"
 description = "Addressless wires and addressed access over ontos values"
 readme = "README.md"
 requires-python = ">=3.11"

{bitspark_bitwire-0.5.0 → bitspark_bitwire-0.7.0/src/bitspark_bitwire.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: bitspark-bitwire
-Version: 0.5.0
+Version: 0.7.0
 Summary: Addressless wires and addressed access over ontos values
 Author: Bitspark
 License-Expression: Apache-2.0
@@ -28,3 +28,12 @@ values (a nominal interface in Java), not opaque route access.
 See the repository's docs/wire/contract.md and docs/wire/carriers.md. Version 0.5.0
 is a clean breaking replacement; compilation and packaged consumers check the
 native surface, while bitruntime supplies independently tested implementations.
+
+The public hydrated declarations add recursive atoms, tuples and send-only live
+wires above the ground boundary. HydratedEndpoint retains receive/lifetime
+ownership; its wire view conveys only sending. Arrival context is established by
+composition outside the message. Runtime construction and recognition enforce
+finite immutable tuples, ground canonicalization and owned capability identity;
+implementing a native interface alone does not make a foreign object exportable.
+See [hydrated native contracts](../../docs/wire/hydrated-native.md) and
+[decision 0019](../../docs/decisions/0019-hydrated-wire-protocol.md).

{bitspark_bitwire-0.5.0 → bitspark_bitwire-0.7.0}/src/bitwire/__init__.py

@@ -33,3 +33,18 @@ class DeixisNode(Protocol[T]):
 WireNode = DeixisNode[Wire]
 __all__ = ['Atom', 'Tuple', 'Value', 'atom', 'tuple_', 'equals', 'Path', 'Termination',
            'Wire', 'Endpoint', 'AddressedWire', 'AddressedEndpoint', 'WireNode', 'Parts', 'DeixisNode']
+
+# These are declarations, not runtime recognition or constructors.
+ReceivedContext = object
+class HydratedTuple(Protocol):
+    def items(self) -> tuple[HydratedValue, ...]: ...
+class HydratedWire(Protocol):
+    async def send(self, message: HydratedValue) -> None: ...
+HydratedValue = Atom | Tuple | HydratedTuple | HydratedWire
+class HydratedEndpoint(HydratedWire, Protocol):
+    @property
+    def wire(self) -> HydratedWire: ...
+    def receive(self, handler: Callable[[HydratedValue, ReceivedContext], None]) -> Callable[[], None]: ...
+    async def closed(self) -> Termination: ...
+    async def close(self) -> None: ...
+__all__ += ['HydratedValue', 'HydratedTuple', 'HydratedWire', 'HydratedEndpoint', 'ReceivedContext']

{bitspark_bitwire-0.5.0 → bitspark_bitwire-0.7.0}/tests/typecheck.py

@@ -12,3 +12,15 @@ async def consume(endpoint: Endpoint, addressed: AddressedEndpoint) -> None:
     await addressed.closed()
     await endpoint.close()
     await endpoint.closed()
+
+from bitwire import HydratedWire, HydratedEndpoint, HydratedValue, ReceivedContext
+async def hydrated_surface(owner: HydratedEndpoint, sender: HydratedWire) -> None:
+    value: HydratedValue = Tuple((Atom(),))
+    def receiver(message: HydratedValue, context: ReceivedContext) -> None:
+        pass
+    detach = owner.receive(receiver)
+    await sender.send(value)
+    await sender.send(owner.wire)
+    detach()
+    await owner.close()
+    await owner.closed()

bitspark_bitwire-0.5.0/README.md

@@ -1,10 +0,0 @@
-# py wire presentation
-
-Addressless Wire sends a ground ontos value. Endpoint adds receive ownership and
-closure. AddressedWire adds an exact byte-path argument; AddressedEndpoint carries
-that layer over one endpoint. WireNode is the complete deixis structure over Wire
-values (a nominal interface in Java), not opaque route access.
-
-See the repository's docs/wire/contract.md and docs/wire/carriers.md. Version 0.5.0
-is a clean breaking replacement; compilation and packaged consumers check the
-native surface, while bitruntime supplies independently tested implementations.