# Documentation changelog and current guidance

Use the newest documentation version and current generated schemas. Older examples are historical context, not authority when they conflict with the current corpus.

## Current version: 2026-08-11.3

Expanded the agent-first corpus from basic task coverage to the full customer planning lifecycle:

- direct and idea-based plan creation;
- RSVP deadlines, tipping, capacity, delivery, active edits, roster management, plan progress, discard, and cancellation;
- recipient authentication, invite claiming, RSVP changes, and calendar handoff;
- Connected Friends, Friends in Mind, connection links, and availability boundaries;
- complete My Dominos status and personal-inventory guidance;
- detailed singular capture and roundup recovery;
- recipient-side shared Ideas List copying and connection consequences;
- created ideas, private places, account access, and security;
- Agent Access token creation, least privilege, rotation, and revocation;
- explicit ChatGPT, Claude, and static-bearer MCP compatibility checks;
- SMS, MCP, and Capability API task recipes;
- cross-surface support and current-limits references;
- machine-readable documentation manifest, search, word counts, and token estimates;
- semantic coverage assertions for representative support questions.

Preferred guidance:

- Use task-specific pages rather than only `/llms.txt`.
- Use `/docs/manifest.json` for catalog metadata and `/docs/search.json?q=...` for discovery.
- Use authenticated MCP `tools/list`, `/docs/mcp-tools.json`, and `/docs/openapi.json` for current schemas.
- Treat `2026-08-11.3` behavior as current unless a newer docs version is available.

## Version 2026-08-11.2

Added complete provider-specific calendar guidance:

- direct Google authorization and access levels;
- Apple/iCloud public calendar publishing;
- Microsoft Outlook/Microsoft 365 ICS publishing;
- other ICS and webcal providers;
- calendar privacy, secret-link handling, multiple calendars, management, and troubleshooting.

Preferred calendar guidance changed from “Google or a calendar URL” to explicit provider routing with accurate Apple and Microsoft limitations.

## Version 2026-08-11

Created the initial agent-first documentation system:

- stable Markdown task pages;
- HTML/Markdown content negotiation;
- global and surface-scoped `llms.txt` indexes;
- `llms-full.txt` offline corpus;
- generated OpenAPI and MCP tool catalogs;
- generated capability reference;
- cross-surface outcome and confirmation rules.

## Deprecation policy

When guidance changes:

1. update the task page and documentation version;
2. update generated schema descriptions when the runtime contract changed;
3. record the preferred replacement here;
4. keep old behavior only when a real supported compatibility window exists;
5. add a semantic documentation test for the user question that exposed the change.

Assistants should not follow a deprecated menu path, capability version, authentication mechanism, or confirmation rule merely because it appears in an older answer.

## Machine checks

Use:

- `X-Domino-Docs-Version` to identify the corpus version;
- `ETag` to cache exact Markdown safely;
- `X-Domino-Docs-Words` and `X-Domino-Docs-Token-Estimate` to budget retrieval;
- `documentation_fingerprint` in generated machine references to detect contract changes.

## LLM answering guidance

- Prefer the newest fetched page over model memory.
- When a user reports different visible controls, acknowledge possible rollout drift and reason from their screen without inventing hidden behavior.
- Never combine an old confirmation rule with a new runtime contract.
