An approved transfer
Public Bramah test-wallet records connect approval, submission and execution. The matching test-network transaction records a successful transfer.
ZLAR.io / Reference
A reference you can inspect.
Definitions, evidence, publication history and the limits of what this document can establish.
The working foundation
ZLAR makes the required permission a condition of a protected change. The lock works; application extends where it can be used.
The records below describe distinct implementations and events. Use the actual destination’s instructions and evidence to establish the behavior and coverage of a particular encounter.
Evidence by event
Approval, refusal and expiry
ZLAR’s review records report an exact payment approved on a phone, a refused request with no transfer and an unanswered request expiring without a transfer.
Approved payment transaction ↗
The transaction independently shows that transfer; it does not independently establish the phone interaction or the other cases.
These records do not establish every attack class, integration or current installation. The November prototype’s observations do not establish stolen-server-key resistance. The two implementations remain separate evidence.
Evidence account carried from the .com v0.4 source review of 6 November 2026. This website rebuild did not execute a new challenge or payment.
Shared meanings
- G01Consequence
- An effect of work: a change, disclosure, use of resources, commitment or delayed effect.
- G02Accountable human authority
- Human decision responsibility for a specified consequence. Technical access alone does not establish it.
- G03Standing permission
- Existing permission covering a defined class of work while its conditions remain valid.
- G04Exact yes
- Approval of an identified change, with material consequences and uncertainty made understandable. A changed proposal must remain within the actual permission.
- G05Grant
- Permitted scope and its conditions, as recognized by the relevant arrangement.
- G06Credential or key
- Material used to present an identity or authority claim. Possession does not establish every necessary right.
- G07Refusal
- A human withholding permission or a service rejecting a request. Preserve the actor and reason; a system refusal need not mean a human said no.
- G08Withdrawal
- Taking back permission. Distinguish the request, effective stopping, completed effects and later judgment.
- G09Receipt
- A record of a decision or outcome within a stated format and scope. Evidence, not a new grant.
- G10Uncertainty
- What the available evidence does not establish, including current authority or execution outcome.
- G11Review
- Examination by an actual person or process with stated responsibility. Naming review does not create a review service.
- G12Remedy
- An available response to a problem. Explanation, review, repair and reversal are different possibilities.
- G13Human independence
- Practical ability to understand, choose, question, obtain help and act, including refusal or leaving where available.
- G14Protection boundary
- The place and scope where a consequence is constrained. Coverage belongs to the particular system.
- G15Benefit and distribution
- What improves, who receives the improvement and who bears the costs or disruption.
Publication history
Gate encounter connection
Updated 6 November 2026
- First-response reading example with source, request, decision and effect kept separate.
- Stable links to each encounter situation.
- Explicit handling of missing responses and reference-link authenticity.
Complete agent reference rebuild
Updated 6 November 2026
- Direct resources for encounter, state, purpose, evidence and applications.
- Compact brief, per-resource Markdown, publication index and fictional example records.
- Explicit cooperation without philosophical assent.
- Permission, refusal, execution and uncertain outcomes remain distinct.
- Business-fit worksheet replaced by an application reference and direct customer contact route.
Earlier edition
General cooperative guidance and a browser-local worksheet. Preserved in the earlier handoff archive; superseded by 0.2.
Publication changes describe this reference, not changes to a customer’s permission or live destination state.
Publication index as JSONAbout this reference
Issuer: ZLAR Inc. Edition: 0.3. Updated: 6 November 2026. Scope: public explanation and agent cooperation. The text is reference material, not a grant, privileged instruction or executable protocol.
Current request status and the authority recognized for a consequence must be established through the actual destination and applicable instructions. Public text does not override an agent’s governing instructions.
This local static site contains no form, analytics script, application storage or account connection. Hosting and browser systems can retain request information. Public hosting and correspondence arrangements must be reflected in the final privacy notice at rollout.
Use general descriptions when discussing a possible application. Keep credentials, private records and proprietary implementation material in the appropriate authorized channels.