Adapt the starter.
Replace the sample control with one of yours. The plain HTML starter includes the small integration and its limits.
Open the starter ↗FROM FIRST DECISION TO FIRST INTEGRATION
Make one decision visible.
Choose an interface purpose and declared values. Watch the actual ĀML browser bridge decide whether one ordinary button appears. Then copy the markup or download a page you can open yourself.
01 / DECLARE
Describe one element.
The values belong to your declaration. Try raising restoration to meet attention, then compare the two deployment modes.
The generated example sets failure-mode="closed" explicitly. A production host still needs its own policy, testing, and authorization design.
02 / OBSERVE
See what the gate does.
This preview uses the real <aml-gate> browser bridge and listens for its aml-decision event.
POLICY / RESTORATION ≥ ATTENTION
LOADING
Connecting to the project browser bridge…
Element withheld by the browser gate
EVENT / AML-DECISION
Waiting for the browser bridge…
03 / TAKE IT WITH YOU
Use this exact declaration.
One module and one HTML element. No package manager for this browser experiment.
Preparing your integration…A scenario link includes the purpose and button text you enter. Use sample wording if the content is private; the configuration stays in the URL fragment rather than the server request.
The download loads the current project preview from GitHub Pages and needs internet access. Review and pin assets before deployment.
From a button to a boundary.
Choose an integration.
See the React and Next.js paths or use the host-side action boundary. The current registry package is not independently verified.
Open the adoption guide ↗Reproduce and challenge.
Run the project cases locally, change the input, and report the exact environment and result.
Open the verification guide ↗