# Capability surface

A public, versioned interface for discovery, evaluation, routing, and reuse by people and language models.

Current stage: Public read and routing layer
Trust boundary: The deployed site publishes information and a contact route. It does not authenticate agents, delegate authority, or execute transactions.

Action layer: not-implemented
Delegated authority: none

## Principles

- The git repository is canonical; the deployed site is the public interface.
- Humans and language models use the same canonical information through appropriate representations.
- Claims should be grounded in shipped content, plain-text mirrors, logs, and source-controlled change.
- Capabilities should be expressed as simple, inspectable web artifacts before becoming heavier software.
- Public discovery never implies permission to act for the represented party.

## Current capabilities

### Site index

Route: https://jayweeldreyer.com/llms.txt
Kind: text/llms
Use: Orient a model to the public site, major collections, and delegation guidance.

### Writing corpus

Route: https://jayweeldreyer.com/llms-full.txt
Kind: text/markdown
Use: Fetch the full public writing corpus as one plain-text document.

### Capability manifest

Route: https://jayweeldreyer.com/capabilities.json
Kind: application/json
Use: Read the current public capability surface as structured data.

### Markdown mirrors

Route: https://jayweeldreyer.com/writing/{slug}.md; https://jayweeldreyer.com/work/{slug}.md; https://jayweeldreyer.com/done/{date}.md
Kind: text/markdown
Use: Use plain source mirrors for individual public entries instead of scraping rendered HTML.

### Done log

Route: https://jayweeldreyer.com/done
Kind: html/rss/markdown
Use: Inspect recent movement and receipts rather than relying on static claims.

### Contact route

Route: https://jayweeldreyer.com/contact
Kind: html/mailto
Use: Prepare a specific introduction when there is enough signal to connect.