How should Approved unlock seller permissions?
Bind the verified event to the tenant, user and session, then apply the customer policy. Approved alone is not permission to publish. The executable example grants only local fixture permissions.
Run the example
Download the ZIP below, extract it and enter the verification_delivery directory. Python 3.10+; no credentials or network calls.
python3 server.py --db /tmp/gridzen-hosted-fixture.sqlite --port 8787
# Second terminal:
curl -s http://127.0.0.1:8787/sessions -H "Content-Type: application/json" -d "{}"
# Open http://127.0.0.1:8787/verify/fixture-session
curl -s http://127.0.0.1:8787/sessions/fixture-sessionInputs, outputs and limits
Input: synthetic event, tenant/user/session and explicit policy. Output: permission_granted and grant_count. Test wrong bindings, missing policy, duplicate and late events. The local link collects no ID; production signatures and real hosted sessions require an authorized adapter.
Test every branch
Engineering tests cover simulated transitions, bindings, duplicate callbacks, restart and timeouts. They do not prove production success, external adoption or Agent superiority.
python3 -m unittest -v test_deliveryDownload runnable synthetic examples
Sources and scope
Based on the alpha contract and source implementation. Live route availability requires separate confirmation.