Skip to main content
Work index
Partial implementationMixedImplementedCS-W-001

Agentic Accessibility

Machine-readable does not mean agent-accessible.

Public, privacy-cleared evidence. The project page distinguishes an implemented artifact from broader claims still under research.

Specification fieldOARSH-C · Emerging
Agent-readyEnvironment
  1. OOrientable
  2. AAddressable
  3. RRelational
  4. SStateful
  5. HHabitable
  6. CComposable
Accessibility expressed as navigable structure, not a retrospective accommodation.

Developer resources

Put the framework into code.

The problem

Agents can receive pages, tools, files, and structured data while remaining unable to determine where they are, what is current, which source is authoritative, or what action is permitted.

Governing idea

Accessibility is an environmental property. An agent-ready environment makes orientation, addressability, relationships, state, habitability, and composition explicit enough to inspect.

What exists now

The OARSH-C working model, a developer guide, machine-readable coverage disclosure, semantic regions, structured entities, discovery metadata, and this site as a partial static reference implementation.

Claim boundary

What this work does not establish.

  • 01

    OARSH-C is an emerging working model, not a ratified standard.

  • 02

    The current site demonstrates only the subset applicable to a static publication environment.

  • 03

    Cross-model cold-start evaluation and independent accessibility review remain ahead.

Learn the distinction

Begin with the difference between access and orientation: finding a file is not the same as knowing why it matters, whether it is current, or what may be done with it.

Evidence state

What the public record currently supports.

These signals are privacy-cleared and intentionally bounded. They show that work exists without inflating maturity or exposing protected source context.

  1. 01

    The public site exposes named semantic regions, structured entities, discovery metadata, and an explicit OARSH-C coverage record.

  2. 02

    The developer guide separates working principles, implementation criteria, security boundaries, and known gaps.

  3. 03

    Source collections document the recurring failure mode: information can be retrievable while the surrounding environment remains operationally illegible.

Next decision

Define the minimum accessible-environment contract and run deterministic cold-start evaluations across different agent systems.

Related research · CS-RC-003

Continue

CS-W-002

Situated Memory