Bramah / Sepolia / 29 October 2026
An approved transfer.
Public Bramah test-wallet records connect approval, submission and execution. The matching test-network transaction records a successful transfer.
Public event recordsMatching transaction
Evidence / Agenda / Shared language
Inspect the evidence, examine the open questions and identify where the next application matters.
What we think we have solved
ZLAR is a working lock for human authority. We believe that separating capability from the permission to produce a protected effect establishes a foundation for safe automation. The next task is to make that foundation useful across more destinations and workflows.
Dated implementation evidence
Bramah / Sepolia / 29 October 2026
Public Bramah test-wallet records connect approval, submission and execution. The matching test-network transaction records a successful transfer.
Public event recordsSeparate wallet demonstration / 4 November 2026
ZLAR’s review records report an exact payment approved on a phone, a refused request without a transfer, and an unanswered request expiring without a transfer.
Approved payment transactionThe public transaction establishes that transfer. The phone interaction and other cases rely on the separate review observations.
These are dated results from distinct implementations. They do not establish every integration, attack class or current installation. A permission mechanism does not by itself prove a permitted action is correct or beneficial. The records describe the implementations and dates shown.
The November wallet observations do not establish stolen-server-key resistance. Preserve that implementation’s scope when considering its results.
Access to the Bramah Challenge is by invitation. Ask about an invitation
What we are working on
Identify the consequence, the accepting paths and the integration that makes human authority binding there.
Preserve scope and allowances as work is delegated, run concurrently or assembled into a larger result.
Keep uncertain outcomes, changed proposals and withdrawal distinct. Make the next supported step useful.
Examine who can change the rules, approvers and protected boundary. Those changes have consequences too.
Make decisions understandable, remove unnecessary interruption and demonstrate value in a real workflow.
This is the product and research agenda. Individual integrations need their own implementation and evidence.
Shared concepts / G01–G15
About this edition
ZLAR is the technology. ZLAR Inc. is the company. This edition of ZLAR.ai, dated 6 November 2026, is for founders, AI insiders and the AI they work with.
The diagrams explain distinctions; the deployment states are fictional examples. Application families describe the opportunity, not a catalogue of installed integrations. The evidence section identifies dated records separately.
This site contains no submission form, account connection or application storage. It counts visits in aggregate with Cloudflare Web Analytics, which uses no cookies and builds no visitor profiles. Email links open the visitor’s own email application, and what you send is used to read and answer your message.
A general description is enough to begin a conversation. Use appropriate authorized channels for confidential information.
Build ZLAR with us
Architecture, product, commercial judgment or a consequential workflow. Start a conversation about turning this foundation into widely used infrastructure.
Talk about building ZLAR