{"topic":"overview","content":"# SecondPage overview\n\nSecondPage publishes Pages that humans can share, review, and revise across models and chatbots. A Page has a stable URL and immutable versions. The control plane is `https://secondpage.cc`; published Pages open at `https://<page-slug>.second.page/`.\n\nConnect to `https://mcp.secondpage.cc/mcp` with OAuth or an organization API key. OAuth MCP clients operate in one organization at a time. `get_organization_context` identifies it; `request_organization_switch` returns a browser handoff the human must approve. API keys stay scoped to their organization.\n\nThe **core contract** is the authoritative publishing workflow. Load it with `load_secondpage_skill({ \"topic\": \"core\" })`. For signed uploads and export/revision examples use `topic: \"publishing\"`; for data-backed Pages use `topic: \"live-data-connections\"`. `topic: \"all\"` includes core once and every reference.\n\nChoose the Page's layout to suit the reader: regular scrolling Page, deck for actual slides, or connected Page when its source must refresh. Agents author and validate the static files themselves. SecondPage stores and serves the supplied bundle, with platform attribution and authorized review tools.\n\nStarter Pages are available for 30 days from creation. `starter_page_expired` means content is unavailable under the current organization entitlement; `list_pages` can still return metadata. Explain the returned state neutrally and ask an organization owner to resolve it. Fair-use limits are temporary and should be retried after their reset window.\n\nHuman feedback stays with the Page. Prefer revising an existing Page over creating a duplicate. Use update reasons and threaded comment replies to explain what changed and why, and preserve stable semantic edit targets across revisions.\n\nFor newly authored slide decks, `prepare_deck` assembles a standard bundle without publishing or calling a model. Publish with deck intent and treat presentation readiness separately from publication: only `ready` verifies controls for the exact version. Follow pending version-bound guidance with compact `read_page` calls and preserve existing deck exports rather than rebuilding them unnecessarily.\n"}