Legacy rendering
Valid markup → rendered element.
An agent asks to use a tool. An app asks to show an interface. ĀML makes the host's policy decision and its evidence inspectable at both boundaries. Change one input below and follow the exact path.
Connecting to the project preview. No tool runs, no message is sent, and no person is asked to approve.
AGENT PROPOSAL · SEND_MESSAGE
No tool callback is connected to this page.
Connecting to planner…Project vector self-check pending.DECLARED ELEMENT · CONVERSION PROMPT
Waiting for aml-decision…
Start with one agent tool call. Run your own host adapter against 13 published cases, then six seeded changes that test whether it actually binds the proposal, rule, and outcome.
Choose one controlled change to a captured run. Predict which check catches it, then reveal the answer and reproduce it in your browser.
Reproduce this change ↗A project-authored, unsigned consistency check. It cannot prove that a historical event occurred.Try another term or search across all paths.
An ĀML evidence capsule packages a decision receipt with a readable summary and two integrity digests. Keep the evidence when the screen, framework, or organization changes.
CAPSULE v1 · SHA-256 + SHA-512 · STRICT JSONExplore the preservation contract ↗Read the append-only renewal contract ↗ · Pack an offline archive ↗ · Review versioned handoff ↗ · Repair from two shares ↗ · Model common storage failures ↗
Integrity alone does not establish truth, independent validation, trusted identity, or a guarantee of long-term cryptographic security.
Conventional markup presents every declared element. The ĀML prototype inserts an inspectable policy decision before presentation.
Valid markup → rendered element.
Declared meaning → policy evaluation → decision.
Change claimed restoration value. The same element may be allowed, degraded, or suppressed—and the rationale updates immediately.
Purpose and semantic value become explicit inputs, not invisible author assumptions.
A named policy evaluates the element before the browser receives its final state.
The build emits both interface output and a machine-readable decision record.