I've written the article package for the LumenDesk 2.0 launch: the article, the metadata file and the editor notes. A script confirmed the article body is 770 words and the headline, excerpt and search description are within your limits.

**What the article tells a small business:**
- **Access now:** only existing Team customers in Canada and the US can use it today, in the browser app. Everyone else can join a waitlist.
- **Later:** an API and EU availability are presented only as plans for Q1 2027, with no date or guarantee.
- **Cost:** the price is USD 29 per seat. The article reports that the USD 19 in the launch screenshot was wrong. With the three-seat minimum, the smallest team pays USD 87 a month before tax, or USD 99 with the scanning add-on (OCR). Uploads are capped per workspace, not per seat. The USD 16 cost for 700 uploads is my own example, not a vendor figure.
- **Performance:** the vendor's 50-to-20-minute figure is credited to the vendor, along with its own caveats: it covers only producing a draft and leaves out human checking. The one outside review is also credited and described as small and informal. Five of its six answers cited the right page.
- **Data handling and advice:** the article covers how documents are stored and processed. It ends with advice on who might try it now, and says up front that neither the author nor Kingy has used the product.

**Claims kept out:** the article includes none of the internal notes' claims. Those are "eliminates hallucinations," "GDPR certified," "runs fully offline," "saves 60% of work time," leading with USD 19, and the unsourced quote "We fired our paperwork department." The editor notes give the reason for each, with the source file and section.

**Checks I ran:**
- Headline 61 characters (limit 50–70); excerpt 38 words (limit 45); search description 153 characters (limit 140–160).
- The article's title matches the metadata headline.
- Body word count is 770, excluding the title but counting subheadings.
- None of the excluded claims or any personal-testing wording appears in the article.

I did not run a separate fact-check script. I checked the citations by hand while writing.

**Limitations and assumptions:**
- If the 600–800 word count is meant to exclude subheadings, the body is slightly under 770 words. That is still within range.
- I took "Kingy" to be the publication or voice owner named in the brief.
- Open questions are listed in the editor notes: the rollout date, the vendor's raw test results, and OCR accuracy.

An editor would need about 20–30 minutes to review it. That is an estimate, not a measurement.

Files are in `output/`:
- `article.md`
- `metadata.json`
- `editor-notes.md`
- `check.py`, the word and character check script
- `trim.py`, which shortened the first draft to fit the word limit