@@ -12,6 +12,10 @@ Assume every commit and every line of history will be public.
 - Be concise; lead with importance. See [STYLE_GUIDE.md](STYLE_GUIDE.md) for
   the full rationale, worked examples, and the complete list of banned words,
   wordiness swaps, and vocabulary rules Vale enforces.
+- Preserve prerequisites, scope, and exceptions when rewriting. Check leads
+  against the procedure and public reference, then reconcile sibling guides,
+  glossary entries, and built-output tests. Shorter wording is not evidence
+  of factual accuracy.
 - Do not add navigation to a section until that section has a real page or
   generated source.
 - Authored navigation comes from `content/**` and its `meta.ts` files.
 
@@ -16,11 +16,13 @@ CI runs `test:docs` after the production build. It uses Node's test runner and e
 - Authored pages open with a subject or action instead of the repeated “After this page…” promise.
 - The homepage and Quickstart offer dashboard Drop before CLI installation, and the linked Publishing page describes the Drop flow.
 - The homepage links to a glossary that defines its recurring product terms.
-- Database explains how to enable Zero before it teaches queries.
+- Database links the full Zero runtime declaration and names its required server file before teaching queries.
 - Troubleshooting gives readers a first diagnostic step before listing error codes.
 - The opening paragraphs on Versions, Crons, Environment variables, Access, Caching, and Traffic stats answer specific reader questions. Each test names the question and the evidence expected near the top of the built page.
 
-These are regression contracts for the changed entry paths and first-screen explanations. They make a future edit fail if it hides those answers again. They do not grade tone, prove that shorter text is clearer, or measure whether a person can complete a real task. Those claims need editorial review and reader testing.
+These are regression contracts for the changed entry paths and first-screen explanations. They make a future edit fail if it hides those answers again. They do not prove product behavior, grade tone, prove that shorter text is clearer, or measure whether a person can complete a real task. Check each expected answer against the public contract and the page's exceptions before encoding it in a test.
+
+The October 6 review corrected assertions that reinforced overbroad access and traffic claims. The checks now distinguish views from requests and unique visitors, retained ready versions from other versions, and removal of one public grant from removal of all access. Cache refresh is a request, not an unconditional freshness guarantee.
 
 ## Other gates
 
 
@@ -1,6 +1,6 @@
 # Authored-docs writing audit
 
