# Editor notes — LumenDesk 2.0 (reviewed submission)

## Scope and editorial decisions

This unpublished package covers the fictional exercise as of October 18, 2026, the latest dated supplied observation (`inputs/S4-independent-review.md`, “Method” and document title). “Now” refers to the packet's access announcement, not a live availability check. No external research, product access or personal testing was performed.

The audience and source-only approach follow `inputs/editorial-brief.md`, “Assignment”. Direct language, concrete costs and attention to verification burden follow `inputs/voice-sample.md`, “Original voice sample written for this exercise”. No customer testimonial or first-person testing claim is invented.

The recommendation is conditional: eligible existing customers may evaluate the product on permitted documents; new customers have a waitlist. Trial design is editorial advice, not an account of tests performed. “Trial” means an evaluation, not a promised free offer. The packet supplies no free-trial terms or waitlist timing (`inputs/S1-announcement.md`, “Access”).

## Evidence and source conflicts

| Issue | Authority and treatment |
| --- | --- |
| Current versus planned access | `inputs/S1-announcement.md`, “Access”: existing Team customers in Canada/US, browser only; new customers waitlist. API and EU availability are Q1 2027 plans without a guaranteed rollout or exact date. |
| Files and capabilities | `inputs/S1-announcement.md`, “Features”: searchable PDFs and DOCX, page-linked citations, 50 MB per file; scans require OCR. It does not approve payments, send emails or execute contracts. |
| Price correction | `inputs/S2-pricing.md`, “Correction”: October 17 pricing supersedes the erroneous October 16 screenshot. USD 29, not USD 19; no annual offer in this packet. “Current plans” governs monthly billing, minimum seats, workspace uploads, OCR and overages. |
| Draft performance | `inputs/S1-announcement.md`, “Vendor test”: explicitly vendor-reported, 40 procurement packets, median draft times of 50 and 20 minutes. Human checking is excluded; end-to-end savings are not established and raw task-level results are absent. |
| Independent observation | `inputs/S4-independent-review.md`, “Method”: six searchable procurement PDFs; five correct page citations and one wrong page with correct answer text. This is not a benchmark or validation of vendor speed claims. No scans, OCR, privacy or team workflow testing. |
| Data handling | `inputs/S3-data-policy.md`, “Handling” and “Processing”: restriction on base-model training is not a blanket data-use promise. Default storage, active-deletion lag, backup persistence and external processing are distinct. No on-device mode, zero-retention promise or guaranteed compliance. |

### Calculations checked

From `inputs/S2-pricing.md`, “Current plans”:

- Minimum monthly subscription: 3 × USD 29 = **USD 87 before tax**.
- Minimum with OCR: USD 87 + USD 12 = **USD 99 before tax**.
- Illustrative three-seat workspace with 750 uploads **in one month**, without OCR: USD 87 + (750 − 500) × USD 0.08 = **USD 107 before tax**. This is a hypothetical bill, not observed spending. The 500-upload allowance is per workspace, not per seat, and does not roll over.

From `inputs/S1-announcement.md`, “Vendor test”: 50 − 20 = **30 minutes**; 30 ÷ 50 = **60%**. These calculations describe the change between reported medians, not individual task savings or total staff time.

## Unsupported internal notes excluded

The following leads appear in `inputs/S5-internal-notes.txt`, “Unverified writer notes, October 18”. None is treated as independent evidence.

- **“Eliminates hallucinations”:** no supporting evaluation; DeskLab's tiny citation observation cannot establish error-free performance (`inputs/S4-independent-review.md`, “Method”). Omitted.
- **“GDPR certified”:** no certification evidence. The policy does not guarantee regulatory compliance (`inputs/S3-data-policy.md`, “Processing”). Omitted; no legal compliance conclusion offered.
- **“Runs fully offline”:** incompatible with the external-processing description and absence of an on-device mode (`inputs/S3-data-policy.md`, “Processing”). Omitted.
- **“Saves every team 60% of their work time”:** unsupported generalization of draft-stage medians. Only the attributed, bounded calculation is retained (`inputs/S1-announcement.md`, “Vendor test”).
- **“Lead with USD19”:** rejected because of the explicit correction (`inputs/S2-pricing.md`, “Correction”). Mentioned in the article only to resolve the discrepancy.
- **Proposed quote about firing a department:** no named source or permission. Not used or paraphrased as a customer account.

## Review checks actually performed

Reread the original assignment, brief, voice sample, all five source packets and original deliverables. Manually compared article and metadata claims with the evidence, including access dates, price precedence, data-policy scope, test attribution and exclusions. No substantive arithmetic or source-conflict error was found. Minor clarity and validation improvements are recorded in `output/change-log.md`.

Ran the revised `output/check_package.py` using Python's standard library:

- Article body: **700 whitespace tokens** including Markdown heading markers and citation text; **665** excluding parenthetical source citations; **660 words** excluding both citations and heading markers. All exclude the headline and separate metadata and satisfy 600–800.
- Headline: **55 characters**; excerpt: **30 words**; search description: **150 characters**. All meet the specified limits. Metadata wording is unchanged.
- JSON has exactly the three required keys with nonempty string values; headline matches the article.
- UTF-8 reads succeeded for the deliverables; checked **11 article source references and 12 section headings** against local files.
- Exact-decimal cost arithmetic and percentage calculations passed.
- SHA-256 checks confirmed all four archived original files match their preservation hashes and all seven inputs are unchanged since this review began.

The script checks reference existence, not whether evidence supports prose; that comparison was manual. These are editorial and file checks, not product, privacy, OCR or workflow tests. Reproducible output is in `output/check-results.txt`.

## Limitations and handoff

The packet does not establish end-to-end productivity savings, broad accuracy or regulatory compliance. It lacks raw vendor results and independent OCR/privacy/team-workflow testing; future access is not guaranteed (`inputs/S1-announcement.md`, “Vendor test” and “Access”; `inputs/S4-independent-review.md`, “Method”; `inputs/S3-data-policy.md`, “Processing”). No new evidence was obtained during review.

Current deliverables are `output/article.md`, `output/metadata.json` and `output/editor-notes.md`, with `output/change-log.md` documenting revision. The four original submission files are preserved in `output/original-submission/`. `output/preservation-manifest.json` records their hashes and the review-start input hashes. `output/review_work.py` is a one-time preservation/edit utility and refuses to overwrite the archive; `output/check_package.py` is the rerunnable validator.

Estimated human finishing time: **5–10 minutes** for final copy edit and approval, not a measured result. Obtaining new product evidence would be a separate task of unknown duration. No publication or images were produced.
