Agentic web hub

Governance artifacts

Governance files brought into scope by this page

This page is anchored to published surfaces that declare identity, precedence, limits, and the corpus reading conditions. Their order below gives the recommended reading sequence.

Entrypoint#01

Canonical AI entrypoint

/.well-known/ai-governance.json

Neutral entrypoint that declares the governance map, precedence chain, and the surfaces to read first.

Governs: Access order across surfaces and initial precedence.
Bounds: Free readings that bypass the canon or the published order.

Does not guarantee: This surface publishes a reading order; it does not force execution or obedience.

Entrypoint#02

Public AI manifest

/ai-manifest.json

Structured inventory of the surfaces, registries, and modules that extend the canonical entrypoint.

Governs: Access order across surfaces and initial precedence.
Bounds: Free readings that bypass the canon or the published order.

Does not guarantee: This surface publishes a reading order; it does not force execution or obedience.

Discovery and routing#03

LLMs.txt

/llms.txt

Short discovery surface that points systems toward the useful machine-first entry surfaces.

Governs: Discoverability, crawl orientation, and the mapping of published surfaces.
Bounds: Incomplete readings that ignore structure, routes, or the preferred markdown surface.

Does not guarantee: A good discovery surface improves access; it is not sufficient on its own to govern reconstruction.

The website as an action environment

The agentic web names a change of regime: a website is no longer only visited by a human, indexed by a search engine, or summarized by a model. It can become an environment in which an agent interprets an interface, plans a path, selects an action, and attempts to execute it.

This page is the personal entry point for my work on that shift. It does not replace Pagup service pages. It carries the thesis, distinctions, and doctrinal consequences: what changes when an interface becomes readable by systems that can act.

Why this hub exists

Classic technical SEO asked a central question: can a search engine discover, read, and understand a page? The agentic web adds another question: can an agent understand what it sees, identify the legitimate action, preserve context, and act without ambiguity?

That question reconnects topics that were often handled separately: semantic HTML, accessibility, visual stability, JavaScript hydration, CTA hierarchy, forms, structured data, internal linking, and machine-readable surfaces. Together, they form a grammar of action.

Canonical concepts

Start with these definitions:

Agentic web: the website as an interpretable and actionable environment.
Agentic navigability: the ability of an agent to traverse and manipulate an interface.
Interpretable interface: coherence between visual intention, HTML structure, and machine exposure.
Accessibility Tree: a programmable map of roles, names, states, and relationships inside an interface.

These terms should be read with agentic, agentic risk, execution boundary and agentic response conditions. The issue is not only to make a page understandable. It is to govern the conditions under which understanding can become action.

Doctrine and framework

The page Agentic web and Dual Web places this transition within the distinction between human surface, machine surface, and agentic surface. A human can compensate for a weak label, an ambiguous card, or a styled button. A crawler can ignore the interface and extract the document. An agent must connect document, interface, intention, and action.

The agentic web readability framework proposes a reading method: DOM stability, coherence between visual rendering and the accessibility tree, actionable semantics, hydration risk, interaction determinism, visual hierarchy, and governance of paths.

Text series

This series states the core implications:

Boundary with Pagup

On this site, I formalize the thesis: systems no longer only read documents, they reconstruct conditions of action. On Pagup, that thesis becomes an audit, design, and technical hardening method. The distinction is deliberate: here, the intellectual category; there, operational implementation.

Reading rule

Do not reduce the agentic web to an accessibility checklist, a machine-readable file, or an AI visibility promise. The deeper question is stricter: does the interface expose its intentions, limits, actions, and states clearly enough for an autonomous system to act without inventing the missing context?