A bounded starting point for agents.

Machine-readable entry points

• https://dove.sh/llms.txt — short index and source-of-truth rules.
• https://dove.sh/llms-full.txt — compact architecture, CLI, API, provisioning, and customization context.
• CLI source and core source — canonical shipped behavior.

Read https://dove.sh/llms.txt first. Follow its source precedence.
Before changing a share page, also read:
https://dove.sh/docs/custom-pages/
https://dove.sh/docs/security/

Source precedence

1. Current tests and source code for what is shipped.
2. Current CLI --help for user-facing syntax.
3. Approved design documents for intended behavior not yet implemented.
4. Marketing copy for explanation, never as an API contract.

If sources disagree, preserve the discrepancy in your report. Do not silently merge a planned command into current documentation or repeat a stale source comment as release status.

Agent checklist: add or customize a page

1. Identify whether the page is the static marketing/docs site or the embedded operator share page.
2. Read the nearest layout/components and reuse the dove mark, tokens, typography, focus treatment, and light/dark behavior.
3. For share/request pages, enumerate states before styling. One trust-sensitive action should have focus at a time.
4. Map every network call. Prove no fragment, content key, plaintext, decrypted metadata, or PIN enters logs or unrelated services.
5. Prove a page load and metadata fetch have no access-policy side effect.
6. Keep the 2 GB browser threshold and CLI handoff unless the implementation contract changes.
7. Build the static output; test keyboard, paste, narrow viewport, dark mode, reduced motion, expired/locked/error states, and an unfurler-like GET.
8. Update relevant human docs, llms.txt, and llms-full.txt when behavior changes.

Interfaces not to invent

There is currently no stable CLI JSON mode, runtime theme manifest, external-backend wire protocol, unattended provision flag, destroy command, or released file-request CLI. Propose those explicitly as designs; do not write examples that imply they ship.

Minimum acceptance evidence

• The static site builds without warnings that affect behavior.
• Every linked internal route exists.
• CLI examples match current clap syntax.
• Rust examples match public signatures.
• No page-load path calls the decrementing download endpoint.
• Custom share pages contain no third-party script or telemetry by default.
• Documentation labels designed and future work honestly.