HTML vs ZML

Same hero, different philosophy

HTML describes page structure. ZML describes a verified static experience: structure, style intent, publisher identity, integrity, AI rules, and trust metadata — all in one readable language.

HTML 1993 · Legacy Web Document

Structure-only webpage markup

<!DOCTYPE html>

<html lang="en">
  <head>
    <meta charset="utf-8"/>
    <meta name="viewport"
          content="width=device-width"/>
    <meta name="description"
          content="Simple syntax"/>
    <meta name="robots"
          content="index, follow"/>
    <title>Home</title>

    <!-- No native publisher identity.
         Workaround: external rel="author" -->
    <link rel="author" href="/humans.txt"/>
    <link rel="canonical"
          href="https://example.com/"/>

    <!-- No native integrity manifest.
         Workaround: separate JSON file -->
    <link rel="manifest"
          href="/manifest.json"/>

    <!-- No native AI policy.
         Workaround: robots.txt meta only -->
    <meta name="robots"
          content="noai, noimageai"/>

    <!-- Styling must be entirely external -->
    <link rel="stylesheet"
          href="/styles.css"/>
  </head>
  <body>
    <div class="hero">
      <div class="eyebrow">ZML</div>
      <h1>Simple syntax</h1>
      <p>Powerful static sites</p>
      <a href="/demo"
         class="btn">
        Open Demo
      </a>
    </div>
  </body>
</html>

<!-- No Zelen seal. No trust metadata.
     No native AI permissions.
     No publisher cryptographic identity.
     No native asset integrity manifest.
     All require external tools, server
     headers, or separate config files. -->

9 explicit closing tags
Tag-based structure
Class-based styling
No native publisher identity
No native AI policy
No native Zelen seal
No native asset integrity manifest

ZML 2026 · Modern Static Trust Language

Static website + trust + AI policy + publisher identity + integrity in one readable language

zml version "0.2"
zstyle "gruvbox-dark"

Strict: true
Style Policy: strict

| Site
Name: Rocheston NovaZel
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Font: Fira Sans

| Manifest
Hash Assets: true
Sign: true
Seal: zelen
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...

| Trust
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Zelen Seal: required
Integrity: required

| Page /
Title: Home
Classification: public

| Hero
Eyebrow: ZML
Title: Simple syntax
Subtitle: Powerful static sites

| Button
Label: Open Demo
To: novazel://demo.novazel
Tone: primary

| AI Policy
Default: deny
Allow: read public
Allow: summarize public
Allow: translate public
Deny: train all
Deny: scrape all
Deny: export restricted
Agent: none

0 closing tags
Margin Bar outline
Readable website structure
Native publisher identity
Native AI policy
Native Zelen sealing
Native asset integrity
Native trust manifest

HTML vs ZML Philosophy — Legacy tag soup vs Modern readable blocks

Three pillars · Three reasons

ZML is what HTML would be if it were redesigned today.

Three things HTML never had and never will. Three things every modern document language must have. Three things baked into ZML from line one of the spec.

◆

Static by design

ZML pages compile into static artifacts. No PHP at request time. No database queries. No hidden server logic. No arbitrary JavaScript unless explicitly permitted by policy.

.zml source → .zmlc compiled
Hashed, signed, cached, audited
Zero server-side attack surface
Edge-deployable, replayable

⬢

AI-aware from day one

ZML pages declare what AI agents may read, summarize, translate, cite, ignore, export, scrape, or train on. Untrusted zones cannot become agent instructions.

Native ai-policy and ai-zone blocks
Per-zone training and export controls
Prompt-injection containment
Agent-tool permission scoping

▲

Trust-aware by default

ZML can require signed manifests, asset hashes, NovaZel publisher identities, Zelen-sealed evidence, and safe link policies before a browser renders the page.

Publisher NZID bound to every page
Asset hash verification required
Zelen quantum-safe sealing
Classification + evidence built in

ZML — Static-first, AI-aware, Zelen-sealed, NovaZel-native, Markdown-compatible, Modern protocol branding

First Look · Quick syntax

Reads like a script. Compiles like a contract.

