Skip to content

Point installation entrypoints to published alpha36 #68

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
qh-work merged 1 commit into from
Sep 30, 2026
Merged

Point installation entrypoints to published alpha36 #68

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 12 additions & 10 deletions .well-known/agent-memory.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,20 +1,20 @@
{
"schema_version": "memory-vault-discovery/v1",
"name": "Memory Vault",
"implementation_version": "0.28.0-alpha.0.35",
"implementation_version": "0.28.0-alpha.0.36",
"implementation_status": "alpha_preview",
"license": "Apache-2.0",
"repository": "https://github.com/qh-work/memory-vault-sync",
"release": "https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.35",
"release": "https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.36",
"release_publication_verified": true,
"release_assets": {
"client": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.35/memory-vault-client-v0.28.0-alpha.0.35.zip",
"protocol": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.35/memory-vault-protocol-v0.28.0-alpha.0.35.zip",
"review": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.35/memory-vault-review-v0.28.0-alpha.0.35.zip",
"network_trial": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.35/memory-vault-network-test-v0.28.0-alpha.0.35.zip",
"checksums": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.35/SHA256SUMS"
"client": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.36/memory-vault-client-v0.28.0-alpha.0.36.zip",
"protocol": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.36/memory-vault-protocol-v0.28.0-alpha.0.36.zip",
"review": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.36/memory-vault-review-v0.28.0-alpha.0.36.zip",
"network_trial": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.36/memory-vault-network-test-v0.28.0-alpha.0.36.zip",
"checksums": "https://github.com/qh-work/memory-vault-sync/releases/download/v0.28.0-alpha.0.36/SHA256SUMS"
},
"previous_release": "https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.34",
"previous_release": "https://github.com/qh-work/memory-vault-sync/releases/tag/v0.28.0-alpha.0.35",
"relative_links_base": "this discovery document",
"start_here": "../AI_START_HERE.md",
"specification": "../PROTOCOL.md",
Expand Down Expand Up @@ -46,7 +46,7 @@
"automatic_sync_default": false,
"readme_is_installation": false,
"runtime_tests_run_for_release": true,
"runtime_test_scope": "Six checks passed using the extracted alpha.0.35 client: native saved-memory receipt return and original-owner confirmation with the old delivery node unavailable; shared completed history reopened by either client; native recovery of a Python-staged pending return; exact upload replay after a lost reply and restart; refusal of unsaved or mismatched messages; and retained denial/expiry enforcement. Exact-source cloud regression passed 1224 tests across 135 modules, with all 303 reported source hashes matching d86d62083566a30804f3cae5ad6643da73e28f9a. All three Python 3.10 suites and cross-platform conformance passed. All eight public assets were downloaded through the authenticated GitHub client and matched. These results do not establish independent external adoption, global reliability or thousand-agent capacity.",
"runtime_test_scope": "Nine checks passed using the extracted alpha.0.36 client: native remote mailbox recovery after removal of old delivery records; selected-memory import and saved receipt retention; cross-client inbox and receiver history; endpoint and sender binding; retained revocation refusal; and native saved receipt return/restart recovery. Exact-source cloud regression passed 1235 tests across 138 modules, with all 314 reported source hashes matching bd3ca97ee56ca59a85c87eb1395e738e1a8c56ca. All three Python 3.10 suites and cross-platform conformance passed. All eight public assets were downloaded through the authenticated GitHub client and matched. These results do not establish independent external adoption, global reliability or thousand-agent capacity.",
"runtime_test_report": "../docs/RELEASE.md",
"full_runtime_test_suite_run": true,
"runtime_parity_verified": false,
Expand Down Expand Up @@ -113,7 +113,9 @@
"routed_original_ack_recovery": true,
"explicit_ack_directory_republication": true,
"native_saved_receipt_return": true,
"native_pending_receipt_restart": true
"native_pending_receipt_restart": true,
"native_remote_mailbox_recovery": true,
"native_registered_mailbox_receive": true
},
"continuation_trial": {
"guide": "../docs/CONTINUATION_TRIAL.md",
Expand Down
8 changes: 5 additions & 3 deletions AI_START_HERE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,12 +1,14 @@
# Memory Vault: connect, remember, exchange, continue

Native TypeScript recipients can now register an authorized remote mailbox and use ordinary Agent `receive` to recover messages and selected memories after old delivery records disappear. Current READ permission, complete original authority and durable inbox checks remain required. Python and TypeScript share receiver configuration, status history and saved inbox evidence. See [native mailbox recovery](clients/typescript/network/README.md).

Native TypeScript recipients can now return an actual saved receipt through `connect/return_receipt`, using separate original owner, recipient and storage permissions. The native client shares the bounded pending/completed journal with Python and can resume the exact pending upload after restart without consuming new consent. See [independent receipt return](docs/OPEN_ACK_PROVISIONING.md#native-saved-receipt-return-development-after-alpha034).

Sources can now republish an original ACK location through another independently consented directory while preserving earlier publication histories and shared resource limits. Python and native TypeScript `connect/recover_routed_receipt` discover directories through existing seeds and routing state, then independently retrieve the actual receipt from the originally authorized source. See [directory republication and routed recovery](docs/OPEN_ACK_DIRECTORY.md#publish-through-another-directory-development-after-alpha033).

Python and native TypeScript senders can now locate an original-source ACK receipt through an explicitly selected directory using `connect/recover_discovered_receipt`. A separate authorized source read must match the actual recipient receipt, published custody and original send. New opt-in `receipt-index` sources fund the whole workflow; existing signed limits stay unchanged. See [directory receipt recovery](docs/OPEN_ACK_DIRECTORY.md#agent-directory-recovery-development-after-alpha032).

Native TypeScript senders can now recover an independent original-source ACK receipt through `connect/recover_receipt`, or by repeating an unchanged original `send` with an already retained preparation while the delivery node is offline. Python and native clients share saved receipts and original-root revocation history, including older installations. Preparation and full replica/mailbox workflows still use Python; explicit saved receipt return is also available natively in alpha.0.35. See [native ACK confirmation](docs/OPEN_ACK_PROVISIONING.md#native-agent-receipt-recovery-source-after-alpha031).
Native TypeScript senders can now recover an independent original-source ACK receipt through `connect/recover_receipt`, or by repeating an unchanged original `send` with an already retained preparation while the delivery node is offline. Python and native clients share saved receipts and original-root revocation history, including older installations. Preparation and replica reception still use Python; native ordinary mailbox reception and explicit saved receipt return are available. See [native ACK confirmation](docs/OPEN_ACK_PROVISIONING.md#native-agent-receipt-recovery-source-after-alpha031).

Python maintainers can retain exact authorized mailbox copies in a [finite persistent worker](docs/OPEN_ACK_RECOVERY.md). Senders can retain selected ACK replicas; repeating an unchanged original `send` confirms the recipient receipt after both original delivery and ACK nodes stop. Exact requests and signed refusal history survive restart. Destination selection and independent permissions remain explicit. See [ACK replica confirmation](docs/OPEN_ACK_PROVISIONING.md).

Expand All @@ -32,7 +34,7 @@ current read checks. Saved receipts use separate return/recovery authority.
Python recipients can now [return a saved cold-mailbox receipt](docs/OPEN_ACK_PROVISIONING.md#development-return-a-receipt-after-cold-mailbox-delivery)
using the message's retained original ACK authority and an independently selected source.
The full native TypeScript mailbox client and automatic replacement-node repair
remain unfinished. Six checks passed using the extracted alpha.0.35 client: native saved-memory receipt return and original-owner confirmation with the old delivery node unavailable; shared completed history reopened by either client; native recovery of a Python-staged pending return; exact upload replay after a lost reply and restart; refusal of unsaved or mismatched messages; and retained denial/expiry enforcement. Exact-source cloud regression passed 1224 tests across 135 modules, with all 303 reported source hashes matching `d86d62083566a30804f3cae5ad6643da73e28f9a`. All three Python 3.10 suites and cross-platform conformance passed. All eight public assets were downloaded through the authenticated GitHub client and matched. These results do not establish independent external adoption, global reliability or thousand-agent capacity.
remain unfinished. Nine checks passed using the extracted alpha.0.36 client: native remote mailbox recovery after removal of old delivery records; selected-memory import and saved receipt retention; cross-client inbox and receiver history; endpoint and sender binding; retained revocation refusal; and native saved receipt return/restart recovery. Exact-source cloud regression passed 1235 tests across 138 modules, with all 314 reported source hashes matching `bd3ca97ee56ca59a85c87eb1395e738e1a8c56ca`. All three Python 3.10 suites and cross-platform conformance passed. All eight public assets were downloaded through the authenticated GitHub client and matched. These results do not establish independent external adoption, global reliability or thousand-agent capacity.

Python agents can now [recover an existing saved-message receipt from an explicitly selected replica](docs/OPEN_ACK_RECOVERY.md#copy-and-recover-an-existing-saved-receipt) after both original delivery and ACK nodes stop. The actual recipient receipt updates the original send, survives restart, and leaves shared memory in the recipient Vault. Recipient, owner, source and maintainer permissions remain independent. New receipt-index preparation can explicitly select a copy maintainer.

Expand All @@ -53,7 +55,7 @@ The publication and recovery commands retain exact original bytes and durable
work limits. Explicit authorized mailbox replicas can retain messages after source
loss; automatic repair remains unfinished.

**v0.28.0-alpha.0.35 open-network preview:** use the [agent quickstart](docs/OPEN_NETWORK_QUICKSTART.md)
**v0.28.0-alpha.0.36 open-network preview:** use the [agent quickstart](docs/OPEN_NETWORK_QUICKSTART.md)
to bind your existing Vault and signing identity to an independent open transport,
join through one or two actual signed node introductions, explicitly approve a
finite delivery, and exchange encrypted chat or selected original memories.
Expand Down
Loading
Loading