docs(commercial): finish the sweep for text aimed at a seller

docs/commercial/execute-api.md

@@ -11,13 +11,13 @@ accepted the request for durable processing.
 
 This page is for an approved private-pilot partner. OpenAdapt supplies the
 service credential and the identifiers from the qualification pack. The hosted
-Execute lane stays gated (`EXECUTE_LANE_ENABLED` is false) until a
-founder-gated production deploy can issue a signed Seal.
+Execute lane is not open yet: `EXECUTE_LANE_ENABLED` is false until the
+production deployment can issue a signed Seal.
 
 ## Oracle tiers
 
-`oracle_tier` on the receipt says how the effect was checked. Mint a
-production Seal only at tier 2 or 3.
+`oracle_tier` on the receipt says how the effect was checked. OpenAdapt
+mints a production Seal only at tier 2 or 3.
 
 | Tier | Check | Production Seal |
 |---|---|---|
@@ -29,14 +29,12 @@ production Seal only at tier 2 or 3.
 `--break-it` on `openadapt-flow qualify` is the fail-closed test. A fake
 success banner must halt. The store must stay unchanged.
 
-## Attended first
+## Attended operation
 
 A person stays the legal actor. A Seal is not a physician signature.
 Consequential writes pause at `decision_required` so an authorized operator
-can finish the signed task on phone or desktop. Do not type a physician
-password.
-
-The rest of this page is the request, poll, receipt, and webhook contract.
+can finish the signed task on phone or desktop. OpenAdapt does not type a
+person's password, reuse a person's login, or share a service account.
 
 ## Choose where execution runs
 

docs/commercial/index.md

@@ -1,7 +1,7 @@
 # Commercial offers
 
-This section explains how a buyer can qualify and deploy one workflow. Every
-price and claim matches the public
+This section explains how to qualify and deploy one workflow. Every price and
+claim matches the public
 [pricing page](https://openadapt.ai/pricing) and the
 [qualification evidence appendix](../get-started/what-works-today.md).
 
@@ -22,15 +22,15 @@ the evidence supports a "do not automate" decision.
 
 ## Buyer and evaluation resources
 
-| Document | Use it when |
+| Document | What it covers |
 |---|---|
-| [Qualification Sprint one-pager](qualification-sprint.md) | Introducing the entry offer to a buyer. |
-| [Scope and prerequisite checklist](scope-checklist.md) | Confirming the customer can actually start. |
-| [Qualification report outline](qualification-report-outline.md) | Showing a buyer what they will receive. |
-| [Acceptance matrix template](acceptance-matrix.md) | Agreeing pass/fail criteria up front. |
-| [Security packet](security-packet.md) | Answering a security or IT review. |
-| [Deployment boundaries](deployment-boundaries.md) | Explaining where execution and sensitive data live. |
-| [External Citrix zero-install brief](citrix-external-brief.md) | A buyer whose workflow lives behind Citrix or VDI. |
+| [Workflow Qualification Sprint](qualification-sprint.md) | The entry offer: price, clock, deliverables, and acceptance criteria. |
+| [Scope and prerequisite checklist](scope-checklist.md) | What you provide before the sprint clock starts. |
+| [Qualification report outline](qualification-report-outline.md) | The structure of the report you receive. |
+| [Acceptance matrix template](acceptance-matrix.md) | The pass/fail contract, agreed before any trial runs. |
+| [Security packet](security-packet.md) | The posture summary a security or IT review asks for. |
+| [Deployment boundaries](deployment-boundaries.md) | Where execution runs and where sensitive data lives. |
+| [External Citrix zero-install brief](citrix-external-brief.md) | A workflow that lives behind Citrix or VDI. |
 | [OpenAdapt Execute private-pilot guide](oem-brief.md) | A vendor that wants to embed verified execution. The API is available to approved private-pilot partners with scoped credentials. |
 | [Invoke a program: Seal or halt](execute-api.md) | The Execute request, poll, Seal-shaped receipt, and webhook contract. |
 | [Procurement FAQ](procurement-faq.md) | Procurement, legal, and vendor-risk questions. |

docs/commercial/procurement-faq.md

@@ -12,7 +12,7 @@ A fixed-scope engineering assessment of one workflow, from $15,000 (native,
 RDP, and Citrix scopes typically $25,000 to $40,000), delivering a signed
 go/no-go report, coverage matrix, and evidence pack. It is paid regardless of
 outcome; "do not automate" is a full-value deliverable. See the
-[Qualification Sprint one-pager](qualification-sprint.md).
+[Workflow Qualification Sprint](qualification-sprint.md) page.
 
 **Is there a subscription?**
 OpenAdapt Cloud is $500.00/month for managed browser execution of approved

docs/commercial/qualification-sprint.md

@@ -33,12 +33,12 @@ of the following are true, confirmed in writing:
 2. Working access to the target application and test environment is verified by
    an OpenAdapt engineer (login succeeds, the workflow's screens are reachable).
 3. Representative test data is available and safe to write against.
-4. The customer has named its workflow owner and security contact.
+4. You have named your workflow owner and security contact.
 
 Days on which access is broken or revoked pause the clock. See the
 [scope and prerequisite checklist](scope-checklist.md).
 
-## What the customer provides
+## What you provide
 
 - A named business workflow with an owner who can demonstrate it.
 - Application access in a test or sandboxed environment (or a
@@ -83,7 +83,7 @@ We recommend against automation, and say so in the report, when for example:
 ## Acceptance criteria
 
 The sprint is complete when the deliverables below are handed over and walked
-through with the customer. A "go" recommendation additionally requires, on the
+through with you. A "go" recommendation additionally requires, on the
 qualified fixture set:
 
 - All representative cases complete with the declared verification strength.

docs/commercial/scope-checklist.md

@@ -1,10 +1,9 @@
 # Scope and prerequisite checklist
 
-What the customer must provide before a
-[Qualification Sprint](qualification-sprint.md) can start. The sprint clock
-does not start until every required item is confirmed. Sending this list with
-the proposal avoids the most common cause of stalled engagements: access that
-arrives three weeks after signature.
+What you provide before a [Qualification Sprint](qualification-sprint.md) can
+start. The sprint clock does not start until every required item is confirmed.
+The most common cause of a stalled sprint is access that arrives three weeks
+after signature, so settle this list early.
 
 ## 1. The workflow
 
@@ -28,7 +27,7 @@ arrives three weeks after signature.
 - [ ] Any VPN, MFA, jump-host, or allowlisting steps completed for the named
       engineers.
 - [ ] Confirmation that automated input against this environment is permitted
-      by the application's terms and the customer's policies.
+      by the application's terms and your own policies.
 
 ## 3. Test data
 
@@ -59,7 +58,7 @@ Effect verification reads the system of record instead of trusting the screen
       fault-case adjudication (roughly 4 to 8 hours across the sprint).
 - [ ] Security contact: for data-boundary questions and access approvals.
 - [ ] IT contact: for environment, VPN, and credential logistics.
-- [ ] Any security review the customer requires of OpenAdapt started early;
+- [ ] Any security review you require of OpenAdapt started early;
       the [security packet](security-packet.md) and
       [security review guide](../guides/security-review.md) answer most
       questionnaires.