ZML uses Margin Bars, readable keys, and plain values — like a config file written for humans. No tag soup. No nested div circus. Just sections, declarations, and English.

home.zml

blog.zml

about.zml

haja.zml

-- A complete ZML page. Static. Signed. AI-aware.

zml version "0.2"
zstyle "gruvbox-dark"

Strict: true
Style Policy: strict

| Site
Name: Rocheston NovaZel
Theme: gruvbox-dark
Font: Fira Sans
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Zelen Seal: required

| Manifest
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Hash Assets: true
Sign: true
Seal: zelen

| Page /
Title: Home
Classification: public

| Hero
Eyebrow: ZML
Title: Simple syntax. Powerful sites.
Subtitle: The web Tim Berners-Lee would build today.

| Button
Label: Open Demo
To: novazel://demo.novazel
Tone: primary

| Section
Id: intro
Title: What ZML does

| Heading
Level: 2
Text: What ZML does

| Text
Identity-first markup with built-in AI policy.

| Image
Src: novazel-flow.png
Alt: NovaZel Flow lifecycle
Hash: required

| AI Policy
Default: deny
Allow: read public
Allow: summarize public
Allow: translate public
Deny: train all
Deny: scrape all
Deny: export restricted
Agent: none

-- Blog listing with typed links and Markdown support.

zml version "0.2"
zstyle "blog-serif"

Strict: true
Style Policy: strict

| Page /blog
Title: Blog
Classification: public

| Section
Id: posts
Title: All Posts

| Heading
Level: 1
Text: All Posts

| Grid 2
Class: blog-grid

| Card
Id: identity-first-web
Title: The Identity-First Web

| Text
Date: 2026-05-01
Tag: protocol

| Link
Label: Read post
To: novazel://blog.novazel/identity-first-web
Type: typed

| Card
Id: zml-vs-html
Title: ZML vs HTML: Side by Side

| Text
Date: 2026-05-10
Tag: language

| Link
Label: Read post
To: novazel://blog.novazel/zml-vs-html
Type: typed

| AI Policy
Default: deny
Allow: read public
Allow: summarize public
Allow: cite public
Deny: train all
Deny: scrape all
Deny: export restricted
Agent: none

-- About page with publisher identity and Zelen seal.

zml version "0.2"
zstyle "gruvbox-dark"

Strict: true
Style Policy: strict

| Page /about
Title: About Rocheston
Classification: public

| Section
Id: mission
Title: Who We Are

| Heading
Level: 1
Text: Who We Are

| Text
Rocheston builds identity-first infrastructure for the modern web.

| Markdown
Mode: block

## Our Mission

Replace the broken, tag-heavy, AI-naive web
with **ZML** — static, signed, and trust-aware.

| Publisher
NZID: nzid:TANIQ5UHPQCPKIUXS2IMR...
Organization: Rocheston
Zelen Seal: required

| Manifest
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Hash Assets: true
Sign: true
Seal: zelen

| Trust
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Zelen Seal: required
Integrity: required

| AI Policy
Default: deny
Allow: read public
Allow: summarize public
Allow: translate public
Allow: cite public
Deny: train all
Deny: scrape all
Deny: export restricted
Agent: none

-- File: haja.zml
-- Personal homepage sample using modern ZML Margin Bar syntax.

zml version "0.2"
zstyle "gruvbox-dark"

Strict: true
Style Policy: strict

| Site
Name: Haja Mo
Theme: gruvbox-dark
Font: Fira Sans
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Zelen Seal: required

| Manifest
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Hash Assets: true
Sign: true
Seal: zelen

| Trust
Publisher: nzid:TANIQ5UHPQCPKIUXS2IMR...
Zelen Seal: required
Integrity: required

| Page /
Title: Haja Mo
Description: Creator, inventor, storyteller, and builder of identity-first web systems.
Classification: public
Lang: en

| Hero
Eyebrow: HAJA.ZML
Title: Haja Mo builds worlds, protocols, and future-ready systems.
Subtitle: A personal static site written in ZML — signed, AI-aware, Zelen-sealed, and designed for the modern web.

| Button
Label: Explore Projects
To: #projects
Tone: primary

