Conversation
# Conflicts: # tests/test_network_packaging.py
…nto feat/native-mailbox-read
…nto feat/native-mailbox-receipts
…nto feat/native-mailbox-authorization
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A native recipient can now issue mailbox admission authorization from its registered mailbox and approved incoming contact, then export the original signed destination and current owner status through bounded pages. A Python sender can use those exact originals for actual HTTP admission, retry and recovery. The recipient signs only with its existing identity; this action reserves no new storage and creates no receipt-return grants.
Python and TypeScript share the finite destination journal. Identical retries and cross-client reads return the same bytes, while input conflicts, stale revisions, expired authority and wrong receiver bindings fail. Both clients now authenticate retained mailbox receive statuses inside the signing transaction: revoked parent or storage authority blocks cached and fresh authorization even after the status expires, and remembered document/revision floors remain effective.
Validation: native-issued authorization used for actual sender HTTP admission, lost-reply recovery, Python reopening every exact exported page, offline rejection cases, and expired retained revocation refusing both clients. Package and CI inventories include the new module; the native SDK now contains 69 files. Final-source cloud acceptance remains pending before alpha.0.38 publication. Native source provisioning, sender admission and replica reception are still unfinished.