AI can propose an interface. ĀML can make its meaning, policy, authority, and evidence inspectable before and after rendering.
HTML tells the browser what to display. ĀML tells the system why it deserves to be displayed.
ĀML is a working research prototype for meaning-native, policy-aware, accountable AI interfaces. It can sit between machine intent and human-facing output as an AI Interface Firewall™ without requiring teams to replace HTML, React, or existing frontend stacks.
Do not endorse ĀML first. Verify it first.
Open this exact state:
https://aruintelligence.github.io/aml-core/proof.html?attention=5&restoration=1&lang=en
It should return SUPPRESS.
Now change restoration from 1 to 5. The same decision should become ALLOW.
Prototype rule:
render_allowed = restoration_value >= attention_cost
The attention/restoration scores are declared or model-supplied prototype inputs. They are not claimed objective measurements of cognition, wellbeing, morality, or clinical state.
If the behavior does not reproduce, that is useful evidence. Please publish PASS / FAIL / MIXED with enough detail for someone else to repeat your result.
git clone https://github.com/aruintelligence/aml-core.git
cd aml-core
npm install
npm testFor the smallest deterministic reproduction, start with:
Project-authored tests are useful engineering evidence, but they do not count as independent external verification.
A generated interface usually has several hidden questions behind it:
- What did the system intend to show?
- Which policy allowed or blocked it?
- What authority or consent applied?
- What evidence explains the decision?
- Can another implementation reproduce the result?
ĀML turns those questions into inspectable data and deterministic decisions that can travel with the interface.
flowchart LR
A[AI / app intent] --> B[ĀML Interface Firewall]
B --> C[Meaning + policy]
C --> D[Consent / privacy / accessibility / attention]
D --> E[ALLOW or SUPPRESS]
E --> F[HTML / React / other renderer]
E --> G[Receipt + provenance + audit evidence]
G --> H[Independent verification]
- ĀML in one page
- Start Here — ĀML in 5 minutes
- Why AI-generated UI needs a firewall
- A critic's guide to ĀML
- Publications index
Zero-install custom element:
<script type="module" src="https://aruintelligence.github.io/aml-core/aml-gate.js"></script>
<aml-gate
purpose="Create urgency"
attention-cost="5"
restoration-value="1">
<button>Act now</button>
</aml-gate>Or keep the existing DOM and add three attributes:
<script type="module" src="https://aruintelligence.github.io/aml-core/aml-dom-gate.js"></script>
<div
data-aml-purpose="Create urgency"
data-aml-attention-cost="5"
data-aml-restoration-value="1">
Offer expires soon.
</div>These browser bridges are intentionally narrow adoption surfaces. They do not claim to contain the full runtime policy, consent, privacy, accessibility, receipt, or trust stack.
The web gave developers View Source. ĀML explores View Meaning™.
import { viewMeaning } from "./index.js";
const report = viewMeaning(receipt);A View Meaning report can expose declared purpose, policy/profile, consent/privacy/accessibility context, attention/restoration inputs, ALLOW/SUPPRESS outcome, rationale, provenance, and receipt integrity.
The repository currently includes:
- lexer/parser, AST, Abstract Meaning Tree, compiler, runtime, and CLI
- semantic and policy diffs
- pluggable policies and multi-policy consensus
- consent, privacy, accessibility, and attention controls
- execution receipts and Ed25519 signatures
- SHA-256 audit streams, provenance graphs, and Merkle inclusion proofs
- Proof-Carrying Interface™ manifests
- capability negotiation, policy passports, replay protection, delegation, threshold authorization, transparency logs, and revocation registries
- browser bridges, React-compatible adapters, starters, an HTTP service, Meaning Gate™ GitHub Action, and View Meaning™ tooling
- RFCs, schemas, golden vectors, conformance fixtures, benchmarking, interoperability, and evidence-reporting surfaces
See API.md, ECOSYSTEM.md, rfcs/README.md, and STANDARDIZATION.md.
ĀML separates project-controlled evidence from independent evidence.
| Level | Meaning |
|---|---|
| E0 | concept / proposal |
| E1 | project-authored demonstration |
| E2 | automated repository verification |
| E3 | independent reproduction |
| E4 | independent implementation |
| E5 | external pilot evidence |
| E6 | production deployment evidence |
| E7 | multi-party ecosystem evidence |
The project should not describe internal tests, project-maintained reference implementations, clone counts, or outreach activity as independent adoption.
A failure, bypass, contradictory implementation, or MIXED result can be more valuable than praise if it reveals where the contract is weak.
v1.3.0remains the stable package/CLI/capability contract.v1.4.0-rc.2is the current GitHub prerelease snapshot of the broader architecture onmain.- ĀML is not a ratified industry or Internet standard.
- No claim is made here of universal adoption, standards-body approval, third-party certification, regulatory approval, scientific validation, or production suitability for every environment.
The reference implementation covers parser/compiler behavior, policy bypasses, receipts/signatures, wire replay, capability escalation, revocation, official trust-root verification, HTTP behavior, and browser-extension permission/privacy boundaries.
It does not replace production authentication, authorization, TLS, rate limiting, secure secret management, application-specific threat modeling, WCAG conformance testing, or independent security review.
The covered software is available under the MIT License. Official ĀML™ / ĀRU™ branding, logos, compatibility branding, certification-style identity, endorsement, OEM/co-branding, and related reserved brand rights are separate from the software license.
Technical conformance is independently testable. It does not automatically grant official ĀRU authorization, endorsement, partnership, certification, or trademark rights.
Official identity and trust resources:
- TRADEMARKS.md
- OFFICIAL_MARKS.json
- OFFICIAL_AUTHORIZATIONS.json
- BRAND_TRUST_ROOTS.json
- COMMERCIAL.md
- RFC 0011 — Official Brand Authorization
Current production public trust root:
- key id:
aru-aml-brand-prod-2026-09-08-01 - SHA-256 fingerprint:
eda0184568cb2110add5130d2a9fffaf53a77e0f2be311be414e7912ed69997c - public key: keys/aru-aml-brand-prod-2026-09-08-01-public.pem
Production private signing material is intentionally kept outside GitHub.
Commercial, OEM, enterprise, and strategic inquiries: Office@aruintelligence.com
When AI generates an interface, can the system prove what it meant, what authority it had, which policies governed it, and why the human saw the result?
Created by Daniel Jacob Read IV and stewarded by ĀRU Intelligence Inc.™.
ĀML™, ĀRU Meaning Language™, AI Interface Firewall™, View Meaning™, Meaning Gate™, EthicalRenderGate™, Meaning-Native Computing™, Proof-Carrying Interface™, and named ĀML compatibility marks are claimed marks. Registration status varies; do not use ® unless a specific mark is actually registered for the relevant goods/services.