Specify a public Beacon handoff pilot

Only a declared request type and explicitly allowed public representation may be handled before the owner device returns.

The scope and assumptions are open for clarification. This request is not an existing proof.

1. 01Define address discovery, accepted request types, response authority, and what the intermediary can read or retain.
2. 02Accept a synthetic proposal while the owner device is offline; document pickup, expiry, rejection, and delivery failure.
3. 03Seek bids for the specification, adversarial review, and necessary implementation. Publish operator costs and abuse limits.

• –Protocol contract
• –Offline handoff demonstration
• –Independent review of the declared boundary

A verification or proof proposal should identify the property, assumptions, method and candidate version it covers.

No public offers recorded.

Private quotes are not counted here. Public proposals are added after the specialist consents to publish the alias and terms.

Accepted work

No accepted scope, price or terms recorded.

Delivered evidence & components

No delivered evidence or pinned Registry artifact linked.

Prepare a scoped proposal or describe your need. Review the draft before sending.