owner: gmikcon status: active last_reviewed: 2026-05-10 review_interval: 90d confidence: medium
Use this structure when documenting an application, infrastructure daemon, smart-home component, project service, or locally hosted tool.
Describe what the service does and why it exists.
List public, local, VPN, API, management, SSH, and other access points. Prefer linking to 40-inventory/endpoints.yml.
List databases, queues, APIs, filesystems, DNS records, upstream services, Home Assistant integrations, or project repositories.
Describe persistent data, important paths, databases, media storage, and backup expectations.
Describe deployment source, repository, branch, build/runtime commands, environment files, and restart procedure.
Do not document raw secret values.
List stale facts, weak assumptions, missing monitoring, backup gaps, security notes, or migration risks.