Skip to content

CONFORMANCE.md

Latest commit

 

History

History
107 lines (79 loc) · 2.84 KB

CONFORMANCE.md

File metadata and controls

107 lines (79 loc) · 2.84 KB
Raw

AVL Conformance

AVL conformance is intentionally layered so a site can become agent-readable in small, useful steps.

Levels

Level Required Signals Purpose
L0 @meta, @intent, and page-level discovery Agents can identify what a page is for.
L1 L0 + @state Agents can read structured page data without scraping.
L2 L1 + @actions Agents can understand available actions.
L3 L2 + @context and @nav Agents can reason over meaning and traverse related views.

Required Checks

Document

  • Response content type is text/agent-view; version=1.
  • @meta.v is present.
  • @meta.route is present.
  • @meta.generated is present.
  • @intent.purpose is present.
  • @intent.audience is present.
  • @intent.capability is present.

Discovery

At least one discovery path is required for L0:

  • .agent URL suffix.
  • Accept: text/agent-view content negotiation.
  • HTML <link rel="alternate" type="text/agent-view">.
  • HTTP Link header.
  • /agent.txt manifest.

Recommended discovery stack:

  • /agent.txt
  • /.agent
  • Per-page /{path}.agent
  • HTML head alternate link.
  • Crawlable body link or badge.
  • /llms.txt companion.

Manifest

/agent.txt should include:

  • version.
  • content-type.
  • producer/platform.
  • discovery methods.
  • route patterns.
  • related companion resources where available.

Security

  • Public AVL documents must expose only public information.
  • Authenticated AVL documents must inherit the same session and permissions as the human page.
  • @actions must only list actions available to the represented viewer.
  • External validation links must be user-initiated unless the plugin clearly discloses automatic calls.

Validator

The root package ships a first-party validator CLI:

npx @frontier-infra/avl validate https://example.com
npx @frontier-infra/avl validate https://example.com/pricing --level L2
npx @frontier-infra/avl validate-file ./samples/page.agent --json

Check groups:

  • document.*
  • toon.*
  • discovery.*
  • manifest.*
  • companion.*
  • conformance.*

The initial validator checks required sections and fields, TOON list/table shape, page-specific .agent discovery, /agent.txt, HTML discovery links, and /llms.txt companion availability. Future versions should expand this into schema, auth, action input, and provenance-specific checks.

Initial grammar and document fixtures live under:

specs/toon-grammar.md
specs/fixtures/valid/
specs/fixtures/invalid/

CMS Adapter Conformance

CMS plugins should verify:

  • /agent.txt.
  • /.agent.
  • /{path}.agent.
  • /llms.txt and /lm.txt where supported.
  • HTML discovery on public pages.
  • Admin readiness checks.
  • No automatic external calls without disclosure.

The WordPress plugin currently implements this pattern and should be treated as the reference CMS adapter.