-The reviewer click-path and command comparisons in [DOCS_QA_COMPARISON.md](DOCS_QA_COMPARISON.md) measure answer findability and factual accuracy. Neither measures whether the authored prose is better for readers. This point-in-time audit checks the writing changes against `main` as of October 5, 2026. Repeatable checks for the current docs are in [DOCS_TEST_SUITE.md](DOCS_TEST_SUITE.md).
+The October 5 audit below measured structure and wording, but missed factual overstatements. Its candidate examples are historical, not verified guidance. The [October 6 semantic review](#semantic-review-october-6-2026) records the corrections and their evidence. Repeatable checks for the current docs are in [DOCS_TEST_SUITE.md](DOCS_TEST_SUITE.md).
 
 ## Method
 
@@ -29,7 +29,7 @@ The edited leads now put several useful answers before the reader has to scan th
 | Caching | How do I force a fresh response? | Promises to explain cache behavior | Says republishing forces one |
 | Traffic stats | Are crawlers included? | Promises to explain counts | Says crawler traffic is excluded |
 
-These rows are illustrative checks of what the opening now tells a reader, not an independent six-question success rate. The underlying facts and the full procedures remain on the pages.
+These rows record what the candidate openings claimed at the time, not an independent six-question success rate. Review later found that several claims dropped necessary qualifications, including the caching and traffic examples.
 
 For example, Versions opened with “After this page you know what a version holds, how it reaches `ready`, how the `live` pointer moves, and how to roll back to any earlier version in seconds.” It now opens with “A rollback doesn't rebuild anything — it just repoints `live` at a version that already exists, which is why it takes seconds, not minutes.” The new sentence answers the likely rollback question; the page still explains version states below it.
 
@@ -38,3 +38,46 @@ For example, Versions opened with “After this page you know what a version hol
 The manual review caught five candidate leads that were shorter but spent the first sentence on a less useful detail: slug validation on Spaces, polling mechanics on Logs, archive flags on Frameworks and builds, CLI naming on Publish from Git, and remote WP-CLI output on WordPress. Each now leads with the page's main task or mental model. The removed detail was checked elsewhere on the same page and retained or moved into the body.
 
 This audit establishes changes in structure and in which facts appear first. It does not show that real readers complete tasks faster or understand the docs better. Shorter openings could also lose useful context for some readers. That requires reader testing. Vale now passes after two existing technical plurals (`GETs` and `TTYs`) were written as plain explanations; its rules do not detect repeated sentence structures or judge whether a page leads with the right fact.
+
+## Semantic review, October 6, 2026
+
+Reviewed every changed MDX hunk in the PR: 78 existing pages plus the new glossary. Compared each rewrite with its original wording, then checked broader claims against the relevant procedures, exceptions, sibling guides, and producer-owned public reference snapshot. This was a documentation consistency audit, not a live product test or a reread of every unchanged paragraph.
+
+The first review fixed eight findings covering stats, caching, routing, anonymous key recovery, Zero pricing, hosted MCP authentication, team plan limits, and Zero setup. The follow-up applied the same reasoning across the full rewrite and corrected related claims at other entry points.
+
+| Claim family | Correction | Evidence checked |
+| --- | --- | --- |
+| Retry safety | Name the key, matching request scope, 24-hour replay window, and unstored outcomes that execute again | `content/api/idempotency.mdx`, Send a key / What is not stored |
+| Pagination | Limit the common cursor model to endpoints that use it; retain endpoint defaults, ordering, offset paging, and unpaginated lists | `generated/openapi/api.json`: `searchDocs`, `listSpaceStorageObjects`, `listSpaceDomains` |
+| Publish and rollback | Preserve no-op publishes, ready/retained targets, manual promotion, and preview behavior | Public reference: `createSpaceVersion`, `promoteSpaceVersion`; `content/(concepts)/versions.mdx`; `content/(publish)/ci.mdx` |
+| URL lifetime | Separate a stable version URL from retained files; distinguish domain attachment from slug rename | `content/(concepts)/spaces.mdx`, Renaming; `content/cli/versions.mdx`, sf versions rm |
+| Access | Revoking one matching grant does not revoke other grants or the team's permissions | `content/(serve)/access.mdx`, scoped grants; `content/(concepts)/teams.mdx`, role and default-access tables |
+| Runtime setup | Scope auto-detection to Functions layouts; preserve the Zero declaration and the Functions database alternative | `content/(dynamic)/functions.mdx`, Where the code lives / Declare it; `content/cli/db.mdx` |
+| Variables and logs | A queued re-finalize can apply variables; logs have retention, ingestion delay, and static-runtime limits | `content/(dynamic)/environment-variables.mdx`; `content/(dynamic)/logs.mdx`; `listSpaceRuntimeLogs` |
+| Archives and Git | Preserve prebuilt archives, branch auto-deploy controls, and the GitHub App prerequisite | `generated/cli/index.md`, sf publish `--prebuilt`; `content/(publish)/git.mdx`; `content/cli/git.mdx` |
+| CLI helpers | Linking selects a Space rather than removing all publish options; apply and continuation helpers mutate state; continuation needs claim approval | `content/cli/project.mdx`; `content/cli/agent-commands.mdx`; `content/(publish)/anonymous-and-claim.mdx` |
+| WP-CLI and storage | Remote WP-CLI returns no printed output, even for read commands; object IDs do not replace read keys | `content/(dynamic)/wordpress.mdx`, Local versus remote; `content/(dynamic)/storage.mdx`, returned URL |
+| Agent reach | Keep supported-client detection, skill installation, permission ceilings, human-only actions, and team-automation revocation exceptions | `content/cli/agents.mdx`; `content/agents/skills.mdx`; `content/agents/permissions.mdx` |
+| Ownership and billing | Distinguish self-serve teams from partner customer ownership; billing reads differ from plan changes; key rotation depends on switching consumers first | `createSpace` public reference; `content/platforms/partner-api/customers.mdx`; `content/(account)/billing.mdx`; `content/(account)/api-keys.mdx` |
+| Cache and schedule application | Repeat public-cache exceptions in troubleshooting; crons follow the live version | `content/(serve)/caching.mdx`; `listSpaceCrons` public reference |
+| Sentence splitting | Limit missing generated CSS to the dynamic class instead of declaring the whole app unstyled | `content/(dynamic)/zero-runtime.mdx`, Styling |
+
+Coverage by original PR section:
+
+| Section | Pages compared |
+| --- | --- |
+| Account | 3: api-keys, authentication, billing |
+| Concepts | 3: spaces, teams, versions |
+| Dynamic | 8: crons, database, environment-variables, functions, logs, storage, wordpress, zero-runtime |
+| Publishing | 8: anonymous-and-claim, ci, frameworks, git, publish, recipes/html, recipes/next, wordpress-data-sources |
+| Reference | 3: config-file, glossary, limits |
+| Serving | 8: access, caching, customization, domains, routing, site-pages, stats, urls |
+| Agents | 9: claude-code, claude-desktop, codex, cursor, mcp-server, other-clients, permissions, sf-setup, skills |
+| API | 9: authentication, errors, idempotency, index, operations, pagination, rate-limits, sdk, webhooks |
+| CLI | 20: agent-commands, agents, api-keys, api, builds, db, domains, env, git, index, login, project, publish, share, source, spaces, storage, teams, versions, zero |
+| Entry pages | 3: index, quickstart, troubleshooting |
+| Platforms | 5: partner-api/configuration, customers, go-live, index, tokens |
+
+The style guide and contributor instructions now require this meaning check. Existing built-output assertions were updated where they reinforced a misleading claim. No new regex suite is presented as independent proof of product behavior. Generated references remain producer-owned and unchanged. The previously recorded support-contact and API-key preset gaps remain outside these corrections.
+
+Verification with Bun 1.3.11 and Node 24 passed: frozen dependency install, generated-reference and command-example checks, type check, strict link validation, production build, all 26 docs tests, composed-site audit, public-safety check, Vale, route verification, and `git diff --check`.
@@ -49,8 +49,38 @@ In practice:
   definition of "wordy." A 22-word sentence that chains four clauses is
   still a problem this rule won't catch; use judgment, not just the word
   count.
-- **Cut filler and hedging.** If a sentence works with a phrase removed,
-  remove it.
+- **Cut filler, preserve conditions.** Remove a phrase only if the shorter
+  sentence remains true for the same readers and situations. A plan limit,
+  required flag, credential type, runtime, or exception is not filler.
+
+## Preserve meaning when shortening
+
+Read a rewritten lead beside the full procedure and its exceptions. Check
+the original wording and the public reference before treating the shorter
+sentence as equivalent. A fact moved out of a subsection must keep that
+subsection's scope: a hosted MCP guarantee does not describe local stdio.
+
+- Keep prerequisites next to the action: a ready version for rollback,
+  an idempotency key for replay, or the plan required to add members.
+- Keep distinct states distinct: available versus free, ready versus live,
+  a permanent URL versus retained files, and configuration saved versus applied.
+- Check words such as "every," "always," "never," "only," and "any" against
+  counterexamples. Name the supported case instead of broadening a claim.
+- After splitting a sentence, make sure its condition still governs every
+  sentence that depends on it. Repeat the condition when necessary.
+- Check sibling guides, CLI pages, descriptions, glossary entries, and tests
+  for the same claim. A correction is incomplete if another entry point
+  teaches the old rule.
+
+For example, "Every list uses cursors" drops offset-based and unpaginated
+endpoints. "Cursor-paginated endpoints return `pagination.nextCursor`; check
+the endpoint's limits and ordering" preserves the useful rule and its scope.
+
+Tests of built docs can check that a prerequisite or exception stays visible.
+They do not prove product behavior. A regex matching confident wording is
+not evidence that the wording is true, and shorter copy is not a pass criterion.
+
+## Concision examples
 
 Worked example, from the page-opener cleanup:
 
@@ -70,9 +100,12 @@ Another:
 > recognize every other credential Spacefast hands you by its prefix." (33
 > words, 4 clauses)
 >