| Button
Label: Read the Manifesto
To: #manifesto
Tone: secondary

| Section
Id: manifesto
Title: The Haja Mo Manifesto

| Heading
Level: 2
Text: Static. Signed. Simple. Powerful.

| Text
The web should be readable by humans, verifiable by machines, respectful to creators, and safe for AI agents. ZML brings structure, publisher identity, trust policy, and AI boundaries into the page itself.

| Markdown
Mode: block

## Why ZML matters

HTML describes a document.

ZML describes a **trusted static experience**.

It carries the page, the intent, the publisher, the AI policy, the integrity rules, and the delivery philosophy in one clean readable file.

| Section
Id: projects
Title: Featured Projects

| Grid 3
Class: project-grid

| Card
Id: novazel
Title: NovaZel Protocol

| Text
Identity-first networking for a moving, zero-trust web.

| Link
Label: View NovaZel
To: novazel://protocol.novazel
Type: typed

| Card
Id: zml
Title: ZML Language

| Text
A simple static-site language designed to replace tag-heavy HTML with readable, signed, AI-aware markup.

| Link
Label: Read ZML Reference
To: /zml-reference
Type: internal

| Card
Id: vega
Title: Vega Browser

| Text
A trust-aware browser experience for rendering ZML, validating Zelen seals, and respecting AI policy.

| Link
Label: Open Vega Demo
To: novazel://vega-demo.novazel
Type: typed

| Section
Id: principles
Title: Core Principles

| Checklist
Item: Human-readable syntax checked true
Item: Static output by default checked true
Item: Publisher identity built in checked true
Item: AI policy built in checked true
Item: Zelen sealing supported checked true
Item: No arbitrary runtime scripts by default checked true

| Section
Id: contact
Title: Contact

| Text
For collaborations, protocol ideas, language design, or ZML ecosystem discussions, use a verified NovaZel identity channel.

| Form
Name: HajaContact
Mode: novazel-flow
Target: novazel://api.haja.novazel/contact
Error Summary: true

| Input
Name: name
Label: Full Name
Type: text
Required: true
Autocomplete: name

| Input
Name: email
Label: Email Address
Type: email
Required: true
Autocomplete: email

| Textarea
Name: message
Label: Message
Max: 2000
Required: true

| Submit
Label: Send Securely
Evidence: true

| AI Policy
Default: deny
Allow: read public
Allow: summarize public
Allow: translate public
Allow: cite public
Deny: train all
Deny: scrape all
Deny: export restricted
Deny: tool-use all
Agent: none

| Footer
Text: © 2026 Haja Mo. Built with ZML. Signed with Zelen.

Why ZML Feels Human

ZML is designed to be read by humans first and verified by machines second. It makes the structure, purpose, ownership, and policy of a website visible in the same place.

Readable verbs

ZML uses words people already understand: site, page, hero, section, image, button, form, card, trust, manifest, and ai-policy. The page reads like intent, not machinery. In HTML, the author writes tags. In ZML, the author writes meaning.

Margin Bar blocks

Every meaningful block begins with a simple margin bar. No closing tags. No braces. No angle brackets. Structure flows downward in a clean readable outline. The | symbol says: "a new block starts here." Properties underneath explain what the block does.

Policy is content

ZML treats AI rules, publisher identity, trust requirements, asset integrity, and Zelen sealing as part of the document itself. These policies are not hidden in headers, cookies, plugins, or external configuration files. The page carries its own rules.

Invented by Haja Mo

ZML was conceived, designed, and specified by Haja Mo as part of the NovaZel Protocol — a ground-up rethink of identity, trust, and markup for the modern web. Every syntax decision, every policy rule, every Margin Bar was a deliberate choice.

Question the rules, change the game

HTML survived for 30 years not because it was good but because nobody dared replace it. ZML dares. Every convention that HTML assumed — closing tags, angle brackets, external trust, no AI policy — ZML questioned and discarded. The result is a language built for where the web is going, not where it has been.

ZML Margin Bar Blocks — Site, Page, Hero, AI Policy

Markdown · Native compatibility

Write Markdown. Get ZML safety. Zero conversion tax.

