live-data-artifactslisted

# Live data artifacts A published page can call **the viewer's claude.ai connectors** and render current data. Powerful, and narrower than it first appears — read the constraints before designing around it. **Load the host's `artifact-capabilities` skill when it is available before writing a connector call.** It carries the live capability roster and authoritative type definitions. If it is absent, do not guess: build the baked snapshot path and state that live mode is unavailable. --- ## Decide whether you should Four questions. A "no" on any of the first three means build a snapshot instead (`artifact-architecture`, Tier 1). 1. **Is the source a connector on the organization's claude.ai account?** A locally-configured MCP server is *not* reachable from a published page. Local setup is irrelevant here — this is about what the org exposes. 2. **Does this page need to avoid being shared publicly?** A page declaring connector access **cannot be shared publicly**. Each viewer authenticates as themselves. For financial data that is the right posture; it is also a distribution constraint. A board pack that only opens for people with warehouse credentials is not a board pack. 3. **Does every intended viewer have access to the connector?** If half the audience gets `not_granted`, you have built a page that works for you and is empty for them. 4. **Would a changing number be a defect?** For anything reported, sent, or presented — yes. Liveness suits an o