-> After: "You can mint a scoped API key with exactly the permissions it
-> needs, then rotate it without downtime." (18 words — the credential-prefix
-> table further down the page already covers the dropped clause.)
+> After: "Team owners and admins can mint scoped API keys. To rotate without
+> interrupting an integration, create a replacement, switch the integration
+> to it, verify a request, and only then revoke the old key."
+
+This version keeps the role prerequisite and the order that makes rotation
+safe. The credential-prefix table can stay below; the rotation condition cannot.
 
 (These two "after" versions also show the fix from the next section — no
 "after this page" framing. The intermediate step, where the sentence was
@@ -96,8 +129,8 @@ Open with the fact itself, not a sentence announcing that a fact is coming:
 > Templated: "After this page you can mint a scoped API key and rotate it
 > without downtime."
 >
-> Direct: "You can mint a scoped API key with exactly the permissions it
-> needs, then rotate it without downtime."
+> Direct: "To rotate a key without interrupting an integration, switch to
+> its replacement and verify a request before revoking the old key."
 
 > Templated: "After this page you know whether to publish your own build
 > output or let Spacefast build it."
 
@@ -5,7 +5,7 @@ sidebar:
   order: 2
 ---
 
-You can mint a scoped API key with exactly the permissions it needs, then rotate it without taking anything down.
+Team owners and admins can mint scoped API keys. To rotate without interrupting an integration, create a replacement, switch the integration to it, verify a request, and only then revoke the old key.
 
 ## Create an API key
 
 
@@ -86,6 +86,6 @@ Reading is never blocked in either state. Settle the payment from the billing po
 
 ## Billing is dashboard-only
 
-Plans, checkout, and cancellation live in the dashboard. There is no `sf` command and no API endpoint for changing a plan. API keys and agent credentials cannot reach billing at all.
+Plans, checkout, and cancellation live in the dashboard. There is no `sf` command and no API endpoint for changing a plan. API keys and agent credentials cannot make those changes.
 
 Reading is a different story. An agent can pull the resolved plan and limits from `GET /v1/teams/{teamId}/entitlements`, current counters from `GET /v1/teams/{teamId}/usage`, and the limits as they are enforced at publish time from `GET /v1/teams/{teamId}/plan-policy`. See [Usage](/usage) for what those numbers mean.
@@ -9,7 +9,7 @@ A Space is one site with a stable hostname. Publishing creates versions inside i
 
 ## What a Space is
 
-A Space is one site. It owns a slug, a hostname, an owner, and one pointer that says which version visitors get. Everything you publish lands in a Space as a new immutable version, and the Space decides which of them is live.
+A Space is one site. It owns a slug, a hostname, an owner, and one pointer that says which version visitors get. A publish can create a new immutable version or report no changes, and the Space decides which version is live.
 
 Ids are `spc_` plus 32 hex characters:
 
@@ -54,14 +54,15 @@ Check before you commit with [`getSlugAvailability`](/api/reference/spaces/getsl
 
 ## The default hostname
 
-Every Space answers at `https://<slug>.view.fast/` from the moment it exists, and keeps that hostname for life. Adding a custom domain never retires it. Version and branch hostnames, the live URL rule, and what a rename does to each are on [URLs and hostnames](/urls).
+A Space gets a default `view.fast` hostname. Adding a custom domain leaves it in place; renaming the slug moves the default hostname and redirects the old one. Version and branch hostnames, the live URL rule, and what a rename does to each are on [URLs and hostnames](/urls).
 
 ## Who owns a Space
 
-Exactly one owner, one of two kinds:
+The owner depends on how the Space was created:
 
 - **A team.** The normal case. Team members reach the Space by their role. Slugs are unique per team rather than globally, so two teams can both own `docs`.
 - **A space key.** A Space published without an account is owned by its `sfc_` key until someone claims it. See [Publish without an account](/anonymous-and-claim).
+- **An external principal.** A customer in a [Partner API integration](/platforms/partner-api/customers) can own Spaces without a self-serve team.
 
 To move a Space to another team, run `sf spaces transfer <team> --space docs`, or open **Space settings → General → Transfer this space → Transfer space…**. If you are an owner or admin of both teams, the move is instant. The Space keeps serving at its current address. Otherwise the target team has 7 days to accept, and nothing changes until they do. Roles and membership are on [Teams](/teams).
 
 
@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-A team owns everything — Spaces, domains, API keys, billing, members — and the role you hold there caps what you can do with any of it.
+A team owns its Spaces, domains, API keys, and billing. Your role in that team caps what you can do with them.
 
 ## Why work in a team
 
@@ -17,7 +17,7 @@ Free and Go allow only the owner. Adding another member needs [Plus](/billing#se
 
 ## What a team is
 
-A team is the thing that owns work. Spaces, custom domains, API keys, billing, and members all hang off it. Every claimed Space belongs to exactly one team, even when you are its only member. There is no separate personal container to reason about.
+A team is the thing that owns work in a self-serve account. Spaces, custom domains, API keys, billing, and members all hang off it. A Space you claim belongs to the team you select, even when you are its only member. [Partner API customers](/platforms/partner-api/customers) use external principals instead.
 
 A team has a name and a slug. The slug is the first segment of its dashboard URLs. You can change it in **Team settings → General**, where a live check tells you whether the new one is free.