GitHub built the largest code economy on Earth using Markdown. Every AI chatbot — Claude, ChatGPT, Gemini — generates in Markdown. The whole industry voted with their fingers. ZML adopts Markdown natively while keeping every trust, AI, and policy rule active.

md-block.zml CommonMark + GFM + ZML-MD

page "/docs" {
  md-compatible true
  markdown-mode gfm

  md {
# NovaZel Docs

NovaZel creates **identity-first** flows.

- Atlas resolves service identity
- FUSE opens the flow
- Zelen seals the evidence

[Open demo](novazel://demo.novazel)
  }
}

md-policy.zmlSafe by default

ai-zone "public-docs" {
  classification public
  allow read summarize translate
  deny  train export

  md file "README.md" safe
  md raw-html deny
  md links external warn
  md links novazel verify
  md assets hash required
}

-- Markdown never bypasses ZML trust rules.
-- Raw <script>, <iframe>, tracking pixels: denied.

# heading→ heading level N · with outline checks

**bold**→ mark strong · safe inline

*italic*→ mark em · safe inline

~~strike~~→ mark strike · GFM

[link](url)→ typed: internal / external / novazel

![img](src)→ alt-required, hash-verifiable

```code```→ codeblock with copy button

| table |→ accessible GFM table

- [x] task→ static checklist

$math$→ inline math / block math

:emoji:→ shortcode rendering

novazel://→ resolved via Atlas as NovaZel Flow

ZML Safety Frame — Markdown Fluent. ZML Safe.

374 entries · 17 categories

A full vocabulary for the modern static web.

From typography to typography-aware accessibility, from media to media-policy verification, from forms to FHE-friendly telemetry — every dimension of a modern web page is a first-class language construct.

Language Core

Grammar, blocks, attributes, strict mode

Markdown Compat

CommonMark, GFM, ZML-MD extensions

Project & Site

Site config, theme, publisher, packaging

Typography

Fonts, headings, text marks, callouts

Layout System

Grid, flex, stack, gallery, container

Components

Reusable cards, templates, includes

Media

Image, audio, video, gallery, 3D assets

Links & Actions

Typed links, downloads, novazel://

Static Interactivity

Tabs, details, accordions, no-JS UX

Safe Forms

Form intent, encrypted submit, captcha

Style System

Themes, tokens, variants, dark mode

Animation

Reveal, fade, transitions, reduced motion

AI & Agent Safety

ai-policy, ai-zone, training, export rules

Trust & Zelen

Manifests, hashes, sealing, classification

NovaZel & novaweb

Flows, Atlas records, identity binding

Data & Packaging

Static data, .zpkg, evidence exports

A11y & Diagnostics

Outline, contrast, alt, lint, audit

AI Policy · First-class citizen

Your page tells AI agents what they can and can't do.

HTML has zero AI permissions. Zero.

In 2026, AI agents read your page, train on your content, summarize your work, scrape your assets, and impersonate your voice — and HTML has no language at all for telling them what's allowed. The whole industry pretends robots.txt is enough. It isn't.

ZML treats AI agents as first-class actors with explicit permissions. Every page, section, or zone can declare what's allowed: read, summarize, translate, cite, ignore, export, scrape, train. Untrusted content zones cannot become agent instructions — prompt injection is contained at the language level.

          The world's first AI-native markup
          Permissions live inside the document. Crawlers respect them. Agents respect them. Your work stays yours.
        

-- Correct ZML Margin Bar format

-- AI policy with allowed actions, denied actions, agent tool limits, and prompt-injection boundary.

| AI Policy
Default: deny
Allow: read public
Allow: summarize public
Allow: translate public
Allow: cite public
Attribution: required
Deny: train all
Deny: scrape all
Deny: export restricted
Instruction Authority: trusted-zone-only

| Agent Tools
Read: allow
Write: deny
Network: deny

| AI Zone
Name: user-comments
Classification: untrusted
Instructions: denied
AI Instruction Authority: none
Can Trigger Tools: false

| Callout
Type: security
Text: Prompt injection contained. User comments may be read as content, but they cannot become instructions, trigger tools, or override the trusted page policy.

AI Policy Native — Read, Summarize, Translate, Cite allowed; Train, Scrape, Export blocked

The AI Era · Why ZML exists now

ZML was created for the artificial intelligence era.

The web was built for browsers that only needed to display pages. That world is gone.

Today, websites are read by people, searched by crawlers, summarized by AI assistants, indexed by agents, translated by models, inspected by security systems, and sometimes acted on by autonomous software. HTML was never designed for that reality. It can show content, but it does not naturally explain who owns the page, what AI can do with it, which zones are trusted, which content is untrusted, what may be summarized, what may be cited, what must never be trained on, or which actions an agent is allowed to take.

ZML is built for this new web.

It treats every page as a static, signed, human-readable, AI-aware document. The structure is simple enough for creators to write, strict enough for machines to verify, and explicit enough for AI agents to respect. Instead of hiding trust and policy outside the page, ZML brings structure, identity, integrity, and AI permissions directly into the document itself.

ZML is not just markup for displaying content.

It is markup for a world where content is read, reasoned over, cited, protected, and acted on by intelligent systems.

Built for agentic AI

AI agents do not just read pages. They summarize, cite, translate, compare, navigate, extract, and sometimes trigger actions. ZML gives those agents clear boundaries: what they may read, what they may summarize, what they may cite, what they must ignore, and what they are forbidden to export, scrape, or train on. The page carries its own AI rules instead of depending on guesswork.

Trusted zones, not blind text

In the AI era, not every part of a webpage should have the same authority. A publisher statement, a product description, a legal notice, and a user comment are not equal. ZML lets the page mark trusted zones, public zones, restricted zones, and untrusted zones. That means prompt injection can be contained, user-generated content can be separated from official instructions, and AI systems can understand which parts of the page carry authority.

Identity and integrity built in

AI needs provenance. Users need proof. Publishers need control. ZML makes publisher identity, asset integrity, trust rules, and Zelen sealing part of the document itself. A ZML page can say who published it, what files belong to it, whether assets are hashed, whether the page is signed, and whether AI training is denied. The result is a web page that is not only displayed, but verified.

ZML for the AI Era — AI Policy, Trust, Manifest, Publisher Identity

Kill HTML
Write ZML.

Same hero, different philosophy

ZML is what HTML would be if it were redesigned today.

Static by design

AI-aware from day one

Trust-aware by default

Reads like a script. Compiles like a contract.

Why ZML Feels Human

Readable verbs

Margin Bar blocks

Policy is content

Invented by Haja Mo

Question the rules, change the game

Write Markdown. Get ZML safety. Zero conversion tax.

A full vocabulary for the modern static web.

Your page tells AI agents what they can and can't do.

HTML has zero AI permissions. Zero.

ZML was created for the artificial intelligence era.

Built for agentic AI

Trusted zones, not blind text

Identity and integrity built in

From .zml file to Vega Browser in five clean steps.

A spec that grows where the web is going.

Deep Markdown & Author Ergonomics

AI Containment & Evidence

NovaWeb & Vega Native

The Full ZML Reference Bible.

The web Tim Berners-Lee
would build today.

Kill HTML Write ZML.

Same hero, different philosophy

ZML is what HTML would be if it were redesigned today.

Static by design

AI-aware from day one

Trust-aware by default

Reads like a script. Compiles like a contract.

Why ZML Feels Human

Readable verbs

Margin Bar blocks

Policy is content

Invented by Haja Mo

Question the rules, change the game

Write Markdown. Get ZML safety. Zero conversion tax.

A full vocabulary for the modern static web.

Your page tells AI agents what they can and can't do.

HTML has zero AI permissions. Zero.

ZML was created for the artificial intelligence era.

Built for agentic AI

Trusted zones, not blind text

Identity and integrity built in

From .zml file to Vega Browser in five clean steps.

A spec that grows where the web is going.

Deep Markdown & Author Ergonomics

AI Containment & Evidence

NovaWeb & Vega Native

The Full ZML Reference Bible.

The web Tim Berners-Leewould build today.

Kill HTML
Write ZML.

The web Tim Berners-Lee
would build today.