VERIFICATION OF UPLOADED DOCUMENTS  -  2026-08-04
=================================================

Legend: [FIX] corrected in final  [ADD] new content added  [OK] verified correct

CUSTOMER SUCCESS & BUSINESS OPERATIONS MANUAL
---------------------------------------------
[FIX] S2 funnel table assigns owners to Marketing / CS+SE / Sales / CS as
      though a team exists. Every role currently maps to one person.
[FIX] S6 triage promises P1 "Immediate" and P2 "Same day". One engineer
      cannot commit to that across a working week containing product work.
      Published commitments become contractual exposure.
[FIX] S5 lists "delete old Netlify deploys" as established practice. It is an
      OPEN action - historical deploy permalinks were never confirmed deleted
      and still serve the July artifact containing the licence root private key.
[ADD] Claims and evidence discipline. No deployed customers exist; every
      external figure must be labelled laboratory or illustrative.
[ADD] Documents required before first sale (attorney-reviewed EULA with
      liability cap, refund, privacy, disclosure contact).
[OK]  S3 Community/paid split, S7 licence operations, S9 publish sequence,
      S11 brand posture - all verified against the code and this session.

OPERATIONS RUNBOOK
------------------
[FIX] S5 states "Lab-only overrides (never production):
      SOVEREIGN_ENFORCE_LICENSE=false". This is wrong and would break every
      Community production install. Community legitimately runs with
      enforcement disabled; it is paid tiers that require a signed licence.
[FIX] S2 lists "Linux/macOS for API+SPA" as a supported prerequisite. Those
      bundles ship WITHOUT bundled dependencies and have never been installed
      on a clean machine.
[FIX] S2 says SQL Server 2016+. Other documents and the migration set say
      2019+. 2016 has not been tested.
[ADD] Publisher identity note - the certificate subject is an individual, not
      the company, until organisation validation in 2029. Security reviewers
      ask.
[ADD] Platform support matrix with an explicit status column.
[OK]  S3 hash 505AB75E... matches the artifact published 2026-08-04.
[OK]  S4 Node Current MSI silent failure, S7 single-process start on 3041,
      S8 acceptance gates, S10 troubleshooting - all verified on the lab VM.

TECHNICAL BLUEPRINT
-------------------
[FIX] S2 "Linux/macOS supported for API with SQL authentication" - same
      overstatement as the runbook.
[FIX] S8 artifact table lists linux/macos without the unverified caveat.
[ADD] Architectural decisions with their costs: dependency bundling, fail
      closed, entitlement in the engine, offline verification. A decision
      recorded without its downside gets reversed the first time the downside
      is felt.
[ADD] Build-time guarantees - the secrets assertion, runnable-tree check and
      cold-start smoke test that now make the July defect impossible.
[ADD] The failure pattern found four times independently, now a principle.
[OK]  S3 layer table, S4 topology, S5 warehouse model, S6 sovereignty
      claims, S7 licensing model - all verified.

USER GUIDELINE MANUAL
---------------------
[FIX] S2 "Windows auth if enabled" for console sign-in. Unverified - the
      product uses JWT for interactive users. Removed rather than risk a
      customer expecting a capability that may not exist.
[ADD] Licence status self-check so an operator can confirm their own tier.
[ADD] Expanded "what empty screens mean" - it is the most common support
      contact and the answer is almost always "no collection has run".
[OK]  S4 core concepts, S6 compliance framing (evidence input, not
      attestation), S8 data residency - all correct and well judged.
