Source: https://mayphus.org/ai-native-website-interfaces/
Title: AI-native website interfaces
Metadata: {"category":"note","id":"ai-native-website-interfaces","kind":"artifact","language":"en","route":"/ai-native-website-interfaces/","tags":["ai","interfaces","agents","web"],"type":"project"}

# AI-native website interfaces

Evolving proposal · 26 July 2026

What should a website become when people and AI agents are both first-class readers? My proposal is to make the durable unit an AI-readable investigation object: a question, claims, evidence, relationships, work state, and possible next actions. The human page is one view of that work.

## Why structure the investigation?

A conventional interface can hide relationships behind menus, tabs, and playback steps. Explicit fields could let a reader inspect a claim alongside its evidence and limits. This is a working hypothesis, not a benchmark result. A chatbot could provide another view, but adding one does not by itself create this structure.

## Worked example: a FreeBSD documentation patch

The [thin-jail documentation fix](https://mayphus.org/a-tiny-freebsd-jail-doc-fix/) provides a small real example. These fields organize its existing public account; they are an illustrative object, not a finalized schema or an executable workflow.

- **Question:** Why can relative symlinks point at the wrong tree after following the NullFS thin-jail layout?
- **Claim:** A link under `/skeleton/etc/ssl/certs` targeting `../../../usr/share/certs/...` resolves under `/skeleton/usr/share`, while the shared files are under `/usr/share`.
- **Evidence and limit:** The [article's path example](https://mayphus.org/a-tiny-freebsd-jail-doc-fix/) explains that resolution. This is a path-level explanation, not evidence that a complete jail was tested here.
- **Proposed fix:** Add `share → ../../usr/share` and `sbin → ../../usr/sbin` inside the skeleton's `usr` directory, bridging back to the shared base.
- **Patch provenance:** [FreeBSD bug 280339](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=280339), its [original patch](https://bugs.freebsd.org/bugzilla/attachment.cgi?id=253021&action=edit), and its [rebased patch](https://bugs.freebsd.org/bugzilla/attachment.cgi?id=271170&action=edit) are the public references for the submitted contribution.
- **Relationship:** The bridge changes the path reached by existing relative links; it does not require rewriting each certificate link.
- **Work state:** Documentation patch submitted. This example does not establish that it was merged or that the current Handbook includes it.
- **Next action:** Check the public patch disposition and test the documented layout in an appropriate FreeBSD environment before claiming a verified end-to-end outcome.

Keeping those fields together makes the distinction visible: an explained path calculation, a submitted patch, and a merged or tested outcome are different claims. Each needs its own evidence.

## What this page demonstrates

The example gives a human-readable arrangement of a real question, claim, source links, and unresolved outcome. It is authored in the same canonical record as the rest of the page and is available through the site's existing text and document interfaces. It does not add a new structured API, automated investigation capability, or permission to perform the next action.

## What still needs testing

The shared schema, permission model, and balance between machine detail and readable prose remain open. There are no measured improvements in clicks, tool calls, time, or recovery on this page.

The next step is to turn this example into a small schema, validate a representation against it, and compare a real reading task with the current page. Keep the source links and uncertainty attached to individual claims throughout that experiment.