AI and Machine Resources

Use this surface to select the smallest authoritative input for an agent, editor, or automation task. Every endpoint is static, versioned with the documentation build, and available without an account or API key.

MACHINE INTERFACE

Agent resource console

VERIFYING

Documents

--

Endpoints

8

Config schema

--

Source

--

DiscoveryContextContracts

llms.txt

Bilingual

Concise map for selecting the smallest relevant source.

/llms.txt

Machine manifest

Bilingual

Versioned page inventory with canonical URLs and SHA-256 digests.

/ai-index.json

AGENT BOOTSTRAPSmallest-context first

Read https://kerr-group.github.io/pmoke/llms.txt first. Select the smallest relevant locale-specific Markdown source. Prefer generated JSON contracts for exact CLI and config fields. Preserve versions, field paths, units, and canonical URLs. Validate configuration semantics with pmoke config validate; do not infer hardware state, credentials, or laboratory addresses.

Copy bootstrap

Retrieval order

1. Start with llms.txt for discovery.
2. Fetch only the relevant per-page Markdown URL from the selected locale.
3. Use generated JSON contracts for exact commands, options, fields, and defaults.
4. Expand to a locale context feed only when the task spans several pages.
5. Use the bilingual full feed only when cross-language context is required.

Authority boundary

Documentation describes supported behavior, but it cannot observe a workstation or instrument. pmoke config validate remains authoritative for configuration semantics; pmoke doctor hardware remains authoritative for compiled features and live hardware. An agent must not infer credentials, addresses, driver availability, or instrument state.

Continue with agent workflow and versioning, inspect the resource contracts, or review search and privacy.